Feature · Sales Pipeline Report

A sales pipeline report that reads the way a Monday forecast call runs.

A sales pipeline report is the written artifact a sales leader hands to the executive team on Monday morning. Stage coverage, aging, slip rate, movement since last review, and the forecast rollup. Strkr builds the report on live CRM data and schedules it to the inbox as PDF or inline HTML, with per-user permission scoping, so no one reads data they are not allowed to see.

Start free trial See pricing
What belongs in a pipeline report

The six sections an executive expects to read.

A pipeline report is not a dashboard screenshot. It is a six-section narrative that an executive reads in under five minutes and leaves with a point of view on the quarter. Strkr ships the report template with the sections pre-built so the sales ops lead does not spend Sunday night in a spreadsheet.

Executive summary

Three sentences, no jargon.

The top of the report is three sentences: pipeline coverage against quota, slip signal, and committed-vs-best-case split. The executive reads the summary first and decides whether to read the detail. Strkr auto-generates the summary from the underlying tiles with the sales leader editable on each send.

Stage coverage

How much pipeline sits at each stage.

A horizontal bar per stage with the deal count, total ACV, and the coverage multiplier against the stage target. The report shades thin stages red and healthy stages green. The executive reads the color before the numbers.

Aging summary

Stuck deals, by stage.

A table of deals above the stage aging threshold with owner, stage, and days-in-stage. The table is capped at the top ten to keep the report readable. The full aging list is one click away in the live dashboard.

Slip trend

Deals that pushed since last report.

A three-period sparkline of slip count and ACV. The executive reads the direction, not the absolute number. A rising slip trend is the first signal of forecast softening and deserves a call-out, which the sales leader writes in the editable note field.

Movement

Deals that advanced since last report.

A short list of the deals that moved forward in stage, with the owner and the stage transition. Movement is the positive counter-signal to slip. The executive reads the win column before the risk column.

Forecast rollup

Committed, best case, pipeline, gap.

The last section is the forecast table: committed number, best case, remaining pipeline, and the gap to quota. The executive leaves the report with the forecast position. Strkr pulls the numbers from the forecast surface so the report and the live forecast never disagree.

How the report is built

Template, filters, schedule, and permission.

The pipeline report is a saved template that pulls live CRM data at send time. The sales ops lead configures the template once and the schedule runs for the quarter. Edits land in the next send. The sections below are the mechanics that let the report scale across regions, segments, and teams.

Report builder

Drag the sections, pick the filters.

The report builder is the dashboard builder in a paginated layout. Drag the sections, pick the segment filter, pick the recipient list. Save as a report template. The template is the write-once artifact that every schedule references.

Segment filters

VP report, region report, team report.

The report builder supports the same filter bar as the dashboard: segment, owner, team, close month, product. The VP report is unfiltered. The regional report scopes to the region. The team report scopes to the team. One template, three schedules.

Schedule

Monday morning, Friday afternoon, month-end.

The schedule is a cron-style rule: Monday 7am for the forecast call, Friday 4pm for the week-end snapshot, last day of the month at 5pm for the board. The schedule runs out of the Flows layer so the sales ops lead does not babysit a Make.com scenario.

Permission scoping

Recipient-aware data.

The report respects CRM permissions on send. A regional manager's report shows only their region's deals. An executive's report shows everything. The report does not expose rows the recipient could not query in the app, which keeps the pipeline report compliant with the same access rules as the live surface.

PDF or inline HTML

Pick the format per recipient.

The PDF format lands as an attachment, which the executive forwards to the board. The inline-HTML format renders in the email body, which the regional manager reads on mobile without downloading. The template supports both and the schedule picks per recipient preference.

Editable note

The sales leader writes the top three lines.

Every send has an editable note field at the top of the report. The sales leader writes the three-line commentary before the schedule fires. The commentary is the human context on the numbers. The schedule holds for a short window after the trigger to let the leader finalize the note.

How teams use the pipeline report

The exact cadence a sales org runs.

A pipeline report is not a one-time artifact. It is a cadence. The sections below describe how a sales org runs the weekly, monthly, and quarterly report cycle on the same template, with the schedule doing the heavy lifting and the sales leader editing the commentary.

Monday executive report

Seven am, before the forecast call.

The template emails the executive team at 7am Monday. The sales leader has edited the top-three-line commentary by Sunday evening. The forecast call opens on the report shared screen. Every attendee has read it. The call starts on action, not on orientation.

Weekly rep report

Each rep reads their book.

A per-rep version of the report lands in each rep's inbox Monday morning. The rep sees their own pipeline, their own aging deals, and their own slip. The report is one page. The rep reads it on the train and shows up to the one-on-one with the gaps already identified.

Mid-quarter checkpoint

Week six of a thirteen-week quarter.

The mid-quarter report is the pipeline reality check. The sales leader runs the same template with a quarter-to-date lens and sends to the executive team. The report answers whether the quarter is still landable with current coverage or needs an action.

Monthly board snapshot

A board-ready page.

The last day of the month fires the board-snapshot variant of the template. The PDF is one page, formatted for the board deck. The CFO drops it into the deck appendix without reformatting. The sales operations team saves eight hours a month.

End-of-quarter close report

