Clear engagement models, honest estimates.

We don't publish a fixed price list, because every system is scoped to how your team works. Here is exactly how we engage and what drives a quote. Every estimate is given in writing, up front, before any commitment.

How we engage

Three ways to work with us.

Fixed-scope build

Best when you know the problem and want it solved.

A defined system (a CRM, an approval workflow, a case manager) scoped from a requirement study with your team into a written statement of work, with a fixed deliverable agreed before development starts.

  • Written scope and a fixed price agreed before we start
  • Requirement study with your team before any development
  • Milestone reviews against the agreed scope
  • Testing, training and go-live support included
Get an estimate ↗

Monthly retainer

Best when software needs to keep evolving.

An agreed amount of senior engineering each month (bug fixes, small features, performance and security work) on a work plan agreed at the start of every month. The work that keeps software useful 18 months in.

  • A written work plan agreed each month, no surprises
  • Priority queue for fixes and small features
  • Security patches and dependency upkeep included
  • Cancel or pause with notice
Get an estimate ↗

Per-user license

Best when a ready-built product already fits.

License one of our ready-built apps (CRM, HRMS, ticketing) on a per-user, per-month basis. Hosted, maintained, and updated by us, so there is no build to manage.

  • Per-user, per-month pricing, scale up or down anytime
  • Hosted, maintained, and kept up to date by us
  • Onboarding and team training included
  • Export your data anytime
Get an estimate ↗
What drives a quote

What goes into a quote.

On the discovery call we map your process, then give you a written estimate. A handful of things move the number more than anything else:

  1. 01

    How much is genuinely custom versus configuration of tools you already own

    If Microsoft 365, Tally or your helpdesk already does part of the job, we configure it rather than rebuild it. The estimate separates what we configure from what we build, so you can see where the effort goes.

  2. 02

    The number of integrations and how well-documented those systems are

    Every system the new software talks to, such as Tally, a bank, the GST portal or an existing ERP, adds design and testing work. A documented API takes less effort than a desktop system reached through a connector, so we check each one during the requirement study.

  3. 03

    Data migration volume and how clean the source data is

    Moving years of spreadsheets or an old system means mapping fields, removing duplicates and reconciling totals before go-live. Registers kept differently by each branch need more cleanup than one consistent file, so we size it from a real sample.

  4. 04

    Compliance and audit requirements (GST, statutory deadlines, access control)

    Statutory deadlines, GST fields, role-based access and an audit trail nobody can edit all need rules, tests and sign-off. We list each one in the scope, so it is estimated up front instead of discovered later.

  5. 05

    Whether you want a one-off build or an ongoing retainer afterwards

    A fixed-scope build ends at go-live and the agreed support period. If the system will keep changing with your business, a monthly retainer with a written work plan usually suits better, and we tell you which we would recommend.

Every written estimate lists

  • The agreed scope, module by module, in the words your team uses
  • Assumptions, and what is explicitly out of scope
  • Milestones, and how each one is reviewed against the scope
  • Testing, user training and go-live
  • Support after go-live, and how change requests are handled

The timeline is agreed with the estimate, after the requirement study, because it depends on the same things as the effort: integrations, data and how many teams the system serves.

A 30-minute discovery call, a written scope, and an indicative estimate are always free and carry no obligation. A project becomes a commitment only once both sides sign a written statement of work.

Book a discovery call

Get a written estimate.

Tell us the process you want to fix. We'll scope it on a 30-minute call and follow up with a clear, written estimate. No obligation, no sales pressure.