Built for sales leaders setting the next-year plan

Sales targets and goals only hold up when the CRM reports attainment live against the number the rep committed to.

Setting sales targets and goals is a Q4 ritual at every B2B company. The ritual produces beautifully formatted spreadsheets. The spreadsheets then disconnect from the CRM where attainment is actually measured. Six months later the rep says "my quota is 850K" and the comp admin says "the plan I have says 950K" and nobody is sure which document is current. Strkr writes targets and goals to the user record so the live attainment report is the single source of truth.

What this audience is actually dealing with

The pains that bring buyers here.

A CRO at a 50-rep SaaS company sent me a frustrated screenshot in October: three spreadsheets open side by side, each one showing a slightly different Q3 quota for the same rep. The spreadsheet from the January kickoff showed $750K. The spreadsheet from the June mid-year adjustment showed $825K. The CRM dashboard showed $800K. Nobody could reconstruct which number the rep was actually comping against or how to pay the Q3 commission. The "sales targets and goals" search comes from CROs, VPs of sales, and sales ops leads who have hit this exact failure mode. The targets live in multiple places; the attainment dashboard is one of them; the comp calculation is a fourth. Here is the framework that keeps the number consistent.

Three documents, three numbers

January plan, mid-year adjustment, CRM dashboard.

A typical sales organization has the quota in three places: the Q4 planning spreadsheet from January, the mid-year adjustment document from June, and the CRM dashboard that pulls from a different source. When the three disagree (and they always do within six months), the rep argues the lowest number, the admin pays against the highest, and the CFO wants to know which was correct. The documents disconnect from the CRM is the structural problem.

Activity goals without targets

"Make 60 dials a day" with no connection to pipeline math.

Sales activity goals (60 dials, 20 connects, 10 meetings) usually get set based on a management intuition about what a productive rep does, not based on the conversion math that actually produces the quota. The rep hits the activity goals, misses the pipeline target, and nobody can diagnose why. Strkr's target framework runs the activity math backwards from the pipeline target so the daily goals produce the quarterly number.

Pipeline coverage ratios undefined

The 3x pipeline coverage assumption without validation.

Pipeline coverage ratios (ratio of pipeline value to quota) are usually set at 3x or 4x by convention. The real coverage math depends on win rate, deal velocity, and segment mix. A team with a 25 percent win rate needs 4x coverage; a team with a 40 percent win rate needs 2.5x. Setting a universal coverage ratio across segments misreads the risk. Strkr pulls the actual historical win rate per segment and recommends segment-specific coverage ratios.

Ramp quota structure is unclear

New hire gets the full number from month one.

A common mistake: a new hire joins in February and gets the full annual quota prorated against the time remaining in the year. The rep has not ramped yet, cannot possibly hit the number, and either demoralizes or triggers a messy comp exception. The right pattern is a ramp quota: 30 percent in month one, 60 percent by month four, 100 percent by month seven. Strkr's comp module handles the ramp schedule per hire natively.

Team KPIs undefined

The CRO asks for "team health"; everyone defines it differently.

Team-level KPIs (pipeline health, forecast accuracy, win rate, discount discipline) usually get set at the end of a planning cycle without clear definitions. "Pipeline health" means different things to different managers. Six months in, the exec review surfaces that the health score is unreliable because each team computed it differently. Strkr publishes team KPI definitions explicitly with the formulas visible and the data sources pinned.

Mid-year adjustments break the plan

Rep leaves; quota redistributes; comp statements get complicated.

Mid-year events (rep leaves, segment reorganizes, new product launches) force quota adjustments. The adjustments usually happen in a side document that disconnects from the CRM. Six months later a commission dispute requires reconstructing which quota was in effect at which time. Strkr tracks quota as a versioned record on the user with effective dates so the historical state is always queryable.

The target framework

Three target layers that build on each other.

Working sales targets and goals operate at three layers: revenue targets (quota per rep, team, segment), activity targets (dials, meetings, demos that produce the pipeline math), and KPI targets (win rate, deal velocity, forecast accuracy that measure the system health). Each layer feeds the next. Strkr writes all three to the user and team records so the dashboard shows attainment across all three.

