Intern
What you actually do
Day one: write the 90-day theme in one sentence. List what is explicitly out. List three KPIs that fit the offer. Do not build a new funnel this week unless it is the theme. No 'and also brand'.
Library / coaches / Washington DC
Everyone is busy. Nobody owns the next 90 days.
Read it once, then stop negotiating with it. Fractional CMO 90-day sprint for operators in Washington DC is a wiring job: one leak → instrument → weekly ship → handoff. Objects, then edges, then one test conversion. You do not need a new tool to start. You need the first writer to land on one contact this week.
Operators in Washington DC do not have a Fractional CMO 90-day sprint problem because they lack Growth systems. They have it because everyone is busy. Nobody owns the next 90 days.
Wire these objects first: 90-day theme (one), KPI set (offer-fit), weekly ship list, GHL pipeline for the work, meeting note custom fields, handoff doc, owner.
Then these edges, in order: Theme chosen → only matching campaigns/workflows allowed to go live this quarter · Weekly KPI → GA4 or GHL report the team will defend; vanity demoted · Ship item done → note on the opportunity or project contact, not only Slack · Day 90 → handoff doc: objects, logins, sequences that must keep running
Done looks like a test you can repeat: Pick this week's single ship. Log it against the 90-day theme. Monday: read the one KPI aloud. If the KPI needs a story, it is vanity — replace it before you add a channel. Handoff is a document a stranger can run, not a slide.
Start here: One priority sequence for 90 days
Operators in Washington DC already have Growth systems. The leak is not a missing feature. Everyone is busy. Nobody owns the next 90 days. Software did not cause it. A missing write-in did: the person exists in one tool and not in the pipeline.
Here is how you actually wire it. Name the objects: 90-day theme (one), KPI set (offer-fit), weekly ship list, GHL pipeline for the work, meeting note custom fields, handoff doc, owner. Then connect these edges, in order: Theme chosen → only matching campaigns/workflows allowed to go live this quarter · Weekly KPI → GA4 or GHL report the team will defend; vanity demoted · Ship item done → note on the opportunity or project contact, not only Slack · Day 90 → handoff doc: objects, logins, sequences that must keep running. If you skip an edge, the next one is decoration. If you add a Growth systems feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Pick this week's single ship. Log it against the 90-day theme. Monday: read the one KPI aloud. If the KPI needs a story, it is vanity — replace it before you add a channel. Handoff is a document a stranger can run, not a slide. How you know it worked on the board: Theme is 1 / 90 days (if everything is priority, nothing is). If that number is a vibe, do not add traffic.
What to do this week, and only this week: One priority sequence for 90 days An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: write the 90-day theme in one sentence. List what is explicitly out. List three KPIs that fit the offer. Do not build a new funnel this week unless it is the theme. No 'and also brand'.
Operator
You already feel everyone is busy. nobody owns the next 90 days. Everyone is busy. Nobody owns the next 90 days. Protect one sequence for 90 days. The four moves are one leak → instrument → weekly ship → handoff. The edges are Theme chosen → only matching campaigns/workflows allowed to go live this quarter then Weekly KPI → GA4 or GHL report the team will defend; vanity demoted. Ninety days, one leak: demand, conversion, show-up, delivery, or retention. Weekly ship. A scoreboard a human believes. Kill criteria. Handoff notes.
CEO
This is a money leak, not a preference about tools. Everyone is busy. Until theme is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Theme chosen → only matching campaigns/workflows allowed to go live this quarter.
Before
Tuesday. Someone among operators in Washington DC. Everyone is busy. Nobody owns the next 90 days. Growth systems is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases.
After
Same Tuesday, after write-in exists. Ninety days, one leak: demand, conversion, show-up, delivery, or retention. Weekly ship. A scoreboard a human believes. Kill criteria. Handoff notes. Theme chosen → only matching campaigns/workflows allowed to go live this quarter The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in operators in Washington DC already paid for Growth systems. Everyone is busy. Nobody owns the next 90 days. They add a page, a form, a calendar. None of it writes into a spec. By Friday the calendar has ghosts and the pipeline still looks like the snapshot.
The fix is not a better template. Ninety days, one leak: demand, conversion, show-up, delivery, or retention. Prove write-in: Pick this week's single ship. Log it against the 90-day theme. Monday: read the one KPI aloud. If the KPI needs a story, it is vanity — replace it before you add a channel. Handoff is a document a stranger can run, not a slide. This week is one move: One priority sequence for 90 days If that feels too small, that is the point. Operators fail by starting at move four.
The leak
Everyone is busy. The roadmap is annual. Execution is weekly panic. Slide decks substitute for shipping. If nothing can be paused, there is no strategy — only anxiety with a calendar.
The system
Ninety days, one leak: demand, conversion, show-up, delivery, or retention. Weekly ship. A scoreboard a human believes. Kill criteria. Handoff notes.
Pick the leak that costs the most this quarter. Not five. Instrument it if you do not trust the numbers. Pause three projects that do not serve it. That pause is the strategy. The rest is theatre.
Done means a system that runs without you in the room: a spec, a sequence, a Monday number. A longer Notion is not a handoff.
Ninety days, one leak: demand, conversion, show-up, delivery, or retention. Weekly ship. A scoreboard a human believes. Kill criteria. Handoff notes.
Fractional work dies when it is a pile of logins and a busy calendar. Wire a 90-day theme as a constraint on objects: if the theme is show rate, you do not launch a new lead magnet. The CRM still needs a place to put the work — an opportunity or a simple project pipeline with stages that are weeks, not moods. KPIs must fit the offer. Traffic is vanity if the offer is high-ticket applications. Emails sent is vanity if the list is unengaged. Choose numbers a CEO will defend in a meeting without a footnote.
Weekly is the unit. A slide deck is not a system. Each week: one ship, one number, one kill-or-hold. Write the ship on the record (GHL note or a field), not only in Slack, or the next operator inherits folklore. Connect analytics (GA4, GSC) and GHL so the Monday number is not a screenshot from three tools that disagree. If GSC says a page moved and GHL says the form died, that is one problem, not two meetings.
Two databases: the client's 'real' tracker in Notion and the CRM that actually sends. Pick one system of record for status. Handoff is the last wire: named objects, which workflow is sacred, which calendar is truth, who owns replies. If handoff is 'I'll stay on Slack', you built a dependency, not a sprint. Interns can run the weekly list. CEOs protect the theme from a second priority. That is the whole job.
90-day theme (one), KPI set (offer-fit), weekly ship list, GHL pipeline for the work, meeting note custom fields, handoff doc, owner.
Theme chosen → only matching campaigns/workflows allowed to go live this quarter
Weekly KPI → GA4 or GHL report the team will defend; vanity demoted
Ship item done → note on the opportunity or project contact, not only Slack
Day 90 → handoff doc: objects, logins, sequences that must keep running
Pick this week's single ship. Log it against the 90-day theme. Monday: read the one KPI aloud. If the KPI needs a story, it is vanity — replace it before you add a channel. Handoff is a document a stranger can run, not a slide.
Day one: write the 90-day theme in one sentence. List what is explicitly out. List three KPIs that fit the offer. Do not build a new funnel this week unless it is the theme. No 'and also brand'.
Name it. Demand, conversion, show-up, delivery, or retention.
If the number is folklore, fix measurement in week one.
Something live every week. Decks do not count.
Spec + sequence + scoreboard. You should be optional by day 90.
On one line, for operators in Washington DC: Everyone is busy. Nobody owns the next 90 days. Add who gets hurt (calendar, cash, inbox, or reputation). If two people write different sentences, you do not agree yet — stop and agree.
Why: Teams skip this and jump into settings. Then every person is fixing a different problem with the same login.
Done when: One sentence. Shared. No adjectives required.
90-day theme (one), KPI set (offer-fit), weekly ship list, GHL pipeline for the work, meeting note custom fields, handoff doc, owner.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Name it. Demand, conversion, show-up, delivery, or retention. Then wire: Theme chosen → only matching campaigns/workflows allowed to go live this quarter
Why: Operators in Washington DC cannot skip this edge. Fractional work dies when it is a pile of logins and a busy calendar. If it is not true, Growth systems is already a second database.
Done when: Theme chosen → only matching campaigns/workflows allowed to go live this quarter is true on a test.
If the number is folklore, fix measurement in week one. Then wire: Weekly KPI → GA4 or GHL report the team will defend; vanity demoted
Why: Operators in Washington DC skip this and the leak returns as a private language. Weekly is the unit. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Weekly KPI → GA4 or GHL report the team will defend; vanity demoted is true on a test.
Something live every week. Decks do not count. Then wire: Ship item done → note on the opportunity or project contact, not only Slack
Why: Operators in Washington DC feel this as Everyone is busy. Nobody owns the next 90 days. Two databases: the client's 'real' tracker in Notion and the CRM that actually sends.
Done when: Ship item done → note on the opportunity or project contact, not only Slack is true on a test.
Pick this week's single ship. Log it against the 90-day theme. Monday: read the one KPI aloud. If the KPI needs a story, it is vanity — replace it before you add a channel. Handoff is a document a stranger can run, not a slide.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Theme (If everything is priority, nothing is), then ship (A live change, not a slide). Write one action or write “hold.” A dashboard with no action is theatre.
Why: What gets reviewed gets run. What only lives in a tool gets ignored the week someone is busy.
Done when: Three numbers. One owner. Fifteen minutes. Actions attach.
One priority sequence for 90 days
Why: Operators fail by starting at move four. Interns fail by making a 40-item checklist. CEOs fail by adding a second priority. One proven write-in beats an elegant plan.
Done when: The move is true, or you can name the blocker in one sentence.
90-day theme (one), KPI set (offer-fit), weekly ship list, GHL pipeline for the work, meeting note custom fields, handoff doc, owner.
If objects aren't named, software invents a second database.
Everyone is busy. Nobody owns the next 90 days.
Name it. Demand, conversion, show-up, delivery, or retention. Then wire: Theme chosen → only matching campaigns/workflows allowed to go live this quarter
Operators in Washington DC cannot skip this edge. Fractional work dies when it is a pile of logins and a busy calendar. If it is not true, Growth systems is already a second database.
On Growth systems, this means the data model matches how operators in Washington DC actually work — not the snapshot demo. Edge: Weekly KPI → GA4 or GHL report the team will defend; vanity demoted
If the number is folklore, fix measurement in week one. Then wire: Weekly KPI → GA4 or GHL report the team will defend; vanity demoted
Operators in Washington DC skip this and the leak returns as a private language. Weekly is the unit. Spec tags, fields, and states have to be the same objects the next workflow will read.
Ninety days, one leak: demand, conversion, show-up, delivery, or retention. Weekly ship. A scoreboard a human believes. Kill criteria. Handoff notes.
Something live every week. Decks do not count. Then wire: Ship item done → note on the opportunity or project contact, not only Slack
Operators in Washington DC feel this as Everyone is busy. Nobody owns the next 90 days. Two databases: the client's 'real' tracker in Notion and the CRM that actually sends.
One priority sequence for 90 days
Because the login already exists. Everyone is busy. The roadmap is annual. A new feature on a missing spec is a second database. Finish this edge first: Theme chosen → only matching campaigns/workflows allowed to go live this quarter.
Day one: write the 90-day theme in one sentence. List what is explicitly out. List three KPIs that fit the offer. Do not build a new funnel this week unless it is the theme. No 'and also brand'. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Pick this week's single ship. Log it against the 90-day theme. Monday: read the one KPI aloud. If the KPI needs a story, it is vanity — replace it before you add a channel. Handoff is a document a stranger can run, not a slide. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
If it is only in someone's head, a new hire needs a story, reporting cannot be defended, and automations fire on folklore. Writing is how two people mean the same object on Monday.
Because setup was a project, not a review. Kill list (What you will not do this quarter) is how you stop the leak returning dressed as a new feature. Pick the leak that costs the most. Instrument it if you do not trust the numbers. Pause three projects that do not serve it. Done means a system that runs without you in the room — not a longer Notion.
More leads into a leak is a more expensive leak. Ninety days, one leak: demand, conversion, show-up, delivery, or retention. Weekly ship. A scoreboard a human believes. Kill criteria. Handoff notes. Watch theme before you buy traffic. If that number is folklore, acquisition is a vanity spend.
Then you only have time for the objects page and one test conversion. One priority sequence for 90 days That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because Growth systems is “set up”.
Do this
90-day theme (one), KPI set (offer-fit), weekly ship list, GHL pipeline for the work, meeting note custom fields, handoff doc, owner.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Theme chosen → only matching campaigns/workflows allowed to go live this quarter
Skip this
Calling it done because a screenshot looks busy.
Do this
Pick this week's single ship. Log it against the 90-day theme. Monday: read the one KPI aloud. If the KPI needs a story, it is vanity — replace it before you add a channel. Handoff is a document a stranger can run, not a slide.
Skip this
Leaving “Handoff” to chance.
Do this
Spec + sequence + scoreboard. You should be optional by day 90.
The usual miss
Calling Growth systems “set up” because someone logged in and imported a snapshot.
Do this instead
Name it. Demand, conversion, show-up, delivery, or retention. Then prove write-in: Pick this week's single ship.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Theme chosen → only matching campaigns/workflows allowed to go live this quarter first. Automations on a missing writer invent a second database.
The usual miss
Adding a page, form, flow, or campaign every time last week hurt.
Do this instead
Name which edge is missing. Fix that edge. Hurt is usually a skipped write-in, not a missing asset.
The usual miss
Reporting that nobody will defend in a meeting — screenshots, vanity opens, 'interested' counts.
Do this instead
Theme: 1 / 90 days. If everything is priority, nothing is. If you cannot say it out loud, it is not a scoreboard.
The usual miss
Hiring or retaining an agency to invent the spec while also running the calendar.
Do this instead
Hands on a known sequence are useful. Hands inside a missing spec pick the louder job (the calendar) and the leak stays.
Theme
1 / 90 days
If everything is priority, nothing is
Ship
Weekly
A live change, not a slide
Kill list
Written
What you will not do this quarter
This week
One priority sequence for 90 days
Washington DC · Mid-Atlantic. Remote-first. The examples follow the city; the spine does not.
One priority sequence for 90 days
KPIs fit the offer, not vanity
Work is weekly, not a slide deck
Handoff is documented
Want the longer lesson, not the page for this niche? Ninety days, one leak ↗
Working notes
Pick the one sequence that deserves the next 90 days. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Operators in Washington DC do not have a Fractional CMO 90-day sprint problem because they lack Growth systems. They have it because everyone is busy. Nobody owns the next 90 days. Wire these objects first: 90-day theme (one), KPI set (offer-fit), weekly ship list, GHL pipeline for the work, meeting note custom fields, handoff doc, owner. Then these edges, in order: Theme chosen → only matching campaigns/workflows allowed to go live this quarter · Weekly KPI → GA4 or GHL report the team will defend; vanity demoted · Ship item done → note on the opportunity or project contact, not only Slack · Day 90 → handoff doc: objects, logins, sequences that must keep running Done looks like a test you can repeat: Pick this week's single ship. Log it against the 90-day theme. Monday: read the one KPI aloud. If the KPI needs a story, it is vanity — replace it before you add a channel. Handoff is a document a stranger can run, not a slide. Start here: One priority sequence for 90 days
Yes. Remote-first, US-friendly hours. Washington DC is how people search — not a storefront.
Examples, timing, and scheduling. The spine does not get rewritten for every skyline: one leak → instrument → weekly ship → handoff.
Before: Tuesday. Someone among operators in Washington DC. Everyone is busy. Nobody owns the next 90 days. Growth systems is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases. After: Same Tuesday, after write-in exists. Ninety days, one leak: demand, conversion, show-up, delivery, or retention. Weekly ship. A scoreboard a human believes. Kill criteria. Handoff notes. Theme chosen → only matching campaigns/workflows allowed to go live this quarter The next move is written. That is the difference between a login and a system.
One priority sequence for 90 days
Because the login already exists. Everyone is busy. The roadmap is annual. A new feature on a missing spec is a second database. Finish this edge first: Theme chosen → only matching campaigns/workflows allowed to go live this quarter.
Day one: write the 90-day theme in one sentence. List what is explicitly out. List three KPIs that fit the offer. Do not build a new funnel this week unless it is the theme. No 'and also brand'. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Pick this week's single ship. Log it against the 90-day theme. Monday: read the one KPI aloud. If the KPI needs a story, it is vanity — replace it before you add a channel. Handoff is a document a stranger can run, not a slide. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
The CRM is open. The operating system is not.
Read ↗Booked calls leak because the CRM never saw them.
Read ↗Traffic hits a page. The journey after that is improvised.
Read ↗Broadcasts exist. A sequence that earns the next conversation does not.
Read ↗Outbound is a tool. The pipeline is a vibe.
Read ↗Email and WhatsApp stay open. A call is for installing the system.