Skip to content

Pricing a Mock-up

/quote answers the client’s next question: “how much?”. It reads the mock-up, estimates the real system behind it, and writes two documents — one for you, one for the client.

A mock-up is a static shell running on mock data. The client is buying the real system: a database, real sign-in, server-side permission checks, payments, integrations, QA, and launch. /quote prices that, not the HTML. It works through a checklist of everything the mock-up fakes, so nothing the real system needs gets left out of the price.

The mock-up itself is billed only if you say so, as its own line — often credited back if the client signs.

/quote never invents commercial terms. Have these ready:

  • your rate and currency (hourly, daily, or per role)
  • tax (for example VAT 12%), any discount, and the payment schedule you use
  • team size, for the timeline

If you quote often, put your standing defaults in quotes/rates.md. It’s yours, it’s read first, and it overrides the built-in sizing guide:

# Rates and terms
- Rate: ₱1,200 per hour, blended
- VAT 12%, added on top
- Payment: 30% on signing, 40% at beta handover, 30% at go-live
- Validity: 30 days
- Team: 2 developers at 30 h/week
- Our auth + roles foundation usually takes 30–45 h
/quote
/quote MVP only — Reports and Loyalty can be phase 2
/quote the mock-up in mock-up-clinic/

Without a mock-up it works from your description of the system, and says so in the costing.

  1. Scope inventory. It reads the mock-up’s tabs, bubbles, roles, permissions, business rules, and data model, and lists every screen, flow, and cross-cutting feature, plus what the mock-up fakes.
  2. Your questions. One message covering your business details, rate, scope or MVP, platform, integrations, after-launch support, and terms, then four quick choices: pricing model, contingency, whether to show hours, and what to do with the mock-up fee.
  3. Estimates. Each line gets three numbers — optimistic, likely, and pessimistic hours — sized from its built-in guide or your quotes/rates.md.
  4. The numbers. A bundled script calculates every figure from costing.json. Nothing is typed by hand.
  5. Your review. You see the total, the range, the price per phase, the biggest cost drivers, and the timeline. You can adjust scope or terms before anything is written.
  6. The documents. After your yes it writes the costing and the quote.

For each line, the expected effort is the three-point (PERT) mean:

expected hours = (optimistic + 4 × likely + pessimistic) ÷ 6

Then, per phase:

phase price = expected hours × rate × (1 + overheads) × (1 + contingency), rounded up

A worked example, at ₱1,200 per hour with 20% QA, 10% project management, and 15% contingency, rounded up to the nearest ₱1,000:

Item O M P Expected
Register with options and split payment 24 40 64 41.3 h
Bar queue board 10 18 30 18.7 h
Phase 60 h

60 h × ₱1,200 = ₱72,000 → × 1.30 × 1.15 = ₱107,640 → ₱108,000.

After the phases come the discount, tax on the discounted subtotal, and the payment milestones. The last milestone absorbs any rounding, so they always add up exactly to the total. Optional add-ons (native apps, phase 2 modules) and recurring costs (hosting, retainers) are priced and listed separately, never inside the total.

Tier Example Likely hours
S Read-only list, detail view, simple settings form 8
M CRUD with validation, search, a report with CSV export 18
L Multi-step flow with rules: checkout, booking slots, enrollment with fees 40
XL An engine: recipe-driven stock, staff scheduling, offline sync 80

Foundation work — setup and CI, data model, authentication, roles and approvals, the app shell — is priced once per project. Integrations such as payment gateways, printers, and accounting sync are priced one by one, with wider ranges. These are starting points; your own quotes/rates.md beats them.

Everything lands in quotes/<YYYY-MM-DD>-<client>/:

File For Contains
costing.json Revisions Items, hours, rate, and terms — the input
costing.md You only Hours, rates, overheads, contingency, the effort range, and assumptions and risks
quote.md The client Summary, scope and price per phase, add-ons, ongoing costs, timeline, payment schedule, assumptions, exclusions, acceptance

On request it also writes a printable quote.html with the mock-up’s accent and logo — open it and print to PDF.

The client quote shows prices, scope, and terms. Hours, rates, and buffers stay in costing.md unless you choose to show hours.

  • Before writing, /quote checks whether quotes/ is ignored by Git and recommends ignoring it if not. Rates and margins don’t belong in a repository the client may receive later.
  • Quotes are never written inside mock-up/, because deploying the demo would publish them.
  • It never emails, uploads, or publishes anything. Sending the quote is up to you.
  • Dashboard activity shows only “Pricing a client mock-up” — never names, rates, or amounts.

Ask in the same chat (“drop Loyalty to phase 2”, “make it 10% contingency”) and the agent edits costing.json and reruns the script. A re-quote after the client has seen one goes in a new dated folder, so the version they received stays exactly as it was.

  • Invent a rate, tax rate, or discount.
  • Do arithmetic by hand.
  • Call a quote final until you say so, or offer it as legal advice.
  • Send, upload, or publish anything.
  • Read or write the Syntaxis plans, specs, or findings.

Start the real project with /scaffold or /onboard, then carry the quoted scope into the plans. See From signed quote to build loop.