FAQs

We start with a short discovery conversation to understand the outcome you need, then produce a written scope that describes what the software will let people do. Pricing follows that scope — either a fixed price for well-defined work, or a time-and-materials rate where the requirements are still taking shape. You get the estimate and the assumptions behind it in writing before anything is committed.

A focused web application or a first mobile release is usually eight to sixteen weeks from kickoff to launch. Larger platform work runs longer and is broken into phases so you see working software every few weeks rather than waiting until the end. We sequence the riskiest parts first, so schedule surprises surface early while they are still cheap to absorb.

Yes. A good share of our work is extending, integrating or gradually replacing software that is already running the business. We begin with a review of the current codebase and data, then recommend whether to extend, refactor or rebuild — and we will say so plainly if rebuilding is not the right call.

You do. On completion, the source code, the repository history and any associated assets are yours, and we hand over the documentation and credentials needed to run it without us. We do not hold clients hostage through access.

Launch is the start of the useful feedback, not the end of the project. We offer ongoing support covering monitoring, security updates, bug fixes and small enhancements, scaled to what the product actually needs. If you would rather run it with your own team, we will help with the handover and training instead.