Skip to Content

Your Salesforce problem is almost never Salesforce

Pipeline reports go fictional in a quarter, adoption is a payback problem, and CPQ kills projects
January 18, 2024 by
Syncritech INC, Bill Roberts

The problem with your Salesforce org is almost never Salesforce.

We get called into Sales Cloud instances that were built competently and that nobody trusts two years later. The objects are sane, the automations still fire, but the pipeline report is fiction, reps update records the night before the forecast call, and finance rebuilds the number in Excel every Monday. That is an ownership failure, not a software failure, and reimplementing does not fix it.

Your pipeline report goes fictional in about a quarter

Here is the test. Filter your opportunity list to close date in the past and stage not Closed Won or Closed Lost, then count the rows. If that number is bigger than your sales team, your forecast is creative writing.

Data hygiene is nobody's named job. Duplicate and matching rules get switched off for a migration and never switched back on. Stages get named as nouns (Proposal, Negotiation) instead of exit criteria ("budget confirmed in writing, with a decision date"), so two reps read Qualified differently and neither is wrong. The fix is boring: written exit criteria, dedupe rules that stay on, validation on forecast fields, and one named person reviewing the exceptions weekly. Companies skip that last part. It is the part that matters.

Adoption is a payback problem, not a training problem

When reps will not use the CRM, the reflex is more training and a stricter manager. It rarely works. The reps are behaving rationally. You ask them to spend twenty minutes a day typing into a box, and everything that comes back out of it goes to somebody else: the manager's dashboard, the board deck, marketing.

Give them something back and behavior changes without a mandate. Logged activity that pre-fills a quote. Assignment rules that route good inbound leads to whoever keeps clean records. The highest-yield adoption change we ship is usually deleting required fields, not adding them.

CPQ is where implementations go to die

Configure, Price, Quote is powerful, and it is where we most often watch a budget disappear. The reason is not technical. Pricing rules are business decisions written in a formula language, and most companies have not made them. What discount can a rep approve alone, by product family, and does that change in Q4? If a customer signs three years and adds seats in month seven, what do those seats cost? Nobody configures past an unanswered question. It shows up as an approval matrix no executive will sign, and a go-live two quarters late.

We run the pricing and approval workshops before anyone touches a product rule. Better to learn in week two that three answers need a decision your CEO has dodged for a year. One note: Salesforce has been steering new buyers toward Revenue Cloud rather than the older SteelBrick-derived Salesforce CPQ. Confirm which one your statement of work covers.

The part most consultants will not say out loud

Salesforce is sold per user, per year, paid up front, and Sales Cloud Enterprise lists north of $150 per user per month. Seats are easy to add mid-term. Removing them waits for renewal. An unadopted org is not a stalled project. It is a line item you pay in full until somebody finally raises it, usually after the non-renewal notice window has closed.

Plenty of SMBs on Enterprise use it like a shared contact database with a good mobile app. If that is you, there are two honest answers, and "buy more consulting hours" is neither. Either commit (pick three processes you will genuinely run through Salesforce this year, then staff the hygiene) or move to something cheaper. A consultant who says that out loud is worth more than one who will not.

We can say it because we sell both sides. Syncritech runs its own company on Odoo 19 Enterprise (accounting, CRM, quoting, inventory, helpdesk, one database), and our CRM and ERP consulting practice covers Sales Cloud, Service Cloud, CPQ, and Experience Cloud alongside Odoo and QuickBooks. So we have no reason to pretend Salesforce fits a 15-person shop that mostly needs quoting and invoicing, or that Odoo fits a sales org with a channel motion and eight approval tiers. The recommendation pays us the same either way, which is the only reason it is worth anything.

Send us the org you already have.

Tell us what your reps actually do in it and what renewal costs. We will tell you whether it needs work, an owner, or replacing.

Share this post
If the DICOM copy never leaves the building, it is not a backup
Per-study pricing, lock-in that surfaces years later, and three questions for any offsite vendor