SaaS revenue scenario calculator.
The engineering brief.

The complete prompt.

Edit business facts, service boundaries and the first-release scope before building. The specification is original public documentation, not a customer project source bundle.

PRODUCT AND OUTCOME
Build saas revenue scenario calculator. Model subscription assumptions without representing projections as actual revenue or connected billing. Build price/customer sliders, explicit time units and a saved scenario comparison.

ROUTES AND ARCHITECTURE
Create Home, Login, Register, scenarios workspace, Record detail, Profile as real, connected routes. Establish the shared design, route and data contract before generating modules. Keep feature modules, shared navigation, data state and styles separate. Use the supported runtime and approved components; do not invent dependencies or disconnected pages.

DATA CONTRACT
Start from this data/schema.json specification: {"version":1,"collections":[{"name":"scenarios","fields":{"title":{"type":"string","required":true},"customers":{"type":"number"},"price":{"type":"number"}},"label":"scenarios","access":"private","seed":[]},{"name":"costs","fields":{"title":{"type":"string","required":true},"amount":{"type":"number"}},"label":"costs","access":"private","seed":[]}]}. Wire list/get/create/update/remove and subscriptions to real Uvilno.db calls. Derive filters, counts and charts from the same returned records. Real transactional collections begin empty; visibly label and separate any fictional demonstration data. Private writes require the actual isolated visitor identity, not a local role label.

IDENTITY AND INTEGRATIONS
Use configured project-scoped Uvilno.auth; preserve the creator's Uvilno session. Handle sign-in, confirmation, errors and sign-out honestly. Do not add model inference or an unrelated AI assistant unless the brief requests it. Do not fabricate payment, email, booking, messaging or infrastructure connections. Preview Admin/Member/Guest controls change presentation only and cannot authorize privileged writes.

DESIGN DIRECTION
A quiet dark technical workspace with tabular numerals, clear units, restrained color semantics and charts derived from actual entered or stored values. Use only supplied or permission-cleared imagery and licensed fonts. Support 320, 390, 768 and 1440px layouts, keyboard interaction, visible focus and reduced motion. Do not invent testimonials, clients, credentials, usage metrics or awards.

ACCEPTANCE
Check zero customers and high costs produce sensible output without fabricated profit claims. Also check invalid input, empty collections, loading, failed writes, cross-page navigation and a second isolated visitor. Preserve form input on failure; do not claim a check passed unless executed.

HANDOFF
Describe unsupported requirements and Uvilno-hosted dependencies explicitly. Source unlock is $4.99 for one project; generation, hosting and services remain separate. Exporting frontend source does not migrate private records, credentials, accounts or managed infrastructure. Prepare this as an editable brief: project naming never starts generation, and the user must explicitly send it.

Related workflows.

• Personal budget scenario tool
• Freelance cash-flow planner
• Invoice register dashboard

Questions before you choose.