01.04
Run the business on a one-page operating process
Name an owner for every stage, set a weekly rhythm (daily blocks, a 30-minute Monday pipeline meeting, a Friday scorecard), and write it on one page your team can follow without you.
Video walkthrough
- Why systems fail without an owner and a meeting
- Owners per stage: one name each, even on a two-person team
- The weekly rhythm: daily blocks, Monday pipeline meeting, Friday scorecard
- The Monday agenda in 30 minutes, minute by minute
- Changing one thing at a time and writing it down
What you're building
A single page that says who owns each stage, what happens every day and every week, which numbers you review, and what you are changing this month. It is the document a new assistant reads on day one, and the one you review in every Monday meeting.
Why it matters
Automations and Smart Lists do not run a business; people working them on a schedule do. When every stage has one owner, a stuck lead has someone to ask. When there is a fixed weekly meeting, the scorecard actually gets read and the constraint from chapter 1 actually gets fixed.
What you need
- Your constraint statement (chapter 1), audit worksheet (chapter 2) and metric definitions (chapter 3).
- The names of everyone who touches leads or clients, including part-time help and your transaction coordinator.
- The one-page template below.
Time and cost
- Time
- 35 minutes to write; 30 minutes every Monday to run
- Cost
- $0
Step by step
Assign one owner per stage
Use the stages from Part 03, chapter 1. One name per stage, the person accountable that nothing sits there too long. On a solo business several stages are yours; write it anyway, and name who covers when you are away.
Example owners (fictional team: Dana Reyes, lead agent; Sam Ortiz, buyer agent; Priya Nair, assistant). Stage Owner Done means Backup New Lead / Attempting Contact Assigned agent Lists 1 and 2 at zero each block; cadence followed Dana Contacted Assigned agent Every contacted lead has a dated next step Dana Appointment Set / Held Assigned agent Confirmations sent, outcome marked same day Priya (confirmations) Signed / Under Contract Dana Weekly client update; deal record current Transaction coordinator Closed / past clients Priya Quarterly touch, anniversary and referral asks logged Dana Nurture Assigned agent List 6 worked weekly Priya Data quality Priya Zero unassigned leads; sources set; opt-outs recorded Dana Check: Every stage has exactly one owner and one backup, and each owner has agreed to it.
Set the daily rhythm
Two follow-up blocks a day on every agent's calendar (for example 9:00 to 9:45am and 4:30 to 5:15pm), worked in the priority order from Part 03, chapter 7. During working hours, the new-lead alert beats everything except a client appointment.
Check: The blocks are on each agent's calendar as recurring, busy events.
Run a 30-minute Monday pipeline meeting
Same time every week, same agenda, cameras on or in person. Use the agenda template below. The meeting reviews numbers and stuck leads; it does not re-discuss definitions or tools. Decisions get written in the operating page's 'changes' log.
Check: The meeting is on the calendar for the next 12 weeks with the agenda in the invite.
Fill the scorecard every Friday
The data-quality owner fills the weekly scorecard from chapter 3 on Friday afternoon (15 to 30 minutes), so Monday's meeting starts with numbers instead of opinions. Same filters, same report settings, every week.
Check: Four consecutive Friday rows exist before you judge any change.
Write the one page and post it
Fill the template: constraint, owners, rhythm, numbers with targets, rules that never change (consent, opt-outs, quiet hours), and the change log. Keep it to one page. Pin it in your team chat and link it from the CRM (for example in a pinned note or the team's shared drive).
Check: A new team member could read it in five minutes and know what to do tomorrow morning.
What success looks like
- One page, posted, with an owner for every stage.
- Monday meeting held four weeks in a row with notes.
- A change log with one dated change and its result after four weeks.
Copyable templates
# Pipeline meeting, {date}
1. (5 min) Scorecard: new leads, speed to lead, contact rate, appointments held, GCI month to date. Compare with target and last 4 weeks.
2. (5 min) The constraint: did this month's one change move its number? Keep, adjust or stop (decide at week 4).
3. (10 min) Stuck leads: open Smart Lists 4 and 5. Each owner names the next step and date for anything older than its rule.
4. (5 min) Appointments this week: who is booked, who needs confirming, any no-shows to recover.
5. (5 min) Data and compliance: unassigned leads (must be 0), opt-out requests logged, sources missing.
Decisions (write in the change log): ______Try it
Every day
Two follow-up blocks
Replies and new leads first, then today's tasks and appointments. Done when lists 1 and 2 are at zero.
Monday
30-minute pipeline meeting
Scorecard, the constraint, stuck leads, this week's appointments, data and compliance.
Friday
Scorecard filled
Same reports, same filters, by the data-quality owner.
Monthly
One change
Re-run the constraint finder. Keep, adjust or stop last month's change. Pick at most one new one.
How to test it
- Hand the page to someone who was not in the room. Ask them who owns a lead that booked and then no-showed. They should answer from the page.
- After four Mondays, check the change log has entries and the scorecard has four rows.
Troubleshooting
The Monday meeting turns into a 90-minute discussion.
Keep the timed agenda and move any tool or definition debate to a separate 15-minute slot later in the week.
Nobody fills the scorecard.
It needs one named owner and a calendar block on Friday. If that person is you, block it before anything else.
We keep changing three things at once.
The change log allows one active change per month. Anything else goes on a 'next' list.
Advanced technical details
Optional. You can follow every step above without these.
Technical detailsMaking the page enforceable in the CRM
Each line of the page should map to something the CRM shows: owners to assignment rules (Part 03, chapter 3), daily blocks to Smart Lists and tasks (chapters 4 and 7), the scorecard to reports (chapter 9), fixed rules to DND, opt-out handling and quiet-hour settings (chapter 2). If a rule on the page has no CRM signal, either find one or accept that it depends on habit and review it in the meeting.