Module 07 — Build your operating system
Your operating system, end to end
You'll see the whole system run for one small business over one week, choose how you'll run yours — by hand, with connected tools or on one platform — and write it on a single page.
The problem
Built piece by piece, a system can still feel like twenty separate chores. The goal was never more tasks. It's one flow: every inquiry moves from capture to conversation to follow-up to a decision, the repetitive steps run on their own, and a weekly number tells you it's working.
Why it matters
A system you can describe on one page is a system you can run in a busy week, hand to a new person and improve one decision at a time. That's the difference between a business that runs on your memory and one that doesn't.
1 The whole flow, in order
- Lead captureEvery door into one log, a first reply and a lane.Lessons 4.1–4.3
- ConversationCoverage and windows, saved replies, takeover rules.Lessons 5.1–5.3
- Follow-upThree useful touches for quiet leads and quiet quotes.Lesson 6.2
- PipelineStages by customer action; a next step and a date for every deal.Lesson 6.1
- AutomationSpecs, safeguards and a weekly check for every automated step.Lessons 3.1–3.3
- MeasurementSix numbers and one decision a week.Lesson 7.2
Underneath all of it: the facts sheet, the answer bank and the prompts from module 2, and the handoffs from lesson 7.1 that connect each part to the next.
2 Four ways to run it — and when a platform makes sense
The system stays the same whatever tools you use. Choose a level for each part of the flow; they don't all have to match.
-
By hand
A spreadsheet, saved replies and a calendar
The lead log, pipeline and scorecard in one spreadsheet; saved replies on your phone; calendar events for sweeps, windows and reviews. Free, and good for a few dozen inquiries a week — if you keep the rhythm.
-
Tools you already have, connected
Forms, email rules and a connector
A form tool that writes to your sheet, email rules, a booking calendar with reminders, and a connector like Zapier or Make for the handoffs. Flexible, but you own the wiring and the weekly checks from lesson 3.3.
-
Automated
AI drafting and automatic reminders
AI drafts replies and follow-ups from your answer bank (lessons 2.2 and 5.2), and reminders fire when a follow-up touch is due. Every automation gets a spec, an owner and a check.
-
Built by the Wioxon team
One integrated platform
When the wiring has become the job
If most of your customers talk to you in chat and keeping five tools connected takes more time than it saves, one platform can carry much of the flow. DenEnter does this for WhatsApp and website chat: one inbox, an assistant that answers from your business information and hands over to your team, every contact with their conversations, a pipeline of opportunities, quotes, and follow-ups and reminders.
What it doesn't cover: email, phone calls and text messages; Instagram and Messenger only switch on after Meta's final approval; and your review routine and weekly scorecard still depend on the habits from this course. It's a paid product — the free levels above work, and they're where most businesses should start.
DenEnter is built by the same team behind Wioxon. denenter.com
3 Step by step: write your operating system
-
Fill in each part of the flow
For each one, write what you built, the tool and the owner. Leave nothing as “we'll figure it out.”
-
Choose a level for each part
Many businesses run capture on connected tools and keep follow-up by hand. Pick what you'll actually keep up this month, not what sounds best.
-
List your automations and their checks
Every automated step, with its owner and its weekly check from lesson 3.3.
-
Put the rhythm in your calendar
Daily: two sweeps, reply windows, the pipeline review. Weekly: the marketing hour, the 20-minute review, automation checks. Monthly: answer bank and takeover rules.
-
Pick the first thing to improve
The Scan ranks your leaks from seven questions. Give the top one a week of your new system, then let your scorecard pick the next.
Example · illustrative
One week at the cleaning company
The two-person business from lesson 1.1, running everything you've learned:
- Monday, 9:00 sweep. Four new inquiries from the form, texts and Instagram, all in the log. The form ones already got the instant acknowledgement over the weekend.
- Monday, 10:30 window. Two hot leads get prices and dates from saved replies. A warm one gets the qualifying question. An out-of-area one gets the kind no.
- Tuesday, 8:30. The 10-minute pipeline review: two quotes are due for their first follow-up.
- Wednesday. A complaint about a missed time slot matches a takeover signal. Ana calls within the hour; the handover note goes in the log.
- Thursday. A job is marked done; the review request goes out the same afternoon.
- Friday, 3:00. The marketing hour, then the 20-minute review. Median first reply: 50 minutes. Mondays are slow because the weekend piles up, so the decision is a short Sunday-evening sweep.
No part of this week depended on anyone remembering something.
Your exercise · about 30 minutes
Write your one-page operating system
MY OPERATING SYSTEM — [business] — version [date] LEAD CAPTURE Doors: ______ Log: ______ Owner: ______ First-reply target: ______ CONVERSATION Coverage: ______ Windows: ______ Saved replies: ______ Takeover rules: ______ FOLLOW-UP Quiet lead sequence: ______ Quiet quote sequence: ______ PIPELINE Tool: ______ Stages: ______ Daily review at: ______ AUTOMATION 1. ______ (owner / check: ______) 2. ______ (owner / check: ______) MEASUREMENT Scorecard: ______ Weekly review: ______ This week's decision: ______ RHYTHM Daily: sweeps __:__ and __:__ · reply windows · 10-minute pipeline review Weekly: 60-minute marketing hour · 20-minute review · automation checks Monthly: answer bank review · takeover rules review
Capture, answer, follow up, measure — every week, on one page.
Your next action
Run the Scan to confirm which leak to work on first, then give it one full week of your new system.
Saved in this browser only — nothing is sent to us.