A pipeline report is the point-in-time artifact a revenue leader presents on the Monday forecast call or the quarterly QBR. It captures coverage, aging, slip, forecast, and the at-risk ranking as of a moment. Strkr builds the report natively, schedules it to the inbox, and keeps the historical snapshots for diff.
A pipeline report is not a dashboard. It is a readable artifact that someone opens in email, prints, or presents on a shared screen. The sections below are the standard anatomy Strkr's pipeline report ships by default.
The report opens with the three executive numbers: committed forecast, weighted forecast, and coverage ratio against quota. The reader absorbs the state of the pipeline in ten seconds and decides whether to read on or hand it off.
A horizontal bar chart per segment showing pipeline dollars at each stage against the segment's quota. SMB thin at Discovery. Mid-Market healthy. Enterprise top-heavy at Negotiate. The chart diagnoses the business before the exec reads the deal list.
A section per stage listing deals above the aging threshold. Proposal over 21 days, Negotiate over 14, Demo over 10. Each row carries the deal name, days-over-threshold, owner, and the one-line note. The leader works the top of the list in the pipeline review.
A table of deals whose close date moved to a later period since the previous report. Owner, deal, old close date, new close date, slip count. The slip summary is the honest signal of forecast confidence over time.
A ranked list of the top ten open deals by composite at-risk score. Each row shows the dollar value, the primary risk signal (engagement decay, stakeholder drop-off, stage-time anomaly), and the next step. The pipeline review opens on this section.
A table by close month showing the three forecast views: weighted (stage-probability math), committed (rep-flagged), and best case (rep upside). The CFO reads the committed line. The sales leader reads the weighted. The exec reads the delta.
A pipeline report is a one-off artifact unless it is scheduled. Strkr's scheduled snapshots turn the report into a weekly, monthly, or on-cadence habit. The sections below describe the delivery model.
The schedule editor supports daily, weekly, monthly, and cron-style cadences. The report runs at the configured time and emails to the recipient list. The VP gets the Monday morning weekly report. The CFO gets the first-of-month report. The team lead gets the Thursday daily snapshot.
The report is generated per recipient with the recipient's record permissions applied. The regional manager sees their region's deals. The VP sees everything. The rep sees their own book. The permission model carries into the email, no leaking across territories.
The schedule can deliver as a PDF attachment, an inline HTML email, or both. The PDF is for the archival exec read. The HTML is for the recipient who wants to click through to the live deals. Strkr renders both from the same report definition.
The HTML version carries deep links from every section to the matching live surface in Strkr. Click the aging section header and the live aging list opens with the same filters applied. The report is not a dead copy.
Every scheduled run saves a snapshot. The snapshot archive is browsable by date. The leader can diff this week's report against last week's and see exactly what changed in the pipeline. Memory of the pipeline is a built-in capability.
The report can also be generated on demand with the current scope. The output is downloadable as a PDF or copyable as a shared link. The leader generates the quarterly report by pointing the scope at the quarter and clicking Export.
Strkr's pipeline report ships with a sensible default template but every section is configurable. The sections below describe the customization paths an ops lead or a sales leader will use.
The report template editor lets the ops lead add or remove sections. Add a win-rate by source section. Remove the detailed slip table if the exec does not read it. Reorder so coverage leads instead of exec summary. The output stays coherent because sections are reusable blocks.
A report template carries a scope filter: segment, team, product, close month, owner. The regional report pins to the region. The product report pins to the product line. One template, many scoped variants. No report-sprawl.
Each section supports an optional narrative block above the data. The ops lead writes the current week's commentary once per week. Strkr embeds it. The exec reads the human context on the first page and the numbers on the second.
The PDF export supports a tenant logo, brand color, and footer line. The archival report looks like the business, not Strkr. The branding carries through to a shared read-only link if the leader forwards the HTML version to a board member.
A single template with scoped schedules produces per-recipient reports. The VP template emails everyone the VP flag. The regional template emails each regional manager scoped to their region. The ops lead builds the template once and the schedule fans out.
A report section can read its data from an API or a webhook. Teams that compute a custom metric outside Strkr can inject it as a report block. The pipeline report is extensible without rewriting the whole surface.
The pipeline report earns its place when it fits inside the review cadence. The sections below describe the weekly, monthly, and quarterly uses Strkr customers actually run on it.
The scheduled Monday 7am report lands in the VP inbox. The VP reads the exec summary and the top-ten at-risk list before the 9am forecast call. The call opens with context already loaded, not generated during the call.
The Thursday report is the shared screen for the pipeline review. The leader walks the sections in order: coverage, aging, slip, at-risk. Each section drills into the live list. The review runs on the report, not off a slide deck remade from scratch.
Monthly, the pipeline report feeds the forecast board. The CFO reads the committed-forecast line against the plan. Variance drives the conversation about reforecast or ramp-up. The pipeline report is the single artifact finance signs off on.
Quarterly, the ops lead pulls the archived weekly reports and overlays them. The quarterly QBR deck is a trend of the thirteen weeks. The trend shows coverage trajectory, slip trajectory, and at-risk density over time. Strkr's archive makes the trend one query.
The board-level pipeline report is a scoped template that strips deal-level detail and shows aggregated coverage and forecast. The CEO forwards it to the board without a redaction pass. The template is a one-time build and runs quarterly.
When a quarter misses, the leader opens the thirteen weekly reports and reads the trend. The slip count that climbed, the at-risk list that grew, the aging that drifted. The archive answers the hardest question in the exec meeting: when did we know this was coming?
Start a free trial, pick the pipeline report template, schedule it to your Monday inbox, and run the next forecast call on the artifact. Scheduled reports, PDF export, and snapshot archive are included on every paid tier.
A pipeline report is a point-in-time artifact that captures the state of the sales pipeline: coverage ratio, aging callouts, slip summary, at-risk ranking, and forecast rollup. It differs from a pipeline dashboard because it is a readable artifact that someone opens in email or presents on a slide, instead of a live surface. Strkr's pipeline report ships with a default template, scheduled delivery to the recipient list, and a snapshot archive for historical diff.
The standard anatomy is an executive summary with three numbers (committed, weighted, coverage), a coverage-by-segment chart, aging callouts per stage, a slip summary of deals that pushed since the last report, a top-ten at-risk ranking, and a forecast table rolled up by close month. Each section links to the live view in Strkr. The template is editable, so the ops lead can add a win-rate section or remove the slip table if the exec does not use it.
Yes. The schedule editor supports daily, weekly, monthly, and cron-style cadences. The report emails to a recipient list in PDF, inline HTML, or both. Each recipient sees a per-recipient version with their record permissions applied, so the regional manager sees their region and the VP sees everything. The schedule can also deliver a shared read-only link that opens the live interactive version.
Yes. Every scheduled run saves a snapshot. The snapshot archive is browsable by date and the leader can diff this week against last week to see what changed. The archive answers the hardest exec question when a quarter misses: when did we know? The archive is included on paid tiers at no extra charge and retains data for the configured retention period.
Yes. The PDF export supports a tenant logo, brand color, and footer line. The HTML version respects the same branding. If the leader forwards a shared read-only link to a board member, the recipient opens a page branded as the business, not as Strkr. The branding configuration is one-time in the tenant settings.
Yes. A single template with scoped schedules can produce per-audience reports. The VP template emails everyone the VP flag with the global scope. The regional template emails each regional manager scoped to their region. The CFO template is a trimmed version with just the forecast table and the slip summary. The ops lead builds each template once and the schedule fans out.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