What landed, what slipped, what carries.

The last Friday of the quarter fires the close-report variant. The report shows what landed inside the quarter, what slipped to next quarter, and what carries over. The executive team uses it to seed the next-quarter plan.

Ad-hoc exec request

A click, not a project.

An executive asks for a slice of the pipeline off-cycle. The sales ops lead clones the template, scopes the filter, hits Send Now. The report lands in minutes. No "pull it from Tableau and email me." The report is the live export.

What the pipeline report replaces

The stack this report retires.

Most sales ops teams build the weekly pipeline report in a spreadsheet pulled from the CRM, formatted overnight by an analyst, and emailed Monday morning. Strkr runs the whole cycle native. The sections below are the trade-offs against the common alternatives.

Spreadsheet pull

Flexible, stale, labor-heavy.

The weekly spreadsheet report is the default in mid-market sales ops. The analyst exports from the CRM Sunday night and formats the pivot tables for the Monday send. The report is accurate on send and stale by Tuesday. Strkr's report is live on send and replaces the analyst hour.

Salesforce reports

Powerful, email-fragile.

Salesforce can schedule a report to email on a cadence. The format is report-shaped, not narrative-shaped. The executive gets a table attachment, not a readable page. Strkr's template emits a narrative report with sections, charts inline, and the editable commentary at the top.

Tableau or Looker send

Beautiful, licensed, slow to iterate.

A BI tool can email a dashboard screenshot or a formatted PDF. The output looks good. The iteration cycle is slow and the license is a line item. For a weekly pipeline report, the BI investment is heavy. Strkr's report ships inside the CRM seat price.

Google Slides deck

Narrative, manual, drift-prone.

Some sales ops leads build the weekly report as a slide deck updated by hand. The deck is readable and narrative-shaped. The cost is three hours every Sunday night and a drift risk on every send. Strkr's report is narrative-shaped and auto-generated.

HubSpot report email

Clean inside the HubSpot bundle.

HubSpot's report email is credible for Sales Hub Pro teams. The template is HubSpot-shaped. Teams considering consolidation to one platform get the same cadence on Strkr with multi-pipeline and custom-object support that HubSpot does not match.

Strkr

Live, scoped, scheduled, no extra SKU.

The pipeline report runs native on every paid Strkr tier. Live data, segment scoping, permission-aware delivery, editable commentary, and PDF or inline HTML. The seat price covers it. No BI license, no analyst hour, no cron server.

Monday morning, no more Sunday night in a spreadsheet.

Start a free trial, clone the default pipeline report template, pick the recipient list, and schedule the first send. The sales ops lead gets Sunday evening back.

Start free trial See pipeline dashboard
Common questions

What buyers ask about this feature.

What is a sales pipeline report?

A sales pipeline report is a periodic written artifact that summarizes the state of open deals: coverage by stage, aging deals, slip since last report, deals that advanced, and the forecast rollup. It is distinct from a live dashboard because it is sent on a cadence, has an editable narrative commentary, and is formatted for an executive to read in under five minutes. Strkr ships the template, the schedule, and the permission-aware delivery native, so the sales ops lead does not spend Sunday night rebuilding it in a spreadsheet.

How is a pipeline report different from a pipeline dashboard?

A pipeline dashboard is a live interactive surface - the sales leader opens it, filters it, drills into deals, and runs the review on it. A pipeline report is a written snapshot of the same data, sent on a schedule, with a narrative commentary and a format designed for inbox reading. The report answers "what should I read before the meeting." The dashboard answers "what should I do during the meeting." Strkr ships both from the same data model with the same tile library, so the report and the dashboard never disagree.

Can we send different reports to different recipients?

Yes. The report template supports a filter bar - segment, owner, team, close month, product - and the schedule can run per-recipient variants. The VP gets the unfiltered report; the regional manager gets the regional slice; the rep gets their own book. Permission scoping also applies on send: a recipient only sees the deals they would be allowed to query inside the app, so a report never exposes rows the viewer could not otherwise see.

Does the sales leader get to add commentary?

Yes. Every send has an editable note field at the top of the report. The sales leader writes the three-line commentary before the schedule fires. Strkr holds the schedule for a short window after the trigger to let the leader finalize the note. If the leader does not edit, the schedule falls back to the auto-generated three-sentence summary. The commentary is the human context on the numbers.

What formats does the report email in?

The report can send as a PDF attachment, as inline HTML in the email body, or both. The PDF is formatted for printing or forwarding to a board deck. The inline HTML renders on mobile without a download. The schedule picks per recipient preference, so the executive gets the PDF and the regional manager gets the inline version. The template is the same, the output format is a per-send choice.

Is the pipeline report included on every tier?

Yes. The report builder, template library, scheduled send, PDF and inline-HTML output, and permission-aware delivery are included on every paid Strkr tier. Per-recipient variants and schedule-level editable commentary are included on Pro and above. There is no separate BI SKU, no credit meter on the send, and no per-report charge. The seat price listed on the pricing page is the full price.

Related features

Pair this with...

Sales Pipeline Dashboard Sales Reporting Sales Pipeline Management Sales Pipeline Sales Forecast Sales Dashboard

Try it free. Bring your team next week.

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.

Start free trial See pricing