How we engage

Discovery. Build. Run.

Every engagement, whatever the service, runs through the same three phases. Here's what each one means, how pricing works, and what you can hold us to.

Discovery

Short and structured.

We scope the problem, the data, the risks, and what “done” means. You get written scope, assumptions made visible, and an honest read on what we would and wouldn’t build.

Deliverable

a scoped plan you could, in principle, take elsewhere. (Nobody has yet.)

Build

Fixed price, milestone-based.

Milestones are accepted on deliverables, not dates: you sign off on working software, not on time passing. Risks get raised early, decisions get documented, and you always know where things stand.

Deliverable

working, reviewed, documented software, milestone by milestone.

Run

What ships stays owned.

Depending on the system: monitoring, drift detection for AI behaviour, human-in-the-loop escalation, audit trails, maintenance, hosting, and ongoing enhancements, on a monthly retainer with named responsibilities.

Deliverable

a system that keeps working, and someone accountable when it doesn’t.

More on Run ->

How pricing works

Three shapes, no mystery.

Pricing takes one of three shapes, depending on the work. We don't publish rate cards because scoped problems deserve scoped numbers.

Fixed-price projects

The default for Build, Agents, and modernisation work. One price, accepted milestones.

Monthly retainers

For Run engagements and dedicated delivery pods. Named scope, named responsibilities, monthly rhythm.

Outcome-linked options

Where the result is cleanly measurable (resolved tickets, processed invoices), we can tie part of the fee to the outcome itself. Most natural in Automate the workflow.

What we do promise: the estimate arrives within 24-48 working hours of a discovery call, and it won't quietly grow.

What you can hold us to

The commitments

  • You’ll always know where things stand. Proactive clarity is a principle, not a slogan.
  • Milestones are accepted on deliverables, not dates. If it isn’t working software, you don’t accept it.
  • Assumptions and risks are written down and shown to you, not discovered later.
  • No inflated promises, no hidden costs. If something threatens the timeline, you hear it from us first.
  • Everything we build is documented in the codebase. If we disappeared tomorrow, your product wouldn’t.

FAQ

The questions we get first

Straight answers to what people ask before starting, the way we'd answer them on a call.

Yes. Discovery is a small, self-contained engagement, and design-only or development-only starts are normal.

Yes, both alongside in-house engineers and as the whole delivery team. We also provide long-term Salesforce and QA capacity. Details.

Then Discovery becomes an audit: what holds, what doesn’t, what it takes to ship. More here.

India, working daily with North America, Australia, and Europe. Clear written communication is the habit that makes time zones a non-issue.

Next step

Start with a conversation.

A short note about what you're planning is enough. We'll take it from there.

Fixed price, milestone-based. Milestones accepted on deliverables, not dates.