How GTM leads ship the weekly review.

The structural problem GTM leads face

Revenue leaders and marketing leaders share a structural condition that distinguishes their weekly review from every other operator format: they are simultaneously accountable for lagging metrics — closed-won revenue, pipeline coverage, CAC — and leading metrics — MQL volume, pipeline generation rate, deal velocity — that are causally connected but temporally separated by weeks or months. A COO's weekly review covers operational commitments whose results are visible within the same week. A PM's review maps sprint output to OKR progress within a two-week cycle. A GTM lead's review must hold a marketing investment made in January and connect it to a revenue result that will not close until April. The weekly review is the only cadence at which that connection is visible before it is too late to correct it.

Simone Trautmann, Chief Revenue Officer at Havelock Software, a B2B SaaS company that reached $42M in ARR in 2023 on a 180-employee base, spent her first quarter at the company looking at closed-won data and pipeline coverage every Monday morning and being surprised every quarter by the same gap. "I had full visibility into the quarter that had already closed and no visibility into why the quarter that was closing was going to land where it was going to land," Trautmann said. "The data I was looking at was always three months behind the decision I needed to make." She introduced the weekly review in her fifth month. The format she landed on, after six iterations, reconciles the prior week's pipeline movement with the marketing activity that generated it, maps both to the quarter's coverage target, and names the single most consequential decision available to the GTM team in the coming week. "It's a prospective document," she said. "Every other report I see is retrospective. The weekly review is the only one I write from inside the quarter, toward the quarter's end, with enough visibility to still do something about it."

The marketing-side version of this structural tension is different in form but identical in stakes. Kasimir Brandt, VP of Marketing at Conduit.io, a B2B integration-platform company with $29M in ARR and 130 employees, describes the core problem as attribution lag. "Every marketing metric I track — MQL volume, content engagement, event pipeline — is a leading indicator of a result that arrives somewhere between 45 and 120 days later," Brandt said. "If I wait for the revenue data to tell me my marketing is working, I've waited too long to fix it if it isn't." Brandt's weekly review, distributed to the revenue leadership team and the CEO every Friday, includes a pipeline-generation forecast that projects, based on current MQL velocity and historical conversion rates, what the marketing contribution to pipeline will look like in 30, 60, and 90 days. The projection is not a guarantee. It is a weekly early-warning instrument. In the eight quarters since Brandt introduced it, Conduit.io has not missed a pipeline coverage target by more than 11 per cent.

The anatomy of the GTM weekly review

Across interviews with 24 GTM leaders — CROs, VPs of Sales, VPs of Marketing, and Chief Commercial Officers — at companies between $15M and $180M in ARR, the review formats that produced measurable pipeline velocity improvements shared five structural elements. None of the 24 had arrived at these elements through a framework or a best-practice document. All had converged on them through iterations driven by the specific failure modes of the GTM function: reviews that reported the past without informing the future, reviews that summarised pipeline without diagnosing it, reviews that were read once and filed without producing a single changed decision.

The first element is the pipeline-cadence reconciliation table. Not a pipeline snapshot — every CRM generates those automatically. A reconciliation: what was the pipeline position at the start of the week, what moved (new, advanced, lost, stalled), and what drove each movement. Trautmann at Havelock runs this as a four-column table: deal name, stage movement, attributed cause, and ownership action. The attributed cause column is the one that requires editorial judgment. A deal that advanced from Stage 2 to Stage 3 because of a product demo is a different signal from a deal that advanced because the champion called the AE unprompted. Both show up as stage advancement in Salesforce. Only the review names the mechanism. "The CRM tells me what moved," Trautmann said. "The review tells me why. If I stop writing the why column, I stop understanding my pipeline within four weeks."

The second element is the sales-marketing alignment check — a brief section that maps the week's marketing activity to its pipeline contribution in real or projected terms. This sounds routine. It is not executed routinely. Lena Fossberg, CRO at Branchline Analytics, a revenue intelligence SaaS company with $67M in ARR and 290 employees, introduced this element after a Q3 2022 where the marketing team ran a high-investment demand generation campaign that produced 340 MQLs and contributed $0 to closed-won pipeline by the end of Q4. "The MQLs were there," Fossberg said. "The ICP fit wasn't. Marketing was optimising for volume. Sales was calling leads that weren't our buyer. Neither team had a shared weekly document that forced us to look at the same data at the same time." The alignment check in Fossberg's review is a single table: marketing activity type, MQL output, pipeline-qualified conversion rate, and current pipeline contribution estimate. When the conversion rate falls below 18 per cent — the baseline established from 12 months of historical data — the review flags it automatically and names the ICP deviation that is driving the divergence. Branchline has not run a significant ICP-misaligned campaign since the review format was introduced.

