Co-review workspace for software delivery

Agree on what you're building, before it is built.

Every client gets one private link. Behind it: the questions that shape the product, the wireframes and designs to approve, the plan to follow and, when code ships, a recorded acceptance video for each use case. Nothing is left to assume.

yourcompany.prebuild.click One subdomain per client. Open on any device, no account to create.
MVComment on auth-02 · 2 min ago
✓Design D-14 approved
auth-03 · AUTHENTICATION
Should staff be able to sign in with their existing Microsoft work account?
Add a note for the team…
10 / 30 answered
The nine stages

One link, in the same order for every project.

The menu on the left of a client's page never changes shape. Each stage opens when there is something to review, and keeps the answers given earlier.

01

Questionnaire QnA · QnA FINAL

The product described as questions, grouped by module. Yes, No, Answer later or a comment on each one. The second round closes the open points before design starts.

Client answers
02

Wireframes SCREEN CODES · CATALOGUE

Every screen drawn on the same grid, with a code the whole project refers to from here on. The client ticks each screen as understood or sends it back with a note.

Client reviews
03

Prototype designs CLICKABLE · PER FLOW

The look and feel, flow by flow. Colours, type and components are decided here, once, and reused everywhere after.

Client reviews
04

Hand-off designs DELIVERED DESIGNS · "UPDATED" MARKS

The final screens the developers build from. Anything changed after approval carries a dated "Updated" mark so nobody re-reviews what they already saw.

Client approves
05

Architecture & infrastructure DIAGRAMS · SERVICES · HOSTING

How the system fits together and where it runs, drawn so a non-engineer can follow it and an engineer can object to it.

Client reads
06

Estimate & delivery plan WEEKS · MILESTONES

Scope split into weekly deliveries with what ships in each. The plan is the contract the next three stages are measured against.

Client agrees
07

Delivery status & source code W1 · W2 · W3 …

Each week's delivery listed per use case with its acceptance video: a real device, real taps, the result on screen. Pass or fail, with a reason.

Client accepts
08

Module completion reviews PER MODULE · SIX CHECKS

When a module is done, a review deck walks through it end to end: documented, implemented, tested, bug-free, reviewed, handed over.

Client signs off
09

Customer feedback OPEN ISSUES · DISCUSSIONS

Everything the client raised anywhere on the link, collected in one list with its status, so nothing said in a comment disappears.

Client follows up
How feedback works

A small vocabulary, used everywhere.

A client never writes a specification. They react to concrete things with the same handful of answers, and those answers are what the team builds from.

YesNoAnswer later Not sureNeeds discussionComment

Answers, not essays

Every question, screen or delivery takes the same answers. Open points stay visible in the progress count until they are closed, so "later" is never "forgotten".

PUT /answers  baseUpdatedAt 14:02:11
→ 409 conflict · someone else saved first
→ reloaded, 3 unsaved answers kept

Safe to answer together

Two people on the same link can't overwrite each other. Drafts live on the device until saved; saved state can be exported as CSV or JSON at any time.

Acceptance by video

Each delivered use case comes with a recording from a real phone or desktop: the steps, their results and the evidence on screen. The client marks it passed or not, and says why.

Behind the link

What the client says becomes work the same day.

  • Feedback turns into tasksA "No" or a comment on screen P-07 becomes a dev task that quotes it, with the project's knowledge base attached: earlier answers, designs, the repo's own rules.
  • Documents stay in step with the codeWireframes, design pages and their text versions are regenerated when a task changes them, so the link always shows what was actually built.
  • Progress you can auditA tracking matrix scores every feature on six steps, per delivery week. Anything the client has not accepted is not "done", whatever the team thinks.
  • Nothing risky without a decisionProduction deploys, destructive changes and open design questions pause as requests. A person approves; then it happens.
Client
No on P-07 · "the filter should remember my last choice"
Prebuild
Task grbc-41 created→kb: P-07, Q58, filters.tsx
Dev agent
Implements, updates wireframe P-07running · 14 min
Request
Deploy to production?awaiting owner→approved
Client
Acceptance video 2.3 · passedW2 · 11 / 12
1 linkper client, no login to manage
9 stagesin the same order, every project
EN / VIbilingual content, switch anywhere
Video ✓evidence on every delivered use case

Start with the questions.

Tell us what you want built. Within days you get your own link with the first questionnaire ready to answer. Everything after that happens on the same page.

Request a prebuild khanhquangdtu@gmail.com