Layer one: revenue quota

Annual ARR number per rep with ramp schedule.

Revenue quota is the annual ARR number each rep commits to. The math starts from the company revenue plan, divides across segments based on pipeline shape, divides across reps per segment with equity math applied. New hires get a ramp schedule (30 percent month one, 60 percent month four, 100 percent month seven). Strkr writes quota to the user record with ramp effective dates and attainment calculating live against closed-won.

Layer two: activity targets

Dials, meetings, demos that produce the pipeline math.

Activity targets reverse-engineer from the revenue number through the conversion funnel. If a rep needs 20 closed-won at $40K average to hit $800K, and the win rate is 25 percent, the rep needs 80 proposals. If the proposal-from-demo rate is 50 percent, the rep needs 160 demos. If the demo-from-meeting rate is 40 percent, the rep needs 400 meetings. Working backwards gives the weekly activity target, which Strkr publishes on the rep dashboard.

Layer three: KPI targets

Win rate, velocity, forecast accuracy as system health.

KPI targets measure the health of the sales system itself: win rate (overall and by segment), deal velocity (days from stage transition to transition), forecast accuracy (committed versus actual), discount discipline (average discount depth). These KPIs are usually leading indicators of whether the revenue plan is on track. Strkr publishes KPI dashboards per team and per segment with target thresholds flagged.

Segmentation and team targets

Each segment carries its own targets.

Segmentation drives target differentiation. Strategic segment gets lower volume per rep but higher ACV. Mid-market gets middle volume at middle ACV. SMB gets high volume at low ACV. The targets reconcile up to the company revenue plan. The CRO rolls up a segment view that shows each segment's contribution to total ARR with target thresholds flagged.

Pipeline coverage math

Segment-specific coverage ratios based on win rate.

Pipeline coverage ratios are segment-specific. A segment with a 40 percent win rate needs 2.5x coverage; a segment with 25 percent win rate needs 4x; a segment with 15 percent win rate needs 6.7x. Strkr pulls the actual trailing-twelve-month win rate per segment and surfaces the segment-specific coverage math on the pipeline review dashboard. Managers see which segments need more pipeline load, not just which reps are behind.

Team and manager-level KPIs

Attainment per team with mix contribution.

Team-level targets aggregate the rep-level quotas and include manager-level accountability KPIs: team attainment percent, mix of segment contribution, team coverage ratio, forecast accuracy at the team roll-up. Strkr publishes a team dashboard with these KPIs so sales managers run their teams against defined metrics rather than vibes.

Named-account targets

Strategic AEs with per-account targets.

Strategic AEs often carry per-account targets in addition to overall quota. A strategic AE might carry $2M annual quota with target amounts set per named account ($400K from Account A, $300K from Account B). Strkr tracks per-account targets with attainment calculated live per account and surfaces the attainment on the account record so the executive sponsor sees the pacing.

How Strkr writes the three layers

Revenue, activity, and KPI targets on live records.

The reason targets stop working is the disconnect between the planning document and the attainment dashboard. Strkr writes revenue quota, activity goals, and KPI thresholds to the user and team records so the live dashboard pulls from the authoritative source and the planning spreadsheet retires. Here is the mechanism.

Quota as versioned user record

Annual quota with effective-date versioning.

Quota writes to the user record as a versioned field with effective dates. The January plan is version 1 with effective date Jan 1. The mid-year adjustment is version 2 with effective date Jun 15. The attainment dashboard reads the quota version in effect at each closed-won date. Comp calculations run against the correct version regardless of when the adjustment happened. Historical disputes resolve to the audit log.

Ramp schedule attached to hire

Per-hire ramp with prorated attainment.

A new hire gets a ramp schedule attached to their user record at creation. The default schedule (30/60/100 across months 1, 4, 7) is editable per hire. The attainment calculation uses the ramp curve during the ramp window and the full quota after month 7. Commission payouts prorate against the ramp quota automatically. The ramp-exception conversation ("they only got 60 percent of the ramp quota this month") disappears because the math is built in.

