Skip to content
All services
03

Custom Software

Internal tools that replace the spreadsheet — dashboards, CRMs and admin panels built around your process.

Starting price₹2,50,000
Typical duration10–20 weeks
Warranty6 months
Code ownershipYours, at go-live

The engagement

The software that holds a business together is usually a spreadsheet nobody can leave. We replace it with a tool shaped around how your team actually works — roles, approvals, an audit trail, and the rules enforced in the API rather than in a document nobody reads.

What it covers

  • Modelled on your real process, not a template
  • Role-scoped access and approvals
  • Full audit trail, trash instead of hard deletes
  • Integrations with what you already pay for
  • Reports your accountant will accept

What you receive

  • Working panel
  • Roles + audit trail
  • Runbooks and handover

Plus the repository, credentials and hosting — created in your name from the first day, not migrated at the end.

03

How a project runs

Six stages, each with a gate.

The full process

Every stage has a condition that has to be true before the next one starts. These are enforced in the system we run the studio on, which is the only reason they hold under pressure.

Project lifecyclegates enforced in the API
01discovery
02proposal sent
03advance pending
04in build50% paid
05qa
06deliveredchecklist
07handovercreds moved
08closed

A stage with a gate cannot be entered until its condition is true. The check lives in the API, not in a document.

  1. 01Scope written down

    Discovery

    We work out what is actually being built and what it costs, in writing. If the timeline is not honest, this is where we say so — week one is the cheapest moment to hear it.

  2. 02Within 24 hours of the call

    Proposal

    A locked-scope statement of work with a fixed price and a fixed date. Same-day is the standard; twenty-four hours is the hard limit.

  3. 0350% advance paid

    Build

    A project cannot start until its advance is paid — that gate is enforced in our own API, not left to good intentions. From there you see working software, not status decks.

  4. 04Checklist passed

    QA

    Delivery means the QA checklist is signed off and the final invoice is out. Real devices, real data, and the states nobody demos: empty, offline, and failed.

  5. 05Credentials transferred

    Handover

    Final payment, then every repository, credential and piece of infrastructure moves to your ownership. Accounts were created in your name from day one anyway.

  6. 06Six months

    Warranty

    Six months of fixes on what we built, included. After that some clients keep us on maintenance and some never need us again. Both are fine outcomes.

A typical build14 weeks · phases overlap
Discovery
2w
Design
3w
Build
7w
QA
3w
Handover
2w
50% advancebefore build50% balancebefore go-live

What you see each fortnight

  • A working deploy

    on a URL you can send to anyone

  • A short written note

    what moved, what is next, what is at risk

  • The updated burn

    against the fixed price, not a running total

How we run a build

Taking new projects

Tell us what you are trying to build.

Bring a rough idea or a finished spec. Either way you get a straight answer about scope, cost and whether we are the right studio for it — and if we are not, usually a pointer to who is.

24h
Reply to every enquiry
24h
Proposal after the call
₹0
Cost of the first conversation