“We need a landing page for our new service next week. Visitors should choose a time, pay online, receive a confirmation, and we need to change prices from a phone. It has to work for everyone.”
Illustrative example
Landing page request → clear first phase
This is an anonymised example of the format. It is not a client project and does not claim that any missing fact is already true.
Input rule: the pack separates a client’s request from facts that must still be confirmed. It does not make technical, legal, payment, or delivery promises on the client’s behalf.
One booking path
A customer selects one available service slot, completes the chosen payment step, and receives one unambiguous confirmation.
What “done” means
- A test customer can request one available slot on a phone.
- The business receives the request with the chosen slot.
- The customer sees a clear confirmation and next step.
Three missing facts
- Who owns availability and how it is updated.
- Whether payment is required at booking, and by which provider.
- What happens when a customer cancels or the business changes a slot.
Not part of phase one
- Editing every price from a phone.
- Multiple service types and complex availability rules.
- Automated refunds, reminders, and reporting.
When the price or deadline must be revisited
If the chosen payment provider, cancellation rule, or availability source cannot support the agreed first flow, stop and choose a cheaper fallback: request-only booking with manual confirmation.