BUILDER’S NOTEBOOK · WORKING PROTOTYPE
Useful first.
Shared for a reason.
Room works across design disciplines. The launch pilot starts with independent brand and identity designers on fixed-price projects, at the moment a client asks for extra work. The five-second hook: “One more thing” doesn’t have to mean free work.
The wedge
Three concrete paths: pay for the addition, replace a named deliverable, or keep this phase as agreed. Existing products cover change requests; Room tests whether explicit scope swaps and a short conversation beat another client portal. The user supplies and verifies the estimates.
The sharing loop
Designer creates options → client gets a useful decision → client copies a reply into their existing conversation. A quiet, optional link lets a recipient create their own card. Peer sharing of permissioned, anonymized examples may be more effective than client conversion.
What works now
Examples across design disciplines, a custom path, price calculation, editable inputs, local draft saving, client-message copying, URL snapshot cards, a recipient decision flow, editable replies, invalid-link handling, and local event inspection. No signup or AI API is required.
Prototype boundaries
This deployment is public. Anyone with a card link can open it; copied messages work immediately. Shared cards are fixed snapshots with their details in the link. Links cannot be revoked or updated. Nothing is automatically sent, approved, or synchronized. Confirm the decision with the client in your existing conversation.
Drafts stay in browser storage. Test events stay in the tab session. Feedback is submitted to FormSubmit for forwarding by email to [email protected]; it is separate from draft and analytics data. There is no remote analytics collector or aggregate dashboard. The hosting service and Google Fonts receive normal asset/page requests.
First experiments
| Test | Sample | Continue when… |
|---|---|---|
| Five-second hook | 10 target designers | 8/10 understand the audience and next step. |
| Uncoached task | 8 designers | 6/8 create an accurate card within 90 seconds. |
| Real client conversation | 10 consenting designers | 6/10 report a clear next step; 5/10 get a direction. |
| Repeat usefulness | 14-day cohort | 40% of those with another qualifying request return; at least 5 eligible people. |
These are pilot decision rules, not measured results. Share a complete free template in two relevant communities with moderator permission. Disclose the builder relationship. No scraped contacts, bulk messages, manufactured urgency, forced shares, or client data in public examples.
Measure resolved work
The outcome is a real scope conversation resolved, confirmed by an opt-in follow-up. Card creations and copied links are proxies. For launch: qualified visit → custom card → message/link copied → recipient reply → confirmed direction. Report message-only use separately from card links.
Download the full launch and analytics plan →
Local test events
Inspect this tab’s events below. They contain event names, timestamps, and a small set of non-content properties; no project text, rates, prices, or client details. Previews are kept separate from recipient views. Raw counts are actions, not users.
Research context
ScopeDue’s change-request workflow shows that the category already exists. freelancermap’s freelancer guide discusses pricing and scope conversations. Neither source validates demand for Room.