Feature · Sales Process Workflow

A sales process workflow the system actually enforces.

A sales process workflow is the sequence of stages, criteria, and handoffs a deal travels through from first contact to signed order. Strkr lets you build the workflow visually, attach entry and exit criteria to each stage, and automate the handoffs. Every deal follows the same path. Every stage transition is auditable. Every rep knows the next step.

Start free trial See pricing
What a sales process workflow is

Stages, gates, and the honest definition of done.

A sales process workflow is the written contract between sales, marketing, and operations about how a deal moves. The contract has stages, entry criteria for each stage, exit criteria, and handoffs. Strkr turns the contract into executable workflow instead of a slide deck nobody reads.

Stages

The named steps a deal moves through.

The workflow defines the stages: Qualify, Discovery, Proposal, Negotiate, Closed Won, Closed Lost. Each stage is a node on the workflow with an owner role, a target duration, and a set of expected activities. The named steps are the backbone of the forecast rollup.

Entry criteria

What has to be true to enter the stage.

A deal enters Discovery only when the Qualify checklist is complete: budget signal captured, decision timeline, pain confirmed. The entry criteria replace the "move it to Discovery because the quarter needs it" promotion. The system holds the line.

Exit criteria

What has to be true to leave the stage.

A deal leaves Proposal when the signed scope, legal review, and close plan are in place. The exit criteria are the stage-completion checklist. The rep knows the list. The manager audits the list. The forecast rolls up on the list.

Handoffs

Rep to SE, SE to deal desk, deal desk to legal.

Workflow steps include the handoffs between roles: AE to Solutions Engineer at Discovery, SE back to AE at proposal, AE to deal desk at Negotiate, deal desk to legal for redlines. Each handoff is a task assigned by the workflow, not a Slack ping.

Target duration

Days-in-stage threshold per stage.

Each stage carries a target duration that drives aging alerts. Qualify at 7 days, Discovery at 14, Proposal at 21. Deals above the threshold light up on the pipeline dashboard and prompt a manager conversation. The thresholds come from the workflow, not from a dashboard setting.

Loss path

Reason, learning, archive.

The loss path is a stage, not an escape hatch. The exit criteria are: loss reason categorized, deal-notes recap captured, competitor flagged, archive. Loss data becomes training for the next similar deal via Strkr AI pattern surface.

How the workflow is built

Visual builder, versioning, and go-live.

The sales process workflow is built in a visual builder that non-admins can read. Changes land as a draft version, go through a review step, and publish to the live workflow. The sections below are the mechanics.

Visual builder

Nodes, edges, criteria panels.

The builder renders the stages as nodes and the transitions as edges. Click a node to open the criteria panel. Add fields, document checks, activity requirements, or custom validators. The builder is the readable artifact - a VP of Sales can read the workflow without a developer.

Versioning

Draft, review, publish.

Every workflow change lands as a draft. The sales ops lead builds the change, the VP reviews, the system publishes. Old deals finish on the old version. New deals start on the new version. No "we changed the process yesterday and nobody told the reps."

Criteria validators

Field-level, document-level, activity-level.

An exit criterion can be a field value, a document attached, an activity completed, or a custom validator written against the deal. Strkr ships the common validators and lets the sales ops lead add org-specific ones. The validator runs on the stage transition.

Automated handoffs

The workflow assigns the next task.

When a deal enters Discovery the workflow auto-assigns the discovery call task to the owner. When the discovery exits, the workflow auto-assigns the SE scoping task to the pod SE. The handoffs are deterministic, not a Slack ping.

Permission on stage change

Who can promote, who can push back.

The workflow enforces who can move a deal between stages. A rep can promote within their book. A manager approval is required to skip a stage. Legal is the only role allowed to flip Negotiate to Closed Won. The permission matrix is the workflow's own.

Audit trail

Every transition, with who and when.

Every stage transition is written to the deal's audit timeline with user, timestamp, and criteria state. Pipeline reviews read the audit when a deal is unclear. The audit is also the forecasting evidence base for the executive report.

How teams use the workflow

Design, enforce, learn, iterate.

The sales process workflow is a living artifact. A sales team designs it in the first month, enforces it in the next six, and iterates on it every quarter from loss-reason data. The sections below walk the actual lifecycle.

Design workshop

Two days with sales, marketing, SE, legal.

The workflow starts as a workshop. The RevOps lead facilitates with sales, marketing, SE, and legal in the room. The output is a stage list, a criteria list per stage, and a role matrix for handoffs. Strkr's builder is the artifact of the workshop.

Go-live and training

The reps know the gates.

The workflow goes live after a half-day rep training. The reps understand the entry and exit criteria. The manager runs the first two weeks of pipeline reviews with the criteria panel open on screen. The reps internalize the gates.

Weekly enforcement

Pipeline reviews use the criteria.

Every pipeline review opens the workflow criteria panel. Deals without criteria met do not pass stage review. The manager stops using willpower and starts using the system. The one-on-ones shift from reminding to coaching.

Monthly loss review

Loss reasons feed the next iteration.

