Question 1

What is a V1 Sprint?

Accepted Answer

A five-day rapid product development service. You get deployed, production-ready software at a live URL — real users can sign up and use it immediately — with full code ownership transferred to you. Fixed price, fixed timeline.

Question 2

Can you really build working software in 5 days?

Accepted Answer

Yes — deployed at a live URL, not a prototype. The pre-flight scoping call is where the magic happens: we agree exactly what the V1 needs to do, then spend five days building only that. Small on purpose, working properly, live on Friday.

Question 3

How much does a V1 Sprint cost?

Accepted Answer

£10,000 + VAT for two senior people across five days, including working software you own. Larger products run across multiple sprints, each £10,000 + VAT, scoped in the pre-flight call.

Question 4

What tech stack do you build with?

Accepted Answer

Modern, boring-in-a-good-way technology: TypeScript, React/Next.js, and a managed database and hosting platform your team can run without us. No exotic frameworks, no vendor lock-in — any competent developer can pick the codebase up.

Question 5

How long does a V1 Sprint take?

Accepted Answer

Five working days for a single sprint. Bigger products run across two or three sprints — we tell you honestly which in the pre-flight call.

Question 6

Do we really own the code?

Accepted Answer

Completely. On Friday you get the GitHub repo, the documentation, and the deployed product, all in your name. No licences, no retainers, no strings. It is yours forever.

Question 7

What happens if you hit the end of the week and it isn’t finished?

Accepted Answer

Our guarantee covers exactly that: if on the final day you don't have working deployed software that does what we agreed in the pre-flight scoping call, we keep building at no additional charge until it does. No asterisks, no conditions.

Question 8

What do I get from a V1 Sprint?

Accepted Answer

Deployed software live at a URL, full code ownership via a transferred GitHub repository, technical documentation (API docs, database schemas, setup instructions, architecture overview), a video walkthrough, and 30 days of post-launch support.

Question 9

What does a V1 Sprint cost?

Accepted Answer

A fixed price per sprint, agreed before we start. Larger products take two or three sprints — we confirm exact scope and price on the intro call, and the number does not move.

Question 10

Can you really build working software in five days?

Accepted Answer

Yes. We build our own products on the same process — for example ContentNow, a full SaaS with AI, Stripe billing and publishing, built in five days. You can try our products at precode.co/labs.

Question 11

What about bugs after launch?

Accepted Answer

Every V1 Sprint includes a 30-day warranty covering bug fixes and support. After that, you can take it in-house, bring in your own team, or run further sprints with us — your call.

Question 12

Is the software actually deployed and usable?

Accepted Answer

Yes. It's live at a URL at the end of the sprint — not a prototype, not a mockup. Real users can sign up and use it.

Question 13

Do we need designs before a V1 Sprint?

Accepted Answer

No. You can bring validated designs from a UX Sprint, or just a clear problem — design is part of the build week. If your product needs deeper UX exploration first, we will say so on the intro call and suggest starting with a UX Sprint.

Question 14

Do I own the code?

Accepted Answer

Yes — fully. The GitHub repository is transferred to you: every line of code and every configuration. It's built so your team owns it from Day 6.

Question 15

Is the code production-ready and maintainable?

Accepted Answer

Yes. You get a documented GitHub repo any developer can pick up and extend, plus a video walkthrough of how it works and where to make changes. We use the same stack for our own revenue-generating products.

Question 16

What technology stack do you build on?

Accepted Answer

Typically React and Next.js on the frontend, Node.js or Python on the backend, PostgreSQL, MongoDB or Supabase for data, and Vercel or AWS for hosting. Integrations include payments, email, authentication, scheduling, CRMs and automation.

Question 17

Can you build mobile apps?

Accepted Answer

We build Progressive Web Apps and React Native apps that work on iOS and Android. We don't build native Swift or Kotlin apps within a V1 Sprint.

Question 18

Can you work with our existing tech stack?

Accepted Answer

We discuss your technical requirements in the pre-flight call. We typically build on Next.js, Supabase and React Native, and API integration with existing systems is usually straightforward. If you need a specific stack, we'll talk through feasibility.

Question 19

What about security?

Accepted Answer

Builds include Row Level Security on all database tables, encrypted credential storage, JWT authentication and HTTPS everywhere. Enterprise compliance such as SOC 2 or HIPAA is typically a follow-up sprint.

Question 20

What can you build in one V1 Sprint?

Accepted Answer

Web apps with real functionality: user authentication, database integration, payment processing, API connections and responsive design. Examples include waitlist platforms, booking systems, task managers, survey tools and directory platforms.

Question 21

What can you build in two sprints?

Accepted Answer

Multi-sided platforms, multiple user roles, payment flows, email automation, file uploads, admin dashboards and more complex integrations — two-sided marketplaces, SaaS with subscription billing, community platforms and CRM tools.

Question 22

What about bigger or more complex products?

Accepted Answer

Three or more sprints handle real-time functionality, custom AI/ML integration, PWAs, multi-step workflows and sophisticated admin systems — EdTech, fintech with transaction processing, healthcare scheduling, and project management platforms.

Question 23

What can't you build in a V1 Sprint?

Accepted Answer

Native Swift/Kotlin apps, blockchain applications, enterprise ERP systems, real-time multiplayer games, VR or 3D rendering, and custom hardware. We're honest about this in the pre-flight call rather than overpromising.

Question 24

What is the 30-Day Launch Shield?

Accepted Answer

Thirty days of bug fixes and clarifications after handover. We don't disappear on Day 6.

Question 25

What happens after a V1 Sprint?

Accepted Answer

Three options: take it fully in-house (you own everything), move to the Subscription for ongoing access to the team, or book a Follow-on Sprint to add features. Most clients test with users for a few weeks, then come back for the next sprint.

Question 26

Who is the V1 Sprint for?

Accepted Answer

Funded startups without developers, scale-up product teams with maxed-out roadmaps, and enterprise innovation leads who can't wait six months for internal IT. Anyone who needs working software fast.

Question 27

Who is the V1 Sprint not for?

Accepted Answer

Pre-funding founders with no budget, anyone needing native mobile or highly specialised tech, anyone needing enterprise-scale infrastructure from day one, or anyone who thinks "five days" means cutting corners.

Question 28

Is a V1 Sprint an MVP build?

Accepted Answer

Yes — it's one of the best ways to ship an MVP fast. You get a real, deployed, usable product in days rather than months.

Question 29

Will the V1 Sprint software scale?

Accepted Answer

It's production-ready and built on real, scalable code you own — not no-code with vendor lock-in. Enterprise-scale infrastructure (for example load testing for 50,000+ users) is available as a follow-up sprint.

Question 30

Is the V1 Sprint guaranteed?

Accepted Answer

Yes. If at the end of Day 5 you don't have working, deployed software that does what we agreed in the pre-flight call, we keep building at no extra charge until it does.

Question 31

Are there ongoing costs after a V1 Sprint?

Accepted Answer

Yes — hosting (typically £30–100/month), third-party API costs (such as Stripe fees or AI API usage), and any app store fees if relevant (£99/year for iOS, £25 one-time for Android). These are billed to you, not us.

Question 32

What does the daily structure look like in a V1 Sprint?

Accepted Answer

A 15-minute morning standup, building all day, and a daily demo each evening with a working URL and screen recording so you see real progress every day.

Question 33

Can you add features to software you've already built?

Accepted Answer

Yes — that's a Follow-on Sprint: the same five-day model pointed at a product that's already live, with the same senior team who already knows it.

The 5-day V1 Sprint