Illustrative scenario — not a client
Lovable-built marketplace taken to production
A founder's Lovable prototype of a local services marketplace works in the demo; real sellers and buyers are about to join.
Reviewed by Atin Agarwal, IOanyT · 5 October 2026
Document 1 · Readable requirements
Plain prose, not a bullet dump
An excerpt. A real specification covers every screen and flow.
- R-01
Each seller sees only their own orders
A seller signed in to the dashboard sees their own listings, orders and payouts, and cannot read another seller's data, even by changing an address in the browser. Buyers see only their own orders.
- R-02
Accounts can be recovered safely
Users can reset a forgotten password by email. Sessions expire after inactivity, and signing out on one device does not sign out the others unless the user chooses "sign out everywhere".
- R-03
Money and records always agree
A buyer's payment, the seller's payout and the order status stay in step. Failed payments leave the order unpaid and visible to the buyer; refunds reverse the payout and are recorded against the order.
- R-04
Problems are seen before customers report them
Errors and slow pages raise an alert to the team. Every release goes to a staging copy first, and the core flows (sign-up, listing, ordering, paying) are covered by automated tests that must pass before a release.
Document 2 · Wireframes
Every screen, to review
A few of the screens. Wireframes show what is on each screen and where — not the visual design.
New orders
To complete
Paid out
Next payout · Monday
- Order 1182 · scheduled
- Order 1179 · refunded part
- Order 1170 · paid
Swipe for more screens →
Document 3 · Walkthrough
A day in the life of the app
People catch missing scope in a story far more reliably than in a table of requirements.
A buyer finds a cleaning service, books Saturday morning and pays by card. The seller's dashboard shows the new order, and only her own orders, the moment it lands. On Saturday evening she marks the job done; the payout is scheduled automatically. On Sunday the buyer asks for a partial refund; support approves it, the payout adjusts, and both see the same numbers. Meanwhile an error on the search page triggers an alert, and the fix goes to staging, passes the tests and ships before Monday.
Document 4 · Scope
Defined by both lists
In this release
- Sign-in hardening, password reset and session handling
- Rules for who can read which data, so each seller sees only their own orders
- Secrets moved out of the browser
- Payments with seller payouts, refunds and failed-payment handling
- Automated tests to 80% coverage on the core flows
- Monitoring and error alerts
- Deployment pipeline with a staging environment
Not in this release
- Native mobile apps
- Reviews and ratings
- In-app messaging between buyers and sellers
- A second language
- Seller analytics dashboard
On a real quote, each carries a price to add it later.
Document 5 · Assumptions register
What the price rests on
If one turns out to be wrong, that is a pre-agreed trigger to re-quote — not an argument.
- The existing screens and flows stay; this is hardening, not a redesign
- Under ten thousand users in the first six months
- One country and one currency
- Read-only access to the repository and the hosting account for the review
Document 6 · The quote
Three tiers. Every line visible.
QA and security sit in every tier. They are never what a smaller tier removes.
| Line item | Lean | Standard | Premium |
|---|---|---|---|
| Sign-in hardening, password reset, sessions | ● | ● | ● |
| Data access rules per seller and buyer | ● | ● | ● |
| Secrets moved out of the browser | ● | ● | ● |
| Monitoring and error alerts | ● | ● | ● |
| Payments with payouts and refunds | — | ● | ● |
| Failed-payment handling | — | ● | ● |
| Core-flow tests to 80% coverage | — | ● | ● |
| Staging environment and release pipeline | — | — | ● |
| Load testing before launch | — | — | ● |
| Priority support, three months | — | — | ● |
| Test coverage 80%+ | ● | ● | ● |
| Security review | ● | ● | ● |
| Dependency scanning | ● | ● | ● |
Your own quote shows a total for each tier, locked for 14 days from the moment it is issued.
Lean
Sign-in, data access rules, secrets and monitoring: the fixes launch needs
Standard
Lean plus payments with payouts and refunds, and tests to 80% coverage
Premium
Standard plus a staging pipeline, load testing and three months of priority support
An illustrative scenario, not a quote for your project. Your quote is built from your own specification, with a blended total on every line instead of a rate card, and locked for 14 days once issued.
What arrives
Enough to decide with. Then enough to build from.
| Artifact | Free | On signature |
|---|---|---|
| Readable requirements Plain prose, not a bullet dump | Included | |
| Wireframes Every screen, to review | Included | |
| Scope summary What the build covers | Included | |
| Explicit exclusions The "not in this release" list, with backlog prices | Included | |
| Assumptions register Every load-bearing assumption, stated | Included | |
| Three-tier itemized price Traceable line items | Included | |
| Machine-readable spec exports | On signature | |
| Editable wireframe files | On signature | |
| openapi.yaml The API contract | On signature | |
| Mapping CSVs | On signature | |
| Given/when/then suites | On signature | |
| Architecture decisions | On signature |
What arrives free
- Readable requirements Included Plain prose, not a bullet dump
- Wireframes Included Every screen, to review
- Scope summary Included What the build covers
- Explicit exclusions Included The "not in this release" list, with backlog prices
- Assumptions register Included Every load-bearing assumption, stated
- Three-tier itemized price Included Traceable line items
What arrives on signature
- Machine-readable spec exports On signature
- Editable wireframe files On signature
- openapi.yaml On signature
- Mapping CSVs On signature
- Given/when/then suites On signature
- Architecture decisions On signature
What happens next
From your description to the build
- 01
You describe it
In plain words. Today a person runs the intake with you by email.
- 02
It asks back
The questions a good engineer would ask, before anything is priced.
- 03
The documents arrive
Everything on this page, for your project, before you pay anything.
- 04
The price holds
The quote is locked for 14 days from the moment it is issued.
- 05
You sign, we build
Every requirement traced from quote line to accepted build. Changes priced before you approve them.
Defined by both lists
Get this quoted for your project.
No signature, no call. A business email unlocks the full quote.