Client Overview

A solar services company sells and delivers projects that each go through an estimate, internal approval, a customer quote and a signed contract. Its sales team works in HubSpot and its finance team works in QuickBooks.

The Challenge

The steps between a first estimate and a closed deal were handled by hand. Estimates were approved informally, quotes were rebuilt from approved estimates, and contract details were spread across deal fields. Managers had no fixed checkpoint between a signed contract and a deal being marked as won, and finance could not always match what HubSpot showed against QuickBooks.

Our Solution

Smplfy works as the company’s engineering team inside its HubSpot account. We build and test in a sandbox first, then move each workflow to the live account.

Two-stage estimate approval

Estimates now go through a two-stage approval workflow in HubSpot, so every estimate is reviewed before it reaches a customer and the approval is recorded on the deal.

Management review before a deal closes

We added review stages between contract signed and closed won. A deal cannot be counted as won until a manager has checked it.

One contract record per deal

We are building a contract record that holds the data for each stage of a deal in one place, so sales, operations and finance read the same numbers.

Approved estimates become the quote

Approved estimates roll into the deal’s quote automatically, which removes the step of retyping line items.

Next: invoices, purchase orders and payment schedules

The next phase creates a draft invoice and purchase order when a quote is signed, adds payment schedules to quotes, and reconciles open invoices between HubSpot and QuickBooks.

Results So Far

  • Estimate approval and management review are live as HubSpot workflows.
  • Every approval is recorded on the deal, not in email or chat.
  • The contract record and automatic quote build are in progress.
  • This engagement is ongoing, and this page will be updated as later phases ship.

Conclusion

Revenue operations problems are rarely about one missing feature. They come from handoffs between people and systems. We start with the handoff that costs the most, build it as a workflow the team can see, and then move to the next one.