Feature · Pipeline Deals CRM

The deal is one object in a CRM that reads as one system.

A pipeline deal does not live alone. It composes with accounts, contacts, leads, products, approvals, forecasts, and reports. The CRM-wide perspective on how deals integrate across the Strkr platform.

Start free trial See pricing
How deals fit the broader CRM

Six objects the deal composes with.

A pipeline deal in a CRM is one object in a graph that includes accounts, contacts, leads, products, activities, and tasks. The six objects below are what the deal composes with. A CRM that models the composition well produces a coherent system; a CRM that treats the deal as isolated produces the fragmented experience that drives reps to spreadsheets.

Account

The customer the deal is with.

Every deal associates to exactly one account. The account carries the ongoing customer relationship (contacts, past deals, support history, product usage). A single account can carry multiple open deals (land, cross-sell, renewal, upsell); the account roll-up shows the full picture across pursuits.

Contacts

The people on the buying committee.

Deals associate to multiple contacts with role tags (champion, economic buyer, technical buyer, user, blocker). The contact-to-deal graph makes the buying committee explicit; the record surfaces who to engage next and what each contact knows about the current state of the pursuit.

Lead

The pre-qualification origin.

Many deals originate from a lead that qualified; the lead-to-deal conversion captures the origin, the source attribution, and the pre-qualification history. The link preserves the attribution for marketing reporting and the context for the rep working the resulting deal.

Products

The structured line items.

Deals carry product line items (SKUs, quantities, unit prices, discounts, term) as structured child records. The deal amount computes from the line items. The product mix feeds the forecasting (annual recurring revenue, one-time revenue, services revenue), the reporting (sales by product), and the renewal workflow.

Activities

Calls, emails, meetings on the deal.

Activities (calls, emails, meetings, notes) attach to the deal and often to the contacts. The activity density per deal is a leading indicator of deal health; the activity timeline reads chronologically across the deal lifecycle.

Tasks

The scheduled next actions.

Tasks spawn on stage changes and manually as the rep plans next steps. Tasks associate to the deal and to the owner. The task density per deal is a leading indicator of deal health; tasks past due surface as risk signals on the manager dashboard.

The account roll-up perspective

Six capabilities the account record carries from the deals under it.

The account record in a mature CRM carries roll-up signals from the deals under it. The six capabilities below are what Strkr customers rely on for the account-level view. The combination gives the AE, the manager, and the leader the full account picture without reading each deal individually.

Open pipeline

All active pursuits at the account.

The account record shows all active open pursuits with the deal name, the stage, the amount, the close date, and the owner. The leader sees the account pursuit landscape at a glance; a strategic account with three active pursuits reads clearly rather than requiring three separate queries.

Lifetime value

Total closed-won across the account history.

The account record rolls up the lifetime closed-won value across the account history. The rep working the next pursuit sees the full customer value context; the manager prioritizes resource allocation against the lifetime value signal.

Win-rate at account

Historical hit-rate signals account health.

The account record carries the historical win rate (closed-won divided by closed) across all deals ever run with the account. A declining win rate at a long-time customer surfaces a relationship issue; a rising win rate at a newer account signals growing fit.

Average cycle

Deal velocity by account history.

The account record carries the average sales cycle across the account history. The rep plans the pursuit with the realistic cycle expectation; the forecast weights the probability by the account-specific cycle rather than the generic stage default.

Contact graph

All contacts across every deal.

The account record aggregates all contacts across all deals ever run with the account. A new pursuit starts with the contact context from past pursuits; the rep sees who was engaged in the last deal, who was the champion, who was the blocker.

Health score

The composite account health signal.

The account record carries a composite health score (deferred to signals ship) that integrates win rate, cycle length, product usage, support history, NPS, and renewal timing. The CSM, the AE, and the leader see one health signal rather than reading five separate metrics.

The forecast perspective

Six ways deals feed the forecast.

Deals are the atomic unit of the forecast. The six capabilities below describe how the deal data feeds the forecast surface. A CRM that produces a forecast the leadership team trusts has to carry all six; shortfalls on any one of them erode the forecast integrity that the whole go-to-market motion depends on.

