Build Your 90-Day Operating Cadence

A transition plan becomes durable when it has a rhythm. Without one, attention moves to whichever issue is loudest. Sales stops when delivery is busy, delivery quality slips when cash pressure rises, and the owner restarts the strategy after every difficult week.

The operating cadence is a repeating sequence:

• Weekly: protect cash, capacity, sales, and quality.
• Monthly: review evidence and make one or two decisions.
• Every 90 days: reassess the customer, offer, model, reserves, and personal constraints.

The cycle is deliberately short enough to learn and long enough to observe real delivery. It replaces perpetual reinvention with controlled adaptation.

The Weekly Operating Review

Choose a fixed thirty-minute period when you can see the records. Use the same agenda every week.

1. Cash: available cash, restricted reserves, expected receipts, overdue invoices, and next commitments.
2. Capacity: committed delivery, review, administration, sales, and recovery hours for the next week.
3. Pipeline: qualified conversations, active proposals, next follow-ups, and start dates.
4. Quality: exceptions, rework, complaints, and unresolved customer approvals.
5. Decision: choose one action that changes the next week.

Do not turn the meeting into a general journal. Record decisions and owners. If you work alone, you are still both operator and reviewer; writing the decision makes the review less subjective.

A weekly dashboard may show:

> Cash is above the floor. Delivery is at 82 percent of protective capacity. One invoice is twelve days late. No sales conversations are scheduled. One source conflict created a correction. Decision: reserve Thursday afternoon for five outreach messages, follow up on the invoice, and add the source owner to the intake checklist.

This is a short operating response with a visible reason.

Monthly Evidence Review

The monthly review looks across several weeks. Ask:

• Did customers pay and repeat?
• Which offers produced contribution after actual time?
• Which customer types created good fit and which created exceptions?
• How much time went to sales, delivery, review, administration, and rework?
• Did quality meet the stated acceptance checks?
• Did any customer become too large a share of cash?
• What changed in the market, tools, law, or customer process?
• Did personal capacity remain sustainable?

Choose no more than three changes for the next month:

1. A demand action, such as contacting a specific buyer group.
2. A delivery action, such as improving an input rule.
3. A financial or resilience action, such as increasing a reserve or collecting overdue invoices.

More than three changes usually means none receives proper attention. If a serious risk exists, it may become the sole change.

The 90-Day Plan

Use a one-page plan with five sections.

Evidence at the start

• Cash floor and current runway.
• Current customer and offer.
• Paid pilots and repeat results.
• Actual hours by activity.
• Quality and payment issues.
• Personal capacity limits.

One primary outcome

Choose a result you control. "Replace lost income" depends on customers and timing. "Complete eight paid diagnostics and deliver three accepted pilots" is observable.

Three bets

Each bet should have an action, owner, evidence, limit, and decision date:

• Demand: contact twenty similar buyers and complete six diagnostics.
• Delivery: test an input gate and reduce rework.
• Economics: raise the offer only after a contribution review.

Stop and protect rules

• Stop sales expansion when committed work exceeds the protective capacity.
• Stop delivery if required access or approval cannot be secured.
• Pause a reinvestment when cash approaches the floor.
• Escalate a privacy or safety issue immediately.

Decision dates

Set the date for the 90-day review before starting. Add a mid-cycle check around day 45. The purpose is to decide from evidence, not to force a successful narrative.

Build the Weekly Sales Floor

When delivery is full, selling feels unnecessary. It is the best time to create the next month's options. Reserve a minimum number of sales actions each week, even if the action is small:

• Five relevant messages.
• Two follow-ups.
• One diagnostic call.
• One referral request after an accepted result.
• One profile or proof update tied to a real customer problem.

Track actions and outcomes separately. Sending messages is activity. A diagnostic conversation with a real buyer is evidence. A paid pilot is stronger evidence. Do not judge the week only by whether someone said yes.

Protect Delivery Quality

Keep the following controls in the weekly rhythm:

• Input gate completed.
• Human reviewer named.
• Material facts checked against source.
• Exceptions logged.
• Customer approval recorded.
• Access reviewed.
• Handoff completed.

If volume rises, increase the review sample before reducing the controls. A quality system that only works during quiet weeks is not a system.

