What should a founder level GTM decision memo include each week?
A short operating document that forces budget decisions
By Janis Plume, Founder, Outbound Pros · 8 min read · 2026-11-03
Quick answer
A founder level GTM decision memo should be a one page operating brief with five parts: what changed, what matters, what decision is required, who owns the next move, and what risk can break the model. It should use kill, iterate, hold, and scale gates, not broad commentary. If a memo cannot tell you whether a channel, segment, or campaign deserves more budget, less budget, or no decision yet, it is not a decision memo.
Why does a founder need a decision memo instead of another dashboard?
Because most weekly GTM reporting is descriptive, not operational. It tells you what happened, but not what to do next. Founders do not need another pile of activity counts. They need a compact document that turns signal into action while there is still time to change spend, sequencing, ownership, or focus.
The weekly memo exists to answer a small set of hard questions. Did anything clear a scale gate. Did anything trip a kill gate. Is the team still inside a valid test window. Did operations break the interpretation of the numbers. If you cannot answer those questions clearly, the business will drift into soft optimism.
That drift gets expensive fast. Teams keep sending because volume feels productive. Meetings get counted before they show. Segments get blended together until weak performance hides behind one decent pocket of signal. Founders then approve budget based on motion, not evidence.
If your review process is already too wide, read this breakdown on standardizing the weekly GTM decision memo. If your issue is bad signal selection, this piece on separating signal metrics from activity metrics is the right companion.
What sections should the weekly memo include?
Keep it tight. A founder memo should usually fit on one screen or one printed page before appendices. The goal is to compress decision quality, not to prove how much work happened.
- This week's decision summary, one line per decision needed
- Signal snapshot by channel, segment, or campaign
- Interpretation, what the numbers mean and what they do not mean
- Operational blockers that can invalidate the signal
- Budget or capacity recommendation
- Named owners and next review date
That first section matters most. Start with the decision, not the narrative. For example, hold budget steady, keep Segment A in iterate, kill Segment B, delay Channel 2 expansion, or scale only after show rate discipline is fixed. If a reader has ten seconds, they should still know the call.
After that, show only the metrics that support the decision. On Allbound Pros we care about arithmetic that changes resource allocation. That means positive signal, meeting quality, show rate, sales cycle implications, operational lag, and whether the test is mature enough to trust.
A practical memo structure
- Decision required: the specific budget or motion decision needed this week
- Evidence: the minimum numbers needed to justify the call
- Confidence: high, medium, or low based on data quality and operating consistency
- Failure mode: what could make the conclusion wrong
- Next move: exact action, owner, and next review point
Which metrics actually deserve space in the memo?
Use metrics that map to founder level choices. Most weekly GTM memos get bloated because they include metrics that feel useful but do not support a decision. Opens, raw activity, and blended totals often belong in execution reviews, not founder memos.
A better filter is simple. Include a metric only if it can change budget, pacing, segment priority, or operating design this week.
| Memo item | Why it belongs |
|---|---|
| Positive signal against gate thresholds | Determines kill, iterate, scale, or pour status |
| Meeting quality by source | Prevents false confidence from weak booked volume |
| Show rate health | Protects pipeline math when calendar discipline is broken |
| Segment level variance | Stops blended reporting from hiding weak pockets |
| Warm up or onboarding status | Shows whether poor output is performance or expected ramp delay |
| Operational blockers | Flags when ownership or handoff issues make numbers misleading |
There are a few verified figures worth using when they genuinely fit. If positive signal on sends is under 0.5%, that is a kill. From 0.5 to 1% is iterate. At 1% or more, you can scale. At 2% or more, you can pour. Those thresholds belong in the memo because they convert messy weekly updates into direct action.
Another one matters more than many teams admit. Where calendar discipline is broken, booked meetings die at roughly a 50% show rate. That means a memo should never present booked meetings as clean evidence when scheduling, rescheduling, reminders, or rep attendance are unreliable. In those cases, the booked number is a weak intermediate signal, not the outcome.
Ramp timing also belongs in the memo. Onboarding takes about 21 days, and warm up takes 4 to 6 weeks. If a founder approves or kills a motion before those constraints are acknowledged, they are often judging implementation lag as if it were channel quality. The memo should state clearly whether the system is still inside an expected ramp window.
How should the memo frame decisions, not just results?
Most teams bury the real call in paragraph four. Do the opposite. Every section should point toward a decision class. Not everything needs a dramatic yes or no. Good operators are comfortable with hold and wait when the conditions for interpretation are not yet stable.
- Kill: signal is below threshold or quality is clearly invalid
- Iterate: early signal exists but message, targeting, or process still needs work
- Hold: no new decision because the test window is incomplete or data quality is weak
- Scale: signal has cleared the threshold and operations can absorb more volume
- Pour: unusually strong signal and stable operations justify aggressive expansion
Founders also need the memo to explain the trade off. A channel can clear a scale threshold and still be the wrong place to add budget if onboarding drag, handoff risk, or review complexity is rising. A segment can look mediocre on volume and still deserve protection if it produces cleaner downstream quality.
That is why the memo should separate signal from capacity. One tells you whether the market is responding. The other tells you whether your operating system can convert that response into pipeline. If either side is weak, the recommendation changes.
What a founder should read in under a minute
- What changed materially this week
- What decision is requested now
- Why the recommendation is justified
- What risk could reverse the conclusion
- What happens before next week's review
What should stay out of the weekly memo?
Execution detail that does not alter a founder level decision. That includes long campaign notes, every test variant, generic CRM exports, and vanity snapshots of total activity. Those belong with operators. The founder memo should be thinner and sharper.
Also keep channel execution tutorials out of it. The mechanics of writing sequences, LinkedIn steps, or multichannel orchestration are better covered by sibling properties. If you need deep execution guidance, that belongs elsewhere in the Outbound Pros group. Here, the job is to decide whether the motion deserves continuation, revision, or expansion.
Avoid blended rates that flatten important differences. A decent aggregate can hide a failing segment. A reply spike can distract from weak quality. A booked meeting count can flatter a system with poor attendance. If the number makes the business look smoother than it really is, it probably does not belong in the top section of the memo.
Where does this advice fail?
It fails when the company is too early to have stable definitions. If sales, revops, and prospecting disagree on what counts as a meeting, a positive, a qualified conversation, or a pipeline contribution, the memo becomes theatre. In that case, define terms first. Reporting discipline comes before memo elegance.
It also fails in very small data windows where weekly movement is mostly noise. Some founder teams force a decision every Friday because cadence feels disciplined. That can produce fake certainty. Sometimes the right weekly memo says no decision, keep the test running, and fix the instrumentation.
This approach is also not for leaders who want a broad company narrative document. A board style summary and a founder GTM decision memo are different tools. The memo is for operating choices. It should feel a little uncomfortable because it forces trade offs.
And one disclosure, because comparison and operating advice should be honest. We run managed outbound under Outbound Pros, so we are not neutral. The reason this is still worth reading is that the memo format here is designed to make weak performance harder to hide, including in work we would be responsible for ourselves.
If you want an external operator view on your current review system, see the GTM audit tool.
Common questions
How long should a founder weekly GTM memo be?
Usually one page before appendices. If it takes too long to read, it will not drive a decision. If it is too short to show evidence, it becomes opinion.
Should the memo include booked meetings every week?
Yes, but only with context. If calendar discipline is weak, booked meetings are not reliable proof of pipeline health because roughly half may fail to show.
Should I include reply rate in the memo?
Include reply context carefully, but anchor decisions to positive signal, meeting quality, and downstream validity. A reply increase can still mislead if the quality worsens.
When should the memo recommend scaling?
When signal has cleared your scale gate and operations can absorb more volume without breaking handoffs, meeting quality, or review discipline. A good number alone is not enough.
Who should own the memo each week?
One operator should compile it, but every line item needs a named owner for the next action. Shared accountability usually means no accountability.
Last updated: 2026-11-03
Talk through your pipeline math
before you spend the budget
30 minutes on your funnel arithmetic. We will say plainly whether the numbers support outbound, inbound, both, or neither yet.
30 minutes, no obligation. The calendar shows real availability.