Questions, answered.

An architecture review, which is a fixed-price engagement of about four working days. It produces a written assessment and a prioritized list of what to fix, and it's a common way to start before committing to a build.

Usually two engineers, occasionally more for work that genuinely parallelizes. We'd rather quote a longer timeline with a small team than a shorter one with people who are learning your codebase at your expense.

Yes, and it's often the better arrangement. Team extension puts a dedicated engineer inside your existing process, using your tools, your review standards and your release cadence.

Yes. We keep a minimum of three overlapping hours with your team each working day, and everything that matters is written down, so progress doesn't depend on catching someone live.

Build work is quoted hourly against an agreed scope, fixed-scope pieces such as discovery and reviews are quoted per engagement, and ongoing work is a monthly retainer. The quote builder on this site prices any combination of those and shows the delivery schedule alongside it.

Yes, and it applies automatically. Larger quotes reach tiered volume discounts, which the quote builder shows as a separate line so you can see exactly what you earned rather than an unexplained round number.

Thirty days from the date it is issued. After that the rates may have moved, so we'd rather reissue it than honor a number we can't deliver against anymore.

Sometimes, and it carries a surcharge because it usually means moving people off other commitments. The quote builder lets you model the effect before you ask, so you can see the trade-off before you ask.

There's a short ramp-up, usually five working days, while we get access, read the codebase, and confirm the plan. Delivery starts after that, and the schedule on your quote already accounts for it.

Work happens in your repository on branches you can see, with a written update at the end of each week covering what shipped, what is in progress and anything that changed our estimate.

We re-quote the delta rather than absorbing it silently or stopping work. You get the revised number and schedule before the change is started, not after it is finished.

Yes, as part of the work rather than a separate line item. Behavior that matters gets a test, and the suite runs on every change so a regression is caught before it reaches you.

The code, the tests, the deployment configuration and written documentation of how it works and how to run it. Nothing is held back, and nothing depends on us staying involved.

If you want us to. An advisory retainer keeps us available for questions and direction without a delivery commitment, which suits teams who have taken over day-to-day work but want continuity.

You do, from the first commit. Work happens in your repository under your account, so there's never a handover step at the end.