Built for teams building a sales function

An explanation of sales for the people building the function, not just reading about it.

Most "what is sales" articles target students or absolute beginners. If you are standing up a sales function, hiring your first rep, or inheriting a messy pipeline, you need the explanation one level deeper: how pipeline stages actually work, what forecast methods are honest, which tooling matters, and how the function connects to the rest of the business.

What this audience is actually dealing with

The pains that bring buyers here.

A business building a sales function from scratch (first time hiring a sales lead, inheriting a messy pipeline from a founder-led motion, converting from a service shop to a product company) runs into a predictable set of confusions. The vocabulary is dense and inconsistent across companies. Pipeline stages mean different things to different vendors. Forecast methods disagree on which deals count. And the CRM selection debate often starts before anyone has clarity on what the sales function is actually doing. Six specific pains show up in these conversations.

The vocabulary is inconsistent

MQL, SQL, SAO, SQO mean different things at different companies.

A new sales lead inherits a CRM where "qualified" means one thing to Marketing and something else to Sales. The ops cleanup starts with a definitions document, because without agreement on what a lead, an opportunity, and a qualified prospect actually are, every forecast number is debatable. Strkr ships a definitions template inside the admin surface with 15 of the most-used sales terms and the right place to debate each one.

Pipeline stages drift over quarters

The seven stages in the CRM are not the seven stages the team actually runs.

A sales function that has been running for 18 months has a CRM pipeline with seven labeled stages and a reality where the team collapses three of them into one and skips another entirely. The RevOps lead cleans up the mismatch quarterly. Strkr pipeline configuration surfaces the actual stage progression velocity (how long deals spend in each) alongside the labeled stages so the drift shows up before it costs a quarter of forecast accuracy.

Forecast methods disagree

Commit, best case, pipeline coverage, weighted stage math.

A new sales lead reads about forecast methods and finds four that look reasonable: commit-based (what reps promise), weighted-stage math (probability times value), pipeline coverage ratio (total pipe divided by target), and historical close rate on current stage composition. Each method gives a different number for the same pipeline. Strkr runs all four in parallel so the exec team sees the honest range rather than one method's point estimate.

Lead qualification is subjective

BANT, MEDDIC, SPICED, challenger: too many frameworks.

Qualification frameworks (BANT, MEDDIC, MEDDPICC, SPICED, challenger) each ask a slightly different question and produce a slightly different qualified set. A new sales function spends three quarters finding the right one for its motion. Strkr qualification fields are configurable per pipeline so a team running SMB inbound can use BANT and the same tenant running enterprise outbound can use MEDDPICC without a schema conflict.

The CRM is a Monday chore

Reps hate the admin burden and skip the entries.

The single most common cause of inaccurate pipelines is reps who stopped logging activities because the CRM data entry burden was too high. Strkr's activity-capture pattern (email thread tie-in, call recording with AI summary, calendar integration for meeting notes) collapses the daily admin burden to roughly 90 seconds per deal per day. The compliance for data entry stops being a Monday ritual and becomes a background hum.

Compensation drives behavior wrong

The comp plan designs the pipeline, not the sales lead.

A comp plan that pays on booked ARR drives reps to sandbag the pipeline. A comp plan that pays on logo count drives small deals. A comp plan that pays on gross profit drives discount discipline. The sales lead designing the comp plan is implicitly designing the pipeline shape. Strkr surfaces the attach rate of each comp plan structure to pipeline health metrics so the sales lead has data when the quarterly comp plan conversation happens.

The sales function explained

What the function actually does, in nine moves.

The sales function moves prospects from unaware to signed, through a sequence of qualified handoffs. The nine moves below are the backbone of what a modern B2B sales function does, in the order they usually happen on a deal.

Prospecting

Identify who might buy, build the list.

