Every question founders ask. Answered honestly.

Scope discipline. We use a standardised production stack — Next.js, Supabase, Vercel, TypeScript — that we know deeply. We spend Day 1 defining exactly what ships and what doesn't. There is no back-and-forth during the build because the spec is locked. That is how 10 days is possible. A generalist agency taking any client with any stack and any scope cannot make this guarantee. We can.

We run a focused scope session — typically 2–3 hours. We map the core user flow: who the user is, what problem they have, what action they take, and what value they get. We define the feature list: exactly what ships, and what does not. We confirm the tech stack, the domain, and the launch URL. At the end of Day 1, you receive a signed spec document. That document is what we build. Nothing more, nothing less.

Not required. Most clients come without designs. We design the UI as part of the build, based on the scope session. If you have existing brand guidelines, Figma files, or visual references, we use them. If not, we build a clean, professional UI in our standard design language.

On Days 3–4, you receive a live preview URL — a real deployed application, not a screenshot. You can review the core flow at that point. On Day 9, you have a structured review round: you give us feedback on what needs changing within scope, and we make those refinements. This is the designed feedback loop. Ad hoc requests during the build are held for the Day 9 review unless they are critical.

Yes. We are UK-registered and operate globally. We have delivered projects for clients and built products for markets in the UK, US, Australia, and Pakistan. Scope sessions are remote. Timezones are managed as part of project setup.

Production quality. The application is deployed on Vercel with a real domain, uses Supabase with row-level security, and has type-safe TypeScript throughout. It is not a prototype. It is not a no-code tool. It is the actual codebase you will use to grow your product. The next engineer you hire will read this code and find it professional and maintainable.

Completely. The GitHub repository is transferred to your account on Day 10. Every deployment credential — Vercel, Supabase, domain registrar — is handed to you. We retain nothing. No ongoing dependency on us for access to your own product. No licence fees. No vendor lock-in.

A README with architecture overview, environment variable setup, local development instructions, database schema notes, and deployment process. Enough for a competent engineer to clone the repo and have it running locally within 30 minutes.

You own the code. You can bring in your own engineers, hire a freelancer, or come back to us for a post-launch build sprint. We do not create dependency. We can quote additional feature development separately — either as a fixed scope or a time-and-materials arrangement for ongoing work.

The 30-day (Build) or 60-day (Launch) post-launch support window covers bugs. If something breaks in the first 30 or 60 days — something in the code we delivered — we fix it at no additional cost. This covers defects. It does not cover new features or requirement changes.

The spec document signed on Day 1 is the acceptance criterion. If we deliver what is in the spec, the work is complete. Day 9 is your structured review and refinement round — this is where we address anything within scope that needs adjusting. We take quality seriously and will not hand over a product we are not confident in.

Scope discipline prevents this in normal circumstances. If a delay occurs due to factors on our side, we absorb it. If scope expands beyond what was agreed on Day 1, additional timeline and cost are quoted before proceeding.

No. You need to know your users and their problem. We translate that into a product. We will explain technical decisions in plain language and ask for your approval on anything that affects the user experience. Many of our best clients have no technical background — they are domain experts who understand their market.

Yes. We integrate existing AI APIs — OpenAI GPT-4, Anthropic Claude, Replicate, Whisper — as part of the MVP build where they are in scope. We do not train custom models. Custom model training is post-product-market-fit work. API-integrated AI features are fast to build and more than sufficient for an MVP stage product.

The MVP is a web application — it is fully responsive and works on mobile browsers. This is investor-sufficient at MVP stage and faster to ship than native apps. If your core use case requires a native app (camera access, offline-first, GPS, push notifications), we can scope that separately — our Tikkit X product is a React Native app built by the same team.

Next.js 14 App Router with TypeScript, Supabase (PostgreSQL with RLS), deployed on Vercel. Stripe for payments if in scope. Resend or SendGrid for transactional email if in scope. Tailwind CSS for styling. This is a deliberate, stable stack chosen for speed, ownership, and developer hire-ability. See the full tech stack rationale.

Yes — you own the code. Any engineer can migrate components of the stack. The technologies we use (Postgres, Next.js, TypeScript) are widely supported and not obscure. Supabase is open-source — you can self-host the database on any cloud provider if you ever want to move off their managed service.

Fixed price forces scope discipline on both sides. Hourly billing incentivises slow work and creates anxiety for you about every email and call. Fixed price means we are aligned: we ship efficiently, you know exactly what you are paying. The scope session is what makes fixed price possible — we know exactly what we are building before the price is agreed.

Free. The Scope Session is a no-commitment call. You leave with a clear feature list and a price. You only pay when you are ready to proceed.

Yes. If you start with the Validate package and decide to proceed to Build or Launch, the £1,500 is deducted from the package price.

For Build and Launch packages: 50% at project start, 50% on Day 10 handover. For Validate: full payment upfront. We do not offer extended credit terms for MVP builds.