Activity goals on user record

Weekly dial, meeting, demo targets.

Activity goals write to the user record as weekly targets: dials, meetings booked, demos delivered, proposals sent. The targets reverse-engineer from the revenue quota through the conversion funnel. The rep dashboard shows weekly actual versus target with the current conversion-rate math visible. Managers run coaching conversations with real activity numbers rather than vibes.

KPI thresholds on team record

Team-level win rate, velocity, forecast accuracy.

Team-level KPI thresholds write to the team record: minimum win rate, maximum average deal cycle, minimum forecast accuracy. The team dashboard flags any KPI that crosses the threshold. Sales managers get a weekly email if their team's KPIs are drifting. The exec review (monthly or quarterly) runs on real KPI numbers with the threshold context visible.

Attainment waterfall

Quota, pipeline, closed-won, remaining in one view.

The attainment waterfall shows quota at the top, pipeline weighted by stage in the middle, closed-won at the bottom, with the remaining gap visible. The rep sees exactly what they need to close in the remaining weeks of the quarter. The manager sees the same view across the team. Strkr AI drafts a weekly narrative on each rep's attainment waterfall.

Mid-year adjustment workflow

Quota adjustment with audit and rep acknowledgment.

A mid-year quota adjustment runs as a formal workflow: the sales ops lead drafts the adjustment, routes to the sales manager for approval, routes to the rep for acknowledgment. The adjustment writes as a new version of the quota record with the previous version preserved. The audit log captures every step. The rep can see the new quota and the reason for the change in Strkr rather than wondering where the latest spreadsheet is.

Named-account targets

Per-account targets on the account record.

Strategic AEs with per-account targets get the target amount written to the account record with the AE assigned. The account record shows attainment against the per-account target in addition to contributing to the AE's overall quota. The executive sponsor sees the pacing on the account record. The CRO sees named-account roll-up as a dedicated dashboard view.

Target vs stretch target

Base plan with upside.

Some teams run a target plus a stretch target. The target is the commitment the rep comps against; the stretch is the aspirational upside. Strkr writes both to the user record with the comp accelerator kicking in at stretch attainment. The dashboard shows both. The team conversation about where the quarter is heading includes both numbers rather than just the base.

The quarterly cadence that keeps targets alive

What happens at week one, month three, mid-year.

Targets that get set in January and reviewed only at year-end do not drive behavior. The quarterly cadence that keeps targets alive runs at four touchpoints: week one of the fiscal year, end of each quarter, mid-year, and end of year. Here is what happens at each.

Week one of the year

Quota handoff and acknowledgment per rep.

In week one of the fiscal year, each rep receives their annual quota, ramp schedule, activity targets, and comp plan. The rep acknowledges in Strkr. The acknowledgment writes to the user record as a timestamp. Any questions or disputes get flagged before the quarter starts. The week-one handoff prevents the "I didn't know my quota was 950K" conversation in September.

End of each quarter

Attainment review with coaching focus.

At quarter-end, each rep gets an attainment review with the sales manager. The review covers quota attainment, activity attainment, KPI contribution, and coaching focus for the next quarter. Strkr's quarterly review template surfaces the key numbers automatically. The conversation focuses on patterns (not events) because the data is visible.

Mid-year adjustment window

Formal review at the half-year mark.

The mid-year adjustment window (typically June or whenever the fiscal mid-year lands) runs a formal review per rep. Reps who are substantially under-pacing get the adjustment conversation (quota reduction, segment change, ramp extension). Reps who are substantially over-pacing may get stretch targets or team-lead responsibilities. The adjustments flow through the quota workflow with audit.

Quarterly executive review

CRO reviews segment-level and team-level attainment.

At the end of each quarter, the CRO runs a segment-level and team-level review. The review covers segment contribution to total ARR, team attainment, KPI trends, and strategic account progress. Strkr publishes the exec-review dashboard automatically. The CRO reads the dashboard, drafts commentary, and ships to the board without rebuilding slides.

Year-end attainment calculation

