How much does a project cost?
It depends on scope, and anyone who quotes before hearing the scope is guessing. What
we will commit to is that you get a fixed number and a fixed date in writing before
work starts, phase by phase — so the risk of being wrong sits with us, not with you.
Who owns the code and the accounts?
You do, from day one. Repositories, cloud accounts, app-store listings and domains
are created in your name, not ours. Leaving is a transfer of access, not a
negotiation.
Is testing an optional line item?
No. A build that isn't tested isn't finished, so we don't quote it as though it were
a choice. The same goes for a basic security pass on anything handling money or
personal data.
Can you take over something half-built?
Often, yes — it is one of the more common things we're asked for. We start with a
fixed-fee assessment of what is there, what is salvageable and what isn't, and you
get that in writing before deciding whether to continue.
What happens after launch?
Whatever you want to happen. A retainer if you want us running it, a clean handover
with documentation if you don't, or nothing at all — the accounts are already yours,
so walking away costs you nothing.
How big is the team, honestly?
Small. That is why you talk to the people writing the code instead of an account
manager, and it is also why we take a limited number of projects at a time. If we're
full, we'll tell you that rather than stretch and miss your date.