Contact Us

There is no minimum. Size matters far less to us than whether the problem is worth solving and whether we are the right people to solve it — a short, well-defined piece of work with a clear decision behind it is a better engagement than a large one nobody can describe. If the work is smaller than the conversation suggests, we will say so, and if it does not need us at all we will tell you that too.

A senior engineer replies within one working day, and the first conversation usually happens within a few days of that. When work actually begins depends on what you need: advisory or a discovery engagement can start far sooner than assembling a team around your roadmap. We would rather give you an honest date at the start than an optimistic one you plan around.

Yes, and for several of our engagement models it is the normal arrangement. When we join an existing team we work in your process without exception — your board, your ceremonies, your definition of done, your review standards. Importing a second process into a working team is the most common way this fails, so we do not do it. Where we lead delivery instead, the split is agreed explicitly before anything starts, so nobody discovers halfway through that a piece of work had no owner.

It follows the shape of the work. Where the scope can be written down and held, the price is agreed against that scope before work starts. Where the work is ongoing or the requirements keep moving, you are paying for people or reserved capacity over time instead. We do not publish rates, because the sensible answer depends on the engagement — but you will see how a number was reached before you are asked to agree to it, and material changes are re-priced transparently rather than absorbed quietly.

You do, from the first commit. Code, infrastructure, credentials and the decision history behind them are yours throughout, and nothing is held back as leverage. Nothing we build depends on us to keep running: if you take the work elsewhere, there is no technical or commercial obstacle in the way. We own the engineering; you own the product.

That is your decision, not a renewal we assume. Some clients take the product in-house after handover, some keep us on a retainer for the work that never fully stops, and some come back only when the roadmap picks up again. Handover is part of delivery either way, so whichever you choose, the team that runs the system next has what it needs.