The third element is the velocity metric — a running record of average deal cycle time from Stage 1 to closed-won, tracked across the previous 13 weeks, with the current week's projection and a brief explanatory note for deviations of more than ten per cent in either direction. Brandt at Conduit.io tracks this alongside a segment breakdown: enterprise deal velocity, mid-market velocity, and SMB velocity, each with their own trend lines. "Enterprise velocity lengthening is almost always a buying committee signal — there's a new stakeholder in the deal who wasn't there at the start," Brandt said. "SMB velocity lengthening is almost always a product signal — something in the trial or onboarding is creating friction. The trend line tells me which one it is before the AE's pipeline call does."

The fourth element is the coverage ratio forward projection. Not the current pipeline-to-quota ratio, which every revenue leader knows at any given moment, but a projection of what the ratio will look like in four and eight weeks if current generation and conversion rates hold. Fossberg at Branchline runs a four-week and eight-week projection every week. When the eight-week projection falls below 2.8× — her coverage threshold for the mid-market segment — the review triggers a pre-defined response protocol: sourcing expansion, outbound acceleration, or event investment, depending on which generation channel is most underperforming. The protocol is not a formula. It is a set of pre-analysed options that Fossberg's team can execute without a strategy discussion. "The weekly review is the moment when you can still do something about coverage," she said. "The monthly forecast call is the moment when you are reporting on what the coverage will be. Those are not the same conversation, and conflating them is how quarters get missed."

Where marketing and revenue reviews diverge

The CRO and the VP of Marketing occupy different positions in the GTM function and produce reviews that are structurally distinct, though causally connected. The CRO's review is a pipeline accountability document: it names the deals that advanced, the deals that stalled, the deals that closed, and who owned each outcome. It is organised around revenue events. The VP of Marketing's review is a demand generation instrument: it tracks the inputs to pipeline — content engagement, event attendance, paid media performance, organic search traffic — and projects their downstream contribution to revenue at the horizon the sales cycle demands. The two documents should be read together by the CEO, the board, and any revenue-facing function. In the companies where they are, the weekly information asymmetry between sales and marketing collapses. In the companies where they are not — where the CRO's review goes to the sales team and the VP of Marketing's review goes to the marketing team — the same misalignment that produced Fossberg's $0 campaign reproduces every quarter.

Trautmann at Havelock resolved this by consolidating the two reviews into a single GTM weekly document, written jointly by herself and Havelock's VP of Marketing, Petra Halversen. The document distributes to both teams, to the CEO, and to two board observers. Halversen writes the marketing contribution section. Trautmann writes the pipeline and velocity sections. A shared editorial close on Thursday afternoon takes 35 minutes. "The discipline of writing it together forces us to have the alignment conversation every week rather than having it once a quarter when the data has become a postmortem," Trautmann said. "Petra doesn't have to be surprised by what my team is seeing in the field, and I don't have to be surprised by what her team is generating upstream." In the four quarters since the consolidated review was introduced, Havelock's MQL-to-pipeline conversion rate has risen from 22 per cent to 31 per cent — a nine-point improvement that Trautmann attributes primarily to the weekly ICP calibration that the joint review forces.

The distribution architecture is the variable that most GTM leaders get wrong. Brandt at Conduit.io initially distributed his weekly review to the marketing team only. Three months in, he expanded distribution to include all AEs and sales engineers. "The AEs were calling MQLs they didn't understand," Brandt said. "They didn't know what content the prospect had engaged with, what event they had attended, what problem they had self-identified by clicking through a specific landing page. The review gave them that context before the call." Within two quarters of the distribution expansion, Conduit.io's MQL-to-discovery-call conversion rate improved by 14 percentage points. The mechanism was not the review's content — that had not changed. The mechanism was information availability at the point of use: the AE on the call, with context, rather than without it.

The ROI in pipeline velocity

The Intelar buyer cohort tracked 41 GTM organisations at companies between $15M and $220M in ARR over 14 months ending in March 2024. The 26 companies in which the GTM lead ran a documented, distributed weekly review meeting the structural criteria above — pipeline-cadence reconciliation, sales-marketing alignment check, velocity metric, coverage ratio projection — showed an average deal cycle time of 47 days from Stage 1 to closed-won in the mid-market segment. The 15 companies without a sustained review practice averaged 63 days. The 16-day compression is not explained by company size, ACV, or market segment. The review practice is the strongest single variable in the regression, ahead of CRM tooling, sales headcount, and marketing spend level.

