FAQ

The questions people are too polite to ask first.

Prices, ownership, what happens when something goes wrong. If your question is not here, ask it directly — a straight answer costs nothing.

Working together

How does a project usually start?: With a conversation about the problem rather than the solution. If it is worth going further you get a written proposal covering scope, approach, price, timeline and what is explicitly excluded. Nothing in it is a surprise by the time it arrives.
Who will we actually be working with?: The people building it. The studio is small on purpose and there is no account layer between the conversation and the code.
Can you work alongside our existing team?: Yes, and for products that is often the best arrangement — we set the foundations and hand over progressively as your team grows.
What if we already have something half-built?: We will assess it honestly. Sometimes the right answer is to continue it, sometimes to replace part of it, and occasionally to start again. You get that answer before committing to anything.

What does a project cost?: It depends entirely on scope, and any figure quoted before that conversation would be invented. What we can promise is that the price is fixed in writing before work starts, and that we would rather tell you a budget will not cover something than take it and disappoint you.
How long does it take?: Also scope-dependent. What matters more is that you see working software throughout rather than at the end, so the timeline is visible as it goes rather than asserted at the start.
Do you charge for the first conversation?: No. It is useful to you even if it goes no further, and it is the only way either of us can tell whether the work is a good fit.
What happens if the scope changes?: It usually does — that is what building in the open is for. Changes get priced and agreed before they happen, not discovered on an invoice.

Who owns the code?: You do. The repository is yours and it runs in your accounts unless you specifically ask us to host it.
Are we locked in to you?: No, and the build is deliberately arranged so that you are not. Conventional stack, documented decisions, no proprietary framework only we understand. Another developer can pick it up.
What happens after launch?: We can hand over completely or stay on for ongoing work. Both are normal and neither is assumed.
Do you fix things that break?: Defects in what we built are our problem to fix. Ongoing support beyond that is a separate arrangement, agreed rather than assumed.

What do you build with?: Typically TypeScript, React and Next.js, with Postgres behind it. Deliberately conventional choices — the point is that you can hire someone else who knows them.
Do you do design as well as development?: Yes. If you have brand guidelines we design within them; if not, we establish enough of a visual system to build against and are clear about where that stops short of full brand work.
Is accessibility included?: It is a build requirement, not an add-on. Semantic markup, keyboard operation, visible focus, sufficient contrast and reduced-motion support are part of what "finished" means here.
What about hosting?: Usually in your own accounts, so you keep control and the bill is transparent. We set it up and document it.