SaaS products
A product with a subscription, a customer, an invoice and an administrator. Authentication, billing, onboarding, empty states and the data model behind them are planned together rather than stitched together afterwards.
Use cases
Echo generates full-stack web applications — products with authentication, data, state and server routes. These are the shapes that come up most often, and what each one needs before the first build starts.
01 / The shapes
A product with a subscription, a customer, an invoice and an administrator. Authentication, billing, onboarding, empty states and the data model behind them are planned together rather than stitched together afterwards.
Dispatch boards, inventory, approval workflows, scheduling and the reporting your team asks for every week. Software that fits how the work actually happens, instead of a generic form with a database behind it.
Branded hubs where customers sign in to see their projects, approve milestones, upload files and pay invoices — replacing the spreadsheet-and-email loop that quietly costs a business hours every week.
Marketing sites, landing pages, calculators, directories and booking tools. Echo targets the web, so the output is a real application with routes and state — not a static page that has to be wired to something later.
02 / What is common to all of them
The relationships in the product are decided once, in the plan, and every screen and API route is built against that same model.
Empty lists, loading, errors and permissions are part of the specification, not something you discover in production.
Payments, authentication, storage and email are connected as plugins against the real provider interfaces.
Every use case ends the same way: a standard React, Next.js and TypeScript project you can export, review and hand to an engineering team.
Start with the outcome and the people who need it. Echo will show you the plan before it writes the code.