Quick Snapshot: Your Current Quoting Rhythm

• How many complex quotes does your team produce in a typical month? Options: 1–10, 11–50, 51–200, 200+
• Tell me about the last time a quote took longer than your target turnaround, what happened and who was involved?
• Which product lines or assemblies create the most quoting complexity for your reps? Options: Multi-level assemblies with nested options, Field-configured products, Custom-engineered solutions, Service bundles, Other
• How many people typically touch a complex quote from first draft to customer delivery? Options: 1, 2–3, 4–6, 7 or more
• Which tools does your sales team reach for first when they need to configure or price a nonstandard deal? Options: Spreadsheets, Email to engineering/pricing, CRM product records, Internal custom tool, Paper or drawings, Other
• What revenue or cost impact do you estimate quote delays and configuration errors will have this fiscal year? Options: Under $100k, $100k–$500k, $500k–$2M, Over $2M, Unsure

Where Configurations Break and Why It Matters

• Which recurring configuration mistake costs you the most, whether in rework, lost deals, or expedited freight? Options: Incorrect BOM nesting, Invalid option combinations, Missing dependencies or exclusions, Wrong lead times causing delivery misses, Pricing errors tied to configuration, Other
• Give a recent example of a configuration error that reached manufacturing or the customer, and describe the downstream cost or consequence.
• How often do configuration errors appear in your top 10 most complex quotes? Options: Almost every time, Often, Occasionally, Rarely, Never
• Who typically detects these errors, and at which point in the workflow do they show up most often? Options: Sales rep during configuration, Sales engineer during review, Quotation reviewer after submission, Manufacturing during build, Customer on delivery, Other
• What single unresolved configuration rule or data gap would prevent you from running a pilot that loads your catalog and tests real quotes? Options: Missing documented BOM logic, No access to price lists, Critical option dependencies undefined, Approval matrix unavailable, None of the above

Approval Chains That Stall Deals

• Which role or committee most often creates the approval delay that stalls a quote, and why does that gate exist? Options: Sales manager, Pricing committee, Finance, Legal, Engineering, Other
• How many manual approval steps does a typical nonstandard quote require today? Options: None, 1–2, 3–4, 5 or more
• When approvals slide over a weekend or holiday, how often do you lose a deal or miss a delivery window as a result? Options: Frequently, Sometimes, Rarely, Never
• Describe any approval thresholds tied to margin, customer, or product type that require human sign off.
• Which missing approval governance or capability would stop you from automating approvals in a pilot? Options: Role definitions unclear, Approval hierarchy incomplete, No single source of pricing truth, Security or compliance constraints, None of these

The Sales Experience — Will Reps Use It?

• If the new quoting flow feels slower than the spreadsheet they know, how quickly will reps abandon it and revert to old habits? Options: Immediately, Within weeks, Over months, They will not abandon
• How do reps currently trade speed for correctness, and which tradeoffs have caused the biggest business problems?
• Which measures matter most to you for adoption, pick any that apply? Options: Time per quote, Number of touchpoints, Quote accuracy rate, Rep satisfaction, Proposal completion rate, Other
• Do you have a group of early adopter reps or sales engineers who will pilot a new flow, and who would they be? Options: Yes, defined group exists, Yes, but need to identify, No, we need to recruit, Not sure
• If a pilot reduced turnaround by 50 percent and removed configuration errors from pilot quotes, what internal barrier could still stop you from moving to rollout that week? Options: Budget approval, Procurement cycle, Operational readiness, Leadership alignment, Nothing would stop us

Costs, Risks, and What Keeps You Up at Night

• Which single cost or risk associated with quoting would, if fixed, pay for a platform like this within a year? Options: Manufacturing rework and scrap, Lost deals to faster competitors, Contract compliance penalties, Excessive discounting, High quote engineering hours
• How do configuration errors or discount slips show up in your financial reports, and who on your team feels the impact most directly?
• When a quote error causes a customer escalation, what is your average remediation cost including labor, expedited parts, and penalties? Options: Under $10k, $10k–$50k, $50k–$150k, Over $150k, Unsure
• Have you run any internal estimates of time saved or margin preserved by reducing configuration errors, and if so, what did they show? Options: Yes with quantified estimate, Yes but qualitative only, No estimate yet, Unsure
• Which risk would kill the project for you, if it could not be mitigated? Options: Data security concerns, Broken integration to ERP, Inability to express product rules, User adoption failure, Budget constraints

Alternatives You're Considering

