Question 1

What does a typical project cost?

Accepted Answer

We scope in two stages. A fixed-scope discovery typically runs two to four weeks and is billed as a separate, fixed fee. The build that follows is estimated and approved in two-week increments, so you commit to one tranche at a time rather than a single large number. Most first releases land somewhere between $40k and $150k, depending on the number of integrations and the volume of legacy data to migrate. Those ranges are illustrative guidance for this demo; we will give you a considered range after discovery, not before it.

Question 2

How does discovery work?

Accepted Answer

Discovery is a paid, time-boxed engagement of two to four weeks. We interview the people doing the work today, map the current process and its data, and then produce a target architecture, a data model, a delivery plan broken into two-week increments, a risk register and a costed estimate for the first release. The output is yours whether or not you continue with the build. If you do continue, the discovery fee is credited against the first increment.

Question 3

Can we sign an NDA, and who owns the IP?

Accepted Answer

We will sign your NDA before the first architecture conversation, and we are comfortable working under your master services agreement. Send diagrams, data models and credentials with confidence. You own the intellectual property in the work we produce for you — source code, designs and documentation — on payment of the relevant invoices. We retain only the right to reuse generic, non-client-specific components and patterns that we brought to the engagement.

Question 4

What engagement models and timelines do you offer?

Accepted Answer

Three models. A fixed-scope increment team, where you approve two-week tranches of defined work. A dedicated product team, where a small senior group works exclusively on your roadmap. Or targeted augmentation to close a specific capability gap in your existing team. A first release typically lands eight to sixteen weeks after discovery, depending on integrations. We do not run open-ended time-and-materials engagements without a defined outcome.

Question 5

How do you work across time zones?

Accepted Answer

We keep a four-hour daily overlap with your team’s working hours, wherever you are. Decisions are written down so progress does not depend on who was awake for a call: architecture decisions, scope changes and status all live in a shared workspace you can read at any time. We commit to a response within one business day and run a single weekly review at a time that suits your team. Anything that needs a live conversation is scheduled in advance with an agenda.

Start with the problem.

Have an idea?
Let’s turn it into software.

Project brief

Before you write to us

Prefer to talk first?

Have an idea?Let’s turn it into software.