Final payout with full audit trail.

At year-end the final attainment calculates per the versioned quota and the ramp schedule. The commission payout runs with the audit trail attached. Any disputes resolve to the audit log. The year-end review informs the next-year plan with real conversion rates, real cycle times, and real win rates feeding the next-year targets.

Weekly pipeline review

The operational cadence that drives attainment.

Between the quarterly rituals the weekly pipeline review drives attainment. Each sales manager runs the weekly review with their reps on Strkr's pipeline dashboard. The review covers the week's activity against targets, pipeline movement, deals at risk, deals progressing. Strkr AI drafts the review summary. The weekly cadence is where the targets actually get hit (or not).

Monthly cross-functional review

CRO, marketing, product, CS review targets together.

Once a month the CRO runs a cross-functional review with marketing (pipeline supply), product (new-feature impact on win rate), and CS (expansion attainment). The review covers whether the target math is still holding or whether the mix is shifting. Strkr publishes the cross-functional dashboard that spans each function's contribution to the sales targets.

Annual planning cycle

Next-year targets built from this-year data.

The annual planning cycle (usually Q3 or early Q4) builds next-year targets from this-year data. The actual win rate, cycle time, segment mix, and conversion funnel from the current year feed the next-year target math. Strkr's target-planning view surfaces the historical data in the shape the planning team needs. The planning cycle runs on real numbers rather than assumptions carried over from the previous year.

Head-to-head

Strkr vs Spiff or CaptivateIQ for sales targets and comp.

Spiff and CaptivateIQ are the dominant specialty tools for comp management. They do that one thing well. For teams that want targets and attainment inside the CRM rather than in a separate comp calculator, the comparison matrix lays out this way.

Feature Strkr Spiff (Standalone comp tool)
Quota on user record Native with effective-date versioning Separate tool with CRM sync
Activity targets Reverse-engineered from quota through funnel Not typically scoped
Ramp schedule Per-hire ramp with prorated attainment Supported in comp calculation
Mid-year adjustment workflow Formal workflow with audit trail Manual plan version update
Pipeline coverage math Segment-specific based on win rate Not in scope
KPI thresholds on team record Win rate, velocity, forecast accuracy Not in scope
Named-account per-account targets On account record with attainment Possible in commission formulas
Commission calculation Native comp module with audit Industry-leading comp calculator
Pricing Flat per seat, all included Per-rep comp add-on subscription
AI narrative on attainment Strkr AI drafts weekly narrative Not available
How teams use Strkr

Sales teams running targets inside Strkr.

The customers who adopted Strkr for target management share one pattern: they had quota in three documents and attainment in a fourth, and the September surprise was the inevitable result. The playbooks below are live motions.

B2B SaaS, 50-rep team

Three-document quota collapsed to one versioned user record.

A 50-rep SaaS team ran quota in a January planning spreadsheet, a June mid-year adjustment doc, and a Salesforce dashboard that disagreed with both. The migration to Strkr wrote quota as a versioned field on each user with the January plan as version 1 and the June adjustment as version 2. Attainment calculated against the correct version per closed-won date. Commission disputes dropped roughly 90 percent in the first full quarter.

Mid-market services, 24-AE team

Activity targets reverse-engineered from pipeline math.

A 24-AE services team set activity targets by intuition ("60 dials, 20 connects, 10 meetings per week"). The team hit activity but missed pipeline because the targets did not reconcile to the conversion funnel. Strkr's activity-target framework reverse-engineered activity from pipeline math per segment. The revised targets ran roughly 25 percent higher for new business and roughly 30 percent lower for expansion. Pipeline health recovered inside one quarter.

Enterprise FinServ, 32-AE team

Named-account per-account targets with executive-sponsor view.

A 32-AE enterprise FinServ team ran named-account coverage with 180 strategic accounts. Per-account targets lived in a Google Doc that nobody kept current. Strkr wrote per-account targets to the account record with executive-sponsor visibility. Executive sponsors reviewed account pacing weekly against targets. Three accounts that were drifting got exec-sponsor intervention early enough to recover; two others got de-prioritized formally rather than quietly abandoned.