• If you could keep your current approach and fix one thing to make it work, what would that be?
• Which of these options are you actively evaluating right now? Options: Continue spreadsheet and email process, Upgrade or configure existing CPQ, Purchase a new CPQ vendor, Build an internal solution, Outsource quoting, Do nothing
• Has anyone on your team proposed building the solution internally instead of buying, and what resource commitment would that require? Options: Yes, with budget estimate, Yes, no estimate yet, No internal build proposed, Unsure
• What would have to be true about your current approach for you to keep it rather than change to an external platform? Options: Faster turnaround, Zero configuration errors, Lower total cost, Less maintenance effort, Clear ownership of pricing rules
• Which vendor or internal option looks most attractive today if it meets your needs perfectly? Options: Your incumbent CPQ, Another CPQ vendor, Internal build, Stick with spreadsheets, Unsure

Readiness: Data, Integrations, and Team Constraints

• Which integration gap would stop a project before it starts, for example no API access to ERP or product data trapped in PDFs? Options: No ERP API, Product data in unstructured documents, No access to approval system, No sandbox environment, None of these
• Which systems would we need to connect to for a meaningful pilot, select all that apply? Options: ERP, CRM, PLM or PDM, Pricing database, Document generation, Approval workflow tool
• Who owns the integrations and will they be available to support a pilot in a test environment? Options: Internal IT team, Third-party integrator, Product operations, No clear owner yet, Unsure
• How clean and accessible is the product catalog data we would need to load for pilot quotes? Options: Ready and structured, Mostly ready with gaps, Scattered across sources, Unstructured or unavailable, Unsure
• Is there an executive or compliance gate that must clear before we can load your catalog into a test environment? Options: Yes, No, Not sure

Measuring Success and Acceptance Criteria

• Which single metric must move in the pilot for you to consider a rollout? Options: Quote turnaround time, Quote accuracy or error rate, Number of touchpoints, Time sales engineers spend on quotes, Margins preserved
• What target reduction in quote turnaround would you consider a clear win for the pilot? Options: 10–25%, 25–50%, 50–75%, 75% or more, No specific target
• How many reps and which roles should participate in the pilot to give you confidence in results? Options: 1–3 reps, 4–6 reps, 7–12 reps, Entire sales team
• Who will have the final authority to approve progression from pilot to paid rollout, and what would block that person? Options: VP Sales Operations, CRO, Head of Finance, Procurement, Cross-functional committee
• If the pilot hits the target metrics, what internal step would accelerate you to sign within 30 days? Options: Pre-approved budget, Simple procurement terms, Executive sponsorship confirmed, Reference from similar customer, Nothing would accelerate us

Next Steps, Timelines, and Potential Deal Stoppers

• If a pilot proves the platform delivers the promised time and accuracy, what single internal obstacle could still prevent procurement from moving forward? Options: Budget cycle timing, Procurement terms, Legal or compliance requirement, Lack of operational owners, Nothing would prevent it
• What is your ideal pilot scope from a product line perspective, and why that line? Options: Most complex product line, Mid-complexity representative line, Simple line for fast wins, Multiple lines
• If you could commit to a pilot today, when would you want it to start? Options: Immediately, In 2 weeks, In 1 month, In 2–3 months, Unsure
• Who needs to be involved from your side during the pilot execution, select all that apply? Options: Sales reps, Sales engineers, Product operations, IT/integration owners, Finance, Executive sponsor
• Are there any nonnegotiable contractual, security, or compliance requirements we should know about before building a proposal? Options: Yes, security/IT requirements, Yes, procurement terms, Yes, compliance or regulatory, No nonnegotiables, Unsure

• Solution Experience — Configuration & Pricing Walkthrough

• Confirm the current state and its cost
• You confirm the demonstrated workflow would have prevented the configuration error that caused the $150,000 rework.
• Provide three of your most complex product scenarios, including one that resulted in manufacturing rework, within three business days.
• You confirm the demonstrated workflow reduces quote turnaround from days to hours and cuts the number of manual steps for the shown scenario.
• Walk through a buyer scenario to prove configuration enforcement
• Provide the product catalog extract, pricing rules spreadsheet, and approval matrix required to run the trial within five business days.
• You agree on the remaining evidence required before a decision and who must participate in the five-rep evaluation trial.
• Apply pricing rules and approval automation to the same scenario
• Load the provided catalog, pricing rules, and approval matrix into the platform and run the five-rep side-by-side trial, delivering accuracy, turnaround time, and step-count results before the follow-up review.
• Identify the five reps who will run the trial and confirm their availability for the trial window.
• Compare quote turnaround, accuracy, and steps vs your current process
• Schedule the follow-up review to present the trial results and decide next steps.
• Validate the future state