Prospecting creates the top of the pipeline. SDRs and AEs build target-account lists (ICP-fit companies, specific personas inside those companies, intent signals from third-party data, inbound-signal match from the website). The output is a list of named contacts and companies worth attempting outreach to. Strkr prospecting surface ties the ICP enrichment to the target-list build and surfaces the intent signals inside the account record.

Outreach

Multi-channel attempt to open a conversation.

Outreach runs email, LinkedIn, phone, and sometimes paid in a sequence over 3 to 5 weeks. The goal is a response that moves the prospect from a cold list to an actual conversation. Strkr Flows run the cadence with AI-drafted personalization against the account record, with human review on every send. We never suggest Zapier because every outreach integration ships as native code.

Qualification

Determine whether this prospect is actually worth time.

Qualification runs on a framework the team picked (BANT, MEDDIC, SPICED, challenger). The output is a decision: pursue, nurture, or disqualify. A healthy qualification motion disqualifies 55 to 75 percent of first conversations, which protects AE time for the deals worth working. Strkr qualification fields on the deal surface the framework's structured answers for Monday review.

Discovery

Understand the buyer's actual problem and context.

Discovery runs 30 to 60 minutes with the primary buyer, often across two meetings. The goal: understand the problem, the current state, the proposed future state, the economic buyer, the timeline, and the decision criteria. Strkr call recording with AI summary surfaces the discovery answers as structured fields on the deal so the AE and the manager read the same shape week after week.

Technical validation

Prove the product solves the problem.

Technical validation runs on products that need buyer-side evaluation: a demo tailored to the discovered pain, a pilot, a proof of concept, a security review. The sales engineer runs this phase alongside the AE. The deal advances when the technical buyer signs off that the product works for the use case. Strkr tracks validation milestones as fields on the deal with pass/fail outcomes.

Proposal

Scope, pricing, terms.

The proposal is the formal pitch at closing-table scale: scope of what the customer gets, pricing structure, contract term, special conditions. Strkr Products module ships CPQ shapes (tiered pricing, approval chains, discount thresholds, usage-overage math) so the proposal generation is a flow rather than a one-off spreadsheet build.

Negotiation

Terms and signature.

Negotiation runs on the proposal: price, term, payment schedule, legal review, SLA, special terms. The economic buyer, legal, and procurement all participate. The deal signs or walks here. Strkr integrates with DocuSign and PandaDoc for e-signature with structured status tracking inside the deal record.

Handoff

From AE to CSM for onboarding.

A signed deal is not a closed deal. The handoff from AE to the Customer Success team sets up the first 90 days of post-sale. A clean handoff with the discovery context, the technical validation summary, and the committed success criteria sets up renewal. A sloppy handoff creates churn risk at month 11. Strkr handoff templates surface the context the CSM needs on the first renewal check.

Renewal and expansion

Keep the customer and grow the account.

Modern B2B sales does not end at signature. Renewal (will they re-up next year) and expansion (will they buy more seats, more products, more use cases) is where the lifetime value compounds. The CSM leads renewal and expansion with support from the AE. Strkr account surface shows renewal date, expansion opportunity, usage health, and support history alongside the pipeline for the account.

The vocabulary

Fifteen terms that actually matter.

Sales vocabulary is messy because every vendor and every methodology coined its own term. Here are the 15 terms that come up on every discovery call, with the definitions a sales lead building the function can actually use.

MQL

Marketing qualified lead.

A prospect that Marketing has deemed ready for Sales attention based on behavioral or firmographic signals: downloaded a specific asset, visited pricing twice, matched the ICP. The MQL definition should be agreed between Marketing and Sales explicitly. A sloppy MQL definition causes the Marketing-Sales handoff fight that burns most GTM teams.

SQL

Sales qualified lead.

An MQL that Sales has verified is worth working. The SDR or AE has had a conversation (or at least a confirmed response) and verified fit, timing, and buying authority at a baseline level. SQL rate (SQL divided by MQL) is a core funnel metric. Healthy mid-market B2B motions see 25 to 45 percent SQL conversion.

Opportunity