Scaling startup, 12-rep team

Ramp quota structure cut the first-hire quit rate in half.

A scaling startup's first six AE hires had three resignations in year one, driven partly by the "full prorated quota from month one" policy that no new rep could possibly hit. Strkr's per-hire ramp schedule (30/60/100) rewrote the first-year experience: new hires felt the targets were achievable, hit the ramp numbers at 70-plus percent attainment, and stayed. The quit rate dropped to one of eight hires in year two.

One quota record, one attainment dashboard, zero spreadsheet drift.

Start a 14-day Strkr trial with quota versioning, ramp schedules, activity targets, KPI thresholds, and comp calculation on the flat per-seat line.

Common questions

What buyers in this bucket ask most.

What is the difference between sales targets and sales goals?

In working vocabulary, "sales targets" usually refers to the quantitative revenue number a rep or team commits to (quota, ARR target, closed-won amount). "Sales goals" is broader and includes revenue targets plus activity goals (dials, meetings, demos), KPI goals (win rate, forecast accuracy, deal velocity), and sometimes qualitative objectives (break into a new segment, develop a strategic account). The practical rule: targets are measurable with one number; goals span multiple metrics and sometimes include qualitative elements. Both should write to the CRM and both should produce live attainment reports.

How does Strkr prevent the "three different quota numbers" problem?

Quota writes to the user record as a versioned field with effective dates. The January plan is version 1 with Jan 1 effective date. A mid-year adjustment creates version 2 with the adjustment effective date. The attainment calculation reads the quota version in effect at each closed-won date, so a deal that closed before the adjustment reconciles against the original quota and a deal that closed after reconciles against the adjusted quota. The audit log captures every version change with user, timestamp, and reason. Commission disputes resolve to the audit log rather than to a Slack argument.

How are activity targets reverse-engineered from the revenue number?

Strkr pulls the trailing conversion rates per stage (meeting to demo, demo to proposal, proposal to close) and works backwards from the revenue quota. If a rep needs 20 closed-won at $40K average to hit $800K and the trailing proposal-to-close rate is 25 percent, the rep needs 80 proposals. If the demo-to-proposal rate is 50 percent, 160 demos. If the meeting-to-demo rate is 40 percent, 400 meetings. The weekly target divides the annual by 48 working weeks. The rep dashboard surfaces the weekly activity target with the current conversion math visible.

What is the right pipeline coverage ratio for my team?

Depends on win rate. The coverage ratio should be roughly the inverse of the win rate: a team with a 25 percent win rate needs 4x coverage, a team with 40 percent win rate needs 2.5x, a team with 15 percent win rate needs 6.7x. Strkr pulls the actual trailing-twelve-month win rate per segment and surfaces segment-specific coverage ratios on the pipeline review dashboard. Segment-specific is important because applying a universal coverage ratio to a mixed-segment team overweights the strategic segments and underweights the velocity segments.

How does the ramp quota work for new hires?

A new hire gets a ramp schedule attached to the user record at creation. The default schedule in Strkr is 30 percent of full quota in month 1, 60 percent by month 4, 100 percent by month 7. The schedule is editable per hire if the ramp expectation differs. The attainment calculation uses the ramp curve during the ramp window, so a rep in month 2 who hits $50K against a $65K ramp-quota target shows at 77 percent attainment rather than the depressing 15 percent they would show against the full annual quota. The commission calculation prorates against the ramp quota automatically.

Does Strkr integrate with Spiff or CaptivateIQ for commission calculation?

Strkr's native comp module handles commission calculation for most teams, including base-plus-variable plans, accelerators, decelerators, SPIFFs, and clawback rules. For teams that specifically want Spiff or CaptivateIQ (common at larger enterprises with complex multi-plan structures), we support export of attainment data to those tools via API. Most mid-market teams drop the separate comp tool when they move to Strkr because the native module covers the standard patterns and the pricing is included. Enterprise teams with specialty requirements often keep the specialty comp tool with Strkr as the attainment data source.

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.