Oceantic

It depends on the work, which is why scoping exists and why it ends in a fixed quote: the number you approve is the number you pay. The sample build is the small way in, a real slice at a price agreed before anything starts. No day rates, no meter running, no surprises mid-project.

As fast as the work allows, and no faster. The plan you approve states what lands and when, and you watch the real progress in the repository from the first week. Well-scoped projects see working software early and often. Vague ones slow down until the spec is honest, and that is what scoping is for.

The engineers you meet in the first call, the same people through to handover. There is no pitch team and separate delivery team here, and no bench of whoever happens to be free. If the team ever grows mid-project, you'll know the new name before they touch your code.

Then you start from what you have. We work in your repository, with your team, inside your process, or take a problem completely off your plate. Either way it starts the same: a working spec of what the system actually does today, so every change to it is deliberate.

Whatever you want. If you'd like us to stay on for care and iteration, that's a normal engagement with a normal quote. If you wouldn't, the handover was built for exactly that: the full handover pack, so the product never needs us to stay alive.

When you want bodies by the hour. We're not a staffing agency, and rented days have no outcome to own. When the work has no engineering in it. And when we're simply not the fit: the sample build exists to find that out cheaply, on both sides, and we'll say so.