Skip to content

Our approach to building

Better questions. A clearer spec. The right build.

Before we ask an AI agent to build, we ask it to interview you. A carefully written prompt helps uncover the needs, assumptions and edge cases that a first brief can miss. Your answers become a Product Requirements Document (PRD): the starting point and reference for the work that follows.

In one sentence

Spec-driven development means agreeing what the software should do before building it, then using that specification to guide implementation and review. It is not a document written once and forgotten. As decisions change, we update the specification and keep the build aligned with it.

The process

Interview, agree, build, keep current.

Four stages, one reference running through all of them.
  1. Interview before implementation

    You explain what you want to achieve. We use a focused prompt so the AI asks follow-up questions about your users, workflows, constraints and missing details. The interview continues until there is enough information to write a useful PRD, with open decisions called out rather than guessed.

  2. Turn answers into a PRD

    The AI organizes the answers into a Product Requirements Document. We review it with you: the problem, the people it serves, the scope, the journeys and the conditions that make a feature complete. You confirm that it describes the product you actually need.

  3. Build against the specification

    We use the agreed PRD to shape the technical plan and focused development tasks. AI coding agents have a shared reference instead of relying on scattered chat messages. We design, implement and check the work against the requirements.

  4. Keep the reference current

    When a new requirement or decision changes the product, we update the PRD and the affected plan. During development and review, we return to it to check what belongs in scope and whether the result matches the agreed behaviour.

Blind spots

The questions a first brief misses.

A few of the questions the interview tends to raise. Open decisions are called out, not guessed.
  • Who can do what?

    Visitors, customers and staff may need different permissions. Who can view, edit, approve or delete each kind of information?

  • What happens off the happy path?

    What should happen when a form fails, a booking is cancelled, a payment is declined or an external service is unavailable?

  • Where does the information go?

    What needs to be collected, where is it stored, who can access it, and which systems need to receive it?

  • What does “finished” mean?

    Which outcomes can you check? What must work on mobile? What happens after a submission, and who needs to be notified?

Inside the PRD

What goes into the PRD.

The PRD describes the what and why. The technical plan describes how we will build it. We keep both connected as the work develops.

  1. The problem, the intended users and the outcome you want.
  2. What is included now, what comes later and which decisions are still open.
  3. User journeys, roles, permissions and important edge cases.
  4. Content, data, integrations, privacy and accessibility requirements.
  5. Acceptance criteria: observable conditions for checking each feature.

Where it starts

The interview prompt.

This is a starting prompt, not a finished specification. Your answers, our follow-up questions and your review make it specific to your project.
Starting prompt
Act as a product requirements interviewer. Help me discover what I have not thought through before we build. Ask one focused question at a time, and use my answers to choose the next question. Explore the users, the problem, the desired outcomes, workflows, roles and permissions, data, integrations, content, privacy, accessibility, constraints and failure cases. Challenge assumptions and distinguish confirmed requirements from suggestions. Do not start coding. Continue until you have enough information to draft a Product Requirements Document. If a decision is unresolved, record it explicitly instead of inventing an answer. Then draft the PRD with scope, user journeys, functional and non-functional requirements, acceptance criteria and open questions. Ask me to review and approve it before proposing a technical plan or development tasks. Use the approved PRD as your reference during development and propose updates when requirements change.

In partnership with Codalio

An idea is the start. A specification gives it direction.

Codalio is a spec-first AI software platform. Describe your idea in plain language and it asks questions to turn that idea into a plan you can review. Its workflow connects a PRD, technical specification, data model and prototype with code you own.

More about our Codalio partnership
  • Clarify before you build

    Guided questions help turn a broad idea into written requirements and a plan you can read.

  • Keep the work connected

    PRDs, technical specifications, user flows and data models give the build a shared reference.

  • Take your work forward

    Codalio offers PRD exports and code ownership, so you and your developers can continue from the work you have defined.

Use Codalio to develop your own idea, or bring your PRD to us. We can help you refine the requirements and turn them into a website or application. Our approach is the same: clarify the intent, agree the specification, and build against it.

Explore Codalio

Partner link: we may earn a commission if you purchase through our Codalio link.

Questions

Common questions

What is a Product Requirements Document?

A Product Requirements Document, or PRD, sets out what your website or application must do, who it is for, and how we will judge whether it meets your needs. It captures the scope, user journeys, requirements, acceptance criteria and open decisions in one reference.

Do I need to arrive with a complete brief?

No. Start with the problem you want to solve and what you know about your users. The AI interview asks follow-up questions, with our guidance, to explore the details and assumptions. We review the resulting PRD with you before using it to guide development.

How is this different from asking AI to build an app?

A single build prompt leaves many decisions unstated. We start by asking questions, agree a written specification, and give the coding agents that reference as they work. The PRD also gives you something concrete to review beyond whether a screen looks finished.

Can the specification change during development?

Yes. The PRD is a living reference, not a barrier to changing your mind. When we agree a change, we update the requirements, consider what else is affected, and use the revised specification to guide the next work.

Can I bring a PRD I made in Codalio?

Yes. Bring your existing PRD and any technical plans or prototypes. We review them with you, clarify open questions, and use the agreed requirements as the starting point for your website or application.

Does this approach work with Replit?

Yes. A specification gives Replit Agent a clear reference for what to build and what to preserve. We use the PRD to guide the technical plan, development tasks and review, rather than treating each prompt as an isolated instruction.

Start with better questions.

Tell us what you want to build. We start with the interview, and the PRD guides everything after.

Your first conversation and your quote are free, with no obligation.