Svette Consulting · Phase 0 Demo

One place to sign, pay, upload — and actually see progress.

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.

Built on the  same Cloudflare stack  as the window CRM Pilot first:  the mill Cost to test this demo:  $0

Services it’s built for: Security Review & Hardening · Backup & Disaster Recovery · Endpoint & Network · Camera Systems · Ongoing Care

Svette ConsultingClient Portal

Welcome back — here’s where things stand

Your project always answers “what happens next?” so you never have to call and ask.

✓ Engagement letter — signed
✓ First invoice — paid
3 Upload your files — 2 of 4 in
4 Watch the work — Assessment underway
5 Ongoing care — after wrap-up
Works on a phone — most clients sign & pay from theirsPrivate to each client
Interactive walkthrough

Click through it like a client would — then flip to your side.

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.

🔒 svetteconsulting.com/portal — what the client sees
● Awaiting signature

Engagement letter

What Svette will do, what it costs, and what happens next — in plain English, signed right here in the portal.

Svette Consulting — Engagement Letter
Example: Google Workspace Audit & Cleanup Sprint
Nov 22–24 · Fixed scope

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.

  • What it costs is stated up front — no open-ended hourly surprise for this sprint
  • Your files and access stay yours; we work in your admin console
  • If we find something bigger, we name it and price it separately — nothing extra runs without your OK
Sign here — tap “Sign” to try it

Demo only — the real build records name, date, and an audit trail for every signature.

● Unpaid

Your first invoice

It shows up the moment the letter is signed. Pay here, get a receipt automatically — no “did you get my check?” loop.

Invoice #1001
Svette Consulting
Due on signing
Google Workspace Audit & Cleanup Sprint$500.00
Scope: OUs, user/admin review, Drive cleanup, 2SV checks, handover callFixed
Total due$500.00
Demo — real build uses a payment provider; unpaid invoices get a gentle, pre-written reminder on a schedule you set.

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).

Upload your files

No guessing what to send. Tap each item to simulate uploading it — watch the checklist and progress move.

0 of 4 received0%

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.

Watch the work happen

Giovanni moves a stage once in the dashboard; the client sees it here instantly and gets notified — no separate update email to write.

✓
AssessmentWe look first
2
FindingsWhat we found
3
FixesWe put it right
4
Wrap-upSummary & next steps
Findings underway — reviewing accounts, devices & backupsToday
Assessment complete — inventory & access review doneYesterday
Files received — 4 of 4 checklist items inYesterday

Stay on for ongoing care

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.

🛡 Care status

Systems covered, last check-in, and anything that needs attention — at a glance.

📄 Periodic reports

Plain-English summaries land here instead of getting buried in email.

🧾 Care invoices

Monthly care billing in the same place as the first invoice. Angela’s Books view stays in sync.

💬 One place to ask for help

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.

Good morning — here’s today

The morning starting point for both of you. Queues open the place where the action lives; nothing sends, charges, or deletes by accident.

1Letter awaiting signature
1Invoice unpaid
3Files waiting for review
2Follow-ups due
3apps in App Studio
Apps
3 apps in App Studio

Mill app building · Bizspa app possible · Window CRM shipped & live

Letter
The Mill — pilot project

Engagement letter sent · not yet signed

Invoice
Bizspa sprint — $500

Invoice ready for the Nov 22–24 sprint

Files
3 uploads to review

Network notes, asset list & photos just landed

Follow-up
Care check-in coming due

Renewal / check-in surfaces here before it lapses

Clients

Every client with portal status, current project, and care status — Giovanni’s home base.

The Mill Pilot

First pilot for the portal — one real project, end to end, before any paying client touches it.

PortalLetter sent
ProjectSecurity review
AppBuilding — tracked in App Studio
CareNot yet

Bizspa — Julie Stevens

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.

PortalExample in this demo
Project$500 sprint
AppPossible — discovery at the sprint
CareTBD after sprint

Example client — local office

Illustrative card — shows how the next client slots in.

