/ 08 — FAQ
The answers other shops
won't put in writing.
// Asked on every first callThe questions we get on every first call — answered up front, in writing. If yours isn't here, ask on the call. We'd rather have the awkward conversation now than a worse one in week six.
Do you build websites, apps, or both? +
Both — websites, web apps, mobile apps, and the AI tools that do the work nobody wants to do.
Both, plus the part that holds them together. Websites, web apps, native iOS and Android apps, AI tools that automate the boring stuff, and the integrations that get your stack to stop fighting itself. Most projects are a mix. The first call is where we figure out which mix is actually worth building — and which parts you don't need at all.
Will I work with the same person from start to finish? +
Yes — the same senior lead is on every call and writes the code on your project, every time.
Yes. The same senior lead is on every call and writes the code. We bring in trusted specialists for native mobile or specialized design when it earns its keep — never an outsourced shop, never a junior team behind a brand we're using as a front. You'll always know exactly who's writing the code that ends up in your business.
How involved do I need to be? +
About an hour a week — we run the project so you don't have to.
About an hour a week, once we've agreed on what we're building. One working session to look at the latest preview and answer a few questions. We come prepared with the right questions, take the decisions, and write them down. Managing the project is our job — you have a business to run.
What if my project changes mid-build? +
It happens on almost every project. Small changes are included. Bigger ones get re-quoted in writing — before any work starts.
It happens on almost every project — your business doesn't pause because the build started. Small changes within scope are included. Bigger changes get a quick re-scope and an updated quote in writing, before any new work happens. The number on the invoice will be the number you agreed to. Always.
What happens if something breaks after launch? +
Two paths — take the keys and run it yourself, or stay on an Ongoing plan that covers monitoring and fixes.
Two paths, your pick. Take the keys: everything is documented and yours, and we're available hourly when something breaks. Or stay on an Ongoing plan — we monitor it, fix things before you notice, and ship small improvements every month. Either path, you keep ownership. We don't believe in the third path where you can't leave.
What does it cost? +
Projects start around $8k. Ongoing plans start at $4.5k/month. Real numbers on the first call — never brochure ranges.
A single project starts around $8k, always fixed-price. Ongoing plans start at $4.5k/month and cover building, launching, and supporting everything as you grow. Embedded Team starts at $18k/quarter. We quote the real number on the first call once we know what you're actually building. Vague ranges like "$10k to $200k" exist to win the next meeting — we'd rather lose it by being specific.
