A construction-tech team's deals don't end at the sale. We built a CRM that runs the whole project lifecycle, extensions included.

Their deals kept going after the sale. Their CRM didn't.

SiteKick's deals are project-based and keep moving after the close: clients add cameras, extend contracts, and renew. Salesforce had no clean model for that, so a change became either a new deal or a mess. On top of that it was an enterprise CRM running a one-salesperson team, it didn't connect to the tools they actually use (ClickUp, QuickBooks, Google Bookings), and the founder exported data to a spreadsheet every week just to see the pipeline.

What it was costing: Extensions and renewals are real revenue, and they were the hardest thing for the old system to hold. A renewal that should have been flagged months ahead could quietly lapse, and every add-on either cluttered the active pipeline or muddied the finances. The founder could not get a clean view of any of it without exporting to a spreadsheet.

The problem was the shape, not the tool

The finding was structural. Their deals are project-based and keep moving after the close, and a generic enterprise CRM has no model for that. The first thing the new system had to do was treat the full lifecycle, extensions included, as the main event and not an afterthought.

One HubSpot system that runs the whole project lifecycle

The same senior team rebuilt it on HubSpot, sized for a lean team and shaped around the work. Three pipelines follow a deal from lead to active sale to live project, and a daily workflow flags every contract 90 days before it ends so a renewal never slips. The system wires HubSpot to the tools they already run on, and replaced the founder's weekly spreadsheet with live dashboards.

Four workflows automate the busywork: lead-to-deal conversion, close-to-project handoff, an equipment-retrieval task on contract end, and the standout, a daily Extension Follow-Up that flags every contract 90 days before it ends so renewal revenue never slips. Integrations wire HubSpot to QuickBooks for invoicing, ClickUp for project creation on close, and Google Bookings for kickoff and closeout scheduling. Role-based dashboards replaced the CEO's weekly spreadsheet. A clean, selective import brought over real records only and merged out roughly 245 duplicates left by a prior failed import.

• Three pipelines, one for each motion: Project Leads (awareness before being invited to bid), Active Sales (bid to close), and Closed Projects (won work, extensions, closeout).
• The Extension Follow-Up workflow, the standout: it runs daily and flags every contract 90 days before it ends, so renewals never slip and the active pipeline stays clean.
• Four workflows in all: lead-to-deal conversion, close-to-project handoff, an equipment-retrieval task on contract end, and the daily extension flag.
• One integrated stack: HubSpot wired to QuickBooks for invoicing, ClickUp for project creation on close, and Google Bookings for kickoff and closeout scheduling.
• A clean, selective import: real records only, with roughly 245 duplicate companies merged out and 330+ companies, deals, and contacts unified into one source of truth.

One system built around how they work, with extensions handled cleanly

The real win is structural: their deals do not end at the sale, so the system runs the whole lifecycle, from lead to install to the contract extensions that drive their revenue. The numbers below support that build, they do not stand in for it.