PortalActive
ProjectFindings stage
CareActive

Example client — church / campus

Illustrative card — camera & network work fits the same stages.

PortalInvited
ProjectCamera system
CareNot yet

Pipeline

Prospects by stage, from first conversation to signed engagement — so no lead quietly goes cold. (Phase 3 module.)

First conversation

New enquiryVia svetteconsulting.com contact
ReferralWord of mouth — follow up this week

Letter sent

The MillPilot — letter awaiting signature

Signed

Bizspa sprintNov 22–24 · $500 fixed scope

Projects

The same stages the client sees, plus internal tasks, notes, and next steps that stay private.

Security Review — The Mill (pilot)

Client sees: Findings · Internal: review admin accounts, check backup status, note next step

Findings
Workspace Sprint — Bizspa

Client sees: Scheduled Nov 22–24 · Internal: GAM audit dumps → findings list, 45-min handover

Scheduled
Camera Systems — example

Client sees: Assessment · Internal: run count, cable, recorder checklist

Assessment

App Studio

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.

3Apps tracked
1Building now
1Possible
1Shipped & live

The Mill — pilot app Building

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.

ForThe Mill — pilot client
StatusBuilding
What it doesCustom app for the mill's own workflow
Next stepKeep building & test with real use
AI at the forefront: AI drafts features and first-pass code and speeds up iteration — Giovanni reviews, decides, and ships. AI speeds up the build; it doesn't run it unsupervised.
Notes — mockPilot scope, what's working, what's next — kept here in the real build instead of scattered across texts. Demo only: this notes area is a mock and nothing typed or tapped here saves.

Bizspa — possible app Possible

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.

ForBizspa — Julie Stevens
StatusPossible
What it could doA small app for how Bizspa runs — TBD
Next stepDiscovery at the Nov 22–24 sprint
AI at the forefront: If it moves ahead, AI would speed up application building the same way — fast first drafts, quick iteration, human sign-off before anything ships.
Notes — mockWhat Julie uses for clients & appointments now, pain points, and whether an app even fits — gathered at the sprint. Demo only: this notes area is a mock and nothing here saves.

Uwharrie Window Cleaning CRM Shipped

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.

ForYour own business — Uwharrie
StatusShipped & live
What it doesJobs, invoices, Books & reviews
Next stepKeep logging paper-cuts as you use it
AI at the forefront: Built and iterated with AI assistance on the same Cloudflare stack — Pages, Workers, D1 & R2 — the template for how fast a one-of-one build can move now.
Notes — mockFriction, ideas, and product lessons from daily use — the stuff that would shape the next client app. Demo only: this notes area is a mock and nothing here saves.

+ Next one-of-one app

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.

Why this matters: One-of-one business, small business apps really are a thing now. App Studio keeps that pipeline visible — building, possible, and shipped — alongside clients and projects.

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.

Messages

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.

M
The Mill — pilot contact

Uploaded our network notes — the switch photo is in there too. What’s next?

J
Julie — Bizspa

Looking forward to the sprint. Where should I send the admin login details?

Books — Angela’s view

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.

$500Open in this demo
CSVExport anytime
AutoReceipt on payment
Paid dateUsed as invoice date*
#1001 — Bizspa sprint

Google Workspace Audit & Cleanup · Nov 22–24

$500Unpaid
Ongoing Care — monthly (example)

Illustrative row — care billing once Phase 2 is live

—Phase 2

*Same rule as the CRM: paid invoices use the paid date as the invoice date; unpaid keep their creation date.

Files

Everything clients uploaded, organised by client, with review status. Private storage — no public links; downloads are signed and short-lived in the real build.

Network notes.pdf

The Mill · Uploaded today

To review
Asset list.xlsx

The Mill · Uploaded today

To review
Switch closet photo.jpg

The Mill · Uploaded today

Reviewed

Phase 3: AI extracts device names, dates, and counts into a summary — Giovanni approves it before anything is saved.

