A first requirements draft in one hour, with an example

Set aside an hour for a first draft: the problem, two journeys, rules to decide and what can wait. A workshop to revisit, not a document to freeze.

In this fictional example, Claire calls your business to book an appointment. You want to let her choose an available time online. Here is a one-hour workshop to prepare an initial requirements document using that example: ten minutes for the problem, twenty for journeys, twenty for rules and ten for limits.

The problem, ten minutes

Write one sentence from the person’s perspective: “Claire needs to book a slot without calling.” Add what happens today: the team calls back, times are recorded in a diary and some requests remain unanswered.

If a solution comes to mind immediately, describe the need it serves. “A calendar” becomes “see available times”. If several problems appear, choose the one you want to address first and keep the others separately.

Two journeys, twenty minutes

Describe booking in the present tense: “Claire opens the page, chooses Tuesday at ten, leaves her contact details and receives confirmation.” Then describe what the team does to view and manage that request.

Two journeys provide a starting point; you can add others later. Note gaps without interrupting yourself at every sentence: what does Claire see if the slot was just taken? How does she find her booking again?

Rules to decide, twenty minutes

Return to the questions you recorded. Start with cancellations: until when can Claire cancel, who is notified and does the slot become available again? If a deposit is planned, record what happens to it without inventing a default rule.

Next, look at access: who views, who changes, who deletes? Then possible errors: the same request sent twice, an incorrect email address, an appointment already taken. Answer in everyday language and use an example when helpful.

“To decide with Léa” is an acceptable answer. It makes the question visible and identifies someone to return to it. You do not need to resolve every detail in twenty minutes.

What can wait, ten minutes

Write what this first version does not include: online payment, text reminders, a mobile app. Keep a short reason for each deferred idea: “We first want to check that customers book by themselves.”

This list helps you discuss new requests and their effect on the budget. Date it: a feature postponed today can become useful later without making the document contradictory.

After the hour

Read the draft with someone who handles appointments. Ask for one forgotten rule and a specific case to add. You can copy your notes into the free template, available in French, and complete the open sections.

Then show it to whoever builds the application, whether an agency, freelancer or AI agent team. In Maestro, it can provide a starting point for questions and documents prepared with agents. This first draft helps the discussion; it does not replace later details or your approvals.