This page walks through the quote-to-cash process one step at a time: what happens at each step, who owns it, how long it takes, what tools come into play, and the decisions that have to clear before the deal advances. The reference covers the standard flow for mid-market SaaS and extends to the exception patterns (co-term adjustments, multi-year prepaid, custom usage caps) that handle 15 to 30 percent of real deals.
The quote-to-cash process reference guide most teams rely on comes from an analyst report, a vendor whitepaper, or a Slack conversation with someone who ran the process at their last company. The references usually describe the happy path at a conceptual level without the operator detail that someone running the process actually needs: what happens at each step in practical terms, who the named owner is, how long the step typically takes, what triggers the next step, what the decision criteria are, and what breaks when the step fails. This page is the operator reference. Each step is documented with the actions, the owner, the duration, the inputs, the outputs, the tooling, and the failure modes. The reference assumes the reader is a RevOps lead, Deal Desk manager, or Finance operator who needs to actually run the chain rather than describe it in a slide deck.
Gartner Q2C references describe stages at a conceptual level, saying the approval step routes the deal through the matrix. The reference does not say which fields the matrix reads, which approvers get the notification, what the SLA is, or what the fallback is if the approver is out of office. Operators running the process need the mechanical detail, not the conceptual framing.
Salesforce Q2C references describe the process as it runs in Salesforce Revenue Cloud. Zuora Q2C references describe it as it runs in Zuora. The references are useful if the reader runs that specific stack, but they miss the mechanics for the capabilities the vendor does not sell. A vendor-neutral step reference covers the full chain regardless of tooling.
Most Q2C step references cover the happy path (standard discount, standard contract, standard billing cadence, standard recognition) and skip the exception patterns that handle 15 to 30 percent of real deals. The exceptions are where operators actually need the reference. A useful reference covers both.
Step references typically describe what happens but not who does it. For an operator writing the process documentation or onboarding a new hire, the named owner per step (deal AE, Deal Desk analyst, Legal reviewer, Order Management specialist, Billing admin, Revenue Accountant) is what makes the reference actionable.
Step references rarely include the typical duration. An operator sizing capacity or diagnosing a cycle time drag needs the benchmark: quote-to-send typically 4 to 24 hours, approval 12 to 36 hours, contract 3 to 7 business days, order management 2 to 24 hours, invoice generation hours, payment 32 to 48 days DSO, recognition 2 business days. The benchmarks make the reference measurable.
Step references rarely document the failure modes: approval timeout with no backup chain, contract signature stuck in a shared mailbox, provisioning webhook timing out, payment processor returning an unexpected response code, GL posting rejecting an entry. Operators need the failure modes to design the escalation paths and the exception workflow.
The reference breaks the Q2C process into twelve steps. Each card below covers the mechanics: the action, the owner, the duration, the input, the output, and the typical tooling. The steps assume a mid-market SaaS running an annual-subscription motion with professional services as a separate line.
Action: the Account Executive confirms budget range, pricing fit, and the tier the buyer will land on. Owner: AE. Duration: hours to days as part of the sales motion. Input: discovery notes and the buyer budget. Output: the pricing target for the quote. Tooling: CRM opportunity record.
Action: AE opens the CPQ quote builder with the account firmographics and product history pre-filled. Products pull from the catalog with pricing applied automatically. Owner: AE. Duration: 10 to 60 minutes for standard configurations. Input: pricing target and product mix. Output: configured quote draft. Tooling: CPQ engine.
Action: AE submits the configured quote. The approval matrix fires based on discount percent, deal size, product mix, term length, and legal red-line count. Owner: AE submits, Deal Desk routes. Duration: minutes to initiate. Input: configured quote. Output: approval chain started. Tooling: CPQ approval engine.
Action: approvers review the quote with context (ARR, segment, discount, product mix) and clear or reject. Routing goes to Deal Desk, Sales Manager, VP Sales, CRO, CFO per the matrix. Owner: approvers per the matrix. Duration: 12 to 36 hours for standard tiers, 3 to 9 days for CRO or CFO. Output: approved quote. Tooling: CPQ approval engine.
Action: approved quote triggers contract generation. The order form generates for every deal. The MSA generates for first-time customers or MSA refresh. The DPA generates for EU customers or healthcare data. The SOW generates for professional services deals. Owner: Legal (templates), AE (generation trigger). Duration: minutes to generate, hours to review. Output: draft contract set. Tooling: CLM.
Action: for deals with customer-requested contract changes, Legal reviews the red-lines with the risk assessment and the pricing adjustment if required. Pre-approved deviations clear without GC involvement. Non-standard changes route to the GC. Owner: Legal Ops reviewer, GC on escalation. Duration: 2 to 7 business days typical. Output: cleared contract. Tooling: CLM.
Action: contract routes for electronic signature via native integration, DocuSign, or PandaDoc. Buyer countersignatures (procurement, legal, authorized signer) capture per the buyer process. Seller countersignature follows. Owner: AE monitors, buyer signs, seller countersigns. Duration: 2 to 5 business days typical. Output: fully executed contract with signature audit certificate. Tooling: signature platform.
Action: signed contract flips the deal stage to closed-won. Notifications fire to CSM team, Order Management, and Finance. The deal record locks against further changes without a change order. Owner: AE marks, automation fires. Duration: minutes. Output: deal in closed-won state with notifications sent. Tooling: CRM, workflow engine.
Action: closed-won fires three parallel paths. Provisioning webhook fires to the product platform. Billing schedule creates with the contract terms. CSM assignment goes to the account. Owner: Order Management orchestrates, Product team receives webhook, Finance receives billing setup, CSM lead assigns. Duration: 2 to 24 hours automated. Output: product available, billing configured, CSM assigned. Tooling: order management, product platform, billing engine.
Action: billing engine issues the first invoice per the configured cadence. Immediate for annual prepay. Net 30 for monthly. Custom for enterprise. The invoice carries contract terms, line items, and payment instructions. Owner: Billing Operations. Duration: minutes for standard cadences. Output: invoice delivered to buyer. Tooling: billing engine, email delivery.
Action: payment captures via the configured method. Failed payments route to dunning with per-processor response-code handling. Soft declines retry on the 24-hour cadence. Hard declines route to AR with human review. Owner: Billing Operations, AR on escalation. Duration: 32 to 48 days DSO typical for mid-market SaaS. Output: cash received or AR escalation. Tooling: payment processor, dunning engine.
Action: ASC 606 schedule generates per contract with performance-obligation identification, transaction-price allocation, and recognition over the delivery period. Schedule runs per month or per service period close. GL feed posts recognized revenue, deferred revenue, and AR entries to NetSuite, Sage Intacct, Xero, or QuickBooks. Owner: Revenue Accounting. Duration: 2 business days automated. Output: recognized revenue posted to GL. Tooling: revenue recognition engine, GL system.
The twelve steps describe the standard flow. Real-world deals carry variants that modify specific steps. The cards below are the common deal types with the step modifications.
Variant: step 10 fires on contract execution rather than per cadence. The buyer prepays the full annual value. Step 12 recognizes revenue ratably over the 12-month term with the deferred revenue booking at execution and the ratable release monthly. The pattern simplifies cash forecasting but requires the deferred revenue tracking.
Variant: step 10 fires on the configured monthly cadence with net 30 terms. Step 11 captures payment on the 30-day cycle. Step 12 recognizes revenue monthly as the service delivers. The pattern simplifies billing but creates working capital drag relative to annual prepay.
Variant: contract carries a 2 or 3 year term with annual billing cycles. Step 10 fires annually on the anniversary with the pricing adjustment per the escalator clause (CPI, fixed percent, or custom). Step 12 recognizes revenue ratably over the full term with the deferred revenue adjustment per billing cycle.
Variant: step 10 fires monthly on the usage rollup from the product platform. Billing engine captures the metered consumption, applies the committed-minimum logic, and generates the invoice. Step 12 recognizes revenue on consumption rather than ratably, with the committed minimum recognized ratably over the committed period.
Variant: step 5 generates a Statement of Work rather than a standard order form. Step 10 fires on milestone acceptance (milestone billing) or monthly against logged hours (T&M). Step 12 recognizes revenue at milestone acceptance (point-in-time) or over the delivery period (percentage-of-completion) depending on the deliverable.
Variant: a customer on an existing contract expands mid-term. Steps 1 through 7 run as a modified flow with the existing contract as the parent. Prorated billing fires on the delta. Step 12 adjusts the recognition schedule with the incremental deferred revenue booking. The parent contract links to the expansion for audit continuity.
Each step has specific failure patterns that operators need to anticipate. The cards below are the six common failure patterns with the typical cause and the resolution path.
Pattern: an approver is out of office with no backup chain configured. The quote sits in the approval queue. Cause: backup chain not configured for the approver. Resolution: route to the backup approver and update the backup chain. Prevention: quarterly review of backup chain coverage.
Pattern: contract routed to the buyer sits unsigned for 10+ days. Cause: wrong buyer signer, procurement review stalled, or buyer dormancy. Resolution: AE outreach to the buyer signer with escalation to the buyer executive sponsor. Prevention: signer verification during the sales motion.
Pattern: closed-won fires the provisioning webhook and the product platform returns an error. Cause: data mismatch (account ID conflict, feature flag conflict), rate limiting, or platform downtime. Resolution: webhook retry with manual CSM intervention if retry fails. Prevention: pre-close data validation.
Pattern: buyer receives the invoice and rejects for data error (wrong PO number, wrong billing address, wrong tax jurisdiction, wrong contract terms). Cause: data mismatch between CRM, contract, and billing engine. Resolution: issue credit memo and reissue with corrected data. Prevention: billing data validation at contract execution.
Pattern: payment attempt returns a hard decline with fraud flag. Cause: card expired, card reported stolen, buyer bank fraud rules. Resolution: AR outreach to the buyer for alternate payment method. Prevention: dunning sequence with per-processor response-code handling, buyer-side payment method update workflow.
Pattern: GL feed submits the recognition entry and NetSuite returns a validation error. Cause: chart of accounts mismatch, closed period, journal entry imbalance. Resolution: investigate the validation error and resubmit. Prevention: GL mapping validation at month-end close dry run.
The practical difference between Strkr and the stitched 5-vendor stack shows up in how each step runs: single tool with one data model versus multiple tools with handoff friction:
| Feature | Strkr | Stitched 5-vendor Q2C stack |
|---|---|---|
| Steps 1 to 4 (quote and approval) | Native CPQ with visual rule tree | Salesforce CPQ + Advanced Approvals |
| Steps 5 to 7 (contract and signature) | Native CLM with per-customer memory | DocuSign CLM separate |
| Step 8 to 9 (closed-won and order) | Automated handoff within hours | Manual CSM assignment, 2 to 10 days |
| Step 10 (invoice) | Native billing engine | Zuora or NetSuite SuiteBilling |
| Step 11 (payment and dunning) | Per-processor response handling | Chargebee or custom script |
| Step 12 (recognition and GL) | ASC 606 schedule native | RightRev or Zuora RevPro |
| Owner visibility | One record per deal | Owner per tool |
| Step duration tracking | Instrumented per step | Not instrumented across tools |
| Failure mode handling | Documented workflow per pattern | Slack channel exception resolution |
| Audit evidence | Full chain on one record | Scattered across 5 tools |
The common pattern: use the step reference as the training material, the process documentation, and the diagnostic tool for cycle time analysis. The playbooks below are motions live on customer accounts.
A SaaS at 110 reps had a stale process runbook that nobody read. The new VP of RevOps used the Strkr step reference as the template for the refreshed runbook with the owners, durations, and tooling mapped to the company roles. The runbook became the primary training material for new RevOps hires.
A SaaS at 85 reps had Q2C cycle time at 28 days. The team activated the Strkr step duration tracking and found Step 7 (signature capture) running at 7.3 days average and Step 11 (payment capture) at 51 days DSO. Both exceeded benchmark significantly. Addressing both cut the cycle to 15 days over 2 quarters.
A SaaS at 65 reps launching a usage-based product line mapped the step modifications before go-live: Step 10 fires monthly on usage rollup rather than annual prepay, Step 11 captures payment on net 30, Step 12 recognizes on consumption rather than ratably. Mapping the modifications surfaced the billing engine configuration needed before launch.
A SaaS at 140 reps built specific resolution playbooks for the six common failure patterns (approval timeout, contract stuck, provisioning webhook failure, invoice rejection, payment hard decline, GL posting rejection). The playbooks reduced the average failure resolution time from 2.4 days to under 4 hours.
A SaaS at 95 reps running a strong expansion motion documented the co-term expansion as specific step modifications: parent contract link, prorated billing on the delta, incremental deferred revenue booking, recognition schedule adjustment. Documentation surfaced two edge cases in the recognition logic that the team then fixed in the configuration.
Start a 14-day trial with the full twelve-step Q2C process configured: step owner mapping, duration benchmarks, parallel path handling, exception workflow, failure mode playbooks, and the full audit chain per deal. The reference serves as the training material for new hires and the diagnostic tool for cycle time analysis.
The reference quote-to-cash process has twelve steps: (1) pricing conversation (AE confirms budget and pricing fit), (2) configure quote (AE opens the quote builder, products pull from catalog with pricing applied), (3) submit for approval (approval matrix fires on discount and deal size), (4) approvals clear (approvers review and clear in sequence or parallel), (5) generate contract (order form, MSA, DPA, SOW from templates), (6) legal review on red-lines (customer-requested changes route through Legal), (7) signature capture (buyer and seller sign via DocuSign, PandaDoc, or native), (8) closed-won advance (deal stage flips, notifications fire), (9) order management handoff (provisioning, billing setup, CSM assignment), (10) first invoice (billing engine issues the first invoice), (11) payment capture and dunning (payment captures via Stripe, ACH, wire, or check), and (12) revenue recognition and GL posting (ASC 606 schedule generates and journal entries post).
The typical owner mapping for the twelve Q2C steps: Step 1 pricing conversation (AE), Step 2 configure quote (AE), Step 3 submit for approval (AE submits, Deal Desk routes), Step 4 approvals clear (approvers per the matrix including Deal Desk, Sales Manager, VP Sales, CRO, CFO), Step 5 generate contract (Legal owns templates, AE triggers generation), Step 6 legal review on red-lines (Legal Ops reviewer with GC escalation), Step 7 signature capture (AE monitors, buyer signs, seller countersigns), Step 8 closed-won advance (AE marks, automation fires), Step 9 order management handoff (Order Management orchestrates with Product, Finance, CSM lead receiving), Step 10 first invoice (Billing Operations), Step 11 payment capture (Billing Operations with AR on escalation), and Step 12 revenue recognition and GL posting (Revenue Accounting). The named owners vary by company structure but the role mapping is consistent across mid-market SaaS.
Typical duration benchmarks for the twelve Q2C steps: Step 1 pricing conversation (hours to days during sales motion), Step 2 configure quote (10 to 60 minutes for standard), Step 3 submit for approval (minutes to initiate), Step 4 approvals clear (12 to 36 hours standard tiers, 3 to 9 days CRO or CFO), Step 5 generate contract (minutes to generate), Step 6 legal review on red-lines (2 to 7 business days), Step 7 signature capture (2 to 5 business days typical), Step 8 closed-won advance (minutes), Step 9 order management handoff (2 to 24 hours automated or 2 to 10 days manual), Step 10 first invoice (minutes for standard cadences), Step 11 payment capture (32 to 48 days DSO for mid-market SaaS), and Step 12 revenue recognition and GL posting (2 business days automated or 7 to 21 days manual). The full-cycle median for teams running Q2C on one surface is 11 to 23 days, versus 23 to 41 days for teams running a stitched 5-vendor stack.
The six common Q2C failure modes: (1) approval timeout where an approver is out of office with no backup chain configured, resolved by routing to backup and updating the chain, (2) contract stuck in signature where the buyer side has not countersigned in 10+ days, resolved by AE outreach to buyer signer with executive sponsor escalation, (3) provisioning webhook failure where the product platform rejects the webhook due to data mismatch or rate limiting, resolved by webhook retry with manual CSM intervention if needed, (4) invoice rejection where the buyer rejects for data error (wrong PO, wrong address, wrong terms), resolved by credit memo and reissue with corrected data, (5) payment hard decline where the credit card is declined with fraud flag, resolved by AR outreach for alternate payment method, and (6) GL posting rejection where NetSuite rejects the journal entry for chart of accounts mismatch or closed period, resolved by investigating the validation error and resubmitting. Mature teams document resolution playbooks per failure pattern.
Strkr implements the twelve Q2C steps on one surface with the step owner, duration tracking, failure mode handling, and audit evidence per step. Steps 1 to 4 run on the native CPQ with the visual rule tree for approvals. Steps 5 to 7 run on the native CLM with per-customer previously-negotiated clause memory and signature via native integration, DocuSign, or PandaDoc. Steps 8 to 9 fire automatically with the full handoff chain (provisioning webhook, billing setup, CSM assignment) running within hours of closed-won. Step 10 runs on the native billing engine with subscription, usage-based, one-time, and hybrid patterns. Step 11 runs with dunning configured per-processor for response-code handling. Step 12 runs the ASC 606 schedule per contract with the GL feed to NetSuite, Sage Intacct, Xero, or QuickBooks. The full chain lives on one record per deal with the step duration, control gate evidence, and failure handling visible.
Different deal types modify specific steps while leaving the overall twelve-step structure intact. Annual prepay deals fire Step 10 on contract execution rather than per cadence, with Step 12 recognizing ratably over 12 months. Monthly subscription deals fire Step 10 on the monthly cadence with net 30 terms. Multi-year with annual billing locks the term and fires Step 10 annually on anniversary with pricing adjustments per the escalator clause. Usage-based deals fire Step 10 monthly on the usage rollup from the product platform with Step 12 recognizing on consumption. Professional services SOW deals replace the standard order form in Step 5 with a Statement of Work and fire Step 10 on milestone acceptance or monthly against logged hours. Co-term expansion deals run Steps 1 through 7 as a modified flow with the parent contract linked and prorated billing on the delta.
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.
