An F7 Project and Advisory Lane diagnostic from Stan Consulting LLC for operators whose Q3 board deck describes one company while the field operation runs a different company. Resolved with the Strategic Advisory Call at $1,250 over 90 minutes or the Decision Architecture engagement at $2,500 over 7 to 14 days. Roseville California. United States.
Stan Consulting · Problem · F7 Project & Advisory Lane
Your Board Deck Contradicts the GTM You’re Actually Running.
The Q3 deck commits the company to enterprise. Slide 7 says it. The 12 SDRs hired in May are calling SMB lists. The roadmap ships features the enterprise buyer does not need. Paid social runs to a B2C audience because that is what the pixel optimizes against. The board reads slide 7 and asks why pipeline is concentrated below $50K ACV. The deck describes one company. The operation runs a different one. The board is being asked to govern a contradiction.
Stan Consulting · Marketing Diagnostics & AI Engineering · Roseville CA · 2026
When the deck and the field operation describe two different companies, the operator is not facing a deck problem or a GTM problem. The operator is facing a governance problem the board will surface first and the team will absorb second. The fix is not a better deck and not a better GTM. The fix is a single, defensible decision about which version of the company is correct, then a rewrite of whichever artifact disagrees. Stan Consulting’s F7 Project & Advisory Lane resolves that decision two ways. A 90-minute Strategic Advisory Call at $1,250 when the contradiction reduces to one decision. A 7- to 14-day Decision Architecture engagement at $2,500 when it does not.
A board governs the company described in the deck. A team runs the company described in the GTM. One has to win.
02
Questions Operators Ask
Four questions that show up before the next board meeting.
Operators in this situation tend to arrive with the same four questions in roughly the same order. The honest answer to each one is below.
If both the deck and the GTM are reasonable, why is this a crisis?
A board deck and a field operation are not two artifacts. They are the same company described twice. When the descriptions disagree, the board is being asked to govern a fiction and the team is being asked to execute against a different fiction. Pipeline data, hiring decisions, and roadmap commitments all carry the contradiction forward. The deck is reasonable in isolation. The GTM is reasonable in isolation. The company that contains both is not reasonable. The crisis is not the deck and not the GTM. The crisis is the seam between them, and the seam compounds every week it is not named.
Is this a strategy problem or an execution problem?
Both descriptions sound like strategy and look like execution from the inside. The deck is treated as the strategic artifact. The GTM is treated as the execution layer. That framing is what hides the contradiction. The deck encodes a strategic decision the team never received. The GTM encodes a strategic decision the board never approved. The mismatch is not weak execution. It is two strategies running in parallel, one of which has not been named, and neither has been ratified by the people closest to the customer.
Should we change the deck or change the GTM?
That is the wrong first question. The first question is which version of the company is correct given the customer evidence in the CRM, the cash position on the books, and the team you actually have under contract. Once that is decided, one of the artifacts gets rewritten and the other one gets re-instructed. Asking the question in the order most operators ask it produces a deck that survives the next board meeting and a GTM that produces the same pipeline mismatch in 90 days. The order matters more than the answer.
What does an Advisory Call or Decision Architecture engagement actually do here?
The $1,250 Strategic Advisory Call is 90 minutes with the principal and is the right format when the contradiction reduces to one decision the operator already knows is theirs to make. The $2,500 Decision Architecture engagement is 7 to 14 days and is the right format when the contradiction touches multiple stakeholders, requires written stress-testing across two or three scenarios, and ends in a single recommendation the board can read and the team can execute. The Advisory Call is faster. The Decision Architecture is more durable. Most operators in this situation need one of the two, not both.
01The mistake
Treating the deck and the GTM as independent artifacts.
The deck is written for the board. The GTM is owned by the team. The two are produced on different cadences, by different people, against different incentives. That separation feels professional. It is the source of the failure.
A board deck and a field operation share one company. They are not independent. They are the same set of decisions documented twice, once for governance and once for execution. When the two documents disagree, the company itself is the contradiction. The board does not see two artifacts. The board sees one company that cannot decide what it is.
The mismatch surfaces on the deck side first because the board reads the deck on a fixed cadence. By the time slide 7 collides with the pipeline report on slide 12, the contradiction has already been visible to the team for a quarter. Nobody named it. Now the board is naming it, and the CMO is being asked to defend a seam she did not author.
[Note] The deck did not lie. The GTM did not betray the deck. The company simply ran two parallel strategies for two quarters and the board scheduled the meeting where they meet.
02Why it happens
Decks are written for board cadence. GTMs evolve daily. Drift compounds when no one audits the seam.
The deck is updated quarterly. It encodes what the operator wanted the company to be at the start of the quarter. The GTM is rewritten every Monday by the head of demand gen, every Tuesday by the SDR manager, every Wednesday by the paid social lead, and every Friday by whoever owns the pipeline number. Each Monday-through-Friday change is small. None of them rolls back to slide 7.
Drift is not a strategic failure. Drift is what a healthy team does. The 12 SDRs hired in May were hired against a real pipeline gap. The B2C-leaning paid social audience emerged because the pixel found CAC there. The roadmap softened on enterprise because the customer interviews rewarded a different feature set. Each move was rational on its own day. The cumulative move is a different company.
No single person is auditing the seam between the quarterly deck and the daily GTM. That is not because nobody is competent. It is because the audit is nobody’s formal job. The CFO governs cash. The CMO governs spend. The CRO governs pipeline. The board governs the deck. The seam between deck and GTM does not have an owner, so it does not have an audit, so it drifts until the contradiction is loud enough to be everyone’s problem.
03What you stop doing
Stop defending both versions. Stop asking the board to trust the trajectory. Stop hiring deck designers to make the contradiction prettier.
The first instinct, when the board surfaces the seam, is to write a slide that defends both artifacts at once. That slide cannot be written. The two versions of the company are mutually exclusive on enough load-bearing points that any synthesis is dishonest. A synthesis slide buys 30 days. The next board meeting buys nothing.
The second instinct is to ask the board to trust the trajectory. That request asks the board to govern hope. Boards that govern hope replace the operator who asked. Boards that see a seam named, a decision made, and a single artifact rewritten do the opposite.
The third instinct is to hire a designer, retitle slide 7, and reorder the appendix. That is the most expensive move on this list. It signals to the team that the deck is the artifact that wins, which means every subsequent GTM decision will be made against a deck the team does not believe. CAC will rise. Sales hires will leave. The next deck will be uglier than this one.
Defending both versions is not a strategy. It is the absence of one. Pretty contradictions are still contradictions.
04What you install instead
Pick the right F7 format. One decision, one engagement.
Two engagements resolve this seam. The Strategic Advisory Call at $1,250 is 90 minutes with the principal. It is the right format when the operator already knows which version of the company is correct, has the authority to decide it, and needs an outside read to confirm the decision and pressure-test the rewrite plan. Most operators in that position leave the call with the rewrite scoped to a single artifact and a single owner.
The Decision Architecture engagement at $2,500 is 7 to 14 days. It is the right format when the contradiction touches multiple stakeholders — the CEO, the board, the CRO, the head of product — and a 90-minute call cannot do the work of stress-testing the decision in writing. The deliverable is a written recommendation the board can read on its own time and the team can execute the next day. Two scenarios are stressed against the customer evidence. One is recommended. The other is documented as the reason it was rejected.
Pick by scope, not by price. The Advisory Call is faster. The Decision Architecture is more durable. The wrong choice is to install neither and hope the next board meeting is kinder than this one. It will not be.
Decide.
05
F7 Lane · Three Formats
Three engagements. Pick by scope, not by price.
Each format resolves a different size of contradiction. The smallest is one decision. The largest is a strategic problem the operator cannot frame in a single question.
F7.1 · 90 Minutes
Strategic Advisory Call
$1,250
If the question reduces to one decision the operator already owns, the call confirms the read and scopes the rewrite. 90 minutes with the principal. Recording included.
If the contradiction touches multiple stakeholders and needs written stress-testing across scenarios, this is the format. Single recommendation. The board reads it. The team executes it.
If the strategic problem is bigger than one decision — if the rewrite cascades into roadmap, hiring, and channel architecture — this is the format. Scoped per project, fixed-fee, written.
A board governs the company described in the deck. A team runs the company described in the GTM. One has to win.
01
Pick the company first
Before the deck or the GTM gets touched, the operator names which version of the company is correct given customer evidence, cash, and the team under contract. That decision is the load-bearing one. Everything downstream is rewriting.
02
Rewrite the loser, do not blend it
Whichever artifact disagrees with the picked company gets rewritten in full, not blended. A blended deck and a blended GTM produce the same seam in 90 days, on a higher budget, with less board patience.
03
Install one owner of the seam
One named person owns the audit between deck and GTM going forward, on a monthly cadence, with the authority to flag drift before the next board meeting. The seam without an owner drifts. The seam with an owner does not.
F7 · Project & Advisory Lane
Resolve the contradiction before the next board meeting.
If the contradiction reduces to one decision, the 90-minute Strategic Advisory Call at $1,250 closes it. If it touches multiple stakeholders and needs written stress-testing, the 7- to 14-day Decision Architecture engagement at $2,500 closes it. Both formats end with a single recommendation the operator can carry into the boardroom and the team can execute the day after.
If your HQ sits in one of these clusters, start here.
The diagnostic is remote-default; the engagement format adapts to the cluster the operator runs inside. These are the California HQ pages most relevant to this problem state.