A Worked 90-Day Cycle

The following is an illustrative composite, not a promise of income.

Tariq completed four paid document-cleanup pilots. His 90-day goal is to create a more predictable service without abandoning the judgment that makes the result useful.

At day one, his evidence shows that the core cleanup produces 1,400 in median revenue, takes fourteen hours including review, and has strong acceptance. Sales time is inconsistent, one client creates most exceptions, and the emergency reserve covers only three weeks.

His primary outcome is five paid pilots delivered within fourteen days each, with contribution above his documented floor and no more than one correction cycle per pilot. The demand bet is to contact twenty legal-aid-adjacent organizations that already employ an intake coordinator. The delivery bet is to add a source-owner field and a missing-document stop rule. The money bet is to collect a deposit for new scopes and move 300 of each month's contribution to the reserve.

At day forty-five, he has two paid pilots and six diagnostics. One pilot took eighteen hours because the source owner was unknown. The team adds a scope requirement that a source owner must be named before work starts. The sales message is revised after the first ten contacts because a specific trigger produces better conversations.

At day ninety, he has four paid pilots, two repeat requests, and zero pilots above the correction limit. The reserve now covers five weeks. The primary outcome is not fully met, but the evidence supports continuing. The next cycle narrows the customer group, tests a modest price increase, and raises the reserve target.

This is progress with limits made visible. It is more durable than a plan that can only be called successful if every target is reached.

After a Bad Quarter

Review in this order:

1. Protect customers, data, and required obligations.
2. Establish the next fourteen days of cash and work.
3. Identify whether the problem is demand, delivery, pricing, fit, or capacity.
4. Continue the parts that still produce evidence.
5. Change one major variable, not five.
6. Record why the change was made and when it will be reviewed.

A bad quarter is information. It may show that the customer segment does not buy, the offer is too broad, the price is below the contribution floor, or personal capacity has changed. It does not require the abandonment of every useful part of the business.

Keep the Review Honest

Do not optimize for showing that the plan worked. Record missed targets with the same care as successes. Ask whether the action was completed, whether the intended signal appeared, and what the result means. Distinguish an execution miss from an evidence miss: sending only five of twenty messages is an execution issue, while twenty relevant messages producing no qualified conversations is a demand issue.

If you work alone, share the review with a trusted peer at least once per quarter. They can challenge a story that has become comfortable and notice a capacity or cash risk you have normalized. Do not share customer-identifying information unless necessary and authorized.

Your Chapter Exercise

1. Choose a fixed weekly review time and copy the five-item agenda.
2. Build a monthly evidence review from your current dashboard.
3. Write one 90-day primary outcome that you can observe.
4. Define three bets, each with evidence and a stop condition.
5. Set a weekly sales floor.
6. Set a delivery quality review sample.
7. Choose one resilience action for cash, access, or personal capacity.
8. Schedule the day 45 and day 90 reviews now.

The first cadence does not need perfect metrics. It needs to happen on time, produce a written decision, and remain short enough to repeat. A simple review that survives a busy month is more useful than a detailed planning system that is abandoned in the second week.

At the end of each cycle, preserve the dashboard snapshots, decisions, and reasons. The record shows whether an action was tested or merely discussed. It also gives the next cycle a starting point without reconstructing the past from memory.

Chapter Deliverable

Create a personal operating cadence containing:

• Weekly review date and agenda.
• Dashboard fields.
• Monthly evidence questions.
• One 90-day outcome.
• Three bounded bets.
• Weekly sales floor.
• Quality controls.
• Stop and protect rules.
• Day 45 and day 90 decision dates.

Source and Decision Caution

This chapter is general operating education, not legal, tax, accounting, financial, or health advice. Business obligations, records, contracts, and personal circumstances vary by jurisdiction. Use current official sources and qualified local advice for material decisions.

AI can help summarize approved dashboard data or draft a review prompt, but it must not invent outcomes, approve customer work, or decide whether a risk is acceptable. Verify figures against source records and keep sensitive information inside authorized tools. A calendar does not create judgment; the cadence gives judgment a regular place to happen.

This completes the 32-chapter core sequence. Continue into the Small Business Starter Library for a concrete specialized offer, and use the general guides as the operating foundation whenever a service route creates a new question.