Double bookings, partial refunds, duplicate webhooks, commission on a cancelled sale. Each one takes a week to find in production.
I've been waiting 20 minutes and the front desk says my booking doesn't exist??
Why did my payout go down? I did that facial, the client just changed her mind.
Why can Fon still see our client list? She left on Friday.
Charged twice for one massage and nobody answers the phone after 8pm.
These numbers don't match the bank statement. I can't close the month like this.
Each Module ships with its schema, screens, routes and workflow tests. Your agent switches on what the business needs and writes only what's specific to it.
Overlapping slots, walk-ins, no-shows, therapist swaps, deposits.
Card and QR checkout, partial refunds, duplicate webhooks, terminals at the counter.
Commission rules per service, reversals on refunds, time clock, payout runs.
Split bills, discounts, receipt and kitchen printers, end-of-day close.
Stock running out mid-checkout, pickup times, order status messages.
Sign-in, booking history, saved cards, LINE and email notifications.
Every app gets its own database branch and a test harness that runs your real routes against it. No mocks, so a green run means the release works.
Postgres, auth, payments and email behave the same in tests and previews as in production.
Agents test whole flows, from booking to checkout to payout, not functions in isolation.
Migrations are checked before they reach production. Nothing gets dropped by accident.
Click through a change on its own copy of the data before it ships.
For agencies and freelancers
Features are Modules, not code woven through the app. When a client adds online ordering or drops memberships in week six, your agent switches a Module instead of rewriting the system.
Start from your own Blueprint and tested Modules. Your agent writes only what's specific to this client.
Add point of sale or drop memberships mid-project. Modules switch on and off without touching the rest.
Restyle or extend a Module's screens. Platform fixes still reach your client's app.
Hosting, monitoring and updates stay with us, not on your retainer.
One command creates the app, connects the Stardeck MCP server to your agent and pulls your environment.
Creates the app from the Blueprint and clones it
Connects the MCP server to your agent
Your agent builds, tests and deploys