Everything founders ask before starting a sprint.

An MVP is not your whole startup. It is the smallest version of the product that proves the core idea with real users: one main workflow, done properly, live on the internet.

One core workflow with the supporting pieces around it: accounts and permissions, a database, payments, file uploads, search, dashboards, notifications, an admin view and a handful of third-party integrations.

Large enterprise systems, multi-sided marketplaces at scale, heavy compliance programmes, legacy migrations and anything that needs a research phase before the product exists. We say so at the fit check rather than after you pay.

Changes inside the blueprint scope are part of the sprint. Anything outside it is quoted separately as a fixed price before we build it, so the $3,500 never moves without your written go-ahead.

No. The service is built for non-technical founders. The blueprint is written in plain English and the handoff includes an operating guide for someone with no engineering background.

No. If you have designs we will build to them. If you do not, we design the interface as part of the sprint.

No. $500 at the blueprint, $1,750 at the start of the build, $1,250 at delivery. Each stage unlocks when its payment clears.

We define the architecture, the data model, every screen, the integrations and the exact build scope, then lock the price against it. You keep the document regardless of what you do next.

We tell you at the fit check and explain what we would change to make it fit, or what kind of team you actually need. There is no charge for that conversation.

Yes. An NDA is available on request before you share anything sensitive.

You do, outright. The repository is transferred into your name at handoff. There is no licence to renew and no platform you are tied to.

You do. The domain is registered in your name, or we deploy to a domain you already own.

You do. Hosting, database and any third-party service accounts are created in your name and billed to you directly, so nothing runs through us.

Yes, and that is the point of the handoff. Standard stack, documented architecture, readable code and a written operating guide, so any competent developer can pick it up.

Yes, as a tool inside a reviewed engineering process. Senior developers own the architecture, the security model and every line that ships. That combination is why the timeline is 14 days rather than 14 weeks.

React and TypeScript on the front end, a Postgres database with row-level access rules, managed hosting and managed secrets. Mainstream, well-documented technology so you are never dependent on us to maintain it.

Yes. Accounts, teams, roles, subscription billing and a usage dashboard are standard parts of a SaaS sprint.

Yes. Chat interfaces, document analysis, retrieval over your own data, generation and agent-style workflows, with usage limits and cost controls built in.

We build mobile-responsive web apps as standard, which run in the browser on any phone. Native App Store and Play Store builds are quoted separately and are not part of the $3,500 sprint.

Yes. Checkout, subscriptions, webhooks and customer billing portals are all within a standard sprint.

Yes, where the API is documented and access is available. Integrations are listed explicitly in the blueprint so there are no surprises mid-build.

Every build ships with authentication, row-level access rules on the database, secrets in managed storage, encrypted traffic and dependency scanning. Security work is part of the sprint, not an upsell.

Equity turns a two-week engagement into a permanent claim on your company. A fixed fee keeps it clean: you pay for the build, you keep the upside, nobody joins your cap table.

Nothing stops working. You keep the app, the code and the guide, and you can continue solo, hire in-house or book another fixed-price sprint. Support is optional, never automatic.