- Which spreadsheet did you use for that quote? The one called NEW_FINAL_v3 or the one from the price folder?
I’ve heard that line in more rollouts than I care to admit. The quote was sent on time, the customer is waiting, and now three people are opening three versions of what is supposed to be the single source of truth.
Excel became the default for quoting for good reasons. It’s fast, it’s everywhere, and it costs nothing to start. That’s exactly why it’s hard to leave.
When you sell complex products, you don’t have time to request a new form, wait two weeks, and train everyone on a new tool. You copy the last good quote, tweak a few cells, and ship it. It works today, so it becomes the habit tomorrow.
Excel rewards speed. You can add a column in seconds, try a what-if for a discount, or insert a new option line without opening a ticket. It’s not a system - it’s a sandbox for getting the job done. For teams under quota pressure, that’s rational behavior.
But speed without guardrails has a cost. Over time, the spreadsheet becomes a product in itself - a living, fragile, undocumented product. Every hidden formula is a rule. Every extra sheet is a policy. Every local tweak is a fork.
I don’t see many dramatic failures with spreadsheets. I see quiet ones. A margin that’s 2 points off because a column wasn’t updated. An option sold together with another option that was discontinued last quarter. A price based on last year’s contract because the template was copied from the wrong folder.
These aren’t edge cases. They are the pattern. And the pattern gets expensive:
The anti-pattern I see most often is what I call Template Drift. It starts as a clean template. Then one region adds a local discount table. One product owner inserts a hidden helper sheet. One salesperson freezes a currency rate. Within a quarter you have six versions that look the same on page one and behave differently everywhere else.
Version control is not a folder name.Could a full CPQ system fix this? Yes. And sometimes that’s exactly what you need. But CPQ introduces its own cost curve: product modeling, rule modeling, integration, governance. For many teams, that jump is too big for the first step. The result is a stalemate - keep the spreadsheet and accept the pain, or start a program that feels like building a harbor before you can launch a single boat.
There is a middle path that’s getting real traction: lightweight quote automation. Think of it as professionalizing quoting without committing to a full CPQ build.
What it does well:
What it doesn’t try to do: replicate an engineering-grade configuration model, serve every product line at once, or replace your CRM and ERP. It aims for the 80-20 - the common 80% of quoting work at 20% of the effort.
Tools in this emerging category - including my own work with Sailsrep - are built for teams who need to get out of spreadsheet chaos now and grow into CPQ when they are ready. They add structure and explainability where Excel is opaque, and they do it without a year-long project.
Here are the rules I use when I help teams take that step.
Rule 1: Start with guardrails, not a grand design. List the top 10 invalid combinations and block them at input. Example: line voltage must match the selected power module. If that fails, stop the quote early. You’ll prevent 50% of rework by ending dead ends before they start.
Rule 2: Put price math in one place everyone can see. Discounts, surcharges, freight, and warranty need a single formula source. Not scattered VLOOKUPs. Not hidden sheets. One table, versioned, with a simple explanation for each adjustment. If policy changes, update it once and watch every quote get it right the same day.
Rule 3: Make the system explain itself. Every decision should have a why that sales can repeat to a customer. If a bundle is selected automatically, show the rule behind it. If a discount is capped, show the cap. Trust grows when answers come with reasons, not just results.
Rule 4: Treat change as an event with safety. Even a light system needs tests. Maintain a small suite of standard quotes and run them after every change. Tag each release with a revision ID. Don’t let fixes break yesterday’s success silently.
Notice what is missing from these rules. No talk of perfect pricing. No talk of modeling every edge case. No giant integration plan. You’re building a controlled path for the most common deals, not paving every street on day one.
To make this practical, apply three actions this month:
Who benefits first from this approach? Newer reps and distributed teams. For them, the difference between guessing and guidance is the difference between a 3-call quote and a 1-call quote. Experienced reps benefit, too. They stop being the safety net for everyone else’s mistakes and spend their time shaping deals, not debugging files.
Who drifts into irrelevance? Teams that keep the spreadsheet as the real system while announcing tools on top. Workarounds become the process. The clever macro becomes the policy. And no one is sure which file is the truth, so everyone asks a person instead of trusting the system.
Let’s be honest about why this works. The value is not in automation for its own sake. It’s in correctness you can explain at speed. When the logic is explicit, updates improve outcomes the same day. When it’s hidden in cells, you fix the same problem in five places and hope you didn’t miss a sixth.
You don’t have to choose between Excel forever and a full CPQ program now. There is a credible middle ground that earns trust quickly and creates a clean on-ramp if you later need the depth of CPQ. Think speedboat now, harbor later.
If sales has to ask someone to trust a number, the system failed.
I started my career helping teams build deep configuration for products that truly required it. I still do that work. But I also spend a lot of time helping companies escape the spreadsheet trap without overbuilding. The pattern is repeatable: guardrails first, shared price math, explainable decisions, and safe change. The outcome is quoting that feels calm instead of fragile.
The quiet win is a quote you can trust, created in minutes.