Operations manager running a team from a shared spreadsheet
2 people edit the same record simultaneously, an order goes missing, and nobody can identify who changed what.
Services
Replace the spreadsheet that runs your operations
We assemble internal tools and workflow applications on Retool, Power Apps and Airtable. For operations teams whose actual process lives in a spreadsheet and an email thread.
What arrives
- A working application your team uses every day for genuine work, not a demonstration in a test account
- Documentation of the data model, with every field and who is permitted to edit it
- Role-based permissions configured for every group that touches the workflow
- Integrations with the systems you already operate, such as Google Workspace or Zoho
Who this is for
Three profiles. If none of them is recognisably you, this is probably the wrong page - and the line below is the one worth reading before you book anything.
Not a fit: Avoid low-code if the application needs unusual logic, heavy traffic or offline use on a phone, because the platform limits will bite.
Finance or HR lead waiting months for an IT slot
The requirement is small, the engineering backlog is long, and the temporary workaround has quietly become the process.
Founder testing a service before committing engineers to it
You need a working tool for 20 staff by next month, and a custom build would take 6 months.
What you get
- A working application your team uses every day for genuine work, not a demonstration in a test account
- Documentation of the data model, with every field and who is permitted to edit it
- Role-based permissions configured for every group that touches the workflow
- Integrations with the systems you already operate, such as Google Workspace or Zoho
- An export path for your records, so migrating off the platform later remains possible
- A recorded training session and a 2-page reference guide for new employees
- A named admin on your side, set up and shown how to change a form
What we build it with
- Retool
- Microsoft Power Apps
- Power Automate
- Airtable
-
Supabase
- n8n
- Zapier
Chosen per project, not per fashion. If your team already runs something else and it works, we use that.
How the work runs
-
1
3-5 days
Map the process
We spend a day beside the employees who perform this job, document every step, and identify where the spreadsheet breaks.
From you: 2 hours with the person who actually operates the process, not only their manager.
-
2
2-3 days
Platform fit
We select the platform against your data, your licences and your exit plan, then state plainly what it cannot deliver.
From you: The software licences you already hold and any rule on where records may sit.
-
3
2-4 weeks
Build the app
We build the application in short iterations, and you review a working version at the end of each week.
From you: 1 reviewer who can say yes or no, and sample data that looks like the real thing.
-
4
2 weeks
Pilot
1 department uses the application for real work for 2 weeks, while we fix whatever the pilot exposes.
From you: A department willing to use it every day and report what gets in the way.
-
5
1 week
Training
We train your administrator, hand over the documentation, and transfer the licences into your own tenant.
From you: An admin named for the tool, and agreement on who pays the platform fees.
How we work together
Fixed project
Scope and price agreed up front. Best when the outcome is known and the deadline is real.
Dedicated team
A named team for a quarter or more. Best when the roadmap will change and you want the context kept.
Staff augmentation
Engineers inside your process and your tools. Best when you have the lead and need the hands.
Invoiced in
- USD
- EUR
- GBP
- CHF
- SGD
- AUD
- CAD
- AED
- SAR
- QAR
- JPY
- INR
Paid by
Card, netbanking, wallet and UPI through Razorpay, which is what our checkout runs on, so anything it accepts we accept. Bank transfer, SEPA, Wise and Payoneer for invoices that prefer it.
NDA before the first call. Full IP assignment on delivery. Contracts under Indian, English or Delaware law.
Work like this
Case studies are being written up
Three are in legal review. We can walk you through the work on a call in the meantime, including the parts that did not go to plan.
What clients say on Google
Live from our Google Business listing - not retyped here.
Loading reviews from Google - read them on Google.
Questions we get asked
You migrate, and we plan for that from the beginning. The data model is documented and the records export cleanly. A later rebuild in React and Postgres begins from a clear specification rather than a guess. Some teams operate the low-code version for 2 years, then migrate once volumes justify it.
You own both. The application is built inside your own tenant or workspace, under your billing, so it never sits in a Recilens account. If you stop working with us, nothing switches off and no records have to migrate. Administrator rights pass to you during the final week.
Most internal tools reach a working pilot in 3 to 6 weeks. A single form with approvals can be operating in 2. What slows it down is unclear rules, data spread over several spreadsheets, and approvals nobody wrote down. We settle all of that in the mapping step.
It can be, with the right platform and the right settings, but it depends on the data. We apply role-based permissions, enable audit logging, and retain records in the region you require. For regulated data such as health records or payment details, we usually recommend a custom build instead.
We modify it during the pilot, which is exactly what the pilot is for. Low-code is quick to alter, so a field, a rule or a screen usually changes within hours. Restructuring the data model is a separate round of work, and we flag that beforehand.
Show us the spreadsheet
Send us the spreadsheet and tell us who touches it, and we will say whether low-code genuinely fits.