Operations lead at a manufacturer running on spreadsheets
2 people spend most of Monday reconciling inventory counts manually, and an expensive mistake finally reached a customer.
Services
Run your operations on software you own
We design and build internal tools, workflow systems and back-office software for companies whose operating processes no longer fit the products they bought off the shelf.
What arrives
- A Git repository you own, with full commit history and admin access
- A running staging environment your team can test against before each release
- Database schema and migration files, versioned and documented
- API documentation generated from the code and updated with every release
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: Skip this if you need a standard online store or a marketing site, because an established platform will deliver that sooner.
Founder whose product outgrew a no-code stack
Automations break weekly, per-record fees keep climbing, and the tool cannot model the logic the business now needs.
CTO at a mid-size firm carrying a legacy system
The original developer left, nobody dares touch the code, and a compliance deadline now forces a change nobody can make.
What you get
- A Git repository you own, with full commit history and admin access
- A running staging environment your team can test against before each release
- Database schema and migration files, versioned and documented
- API documentation generated from the code and updated with every release
- An automated test suite covering the core workflows we build
- A recorded handover session, plus a written runbook for deploys and backups
- 2 weeks of post-launch support for defects found in what we shipped
What we build it with
-
Python
-
Django
-
PostgreSQL
-
TypeScript
-
React
-
Docker
-
GitHub Actions
-
Redis
Chosen per project, not per fashion. If your team already runs something else and it works, we use that.
How the work runs
-
1
1-2 weeks
Discovery
We sit with the people doing the work, document the current process, and record every rule that matters.
From you: Access to 2 or 3 staff who use the current process daily, plus a sample of real data.
-
2
1 week
Scope and estimate
We convert the discovery map into a phased build plan, and mark the features we believe you should remove.
From you: A decision on what belongs in phase 1, and 1 named person who can approve changes.
-
3
8-16 weeks
Build
We ship working software to staging every 2 weeks, so you correct direction early instead of at the end.
From you: Feedback on each staging build within 3 working days, and credentials for any third-party services.
-
4
1-3 weeks
Data migration
We migrate your existing records, operate the old and new systems side by side, and compare the totals.
From you: An export of current data, and someone who can confirm the numbers look right.
-
5
1-2 weeks
Handover
We deploy to production, train your team, and walk your developers through the codebase until they can change it.
From you: The developers or vendor who will maintain the system after us.
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 do. The repository is yours from the first commit, and we work inside your GitHub or GitLab account where possible. That covers source code, database schema, deployment scripts and documentation. We keep no licence over any of it, and we do not charge to release it later.
Most first versions take 3 to 5 months from discovery to production. The range depends on how many systems we integrate with and how clean your existing data is. We can narrow it after discovery, which takes about 2 weeks. Any figure quoted before discovery is a guess, so we hold off until then.
You stop at the end of any 2-week cycle and keep everything already delivered. Because each cycle finishes with working software on staging, a wrong direction costs 2 weeks, not 6 months. If a defect belongs to us, we correct it at our expense. If the requirement changed, we re-estimate before writing code.
We run handover as a scheduled phase, not an email. Your developers get the repository, a recorded walkthrough of the architecture, and a runbook covering deploys, backups and common failures. We then pair with them on the first 2 changes they make, so the first real edit happens while we are still around.
Small changes inside a cycle cost nothing additional, because we plan each cycle with slack. Anything that adds a screen, an integration or a data model gets documented and estimated in days. It then either replaces something already planned or extends the timeline. You decide which, and nothing begins until you approve it.
Tell us what breaks every week
Describe the process that hurts most, and we will tell you honestly whether custom software is the wrong answer.