A deal with real buying intent.

The CRM opportunity object is the formal record of a deal in progress: value, close date, stage, probability, products, contacts, next steps. Opportunity creation is a milestone that implies the deal has crossed the SQL bar and now carries real forecast weight.

Pipeline

The set of open opportunities.

Pipeline is the aggregate of open opportunities (not closed-won, not closed-lost) with their value and stage. Pipeline health is measured by coverage ratio (pipeline value divided by quarterly target, typically 3x to 4x for healthy mid-market B2B), velocity (how fast deals move stages), and composition (balance across stages).

Forecast

What Sales commits to closing.

Forecast is the quarterly or monthly number Sales commits to the exec team. Commit (deals the rep is confident will close), best case (deals that could close with upside), and pipeline (everything open) are the three bands. Forecast accuracy is a leading indicator of sales management maturity.

ARR and ACV

Annual recurring revenue and annual contract value.

ARR is the normalized annual revenue from recurring contracts (subscriptions, retainers). ACV is the per-customer annual contract value. New ARR added in a quarter is the headline sales number for most SaaS and recurring-service businesses. Expansion ARR, churn ARR, and net new ARR break the number into components.

Churn

Revenue or logos lost to non-renewal.

Gross churn is revenue lost from non-renewing customers (independent of expansion). Net churn is gross churn minus expansion from retained customers. Healthy mid-market SaaS runs gross churn under 15 percent annually; healthy enterprise SaaS runs it under 7 percent. Churn trends drive customer success investment decisions.

CAC

Customer acquisition cost.

