[ 03 // UNDER THE HOOD ]
Built Like Real Software
This is where being an engineer who also does security shows up. The whole thing is a proper application — a public front end, a serverless API, and cloud storage — and it's built so the data is actually protected, not just tucked out of sight.
Public Sitereads live settings
→
Serverless APIauth-gated functions
→
Cloud Storageclients · jobs · prices
Security built in, not bolted on
Every function that touches client data checks for a logged-in operator first and rejects the request outright if there isn't one — enforced on the server, where it can't be bypassed by fiddling with the page. Public visitors can read prices; only an authenticated operator can read or change customer records. That's the difference between a developer who's heard of security and one who breaks into software for a living.
- Public front end — fast, mobile-first, pulls live pricing and settings from the backend.
- Authenticated staff app — five-view operations dashboard behind an identity login.
- Serverless backend — API functions for settings and full client/job CRUD.
- Cloud data store — clients, jobs, pricing, and location live in the cloud — no hardware, no server for Palmer to maintain.
- Server-side authorization — writes require a logged-in operator; customer data never exposed to the public.
- Customer self-booking — one booking system shared between the public site and the staff console.
Why this matters
Palmer went from a phone number on a truck to running clients, scheduling, pricing, and bookings from his pocket — with zero hardware and nothing to maintain. That's not a website. It's the operating system for a one-man business, and it's the kind of thing most agencies quote five figures for.
