If your techs quote good-better-best, your estimates hold more information than your reports do. Which tier wins. How often the premium option lands. What your open pipeline is really worth. On the estimate screen in Service Fusion, the options are all there. In the reporting data, they are not.
This post is about that gap: why it exists, what it costs you, and what closing it looks like.
The flattening problem
When an estimate with three options leaves Service Fusion through the API or an export, it arrives as one number. The option structure, the thing your sales process is built on, gets flattened away. I covered the API’s quirks broadly in what the Service Fusion API can actually do, and this is the quirk with the biggest reporting consequence.
What that costs in practice:
- Pipeline value is wrong. Is the open estimate worth the good number or the best number? One flattened total cannot say.
- Option win rates are invisible. If customers pick the middle tier 80 percent of the time, your pricing spread is telling you something. You cannot hear it.
- Follow-up is unprioritized. A stack of open estimates with no honest values is a to-do list. The same stack with real values is a ranked one.
The workaround, honestly described
The fix is capturing the option-level detail into a database alongside the regular nightly sync, so each option on each estimate is stored as its own row: its tier, its amount, and eventually whether it won. It is real work rather than a checkbox, and it is the kind of thing I build once per client and then it just runs.
I will not pretend the plumbing is elegant. The point is what it unlocks: estimate reporting that matches how your team actually quotes.
Expected revenue: the number owners end up using most
Once option-level estimate data exists, one number changes how the whole backlog reads: expected revenue.
Take every open job, value it by what its estimate says, and add it up. The owner stops seeing “43 open jobs” and starts seeing what those jobs are worth. Scheduling decisions, follow-up urgency, and cash planning all get sharper when the backlog has dollars on it. On one client’s dashboard this became the tab the owner checks first, next to the stuck-jobs list from the reporting post.
A warning from the same build: garbage options make garbage numbers. One zero-dollar option on one estimate quietly poisoned an expected-revenue calculation until we taught the reporting to handle it. The reporting layer has to be defensive, because real estimate data is messy.
Your team changes nothing
The part sales managers ask about first: nobody re-learns anything. The team keeps writing estimates in Service Fusion the way they already do. The reporting layer adapts to the estimates, and that is the correct direction. Tools that make the field change its habits to make the reports prettier tend to lose.
If your company quotes options in Service Fusion and your pipeline number is a guess, this is a solved problem. The rest of my Service Fusion work, posts and case studies, lives on one page, and a short call is enough to tell whether your estimate data can support it.