CAC is the fully loaded cost of acquiring a new customer: Marketing spend, Sales spend, tools, management overhead, divided by new logos closed. CAC payback period (how long it takes the customer's ARR to repay the CAC) is a core efficiency metric. Healthy B2B SaaS runs CAC payback under 18 months.

LTV

Lifetime value.

LTV is the expected total revenue from a customer across the full relationship. Simple formula: ACV divided by churn rate. LTV to CAC ratio is a core unit-economics metric; healthy B2B SaaS targets 3x or higher on LTV to CAC.

Win rate

Of qualified opportunities, how many close won.

Win rate is closed-won divided by (closed-won plus closed-lost). Healthy mid-market B2B win rate runs 25 to 40 percent on fully qualified opportunities. Win rate below 20 percent on qualified deals suggests qualification or discovery issues; above 50 percent suggests the team is not pushing enough deals through qualification.

Sales cycle

Median days from opportunity creation to closed-won.

Sales cycle length is the median time (not mean, because outliers skew mean badly) from opportunity creation to closed-won. SMB B2B runs 20 to 60 days. Mid-market B2B runs 60 to 150 days. Enterprise B2B runs 180 to 365 days. The cycle length drives pipeline-coverage math.

Quota

The number a rep commits to closing.

Quota is the quarterly or annual target assigned to a rep. Attainment (percentage of quota closed) is the core performance metric. Healthy teams see 60 to 70 percent of reps hitting quota in a given period, with 20 to 30 percent exceeding. If 90 percent of reps hit quota, the quotas are too low.

Capacity

How much pipeline a rep can work at once.

Rep capacity is the number of active opportunities a rep can meaningfully progress. Mid-market B2B AEs typically run 15 to 30 active deals. Routing and territory assignment should respect capacity, not just assign by geography. Strkr routing with capacity caps prevents reps from drowning in a bad month.

ICP

Ideal customer profile.

ICP is the structured description of the customer who buys, pays, stays, and expands. Firmographics (company size, industry, geography), technographics (what tech stack they run), buyer persona (who in the org buys), and situation (what triggered the need). A tight ICP is the single highest-leverage asset in a GTM function.

Attribution

Which channel earned the deal.

Attribution assigns credit for a closed-won deal to the Marketing or Sales activity that drove it. First-touch (which channel introduced the contact), last-touch (which channel converted), and multi-touch (shared credit across the journey) are the three common models. Strkr runs all three in parallel so the exec team sees the honest range.

The tooling that matters

What a modern sales function actually needs.

Sales tool spending at a mid-market B2B company often hits $400 to $700 per rep per month across CRM, dialer, cadence tool, enrichment, meeting intelligence, proposal, and reporting. Strkr collapses most of that stack. Here is what the function actually needs.

The CRM

The system of record for accounts, contacts, deals.

The CRM holds the authoritative state of every prospect and customer relationship. Record creation, pipeline progression, activity logging, forecast rollup, reporting all live here. Strkr ships the CRM core plus most of the surrounding tools (routing, enrichment, cadence, meeting intelligence, proposal, reporting) on the same per-seat line.

Routing and booking

Match leads to the right rep, fast.

Inbound leads need routing to the right rep based on territory, product line, deal size, and rep capacity. Modern routing takes 15 seconds from form submit to rep assignment with a booking link ready to send. Strkr routing is included on the standard tier; no Chili Piper line.

Cadence and sequencing

Automated outreach steps with human review.

Outbound cadences run 6 to 12 steps over 3 to 5 weeks: email, LinkedIn, phone. The AI drafts personalization against the account record; the human reviews and sends. Autonomous outbound is deliberately not shipped because the deliverability and brand-voice risk is too high in the current model generation.

Dialer and conversation intelligence

Call recording with AI summary.

Modern sales teams record every discovery and demo call. The AI transcribes, extracts outcome, surfaces objections, flags talking-point gaps for coaching. Strkr Messaging ships native dialing with transcription and runs the AI call summary on the standard tier.

Enrichment

Firmographic and intent data on contact write.

A new contact arrives with firmographic data attached: company size, industry, funding stage, tech stack where available. Strkr enrichment runs on contact write via native integrations with the common data providers (Dealfront, Clearbit alternatives, Apollo). The enrichment payload lives on the contact record and feeds ICP-fit scoring.

Proposal and e-signature

Products module with CPQ shapes.

The proposal and e-signature step runs through Strkr Products module (CPQ shapes, approval chains, discount thresholds) with DocuSign and PandaDoc as the signature partners. The proposal references the live pricing from the pricing book, so a sales lead who changed pricing on Monday sees the change in Tuesday's proposals automatically.

Reporting and forecasting

Pipeline waterfall, forecast rollups, win-loss analysis.

Reporting runs on the shipped Strkr reports: pipeline waterfall, forecast rollup with four methods in parallel, win-loss analysis, cohort retention, CAC per channel. The reports are templated so a new sales lead inherits a starting set rather than building from a blank canvas.

Marketing module

Campaign attribution tied to the CRM.

The Marketing module ships campaign tracking, UTM parsing, journey logic, and attribution rolled up to deal and account records. The Marketing and Sales teams see the same contact lineage, which collapses the Marketing-Sales handoff fight. No separate Supermetrics line.

Admin and permissions

Claims-based permissions and audit log.

Modern sales functions have 10 to 30 roles with different data visibility rules. Strkr claims-based authorization gates every endpoint and query, with per-role Layouts controlling field visibility. The audit log captures every record change for compliance review, which matters for FinServ, healthcare, and public-sector buyers.

Head-to-head

Strkr vs the typical mid-market sales stack.

A new sales lead costing out the tool stack usually lands at $400 to $700 per rep per month across 6 to 10 vendors. Strkr collapses most of that into one line. Here is the shape.

Feature Strkr Pipedrive + separate marketplace tools
CRM core Native pipeline, forecast, reports on standard tier Pipedrive Professional at $64 per seat per month
Routing with capacity Native round-robin + weighted + capacity cap Chili Piper or similar at $30+ per seat per month
Cadence and sequencing Native Flows with AI-drafted personalization Outreach or SalesLoft at $100+ per seat per month
Dialer with AI summary Signal House integration with AI summary native Aircall + Gong at $100+ per seat per month combined
Enrichment Native integrations with common data providers Dealfront or ZoomInfo at $20-80 per seat per month
Proposal and CPQ Native Products module with approval chains PandaDoc Business at $65 per seat per month
Marketing attribution Native Marketing module with UTM to deal roll-up HubSpot Marketing Hub Pro or separate attribution tool
Admin and permissions Claims-based auth, audit log, Layouts on standard tier Higher-tier plans or custom admin builds
AI drafts and summaries Flat per-seat, no credit meter Credit-metered or higher-tier gates
Fully loaded per-rep monthly cost Roughly $60-80 per rep per month Roughly $400-700 per rep per month across 6-10 vendors
How teams use Strkr

Building the sales function on Strkr.

Teams that stand up a sales function on Strkr follow similar patterns. The playbooks below are shapes we have seen from first-rep hires to 50-rep teams.

First sales hire, founder-led handoff

Document the ICP, inherit the pipeline, run the first quarter.

A founder-led motion handing off to the first sales lead needs three things: an ICP document, a pipeline inventory, and a 90-day plan. Monique, who inherited a 55-opportunity pipeline from the founder, spent her first week in Strkr documenting the ICP from the closed-won history, scrubbing the pipeline from 55 to 32 active opportunities, and establishing a Monday review ritual. The founder stepped back from pipeline reviews after week two. Monique closed four deals in her first full quarter and the founder got back the two hours a week she was spending on sales ops.

From 2 reps to 8 reps in a year

Standardize the pipeline before you add seats.

A 2-rep team growing to 8 reps in a year needs a standardized pipeline shape so new hires ramp against a consistent map. Devin, the sales lead running the hiring plan, used Strkr's pipeline configuration to lock the seven-stage shape, define the exit criteria for each stage, and ship a one-page playbook for new hires. The first two hires ramped to full quota in four months; the next four hires ramped in three months because the playbook was tighter. The pipeline shape held even as team doubled.

Inherited a messy pipeline

Scrub the pipeline, fix the forecast.

A new sales lead inheriting a messy pipeline runs a scrub in the first two weeks. Priyanka inherited a 240-opportunity pipeline where roughly 90 opps had no activity in 30+ days. She ran a Strkr Flow to flag the stale opps, worked with reps on a 1-on-1 basis to disqualify or revive each one, and ended the scrub at 118 active opportunities. The quarterly forecast dropped 35 percent in the scrub, which was uncomfortable for the exec team but accurate. The next quarter's forecast accuracy was within 8 percent, the best the team had hit.

Converting from services to product

Build a product sales motion from a services pipeline.

A 30-person services firm launching a product line needs a separate sales motion. Charles, the newly-hired product sales lead, built the pipeline in Strkr with the product sales stages distinct from the services pipeline, hired two AEs dedicated to product, and ran the product motion as its own pod. The services team continued to earn referrals into product; the product AEs ran a dedicated outbound motion. First-year product ARR hit $780K against a target of $600K because the dedicated motion did not compete with services engagement.

Standing up BDR team as separate function

Pipeline shape, handoff rules, comp plan.

A 12-rep team hitting velocity ceilings needed a dedicated BDR function. Rachel, the sales lead, used Strkr to build the BDR pipeline shape (prospect to SQL), define the handoff criteria to AE (meeting booked, qualification pass), and run the BDR comp plan on booked meetings plus qualified pipeline value. The BDR hire took two months. Pipeline volume to the AE team rose 60 percent in the next quarter, and the AE time on prospecting dropped 70 percent, which recovered 12 hours per AE per week for discovery and closing work.

Build the sales function on one platform.

Start a 14-day Strkr trial. CRM, routing, cadence, dialer, enrichment, proposal, marketing, reporting, AI drafting, admin and permissions on the flat per-seat line. See what a modern function looks like when the tools do not fight each other.

Common questions

What buyers in this bucket ask most.

What is sales in the simplest useful definition?

Sales is the function that moves a prospective buyer from unaware to signed, through a sequence of qualified handoffs. In B2B, that sequence usually includes prospecting (building a target list), outreach (opening a conversation), qualification (deciding whether to pursue), discovery (understanding the problem), technical validation (proving the product fits), proposal (scope and pricing), negotiation (terms and signature), handoff (transition to post-sale), and renewal/expansion (keeping the customer and growing the account). A healthy sales function has a documented process for each step, measures the conversion between steps, and uses tools (CRM, cadence, enrichment, reporting) to run the process consistently rather than relying on individual rep intuition.

How does the sales function differ from marketing?

Marketing creates awareness and interest at scale; sales converts that interest into revenue one deal at a time. Marketing owns the top of the funnel (brand, content, demand gen, lead generation) and the first qualification pass (MQL creation). Sales owns the deeper qualification (SQL and beyond), discovery, technical validation, proposal, negotiation, and signature. The handoff from Marketing to Sales (the MQL-to-SQL transition) is the single most-debated interface in B2B GTM teams because the two functions measure success differently. A healthy GTM team has an explicit shared definition of MQL and SQL, shared ownership of the handoff metrics, and a joint pipeline review cadence that keeps both teams accountable.

What is a reasonable pipeline-coverage ratio?

Pipeline coverage ratio is total open pipeline value divided by the quarterly target. Healthy mid-market B2B targets 3x to 4x coverage, meaning the pipeline value is three to four times the quarterly target. The ratio accounts for the fact that most opportunities will not close in the current quarter and some will not close at all. Enterprise B2B with longer cycles and lower win rates often needs 4x to 6x coverage. SMB B2B with shorter cycles and higher win rates often runs on 2x to 3x. The right ratio for a specific team comes from the historical win rate and the typical cycle length. Strkr pipeline coverage reports show the ratio against both the current-quarter target and the next-quarter target so the sales lead sees the forecast risk for the quarter after this one.

What are the common sales forecasting methods?

Four methods come up repeatedly. Commit-based: each rep flags deals they are confident will close, the manager aggregates. Weighted-stage math: each stage has a probability (10 percent to 90 percent), opportunity value times probability sums to expected revenue. Pipeline-coverage ratio: total open pipeline divided by target, with historical ratios applied. Historical close rate on current stage composition: look at how deals have historically closed from the current stage distribution. Each method gives a different number for the same pipeline. Strkr runs all four in parallel so the exec team sees the honest range (often a $200K to $400K spread on a $2M quarterly target), which is more useful than a single-point estimate that is probably wrong.

What qualification framework should a new sales team use?

The honest answer: whichever one the sales lead can get the team to actually use consistently. BANT (Budget, Authority, Need, Timeline) is simple and works for SMB velocity motions. MEDDIC and MEDDPICC add Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion, Competition, and Paper Process, which is deeper and fits enterprise. SPICED (Situation, Pain, Impact, Critical Event, Decision) is lighter and fits mid-market. The framework matters less than the discipline of running it on every opportunity. Strkr qualification fields are configurable per pipeline so a team running SMB inbound can use BANT and the same tenant running enterprise outbound can use MEDDPICC without a schema conflict.

How much should sales tooling cost per rep per month?

A mid-market B2B team running a typical stack (CRM, dialer, cadence tool, enrichment, meeting intelligence, proposal, reporting) spends $400 to $700 per rep per month across 6 to 10 vendors. That is before marketplace add-ons and before any custom-code or BI work. Strkr collapses most of that stack into one per-seat line at $60 to $80 per rep per month on the standard tier. The savings pay for a mid-level RevOps hire on a 40-rep team, which is often more impactful than the raw cost delta because the admin burden across 6 to 10 vendor contracts is itself a hidden cost of the sprawled stack. The right question for a sales lead costing out tooling is not "which single tool is cheapest" but "what's the fully loaded per-rep monthly cost including admin time."

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.