Questions, answered.
The things founders ask us before they book a call. If yours is not here, just ask.
Frequently asked questions
Cost and scope
It depends on what you need, so we quote a fixed price for your specific scope rather than working from a rate card. What moves the number is how many user journeys the product has, whether it needs to handle payments, whether there is an AI feature, and how much of the design already exists. You get that price in writing before any work starts.
Because a number on its own tells you nothing. Two builds at the same price can include wildly different amounts of work, and a figure with no scope attached just invites you to compare us against something that is not comparable. We would rather hear what you are building first, then give you a real price for it. That takes one 30 minute call.
No. Plenty of the founders we want to work with are bootstrapped or paying out of revenue. What matters is that you have a budget for the build, not where the budget came from.
It usually does, and that is fine. When something new comes up we tell you what it does to the price and the timeline before we build it. You decide whether it goes in now, waits until after launch, or gets dropped. Nothing gets added to your invoice quietly.
Timeline and process
Most builds land between 4 and 10 weeks. One core user journey with accounts, login and a working dashboard sits at the short end. Payments, serving several customers on one system, or a production AI feature push it longer. You get a real timeline with the proposal, not a guess on the first call.
You see working software at the end of every week, starting from the first one. No months of silence followed by a big reveal. If something is going slower than we said, you hear it that week rather than at the end.
No. If you already have a brand we build to it. If you do not, we design one first, then the screens, and you sign those off before development starts. Turning up with nothing but an idea is a completely normal starting point.
Working with us
The engineer building your product. There is no account manager in the middle relaying messages, and the first call is not a sales call.
We pick the tools to fit the project rather than forcing every build through the same stack. In practice that is usually TypeScript with Next.js and React, and we choose the database, hosting and AI approach based on what your product actually has to do. On the first call we will tell you what we would build yours with and why.
No, and we will say so if yours does not need one. AI is worth adding when it does something real for your users. Bolting it on so the product has a buzzword in it is a good way to spend money for nothing. A plain MVP with no AI in it is a legitimate thing to build.
After launch
You do. The repository, the accounts, the infrastructure, all of it is yours and in your name from the start. You are not renting your own product from us, and you can take it to another team whenever you want.
Only if you want us to. Launch is when you start learning what your users actually do, and that usually means changes. We can carry on with feature work, monitoring and improvements on a monthly basis, or hand everything over cleanly and be done. Either is fine, and you decide after launch rather than committing up front.
Still have questions?
Ask us directly. The first call is free and there is no pitch.