Commit category

The rep calls on deal confidence.

Every open deal in the current forecast period carries a forecast category: Commit, Best Case, Pipeline, Omitted. The rep calls the category based on confidence; the manager rolls up the Commit calls for the week-over-week forecast number.

Weighted pipeline

Amount times probability feeds the math.

The weighted pipeline value multiplies deal amount by probability. The forecast reads weighted pipeline for the long-tail Pipeline category deals; the Commit number is the sum of amounts for Commit deals (unweighted, since the rep is calling it as a go).

Period slip

Close-date changes surface the slip.

Changes to the close date across the forecast period surface as period slip: deals moving from current quarter to next quarter, from current month to next month. The slip rate is a leading indicator of forecast quality; a high slip rate signals forecast discipline issues.

Snapshot history

The weekly forecast captures a snapshot.

The weekly forecast captures a snapshot of the Commit, Best Case, and Pipeline numbers against the deal state at the moment of snapshot. Comparing snapshots over the quarter surfaces the pattern of forecast slip, forecast add, and forecast miss by rep and segment.

Accuracy tracking

Forecast versus closed-won.

Each closed-won deal compares against the forecast call at various points in the quarter: forecast at creation, forecast at mid-quarter, forecast at week-of-close. The accuracy pattern reveals forecast discipline: a rep who commits deals that consistently close is forecast-reliable; a rep whose Commit deals slip or lose produces unreliable forecasts.

AI forecast assist

Strkr AI reads the risk signals.

Strkr AI reads the deal timeline (last activity gap, decision maker engagement, competitive pressure, discount dynamics) and produces a risk signal on each Commit deal. The manager running the forecast review uses the AI signals as the starting point for the rep conversation rather than reading every deal from scratch.

What Strkr delivers for the CRM-wide deal perspective

Six capabilities that make the CRM read as one system.

Strkr composes the deal with the rest of the CRM through specific native capabilities. The six below are what makes the Strkr CRM read as one system rather than a stack of disconnected objects. All six ship as default behavior.

Native relationships

Accounts, contacts, products as first-class.

Accounts, contacts, products, leads, and tasks are first-class CRM objects natively related to the deal. The relationships are enforced at the schema level rather than modeled through free-text fields. The system knows the deal belongs to the account and the contacts belong to the deal; the reporting and workflow read against the enforced graph.

Roll-up fields

Account carries deal signals natively.

Account roll-up fields (open pipeline, lifetime value, win rate, average cycle, latest activity) ship as native deal roll-ups on the account record. The rep working the next pursuit sees the account context without a parallel query; the manager prioritizes against the roll-up signals.

Lead conversion

The lead-to-deal link preserves attribution.

Lead conversion creates the deal with the lead attribution preserved (source, campaign, first-touch, last-touch). The marketing reporting sees the pipeline impact of the lead-source and campaign; the sales rep working the deal sees the pre-qualification history.

Forecast surface

Commit, Best Case, Pipeline on the deal.

Every deal in the current period carries the forecast category inline. The weekly forecast review runs against the deal records with the category calls; the leader sees the roll-up without a separate forecast tool. The audit trail captures every forecast category change for discipline review.

Reporting surface

Deals power the pipeline reports.

The Strkr reporting surface runs against the deal data with the full relationship graph: deals by stage, deals by owner, deals by product, deals by account, deals by lead source. The reports read live data; the dashboard tiles drill through to the deals contributing.

Audit integration

One log across every object.

Every change on deals, accounts, contacts, products, tasks, and leads lands in the same audit log with the actor, the timestamp, the old value, and the new value. The compliance review walks one log for the full CRM history rather than reconciling across object-specific logs.

The deal is one object in a system that reads as one surface.

Strkr composes deals with accounts, contacts, leads, products, forecasts, and reports through native relationships and native roll-ups. Start a trial and the CRM reads as one coherent surface from day one rather than a stack of disconnected objects.

Explore the CRM Start free
Common questions

