How it works

One proposal to build it. A subscription to run it. No surprises along the way.

No hourly billing, no scope creep by a thousand emails, no codebase dumped on your desk. You always know what's being built, what it costs, and where it stands.

The engagement

Four stages, start to finish

Scope & proposal

We sit with the people who'll use it, map the real workflow, and write one proposal — a fixed scope, a real timeline, and a single fixed price for the build. You accept it in the portal, and that acceptance is recorded.

about a week

Build

An independent stack chosen for your domain — typically Node and Postgres for web systems. You get progress you can see and a staging environment to try, not a black box for three months.

most builds: a few weeks to a couple of months

Launch

Deployed to production, your data migrated, your team walked through it. From here it's running your operation.

a few days

Host & run

We host it, monitor it, back it up and support it — on a monthly subscription. A bug at 9pm is our problem. Every change request and support ticket runs through your portal.

ongoing
Ownership

We own and host it by default — so reliability isn't your job.

Most vendors hand you a codebase and move on. We do the opposite: we keep operating what we build, so it stays reliable without you staffing for it. You pay a monthly subscription for hosting, monitoring, backups and support.

If you'd rather bring it in-house — now or in three years — the buy-out clause hands over the running system, the full source code, and the documentation, at a price agreed up front in the proposal. The subscription is a convenience, not a lock-in, and the exit is written down before you sign.

Your portal

The paperwork isn't scattered across email

Every engagement comes with a login at clients.corehq.in.

Proposals

Read, and formally accept, with a timestamped record.

Invoices

Every invoice, its status, and how to pay — in one place.

Service status

What's live, what's in progress, what's paused.

Support

Raise a request, get a reply, track it to done.

Not ready for a build?

We can work with the tools you already have

Sometimes the answer isn't a new system. If your current tools could do the job with the right setup, we'll say so — and we can do that setup.

Workflow automation

Connecting the tools you use so a task that touches five apps happens once. Built on n8n, hosted and maintained by us.

Zoho & QuickBooks implementation

Setting up, configuring and integrating the platforms you've bought so they actually fit your process, plus ongoing support.

How you'll work with us

No account managers, no hand-offs, no telephone game between scoping, building and running it. What you ask for is what you get, start to finish.

How we ship

We're an AI-native studio — modern tooling lets us deliver what used to take a much larger operation. That's what makes the price work and the timeline short.

On price

A fixed number for the build, a monthly number to run it, both bespoke to the system and both in the proposal. Tight scope keeps them sensible; the return should be obvious.

Questions

Before you get in touch

The price and terms are set in your original proposal, so there's no negotiation later. When you trigger it, you receive the production deployment, the full source repository, and the documentation. From that point you can host and run it yourself or hand it to another team.

Small adjustments are part of building well and we absorb them. A genuine change in direction gets its own short proposal — a clear addition, priced up front, that you approve before we act on it.

Hosting, monitoring, backups, security updates, and support — plus small changes and fixes. Larger new features are scoped separately. The figure is bespoke to the system and set before launch.

Sometimes — it depends on the state it's in. We'd look at the code and the deployment first and tell you honestly whether it's better to continue it or restart.

Yes, routinely. Send yours over, or use ours.

Encrypted in transit and at rest, hosted on infrastructure we control, access limited to what's needed to build and run the system. Details go in the proposal.

Ready when you are.

A paragraph on how the operation runs today and where it's breaking is enough to start.