Straight answers

Building the app, and then keeping it alive: hosting, domain, SSL, monitoring, backups, security updates, bug fixes and the changes you ask for as you go. If the app is running, it is covered. There is no separate maintenance plan and no per-seat charge, because the monthly figure already is the maintenance plan.

Anything metered that a third party charges us for on your behalf — model APIs like OpenAI or Anthropic, email and SMS delivery, payment processing fees, mapping or data APIs, paid third-party services your app depends on. These are passed through at exactly what they cost, with the invoice, and never marked up. They are separate because nobody can honestly quote a fixed price for usage they cannot predict.

No. No credit check, no term sheet, no personal guarantee, no equity and no pitch meeting. We are not a lender and we are not investors — we are the people building the thing, spreading our own invoice over twelve months. What we assess is the project: whether we can build it in a month and support it for a year. That is a conversation about software, not about your balance sheet.

When the build starts, not before. You apply, we quote, and if you accept, the first monthly payment initiates the project — that is what puts a developer on it. The remaining eleven follow month by month. There is no deposit on top of that and no staged invoicing: the first payment is simply the first of twelve, brought forward to the day work begins.

Your app is live within 30 days of the build starting. Not a target, not an estimate — a guarantee we back. It is also the reason we are careful at the quoting stage: if we do not believe something can be built and shipped inside a month, we will say so then rather than discover it in week five. Scope you add along the way is quoted separately and does not count against the clock.

None. 0%, and no arrangement fee, no admin fee and no balloon payment. Twelve equal payments, and the total is exactly the same whether you pay them monthly or clear the balance in month two. We make money building software, not lending it.

You do, once it is paid for. We hold ownership while the balance is outstanding, which is precisely what lets us fund the build without a deposit or a personal guarantee. On the twelfth payment it transfers to you in full — source, assets and copy — and you can take it anywhere. Settle early and it transfers that day instead.

Any time, and there is no penalty for it. Since there is no interest, paying early does not save you money — it just moves the code into your name sooner. Some people do it the moment the app starts earning.

The payments stop and the code is yours. If you want us to carry on hosting and maintaining it, we will quote you for that separately — but it is a choice, not a renewal that happens to you. An app that needs nothing costs nothing.

Talk to us first — we would much rather rework the plan than have a difficult conversation later. Formally, the code stays ours until the balance is settled, and we can suspend the service if payments stop. In practice a business that is struggling is not helped by having its website turned off, so we start with a conversation.

Because we are financing the build, we can only start so many at once, and we need to understand what you want before we can put a number on it. Tell us what you are building, we come back with an all-inclusive monthly figure, and you decide. No call, no credit check for the quote itself.

Yes, and in both directions. The box on the application form is a mutual NDA: what you describe stays between us, and anything we share with you while quoting does too. It binds us as much as it binds you, which is the point — you should not have to be vague about your own idea to get a price for it.

No — not in the chat and not in your inbox. Every message is read and answered by a senior human developer. They ask real questions because they need real answers, and you will never get "Great question!", an apology for a delay that did not happen, or three paragraphs restating what you just said.

No. Your app is written by a human developer, line by line. We are not assembling generated code and reviewing it afterwards — somebody sits down and builds the thing, understands all of it, and is still the person who answers you about it in month eleven. If your app needs to call a model to do its job, that is a different matter and we will build that for you; it just is not how the code itself gets written.

Yes, and within reason they are included. Copy edits, tweaks, small features and the things you only notice once real people are using it — that is normal and it is covered. If you ask for something that is genuinely a second product, your developer will say so and quote it separately rather than quietly absorbing it or quietly refusing.