Monthly loss review opens the losses by reason and by stage. Patterns surface: too many Proposal-stage losses to competitor X, too many Qualify-stage losses on no-budget. The workflow team updates criteria to catch the signal earlier. Strkr AI flags recurring loss patterns automatically.

Quarterly iteration

Version two, three, four.

The workflow versions quarterly. Each version is a readable diff from the previous. The RevOps lead publishes the new version with a changelog. Reps read the changelog. Managers run the next review on the new criteria.

New-hire ramp

The workflow is the onboarding doc.

A new rep ramps by reading the workflow. The stages, criteria, and handoffs are the sales motion. The onboarding call is a workflow walkthrough. The ramp time compresses because the system teaches the process, not a tribal-knowledge PDF.

What this replaces

The slide deck and the honor system.

Most sales orgs document the sales process in a slide deck, a sales playbook, and a wiki page. The documentation is read once and ignored. The actual process is tribal knowledge. Strkr's workflow replaces the honor system with an enforceable artifact.

Slide-deck playbook

Readable, unenforced.

The sales playbook deck is a sales-enablement standby. It is read at onboarding and never again. Reps default to their own motion by month three. Strkr's workflow makes the deck executable: criteria are enforced in the record, not read on a slide.

Honor-system CRM

Every rep plays by their own rules.

Many CRMs have stages but no criteria. Reps advance deals by habit and the forecast is a wish. Strkr's workflow enforces criteria on transition. The forecast firms up because the stage definitions are shared.

Salesforce flows

Powerful, admin-only, fragile.

Salesforce can enforce stage criteria with Flows and validation rules. The build requires a Salesforce admin. Every change is a release. Strkr's workflow is readable by the VP, editable by the sales ops lead, and testable in a draft version without a release train.

HubSpot pipeline rules

Credible, bundled, limited at scale.

HubSpot Sales Hub Pro has stage probabilities and required fields. The capability is credible for mid-market teams. Multi-pipeline enforcement, role-aware handoffs, and criteria validators at the depth of enterprise sales are limited. Strkr's workflow scales.

Make.com or Zapier

Possible, brittle, invisible to reps.

Teams sometimes glue stage automation together in Zapier or Make. The scenarios work until they do not, the audit is in the Zapier log, and the reps have no visibility. Strkr's workflow runs native in the record and audits in the deal timeline.

Strkr

Visual, enforceable, native.

The sales process workflow is included on every paid Strkr tier. Visual builder, criteria validators, automated handoffs, permission matrix, versioning, and audit. The seat price covers it. No add-on, no admin tax.

Build the sales motion once. The system enforces it on every deal.

Start a free trial, open the workflow builder, pick a starter template, and publish version one. Then run the next pipeline review with the criteria panel open on screen.

Start free trial See sales workflow
Common questions

What buyers ask about this feature.

What is a sales process workflow?

A sales process workflow is the written and enforced sequence of stages, entry and exit criteria, and handoffs that every deal moves through from first contact to signed order. It is the shared contract between sales, marketing, and operations about how deals progress. In Strkr the workflow is a visual, versioned, enforceable artifact - criteria validators run on stage transitions, handoffs auto-assign the next task, and every transition writes to the deal audit timeline. The workflow replaces the slide-deck playbook with executable process.

How is it different from a sales pipeline?

A sales pipeline is the collection of open deals and their stages. A sales process workflow is the rulebook that governs how those deals move. The pipeline is the inventory, the workflow is the production line. Many CRMs ship a pipeline without a workflow, which means stages exist but criteria do not - the forecast rolls up on vibes. Strkr ships both: the pipeline as the record of deals, and the workflow as the enforceable motion.

Can we have different workflows per segment or product?

Yes. Strkr supports multi-pipeline, and each pipeline carries its own workflow. SMB new business runs a short workflow with lower-stakes gates; enterprise new business runs a longer workflow with legal and deal-desk handoffs; renewal runs a renewal-shaped workflow. The sales ops lead builds each as a version and publishes it. Deals route to the pipeline that matches segment and product.

What happens to a deal when the workflow changes?

Workflow changes land as a draft version. On publish, new deals start on the new version. In-flight deals finish on the version they started on, unless the sales ops lead explicitly migrates them. This versioning model prevents the "we changed the process yesterday and the forecast is now wrong" problem. The audit timeline on a deal records which workflow version governed each stage transition.

Can the workflow enforce stage criteria?

Yes. Each stage transition carries entry and exit criteria. Criteria can be field values, documents attached, activities completed, or custom validators written against the deal. On transition, the validators run and either allow the move, block it with a reason, or require a manager approval. The enforcement is where the workflow stops being a slide and starts being a system.

Is the workflow included on every tier?

Yes. The visual builder, criteria validators, automated handoffs, permission matrix, versioning, and audit are included on every paid Strkr tier. Multi-pipeline workflow (different workflows per product or segment) is included on Pro and above. Strkr AI loss-pattern surfacing is included on tiers that bundle Strkr AI. There is no separate automation SKU, no credit meter on transitions, and no per-workflow charge.

Related features

Pair this with...

Sales Workflow Sales Process Automation Sales Pipeline Management Sales Pipeline Sales Pipeline Dashboard Sales Forecast

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