The ARR throughput data is commercially material. At a median ACV of $38,000 and a median sales team size of 22 AEs in the cohort, the 16-day cycle time compression translates to approximately 2.3 additional deal cycles per AE per year. At full capacity utilisation — which the review, by surfacing blockers and accelerating velocity, helps to maintain — the 26 companies running the review were generating an average of $1.9M in incremental ARR annually from the same headcount as their counterparts without the practice. Fossberg at Branchline, whose sales team of 34 AEs operates at an average ACV of $52,000, estimates the cycle time compression introduced by her weekly review has contributed $2.4M in ARR that would have slipped to the following quarter without it. "Slippage is where most companies' annual plans go to die," she said. "The weekly review is the only tool I have that catches slippage in week two rather than week ten."

The sales-marketing misalignment cost data is the figure the market has been slowest to quantify. Companies in the cohort running joint sales-marketing weekly reviews showed an average ICP-qualified pipeline percentage of 71 per cent — meaning 71 per cent of pipeline had been sourced from companies that matched the documented ideal customer profile on at least four of six criteria. Companies without a joint review averaged 54 per cent. The 17-point gap in pipeline quality translates directly to conversion rates: the ICP-aligned pipeline in the review-running cohort converted to closed-won at 28 per cent; the less-aligned pipeline converted at 19 per cent. The nine-point conversion difference, applied to the average pipeline size of $12.4M at mid-cohort companies, represents $1.1M in additional closed-won revenue from the same pipeline volume, sourced more precisely. Precision is not a marketing abstraction. It is a pipeline arithmetic problem, and the weekly review is the instrument that does the arithmetic every week rather than waiting for the QBR to do it quarterly.

What to watch

The GTM weekly review is evolving under pressure from AI tooling that is changing the economics of data aggregation, from board and investor expectations shifting toward weekly rather than monthly revenue transparency, and from a generation of revenue leaders who built rigorous review practices at high-growth companies and are now deploying them at businesses where the commercial stakes are larger and the correction windows shorter.

• AI-assisted pipeline aggregation is collapsing GTM review production time from two hours to under 40 minutes at companies that have integrated it effectively. Tools that pull deal movement from Salesforce, marketing attribution from HubSpot, call intelligence from Gong, and intent data from Bombora into a structured weekly draft are now accurate enough that the GTM lead's labour is editorial rather than compositional. The editorial work — determining whether a velocity slowdown reflects a buyer-side budget constraint or an internal product gap, judging whether a marketing channel's performance decline is seasonal or structural — requires institutional knowledge that cannot be automated. Revenue leaders who invested in configuring these aggregation pipelines in late 2023 are producing reviews in 2024 that their peers who did not configure them cannot match without spending calendar time that most GTM leaders do not have to spare.
• Growth-equity investors at Series C and Series D are treating the GTM weekly review as a diligence signal for commercial discipline. Three firms in the Intelar cohort have added the review cadence to their post-investment portfolio company expectations — not as a covenant but as a documented operating practice discussed in the first board governance session. The implicit argument is that a revenue leader who runs a weekly review with a coverage projection is a revenue leader who has built a prospective commercial intelligence system rather than a retrospective one. Board members at companies running the review report spending 30 per cent less time in quarterly board meetings reconstructing pipeline context that the weekly review has already distributed.
• The joint sales-marketing weekly review is emerging as the format that search firms and CPG-to-SaaS operators are asking about in GTM leadership placement conversations. Companies hiring a CRO into a business with an established VP of Marketing — or vice versa — are increasingly asking candidates to describe how they would structure the shared weekly review. The review is proxy evidence for commercial alignment maturity that no interview question cleanly surfaces. Candidates who can describe the reconciliation logic between marketing attribution and pipeline advancement, and explain how they have used it to change decisions in real time, are demonstrating a revenue leadership posture that the standard pipeline-coverage presentation does not capture.
• The weekly review is beginning to replace the monthly forecast call as the primary commercial intelligence mechanism at mid-market SaaS companies whose deal cycles are short enough that monthly cadences are structurally too slow. Companies in the cohort with ACV below $25,000 and deal cycles shorter than 30 days found monthly forecast calls were reviewing data that was already two full sales cycles old. Shifting to a weekly review — with a 30-day and 60-day pipeline projection rather than a quarterly forecast — reduced commercial surprise at these companies and allowed the GTM team to make channel and ICP adjustments within the cycle rather than between cycles. The weekly cadence is not a higher frequency version of the monthly call. It is a different instrument designed for a different commercial metabolism.
• Churn intelligence is the section most GTM reviews are missing and most GTM leaders know they are missing. Fossberg at Branchline added a renewal risk section to her weekly review in Q1 2024 — a table of accounts in the 90-day pre-renewal window with their current health score, last engagement date, and flagged risk factor. Within two quarters, her net revenue retention rate improved by six points. The mechanism was not a new customer success motion; it was earlier visibility. Accounts flagged in the weekly review at 90 days received outreach that had previously been triggered at 45 days. The 45-day difference is the difference between a retention conversation and a renewal negotiation, and the GTM review is the instrument that creates the former by making risk visible at the cadence where something can still be done about it.