• Solution Experience — Configuration & Pricing Walkthrough
• Solution Experience Deck
• Solution Experience Brief

• meeting
• slides
• document

• Import and Normalize Product Catalog with Multi-Level BOM
• Translate Spreadsheet Pricing Rules into Platform Logic
• Author Configuration Rules, Dependencies, and Exclusions
• Configure Discount Governance and Automated Price Calculations
• Implement Approval Matrix and Automated Approval Flows
• Build Guided Sales Configuration UI for Reps
• Generate Branded Proposal Templates and Document Exports
• Configure Buildability Validation and Manufacturing Constraints
• Provision Role-Based Access and Permission Controls
• Deploy Admin Tools for Ongoing Product Rule Maintenance
• Configure Discount and Margin Visibility Dashboards
• Integrate Quote Handoff with Source CRM

Import and Normalize Product Catalog with Multi-Level BOM

• How many SKUs in your product catalog CSV need multi-level Bill of Materials (BOM) import? Options: Less than 500, 500-2,000, 2,000-10,000, More than 10,000
• Identify product families in your catalog that require nested assemblies (for example: power packs, chassis, and subassemblies). List product family IDs or file paths.
• Provide the primary file format you will upload for catalog import (for example product_catalog.xlsx, catalog_export.csv, or PLM export JSON). Options: Spreadsheet (XLSX/CSV), PLM export (XML/JSON), ERP export (CSV), Other
• Where are the master BOMs currently maintained for your flagship product line (PLM, ERP BOM table, engineering spreadsheets)? Options: PLM, ERP, Engineering spreadsheet, Other
• What acceptance criteria will confirm a successful catalog import for your product families (for example: SKU count match, BOM parent-child links preserved, and assembly level parity)?

Translate Spreadsheet Pricing Rules into Platform Logic

• Name the pricing spreadsheets or worksheets that contain your list price, cost, and waterfall logic (provide file names or folder paths).
• List the top three pricing rules in your spreadsheet that are hardest to reproduce (for example tiered volume tie-breakers, geographic surcharges, or bundled-component discounts).
• Provide an export sample of a pricing rule worksheet that shows cost, margin floor, and promotional adjustments (attach a redacted file or paste a few rows).
• How will you verify pricing parity during the trial using your exported quote samples (define an acceptable variance threshold and sample size, for example: <=0.5% variance on 95% of sample quotes)? Options: <=0.5% on 95% of samples, <=1% on 95% of samples, Custom threshold (describe)
• Who currently maintains the pricing formulas in your spreadsheet and who will be the platform contact for ambiguous calculations?

Author Configuration Rules, Dependencies, and Exclusions

• List assembly options from your engineering spec that must be mutually exclusive (for example option codes or rows in your configuration spec).
• Describe a representative complex configuration scenario using specific SKU or option IDs, selected options, and the expected BOM expansion we should use to author rules.
• Attach conditional dependency rules from your configuration spec or engineering change notices (ECNs) that must be enforced during quoting.
• Name the person on your engineering or product team we should consult when a rule conflicts with manufacturing constraints, and provide their role and contact method.
• When conflicts arise between sales-preferred options and engineering rules, describe the escalation path in your change-control process (for example: engineering review ticket → product manager → CTO).

Configure Discount Governance and Automated Price Calculations

• What discount tiers and margin floors are defined in your pricing worksheet for each customer segment (attach the tier rows or summarize thresholds)?
• Who approves discounts above standard thresholds today (role or email alias) and should be represented in the automated governance model?
• Specify any customer- or channel-specific override rules currently captured in ContractOverrides.xlsx or similar (for example strategic account exceptions). Options: Yes - attachments ready, Yes - need to collect, No overrides
• Indicate the calculation basis your pricing team uses for list price adjustments (cost-plus, margin-percent, target-margin) and point to the worksheet column names if possible. Options: Cost-plus, Margin-percent, Target-margin, Hybrid/Other
• Are there blackout dates or promotional windows in your commercial calendar that should disable automated discounts (for example end-of-quarter rebates or seasonal promos)? Options: Yes - schedule attached, Yes - will provide schedule, No

Implement Approval Matrix and Automated Approval Flows

