We started with the reply, not the dashboard. The hard part of review management is writing something that sounds like the business, so the product is organised around one view: the review, the draft and the approve button.
Maltese was the test. A draft has to work in the language the review arrived in, and an owner still has to check it, so every draft is labelled for review before sending. The AI does the first pass and the person stays in charge.
We put the controls in place before the first customer, and audits in August and September tightened them. Row-level security covers every public table, connection tokens are encrypted, and a state machine is designed to stop one reply being posted twice.
The stack is Next.js and Supabase on Vercel, with Claude drafting and Stripe wired in for billing, still in test mode. The September release passed 172 unit and integration tests and 65 browser tests.
The interface stays quiet on purpose. Owners open it between jobs, so it uses one list, clear states such as Draft ready, and very little else.