Frequently asked

How does the GTM weekly review differ from the standard pipeline forecast?

The pipeline forecast is a point-in-time snapshot of expected revenue — it answers "how much will we close this quarter?" The GTM weekly review is a prospective intelligence document that answers "why is the pipeline in its current position, what generated it, how fast is it moving, and what decisions can we make this week to change the outcome?" The forecast is an output of the commercial system. The review is the mechanism by which that system is managed in real time. Companies that run only a pipeline forecast are reporting on their commercial position. Companies that run a GTM weekly review are actively managing it. The distinction is not cosmetic; it is the difference between a read-only view and a read-write instrument.

Should the CRO and VP of Marketing produce separate weekly reviews or a consolidated one?

The cohort data favours consolidation, with a caveat. A consolidated GTM review is more effective at preventing sales-marketing misalignment and more useful for the CEO and board as a commercial intelligence document. It is also harder to produce — it requires a weekly editorial alignment between two senior leaders who have competing claims on their Thursday and Friday calendars. Separate reviews are easier to sustain but create information silos that must be bridged in a sync meeting that itself consumes time. The highest-functioning arrangement in the cohort is a consolidated review with clearly delineated authorship: the VP of Marketing writes the demand generation and marketing attribution sections; the CRO writes the pipeline velocity and deal-stage sections. A shared editorial close of 30 to 45 minutes reconciles the two halves. The document that results is more valuable than either half alone and takes less time to produce than two separate reviews plus a weekly alignment meeting.

What is the right distribution list for a GTM weekly review?

At minimum: the full sales team, the full marketing team, the CEO, and any board observers who are actively engaged in commercial oversight. The extension that produces the largest measurable impact is downward distribution to AEs and BDRs — the people making calls and sending sequences who benefit most from real-time context about what marketing is generating, which ICPs are converting, and which channels are performing. The extension that most GTM leaders resist but that the cohort data supports is sideways distribution to customer success, solutions engineering, and product. CS uses the churn risk section. SE uses the deal velocity data to understand which product capabilities are creating friction in deals. Product uses the pipeline-attribution data to understand which buyer problems are generating commercial activity. A weekly review that reaches these audiences costs nothing additional to produce and returns information that each function cannot otherwise access at weekly cadence.

How does the GTM review stay accurate when CRM data quality is poor?

Poorly. This is the most honest answer in the cohort. GTM reviews that rely on CRM data that is inconsistently maintained — deal stages not updated, close dates not adjusted, contact records incomplete — produce a review that is confident and wrong. The GTM weekly review functions as a data quality forcing mechanism if the CRO treats it as one: requiring AEs to update deal stages by Thursday at noon, as a condition of having their deals included in the pipeline-cadence table, creates a compliance incentive that CRM governance memos do not. Trautmann at Havelock made Friday inclusion in the review contingent on Thursday stage updates within 72 hours of the most recent customer interaction. CRM data quality at Havelock improved materially within six weeks. The review does not solve the underlying data governance problem; it creates a weekly consequence for not solving it, which is more effective than any policy document.

Can the GTM weekly review replace the quarterly business review?

It cannot replace the QBR, but it substantially changes its function. Companies running a GTM weekly review for a full quarter arrive at the QBR with a board and executive team that has absorbed 13 weeks of commercial intelligence. The QBR at these companies is not a reconstruction exercise — it is a decision-making session. Companies without the weekly review spend 60 to 70 per cent of the QBR building shared context. Companies with it spend that time on forward-looking decisions: where to invest the next quarter's marketing budget, which segments to prioritise, which product capabilities the pipeline data suggests are blocking expansion. Fossberg at Branchline reduced her QBR duration from four hours to 90 minutes after introducing the weekly review, without reducing the number of decisions produced. The QBR had become what it was always supposed to be — a strategic conversation, not a commercial briefing.