This is Svette's own client portal, mapped from the reel you liked — not Hubflo, not another subscription. Clients get a clean 5-step journey. You and Angela get one dashboard behind it — now with App Studio to track the one-of-one apps you're building. Click through both sides below — nothing here is live yet, this is the walkthrough to show the mill and Julie.
Services it’s built for: Security Review & Hardening · Backup & Disaster Recovery · Endpoint & Network · Camera Systems · Ongoing Care
Your project always answers “what happens next?” so you never have to call and ask.
Try signing, paying, and ticking off uploads on the client side. Then switch to the dashboard — all 9 modules, including the new App Studio — to see what that same moment looks like for you and Angela, and where app building is tracked.
What Svette will do, what it costs, and what happens next — in plain English, signed right here in the portal.
What we’ll do: OU setup, user & admin review, Drive / app cleanup, 2-step verification and auto-forwarding checks, plus a 45-minute handover call.
Demo only — the real build records name, date, and an audit trail for every signature.
It shows up the moment the letter is signed. Pay here, get a receipt automatically — no “did you get my check?” loop.
Other first invoices look the same — e.g. the first month of Ongoing Care for a care client. Angela sees every payment land in Books (see the dashboard).
No guessing what to send. Tap each item to simulate uploading it — watch the checklist and progress move.
Files land in private storage (R2 in the real build) — visible only to that client and to Svette. If something’s missing, the reminder names exactly what it is. In Phase 3, AI drafts a summary of each upload for Giovanni to approve — it never files anything on its own.
Giovanni moves a stage once in the dashboard; the client sees it here instantly and gets notified — no separate update email to write.
After the project, the same portal — no new login, no new system — becomes the care home. This is where the back-burner MSP tooling (SOCFortress, Tendril, endpoint tools) would surface for a client when it’s ready, not before.
Systems covered, last check-in, and anything that needs attention — at a glance.
Plain-English summaries land here instead of getting buried in email.
Monthly care billing in the same place as the first invoice. Angela’s Books view stays in sync.
Messages stay tied to the client and project — not scattered across texts and threads.
For you: care clients, renewals, and check-in reminders surface in the follow-up queue before anything lapses.
The morning starting point for both of you. Queues open the place where the action lives; nothing sends, charges, or deletes by accident.
Mill app building · Bizspa app possible · Window CRM shipped & live
Engagement letter sent · not yet signed
Invoice ready for the Nov 22–24 sprint
Network notes, asset list & photos just landed
Renewal / check-in surfaces here before it lapses
Every client with portal status, current project, and care status — Giovanni’s home base.
First pilot for the portal — one real project, end to end, before any paying client touches it.
Google Workspace Audit & Cleanup Sprint, Nov 22–24. The sprint is discovery for what small service businesses actually use — not a sales pitch for this OS.
Illustrative card — shows how the next client slots in.
Illustrative card — camera & network work fits the same stages.
Prospects by stage, from first conversation to signed engagement — so no lead quietly goes cold. (Phase 3 module.)
The same stages the client sees, plus internal tasks, notes, and next steps that stay private.
Client sees: Findings · Internal: review admin accounts, check backup status, note next step
Client sees: Scheduled Nov 22–24 · Internal: GAM audit dumps → findings list, 45-min handover
Client sees: Assessment · Internal: run count, cable, recorder checklist
One place to track what applications you're building — for clients and for yourself. One-of-one business apps, built for a single small business instead of off-the-shelf software, with AI at the forefront and speeding up application building. This panel is illustrative in the demo — it shows the shape of the tracker, with no live backend behind it yet.
One-of-one app being built for the mill — shaped around how that one business actually works. This is the pilot build tied to the mill's portal pilot.
Illustrative — possible, not started and not promised. Julie may want an application as well — the shape would come from what she actually needs, not a pitch made before discovery.
Your own one-of-one app — already shipped and live at crm.uwharriecleaning.com. The proof this model works: jobs, customers, invoices, Books for Angela, and review follow-up in one system built for exactly one business.
Illustrative — this is where the next idea lands.
A new card starts here whenever a small business needs its own app: who it's for, what it does, status, and next step — added in one place instead of living in your head.
Honest scope: App Studio in this demo is a tracker mock only — no live backend, no saving, no syncing. In the real OS it would store these cards alongside Clients and Projects, on the same Cloudflare stack as the CRM.
All portal messages in one inbox, tied to the client and project they belong to. (Phase 3 module.) AI can draft a reply — you edit and send it.
Uploaded our network notes — the switch photo is in there too. What’s next?
Looking forward to the sprint. Where should I send the admin login details?
Invoices, payments, and totals in a spreadsheet-style view Angela can scan and export — modelled on the CRM Books view she already uses. Lands in Phase 2, with her sign-off on the shape before any money moves.
Google Workspace Audit & Cleanup · Nov 22–24
Illustrative row — care billing once Phase 2 is live
*Same rule as the CRM: paid invoices use the paid date as the invoice date; unpaid keep their creation date.
Everything clients uploaded, organised by client, with review status. Private storage — no public links; downloads are signed and short-lived in the real build.
The Mill · Uploaded today
The Mill · Uploaded today
The Mill · Uploaded today
Phase 3: AI extracts device names, dates, and counts into a summary — Giovanni approves it before anything is saved.
The wording and timing that run the portal. Angela and clients never see this; destructive actions stay admin-only, like the CRM.
Plain-English master wording for new engagements
Business name, payment provider, receipt wording
When unsigned-letter and unpaid-invoice nudges go out — drafts always visible first
Welcome text, checklist labels, care view copy
Demo data is illustrative — the two named engagements (the mill pilot and the $500 Bizspa sprint, Nov 22–24) are the real ones from the OS map. Nothing you tap here saves, sends, or charges anything.
Clients only ever see the top layer. You and Angela work in the middle. The bottom is shared plumbing — and most of it already exists from the CRM.
A branded login at svetteconsulting.com. Sign, pay, upload, follow progress, stay for care.
One view for Giovanni and Angela instead of threads, texts, and spreadsheets scattered across phones — 9 modules in all, including App Studio for app building.
Reuse, don’t rebuild: sign-in, database, file storage, and the deploy pipeline already work for the CRM at crm.uwharriecleaning.com. This OS reuses that pattern — it does not touch the live CRM. The same stack is what App Studio builds on.
AI reads uploads into summaries you approve, and drafts client updates in plain English for you to edit and send.
It does not message clients unsupervised, change invoices, or make security findings. For a security firm, that line is the reputation.
Same gated approach you set for productising the window CRM. Stop anywhere without being locked in — nothing here requires buying a platform.
This walkthrough page — looks like the reel, tests whether clients care. No login, no backend.
Client login, engagement letter with e-sign, file upload with checklist, live project stages. Dashboard: Clients, Projects, Files.
Invoices & payment in the portal, automated payment reminders, and Angela’s Books view with export.
AI summaries of uploads, message inbox, pipeline view, care view, and the full follow-up automation set — plus App Studio & one-of-one app builds, tracking every app you're building for clients and for yourself with AI speeding up the build.
Show it to the mill and to Julie after the Nov 22–24 Bizspa sprint. If they shrug, you’ve lost almost nothing. If they light up, Phase 1 — the real portal for the mill pilot — gets built with confidence. The dashboard now runs to 9 modules with App Studio included, so app building has a home from the start: the mill app building, a possible Bizspa app, and your own shipped CRM, all tracked in one place. Two systems, two jobs: this OS never replaces the window-cleaning CRM, and the CRM never becomes this — App Studio is simply where you track building apps like it.
What a “yes” to Phase 1 needs