Get everyone alignedon requirements before you build.
We help teams align on requirements by building a clickable prototype together.
Without a prototype
You read the flow. Gaps stay buried.
REQ-SEND-02Spec · p. 2
Recipient
The sender picks a saved recipient or adds one with a name and account. The screen shows the country and the currency they will receive. If that account cannot take the currency, stop the transfer before an amount is entered.
REQ-SEND-05Spec · p. 5
Amount and fees
The sender enters an amount in their own currency. Show the converted amount, the exchange rate, and the fee before they continue. If the fee changes while they are looking, update the total and ask them to check it again.
REQ-SEND-09Spec · p. 9
Confirm
The sender reviews who is paid, what they send, what arrives, and the fee. One confirmation produces a receipt with a reference. If the payment fails, keep the details on screen and offer a retry.
REQ-BOOK-02Spec · p. 3
Meeting type
The host publishes a 30-minute intro call. The invitee must pick that type before any date is shown. Duration, the video location, and a 15-minute buffer are stored on the type, not on the event.
REQ-BOOK-07Spec · p. 8
Availability
Offer times from the host’s working hours, minus events already on the calendar, blocked days, and four hours’ notice. Hide past slots. Convert every remaining slot into the invitee’s timezone before listing it.
REQ-BOOK-12Spec · p. 11
Confirm
The invitee enters a name and email, confirms Tuesday at 10:00, and receives a calendar invite. Show the time, a reschedule link, and a cancel link. If the slot was taken, return them to the calendar.
REQ-ORDER-02Spec · p. 2
Dish and modifiers
The guest picks a dish and any modifiers, such as spice level or an extra egg. Show the price of each choice as it is added. If a modifier is sold out, remove it before the dish can be added.
REQ-ORDER-06Spec · p. 6
Address and arrival
The guest confirms a delivery address and sees an arrival window before they pay. If the kitchen cannot deliver there, say so and offer pickup. Update the window if the kitchen time changes.
REQ-ORDER-10Spec · p. 10
Pay and confirm
The guest sees the dishes, the delivery fee, and the total, then pays. The confirmation shows the address and the arrival window. If payment fails, keep the cart and return them to pay.
REQ-FILE-03Spec · p. 3
Category and weight
The producer picks a packaging category and a material, then enters the weight placed on the market. Weights are in kilograms. A row with no material cannot be saved.
REQ-FILE-07Spec · p. 7
Reporting period
Each filing covers one quarter. Show the period, the producer, and the country of the scheme. If that period is already filed, open the acknowledgement instead of a blank form.
REQ-FILE-11Spec · p. 11
Submit
The producer reviews every row and the total weight, then submits. The acknowledgement shows a reference and the period. If a required row is empty, stay on the form and name the gap.
We help your team get clear on requirements, then turn them into a clickable prototype you can walk through together. That includes research: finding what the market and users need, discussing the gaps in the room, and prototyping from that, not only from a doc you already wrote.
Anyone who decides what gets built: product, design, engineering leads, ops, and the stakeholders who usually sign off. If they cannot all sit in the same room at once, we run short feedback sessions so each group still sees the prototype and you still leave aligned.
The same written requirement can mean different things to different people, even experienced teams. In one study, 104 requirements professionals disagreed on what simple if/then requirements meant. A clickable prototype gives everyone one concrete thing to walk through, so gaps show up in the room. Fixing problems after delivery is often far more expensive than catching them in requirements and design (Boehm and Basili, 2001).
A short intake first so we know the workflow and who needs to be there. The workshop itself is about a day of work. For distributed teams we can split it across sessions that fit your calendar instead of one continuous day.
A clickable prototype of the workflow you needed to align on, plus handoff notes engineering can build from. On We run it and teach ($4,500), your team also leaves with a short playbook so you can run the next cycle without us. We run it is $3,000.
That is normal. Part of the sprint is sorting what is known, what is assumed, and what still needs a decision. We research and discuss those gaps, then prototype the version you agree on.
Sign-off often means people agreed on words, not on the product. Walking the prototype is how you find out whether they meant the same thing before build cost goes up.