## 1. Why This Keeps Stalling **Assumption:** The deadline is **30 November 2026**, and because your conversion data is unavailable, the system assumes roughly **one signed retainer for every four qualified sales conversations**. | Failure point | What sets it off | Structural cause | Cost of leaving it | | ----------------------------------------------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------- | | Revenue work disappears after the initial push | One or two client emergencies consume the time reserved for sales | Sales has no protected capacity, displacement rule, or recovery trigger; client delivery automatically wins every conflict | You repeatedly lose several selling cycles, leaving the final month responsible for an unrealistic share of the target | | Activity happens without a durable next action | You send messages, hold calls, or prepare proposals, then return to delivery work | Pipeline ownership exists informally in your head rather than through one dated, visible commitment per opportunity | Interested prospects cool, proposals remain open, and follow-ups depend on memory | | The contractors reduce workload but do not protect growth | Emergencies arrive directly with you, regardless of who could triage or resolve them | Delivery escalation and sales support responsibilities are not explicitly assigned | Your highest-leverage work remains the easiest work to interrupt | | Weekly review becomes retrospective rather than operational | Friday arrives after a disrupted week | The review identifies what happened but does not produce protected calendar commitments and named artifacts for the next cycle | The same failure is observed repeatedly without changing the following week | **Reported problem:** Client emergencies take over after two weeks, and you never return to business development. **Actual mechanism:** Revenue work is treated as discretionary capacity. It has no minimum weekly allocation, no rule governing when client work may displace it, and no automatic recovery action after displacement. The system therefore converts every urgent delivery event into an indefinite suspension of the goal. --- ## 2. The System **Design principle:** Run one small, non-negotiable revenue cycle each week: select the few opportunities that can move, assign one verifiable next artifact to each, protect the execution time, and recover missed work without expanding the next cycle. **Single progress signal:** **Signed-and-paid retainer clients: X/12.** **Overhead per cycle:** **30 minutes**: 20 minutes for the Friday review and no more than 10 minutes updating Notion and Calendar. Prospecting, calls, and proposals are execution work rather than system overhead. | Component | What it does | Where it lives | Time cost | | ------------------------ | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------------------- | --------------------------- | | Retainer scoreboard | Holds every active opportunity, its current stage, one next artifact, owner, and due date | One Notion database view | 5–10 minutes weekly | | Protected revenue blocks | Reserves two execution periods that client work cannot silently consume | Google Calendar | Two 60-minute blocks weekly | | Weekly commitment post | Makes the cycle’s commitments visible to both contractors and records any displacement | One dedicated Slack channel or existing agency channel | 2 minutes weekly | | Emergency triage rule | Prevents every urgent request from escalating directly to you | Pinned Notion procedure and Slack channel topic | No recurring administration | | Paper capture rule | Prevents prospect details and follow-ups from remaining only in your notebook | Paper notebook during the day; transferred to Notion before Friday review | 5 minutes weekly | Use only these Notion fields: | Field | Required content | | ------------- | ---------------------------------------------------------------------------------------- | | Prospect | Company or decision-maker | | Stage | Target, contacted, qualified conversation, proposal, verbal yes, signed-and-paid, closed | | Owner | Agency Principal, Pipeline Contractor, or Delivery Contractor | | Next artifact | One externally verifiable output or event | | Due date | A real date inside the current cycle | | Blocker | Blank unless action from another person is required | | Last movement | Date the opportunity last changed stage | Your two recurring revenue blocks are: * **Tuesday morning: 60 minutes** for outreach, follow-ups, and booking qualified conversations. * **Thursday morning: 60 minutes** for proposals, commercial decisions, and closing actions. Each block may be moved **once**, but only to another slot within the same calendar week. It may not be deleted. When moved, you record the replacement time immediately. Use the contractors as follows: | Role | Primary responsibility | Fallback responsibility | | ---------------------- | -------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | | Agency Principal — you | Qualified sales conversations, offers, pricing, proposals, and closing | If unavailable for more than three working days, the Pipeline Contractor schedules follow-ups and preserves next actions; they do not negotiate terms | | Pipeline Contractor | Prospect research, CRM hygiene in Notion, drafting outreach, scheduling, and chasing missing information | Delivery Contractor updates due dates and flags stalled prospects | | Delivery Contractor | First-line triage of client emergencies and identification of what genuinely requires you | Pipeline Contractor acknowledges the client and schedules your intervention | **Defence against urgent work:** A client issue may displace a revenue block only when it creates an immediate risk to live delivery, client data, contractual deadlines, or material revenue. The Delivery Contractor triages first. Routine revisions, status questions, and internally created urgency wait until after the protected block. A displaced block must be rebooked within 48 hours, not added on top of the following week. --- ## 3. What You Stop Doing | Dropped or downgraded | Why it competes | What it frees | | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------- | | Same-day responses to non-critical client requests | It trains clients to treat every request as urgent and fragments the time required for commercial work | Two uninterrupted revenue blocks each week | | Fully custom proposals before commercial fit is confirmed | You spend proposal time on prospects who have not agreed on problem, scope, authority, timing, or budget range | Closing capacity for qualified opportunities | | Joining every delivery escalation immediately | It bypasses contractor triage and makes you the default owner of all ambiguity | Principal attention for sales conversations and decisions | | Unscheduled internal polishing, documentation, and process cleanup | These tasks feel productive but have no deadline tied to client risk or the retainer target | A defined overflow window for prospect follow-ups | | Maintaining prospect information in both Notion and the paper notebook | Duplicate systems create incomplete records and make follow-up dependent on whichever source you remember to check | One reliable pipeline record | Nothing else gets added to the system unless an existing activity is removed. Refusing to downgrade client responsiveness or internal polishing would preserve the condition that currently stalls the goal. --- ## 4. Checkpoints and Commitments To sign 12 retainers, plan for approximately **48 qualified sales conversations** before the deadline. Across 17 weekly cycles, that requires an average of roughly **three qualified conversations per week**. If your actual close rate is lower than 25%, reduce the market segment or offer complexity before increasing the system’s administrative load. | Checkpoint | Date | Owner | Concrete commitment | Done looks like | | ---------------------------- | ---------------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- | | Operating baseline installed | 7 August 2026 | Agency Principal — you; fallback: Pipeline Contractor | Publish the Notion scoreboard, enter every current opportunity, and place recurring Tuesday, Thursday, and Friday blocks in Google Calendar | Notion contains no active prospect without an owner, next artifact, and due date; recurring blocks are visible in Calendar | | First commercial proof | 4 September 2026 | Agency Principal — you; fallback: Pipeline Contractor for follow-up administration | Reach **3 signed-and-paid retainers** and complete at least **12 qualified sales conversations** cumulatively | Three signed agreements and evidence that the first invoice or retainer payment has been received | | Midpoint | 2 October 2026 | Agency Principal — you; fallback: Pipeline Contractor for pipeline continuity | Reach **6 signed-and-paid retainers** and at least **24 qualified sales conversations** cumulatively | Six signed agreements with payment evidence; every open proposal has a dated decision event | | Closing position | 30 October 2026 | Agency Principal — you; fallback: Delivery Contractor for emergency shielding | Reach **9 signed-and-paid retainers**, with at least six additional qualified opportunities scheduled for a decision before 20 November | Nine paid retainers and six prospects in proposal, verbal-yes, or scheduled decision stages | | Final target | 30 November 2026 | Agency Principal — you; fallback: Pipeline Contractor preserves follow-ups during any absence | Reach **12 signed-and-paid retainers** | Twelve executed agreements and twelve initial retainer payments received | For each weekly cycle, you commit to no more than: * **Three qualified sales conversations completed or firmly scheduled.** * **Three prospect-specific next artifacts delivered.** * **One closing action on every open proposal.** Examples of qualifying artifacts include: * Outreach sequence sent to a named prospect list. * Qualified sales conversation completed. * Proposal sent. * Commercial objection answered in writing. * Decision meeting held. * Contract sent for signature. * Signed agreement received. * Initial retainer invoice paid. “Work on outreach,” “follow up,” and “make progress on the proposal” do not qualify. --- ## 5. The Review Session **Length:** 20 minutes · **Runs on:** Friday morning · **Evidence pulled from:** Notion stage changes, signed agreements, payment records, Calendar activity, and the weekly Slack commitment post | Minutes | Agenda item | What actually happens | | ------- | ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- | | 0–3 | Read the signal | Record the current number of signed-and-paid retainers. Do not discuss effort before recording the number | | 3–7 | Verify the completed artifacts | Mark commitments complete only when the linked message, meeting, proposal, agreement, or payment evidence exists | | 7–12 | Diagnose displacement | Identify which commitment moved or failed, what displaced it, whether the emergency met the triage rule, and who owned recovery | | 12–17 | Select the next cycle | Choose no more than three opportunities that can materially change stage; assign one next artifact, one owner, and one due date to each | | 17–20 | Defend execution | Confirm the two revenue blocks, remove conflicts, and post the commitments in Slack | The Friday Slack post uses this format: > **Signal:** X/12 signed-and-paid retainers > **Completed this cycle:** [linked artifacts] > **Missed:** [artifact and reason] > **Next cycle commitments:** [artifact — owner — due date] > **Protected blocks:** [Tuesday time] and [Thursday time] **Closing question every session:** Which specific commitment is most likely to be displaced next week, and what will absorb the interruption instead? --- ## 6. Drift and Recovery | Stage | What you will notice | What you do | Act within | | ------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------- | | Early drift | A revenue block is moved, a prospect lacks a dated next artifact, or no pipeline artifact exists by Wednesday afternoon | Rebook the block within the same week and have the Pipeline Contractor prepare the smallest executable next artifact before the replacement slot | Same working day | | One missed commitment | A promised outreach, call, proposal, or decision event did not occur by its due date | Do not add it to the next cycle automatically. Decide whether to complete, delegate, shrink, or kill it; then assign a new date only if it remains one of the cycle’s three priorities | During the Friday review | | Two consecutive misses | The same opportunity or type of action misses twice | Remove custom work, reduce the action to its smallest external artifact, and assign preparation to the Pipeline Contractor. You retain only the decision or conversation that requires principal authority | Within one working day | | A full silent cycle | No qualified conversation, proposal, closing event, or signed client occurs during the week | Activate a recovery cycle: keep the next week’s target at three artifacts, cancel one non-critical internal commitment, and use the first protected block exclusively to restart conversations with the five warmest prospects | By the next Tuesday block | | Two full silent cycles | No material pipeline movement for two consecutive weeks | Cut the active acquisition scope to one segment, one retainer offer, and one outreach message. Stop serving secondary segments until one new retainer signs | At the second Friday review | | Behind checkpoint by three or more clients | The signed-client signal is at least three below the checkpoint target | Remove low-probability opportunities, concentrate on prospects able to decide before the next checkpoint, and reduce offer customization. Do not increase the number of weekly meetings or reviews | Within one cycle | **Never do this when recovering:** Do not restart the plan, create a larger backlog, double the next week’s target, or schedule “catch-up” work. Preserve the normal cycle size and remove competing work instead. --- ## 7. How the System Evolves **Scale up after:** **Three consecutive completed cycles** in which all three weekly artifacts are delivered → increase the execution capacity from two 60-minute revenue blocks to one 60-minute and one 90-minute block, while keeping the Friday review at 20 minutes. **Simplify after:** **Two consecutive cycles** in which maintaining the Notion pipeline takes more than 10 minutes → archive all fields, views, and notes except stage, owner, next artifact, due date, blocker, and last movement. **Increase contractor ownership after:** **Four completed cycles** with accurate pipeline updates → let the Pipeline Contractor select and prepare the initial prospect list for each cycle; you approve or replace it during the Friday review. **Reduce active pipeline after:** **Two consecutive cycles** with more than 15 opportunities lacking movement → archive every prospect without a credible decision path inside 30 days and cap the active view at 15 opportunities. **Recalculate the funnel after:** **Six completed cycles** → replace the assumed 25% close rate with your actual qualified-conversation-to-paid-retainer conversion rate and adjust the remaining conversation requirement. **Kill the goal deliberately if:** After **eight completed cycles**, you have fewer than two signed-and-paid retainers and fewer than eight qualified sales conversations despite protecting the scheduled blocks. At that point, the acquisition approach or retainer offer lacks sufficient evidence. Close the initiative, document the result, and replace it with a narrower commercial test rather than continuing an unsupported target. --- ## 8. Set It Up in the Next 48 Hours 1. Create one Notion database called **Retainer Scoreboard** with the seven required fields, enter every current opportunity, and archive anything with no credible next action. 2. Put recurring **Tuesday and Thursday 60-minute revenue blocks** and the **Friday 20-minute review** into Google Calendar through 27 November 2026. Mark the revenue blocks as busy. 3. Assign one contractor as **Pipeline Contractor** and the other as **Delivery Contractor**. Publish the emergency triage and fallback responsibilities in Notion and pin the link in Slack. 4. Post the first Slack commitment with the current signed-client signal, three prospect artifacts due before 7 August, their owners, and the protected execution times. **If you only do one thing:** Put the two recurring revenue blocks in Google Calendar and apply the rule that each may be moved once within the same week but never deleted.