What buyers ask about this feature.

How does a deal relate to the rest of the CRM?

A pipeline deal composes with six primary CRM objects. The deal associates to exactly one account (the customer) and the account carries the ongoing relationship. The deal associates to multiple contacts with role tags (champion, economic buyer, technical buyer, user, blocker) that make the buying committee explicit. Many deals originate from a lead that qualified; the lead-to-deal conversion preserves the attribution and pre-qualification history. Deals carry product line items as structured child records; the deal amount computes from the line items. Activities (calls, emails, meetings, notes) attach to the deal and often to specific contacts. Tasks spawn on stage changes and attach to the deal with the owner assignment. The composition is the CRM; a deal that stood alone would be a shadow spreadsheet.

What roll-up signals should the account record carry from deals?

Six account-level roll-up signals cover the common operational decisions. Open pipeline across all active pursuits at the account. Lifetime value from all closed-won deals in the account history. Win rate (closed-won divided by closed) across all deals ever run with the account. Average sales cycle across the account history, informing the realistic expectation for the next pursuit. Contact graph across all deals, surfacing the engagement history for every contact. Composite health score (deferred until the underlying signals ship) integrating win rate, cycle length, product usage, support history, NPS, and renewal timing. The combination gives the AE, the manager, and the leader the full account picture without reading each deal individually.

How does the forecast read against the deal data?

Every open deal in the current forecast period carries a forecast category (Commit, Best Case, Pipeline, Omitted) on the deal record directly. The rep calls the category based on confidence; the manager rolls up the Commit calls for the week-over-week forecast number. The weighted pipeline value multiplies amount by probability for the long-tail Pipeline category deals; the Commit number sums amounts for Commit deals (unweighted, since the rep is calling it as a go). Changes to the close date across the forecast period surface as period slip. The weekly forecast snapshots the state; comparing snapshots across the quarter surfaces the pattern of forecast slip, add, and miss by rep and segment. Strkr AI produces a risk signal on each Commit deal from the activity timeline, which the manager uses as the starting point for the forecast review.

How does lead conversion preserve attribution?

When a qualified lead converts to a deal, Strkr preserves the lead attribution automatically: the lead source (web form, campaign, inbound referral, outbound SDR), the first-touch and last-touch campaign, and the pre-qualification activity history. The deal record carries the attribution fields so marketing reporting can see the pipeline and revenue impact of lead sources and campaigns. The sales rep working the deal sees the pre-qualification history (what the SDR learned, which assets the lead engaged with, what the lead said about the pain) as context for the opening conversation. The attribution persists through close; closed-won revenue attributes back to the originating lead source for the full marketing-to-revenue reporting.

How does product line-item structure benefit the pipeline?

Product line items as structured child records (not free-text amount fields) give the pipeline four specific benefits. First, the deal amount computes from the line items rather than being free-typed, which prevents amount drift when products change. Second, the product mix feeds forecasting that separates annual recurring revenue from one-time revenue from services revenue. Third, approval routing can key off the product mix (deals including the enterprise SKU route to enterprise deal desk; deals including the services SKU route through services approval). Fourth, the renewal workflow uses the product line items to spawn the renewal pursuit automatically at the right lead time before each contract-end date. Free-text amount fields produce none of these benefits.

How does the audit log work across all CRM objects?

Every change on deals, accounts, contacts, products, tasks, and leads lands in the same Strkr audit log with the actor, the timestamp, the old value, and the new value. Compliance reviews walk one log for the full CRM history rather than reconciling across object-specific logs. The log is immutable; no actor including a tenant admin can modify or delete an entry. The log captures every automated action (Flow executions) alongside human actions; the compliance team sees the full picture without separating human from automated activity. Retention is configurable to meet the common frameworks (7 years for HIPAA and SOX contexts, longer for regulated financial services). Export is available by API or scheduled report for external compliance review.

Related features

Pair this with...

Pipeline Deals Pipeline Management Opportunity Pipeline Pipeline Fields CRM Pipeline Management Account Management Pipeline Automation CRM Pipeline Stages

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