• Count the approval tiers recorded in your approval_matrix.xlsx and list the role or alias assigned to each tier.
• List notification endpoints (email aliases, Slack channel, ITSM ticket queue) currently used for approvals that should receive automated approval requests.
• Attach the escalation rules you use today (for example escalate after 24 hours to next tier) and specify acceptable timeout values. Options: 24 hours, 48 hours, 72 hours, Custom (describe)
• Designate the legal or commercial operations approver who must sign off on nonstandard approvals during the pilot and provide their contact alias.
• Identify artifacts that will validate the approval flow in the pilot (for example approver audit trails, email receipts, and measured approval lead times).

Build Guided Sales Configuration UI for Reps

• Select the key sales workflows your reps follow when building a complex quote (for example configure options → request engineering review → finalize pricing). Options: Configure only, Configure + Engineering review, Configure + Approvals, Full flow (configure→price→approve→proposal)
• Estimate the number of representatives who will use the guided UI during the pilot and list the sales roles to include (AE, SE, Inside Sales, Channel).
• Attach examples of the slowest existing quote flows from CRM opportunity histories (for example screenshots or exported timestamps) that the guided UI must improve.
• Enumerate device types and browsers your reps use for quoting (for example Windows Chrome, Mac Safari, corporate tablet) to guide interface decisions.
• Define UI acceptance criteria for the guided configuration (for example: average steps per quote under X, guided validation catches >Y% of invalid combos, and rep time-to-quote reduced by Z%).

Generate Branded Proposal Templates and Document Exports

• Provide a sample of your current proposal document (PDF or DOCX) that we should use to map branding, placeholders, and line-item layout.
• List mandatory fields that must appear on every exported proposal (for example bill-to, ship-to, lead time, NRE line items, and warranty terms).
• Attach example clauses or legal language that must be included conditionally (for example export control, special warranty, or country-specific clauses).
• Who on your marketing or brand team will approve the template mockups and provide high-resolution logos and signatures?
• Specify which export formats you require for signed proposals (for example PDF/A, DOCX, or printable HTML) and any downstream storage rules. Options: PDF, PDF/A, DOCX, HTML

Configure Buildability Validation and Manufacturing Constraints

• Describe manufacturing constraints from your shop floor that must block certain configurations (for example maximum axle length, thermal-stack limit, or PCB layer count).
• Attach representative CAD or assembly notes and identify the fields that define build rules (for example 'max_load_kg' or 'PCB_layer_limit').
• Name the ERP or MES data points we should reference for lead-time and routing validation (for example work center code, operation lead time API endpoint).
• How will you accept the buildability validation test results during the trial (for example: zero invalid configurations in 100 sampled quotes or fewer than 2% acceptance defects)? Options: Zero invalid configs in sample, <=2% defects in sample, Custom threshold (describe)
• Specify any supplier or subassembly constraints that vary by region (for example region A uses vendor X component only) and provide the mapping file if available.

Provision Role-Based Access and Permission Controls

• List the user roles you require during pilot (for example quoting rep, sales engineer, pricing approver, admin) and approximate headcount per role.
• Assign the person who will serve as platform administrator during onboarding and provide their contact alias and availability for setup sessions.
• Specify sensitive data fields that require restricted access (for example cost, supplier lead times, contract-specific margins) and the roles that should be blocked.
• Provide your single sign-on (SSO) provider type and whether you will provide SAML/SCIM metadata for user provisioning during the pilot. Options: SAML, SCIM, OAuth/OpenID, None / local accounts
• Indicate if you require audit logging for permission changes and where those logs must be exported (SIEM endpoint, admin email, or platform log view). Options: SIEM endpoint, Admin email, Platform logs only, Other

Deploy Admin Tools for Ongoing Product Rule Maintenance

• Describe the cadence your product team expects for rule updates (daily, weekly, monthly) and typical change sizes (single SKU, product family, entire catalog). Options: Daily, Weekly, Monthly, Ad-hoc
• Attach examples of your current rule-change tickets or spreadsheets that document rule edits and approval history.
• Assign the owner who will be trained to use admin tools for rule edits and indicate their expected hours per week for maintenance.
• Specify whether you need role-based versioning of rules (ability to roll back a rule set to a prior effective date). Options: Yes - required, Optional, No
• Identify the export/import formats your product team prefers for bulk updates (for example CSV templates, Excel macros, or API endpoints). Options: CSV templates, Excel, API, Other

Configure Discount and Margin Visibility Dashboards

