The part of the site that runs the business, not just describes it.
Most small business sites stop at the brochure. Then bookings come in by phone, inventory lives in a spreadsheet, and someone emails me every time a price changes. I build the screens behind the site so the people who work there can run it themselves.
Expected outcome
- Staff can change prices, hours, and content without calling me.
- Bookings and inquiries land somewhere you can actually work through.
- One record of what changed and who changed it.
- A system the business keeps running after the invoice is paid.
01
What usually needs building
Every business has two or three things it does by hand that it shouldn't have to. Those are the screens worth building first.
- Booking and scheduling, with the rules your day actually runs on
- Inventory, catalog, and pricing your staff can update
- Content editing that doesn't need a developer
- Staff accounts, roles, and a record of who changed what
02
Built for whoever is at the counter
These screens get used by the person covering the front on a Tuesday, not by a developer. That decides how they are built.
- Plain language instead of terms borrowed from the database
- A confirmation step before anything is deleted
- Works on the phone behind the counter, not just on a desktop
- Simple enough to show a new hire once
03
Scope and investment
Admin work is scoped with the build rather than sold off a list, because what it needs depends on what the business is doing by hand today.
- Usually part of a structured build or rebuild, $5,000–$25,000+
- A single workflow added to an existing site can be smaller
- Scoped from a walkthrough of how the work gets done now
- Handoff notes and a walkthrough with the people who will use it
Doing something by hand that should be a screen?
Tell me what the workaround is right now. The spreadsheet, the notebook, the calls that come in after hours. That's usually where the work worth doing starts.