Asked on every call

Straight answers, before you ask.

Thirty minutes on your idea — or your half-built product. No pitch. If we're not the right move, we'll say so on the call.

Who owns the code and the IP?

You do, from day one. The repository, the code and every piece of IP sit in your name — even if we're the ones hosting it for you. At handover you get full documentation and a recorded walkthrough. There is nothing to hold hostage.

I can't judge code quality. How do I protect myself?

You shouldn't have to read the code — that's what the process is for. What 'finished' looks like is agreed up front in plain terms a non-technical person can check, demos happen regularly, and any defect in the first 60 days is fixed at our cost.

What happens after launch — do you just disappear?

No — we're still around after handover. Changes get made quickly, not queued into a support ticket black hole. If you'd rather have a more hands-off arrangement, that works too — the system's built to run without us either way.

How does it get online — do I need my own hosting?

You don't need to sort this yourself. We handle getting everything live and keeping it running, so you're not left figuring out servers or deployments on your own. However it's hosted, ownership stays with you — same as everything else.

I've already vibe-coded something in a tool like Lovable or Bolt — can you use it?

Not the code itself — those tools don't let us export or take over what's underneath. But the thinking behind it usually isn't wasted. It's already told us what you actually need: the screens that matter, the workflow you were picturing, the bits that felt right and the bits that didn't. That's most of the hard part done before we've even started.

What does it cost?

One fixed price, split across modules — each one scoped and priced before it starts, so you always know exactly what the next module costs before you commit to it. No open-ended hourly meter, no guessing.

How long does it actually take?

Depends on scope, but most projects land somewhere between a few weeks and a few months. Once we've scoped your modules, you'll get real dates for each one — not a vague estimate that slips.

Can it connect to the other tools we already use?

Usually, yes. Most systems we build talk to whatever you're already running — accounting software, CRM, email, whatever's core to how you work. If there's something specific you rely on, mention it early and we'll factor it in.

Do I need to understand tech to work with us?

No. Conversations happen in plain English, not tickets or jargon. If you can describe what's going wrong in your own words, that's all you need to bring.

What happens after I book?

You'll get a booking link straight away — pick a 30-minute slot with the team whenever suits. If a project isn't the right answer for you, you'll hear that on the call — and you'll hear why.

What if I don't know exactly what I need yet?

Most people don't, and that's fine — most of our best projects started as "something's broken, I'm not sure what the fix looks like." The first conversation is about understanding the problem, not reviewing a spec you've already written.