• Select the KPIs you need on launch dashboards (for example discount usage by rep, margin erosion by product family, time-to-approve statistics). Options: Discount usage, Margin erosion, Time-to-approve, Custom
• Estimate the reporting latency you require (near real-time, hourly, daily) for discount and margin dashboards. Options: Near real-time, Hourly, Daily
• Provide sample rows from your current discount-tracking spreadsheet or BI report to validate dashboard mapping.
• Assign the finance or revenue operations contact who will validate margin calculations and dashboard definitions during the pilot.
• Indicate whether dashboards need role-based views (for example rep view, manager view, CFO view) and which metrics should be hidden per role. Options: Yes - role-based, No - single view, Limited role splits

Integrate Quote Handoff with Source CRM

• Describe how you want finalized quotes to be pushed to your current CRM opportunity (for example attach PDF to opportunity, update line items, or create a child quote record). Options: Attach PDF, Update line items, Create quote record, Other
• List the CRM system and API access method you will provide for the pilot (for example REST API endpoint, OAuth client credentials, or CSV export path).
• Attach a sample CRM opportunity record (redacted) that contains the fields we must populate on quote handoff (for example opportunity ID, account ID, region).
• Who on your CRM or IT team will approve integration endpoints and provide test credentials for the sandbox environment?
• Specify the acceptance criteria for CRM handoff during the pilot (for example: quotes created in CRM with correct line items for 95% of sample transfers and attachments accessible).

• decision_readiness
• stakeholders
• current_state
• desired_state
• success_criteria
• gaps
• decision_readiness
• gaps
• current_state
• desired_state
• stakeholders
• success_criteria
• decision_readiness
• stakeholders
• desired_state
• success_criteria
• current_state
• gaps
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Subscription Agreement & Order Form
• Statement of Work (SOW)
• Master Services Agreement (MSA)
• Service Level Agreement (SLA)
• Support & Governance Addendum
• Acceptance Criteria & Readiness Confirmation
• Data Processing Agreement (DPA)
• Change Order Agreement

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• Acceptance Gate and Incumbent Wind-down (around day 90)
• Quarterly Success Review (ongoing)

• Update the issue tracker with next steps and target closure dates for all high-priority incidents.
• Update configuration rules or approval thresholds identified during root-cause analysis and document the changes.
• Restate acceptance criteria from Solution Evaluation
• Produce a documented acceptance outcome against each criterion recorded in the Solution Evaluation stage.
• Confirm a clear, time-bound plan to retire or retain the incumbent spreadsheets and email fallback, including data archival steps.
• Agree remediation tasks and final evidence requirements for any conditional acceptance decisions.
• Publish the formal acceptance record showing pass/fail per criterion and the buyer's documented decision.
• Execute legacy data archival or migration plan and confirm read-only or removal of write access to legacy spreadsheets and email templates.
• List remediation tasks for any failed criteria with target completion dates and required evidence for closure.
• Metrics and trend review
• Confirm whether quote accuracy and rep adoption remain at or near the targets recorded in the Solution Evaluation stage.
• Triage and prioritize the enhancement backlog so that high-impact items are scheduled.
• Ensure open high-priority issues have clear remediation tasks and target closure dates.
• Publish the quarterly metrics dashboard and a short trend analysis highlighting any deviations from targets.
• Create a prioritized enhancement list with expected delivery quarter and acceptance criteria for each item.
• Re-confirm acceptance criteria and owners
• Confirm deployment completion and validation of data flows and sample quotes.
• Establish an early usage baseline (active quoting users and sample quote volume).
• Record all open issues with remediation actions and target dates.
• Publish a deployment validation summary showing environment status, integration endpoints, and sample-quote evidence.
• Create a short issue tracker with replication steps and target resolution dates for each open blocker.
• Distribute user onboarding checklist and confirm training completion status for the initial quoting cohort.
• Present first-period outcome data
• Determine whether quote accuracy rate and average quote turnaround time are trending to the targets recorded in the Solution Evaluation stage.
• Agree a prioritized corrective plan with deliverable dates to close gaps before the acceptance gate.
• Confirm the data sources and reports that will be used at the acceptance gate.
• Produce a short remediation plan listing each corrective task, expected outcome, and completion date.
• Export and share the dataset and report definitions used to calculate quote accuracy and turnaround time for auditability.
• Present outcome data against each acceptance criterion
• Persistent issues and incident burn-down
• Deployment and data-validation walk-through
• Root-cause analysis for gaps
• Document pass/fail and formal acceptance decision
• Early adoption signals
• Enhancement request triage
• Agree corrective actions and timelines
• Open issues and immediate remediation
• Confirm readiness path to acceptance gate
• Adoption and training updates
• Incumbent wind-down and data disposition
• Next steps and short-term checkpoints
• Remediation items and closure plan
• Short meeting summary and next checkpoints