Settings — admin only

The wording and timing that run the portal. Angela and clients never see this; destructive actions stay admin-only, like the CRM.

Engagement letter template

Plain-English master wording for new engagements

Invoice details

Business name, payment provider, receipt wording

Follow-up timing

When unsigned-letter and unpaid-invoice nudges go out — drafts always visible first

Portal wording

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.

Under the hood

Three layers, one system.

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.

Layer 1 — Clients see this

Client Portal

A branded login at svetteconsulting.com. Sign, pay, upload, follow progress, stay for care.

Engagement letter & e-signInvoices & paymentFile uploadProject progressMessagesOngoing care status
Layer 2 — You run this

Internal Dashboard

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.

Home / TodayClients & pipelineProjects & tasksApp Studio & one-of-one buildsMessage inboxBooks viewFollow-up queueFilesSettings
Layer 3 — Shared plumbing

Cloudflare Backend

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.

Pages — siteWorkers — logicD1 — databaseR2 — filesAccess — sign-inApp Studio & one-of-one builds
Letter sentDashboard → client welcome
→
SignedInvoice issued, follow-up armed
→
Files inReview queue (+ AI summary in Phase 3)
→
Work liveStages update for the client

Automations that chase the paperwork

  • Follow-up nudges — an unsigned letter or unpaid invoice gets a polite, pre-written reminder on a schedule you set. Drafts are visible; nothing surprising ever goes out.
  • Upload reminders — if a requested file hasn’t arrived, the nudge names exactly what’s missing.
  • Progress notifications — move a stage once; the client is notified. No separate update email to write.
  • Care reminders — renewals and check-ins surface in your queue before they lapse.

AI stays in its lane

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.

Security is the product — so it comes first

  • Sign-in — Cloudflare Access in front of the dashboard; per-client accounts for the portal. Google sign-in is the proven pattern from the CRM.
  • Client separation — every file, invoice, and project is tied to one client record and checked on every request.
  • File safety — private R2 storage, no public links; downloads are signed and short-lived.
  • Audit trail — signatures, payments, uploads, and admin actions logged with dates, like the CRM audit log.
  • Backups — full export for admin, on the same pattern as the CRM backup export.
  • Tested before trust — client separation and sign-in get tested with dummy accounts before any paying client uses it — same discipline as the CRM security audit.
Gated build

Each phase has to earn the next.

Same gated approach you set for productising the window CRM. Stop anywhere without being locked in — nothing here requires buying a platform.

You are here
Phase 0

Demo

This walkthrough page — looks like the reel, tests whether clients care. No login, no backend.

Proved by
Showing it to the mill & to Julie after the Bizspa sprint
Running cost
$0 — static page
Phase 1

Portal MVP

Client login, engagement letter with e-sign, file upload with checklist, live project stages. Dashboard: Clients, Projects, Files.

Proved by
The mill piloting one real project end to end
Running cost
Cloudflare free tiers, as with the CRM
Phase 2

Money

Invoices & payment in the portal, automated payment reminders, and Angela’s Books view with export.

Proved by
First real invoice paid through the portal
Running cost
Free tiers + payment fees on paid invoices only
Phase 3

Smart

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.

Proved by
A care client running a full cycle in the portal — and App Studio tracking a real build end to end
Running cost
Free tiers; AI pay-as-you-go, capped by design
Risk: scope creep. The reel makes it look effortless. The gates above are the control — no phase-jumping.
Risk: support time. Clients will sometimes need login help. One friendly pilot first keeps it small while you learn.
Risk: client data. Hosting other businesses’ files is a real obligation. Phase 1 security checks are not optional.
The decision — Option A, then B

You picked demo first. This page is that demo.

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

  • 1. Confirm the pilot — is the mill first, as planned?
  • 2. Confirm the address style — a client area on svetteconsulting.com, alongside the existing site.
  • 3. Angela’s sign-off on the Books view shape — at Phase 2, before any money moves through it. Nothing else is needed now.