How IT Services Companies Can Manage Complex Sales Cycles in HubSpot

Key Takeaways

• An IT services deal has people on both sides: buyers, presales consultants, architects and delivery leads. HubSpot should show all of them.

• Name deal stages after real bid milestones: discovery, solution design, internal review, proposal, SOW review and negotiation.

• Label each buyer's role on the deal, so a proposal with no Decision maker on record shows up as a risk.

• Treat presales as a cost you track: who joined the bid, when, and how many hours it took.

• Watch stage conversion, days in solution design and SOW turnaround to see where architect time turns into signed work.

Procurement emails to ask which SOW is current, and the architect who wrote version three is already on another bid. The answer exists somewhere in your company, just not on the deal record where your sales lead is looking.

What makes HubSpot for IT services different from a standard sales setup?

HubSpot for IT services has to track a chain of people and documents, not just one owner, one amount and one stage. A default pipeline holds those three fields. In an IT services sale, they hide most of what decides the outcome.

Picture a typical bid. A business sponsor raises the need. An IT leader shapes the requirement, a security team reviews the approach, and procurement negotiates the contract. On your side, the account executive pulls in a solution architect, and a delivery lead checks that the estimate can be staffed.

Each handoff creates a fact the deal needs. Has anyone met the security reviewer? Did delivery sign off on the estimate? Which proposal version is the client reading? Without a place in the CRM, those answers end up in email threads, shared drives and the architect's memory.

What this means for you: take your last three won deals and list every person, on both sides, who touched them. Use the list as your design brief.

What deal stages should IT services companies use in HubSpot?

Use stages that each mark a milestone where the buyer or your team must do something new. For a project-based IT services sale, that usually means a confirmed need, a scoped solution, an approved internal approach, a priced proposal, an agreed SOW and a signed contract.

HubSpot lets you make chosen properties required when a deal moves into a stage. A deal entering proposal can be required to name a solution architect. A deal entering SOW review can be required to carry a proposal version and a delivery review outcome.

Here's the catch. A required property only confirms that a value has been entered, so "rejected" passes the rule just as "approved" does. Add a workflow that alerts the practice head when a deal reaches SOW review with any outcome other than approved. Then check that outcome in the pipeline meeting and pull back any deal that skipped delivery's sign-off.

The table is a Markivis recommendation, so merge or split stages to fit your offers. Required stage properties, association labels and custom objects depend on your subscription, so check what your portal includes before you design around them.

At a glance: an IT services pipeline for HubSpot, with entry rules and stakeholders for each stage.

How do you track the buying committee and your bid team in HubSpot?

Associate every buying-side contact with the deal and add a buyer-role association label, such as Decision maker or security reviewer. The deal record then shows which seats on the buying committee are filled and which are still empty.

We recommend flagging any deal at proposal stage with no Decision maker associated, whatever probability the stage carries. A saved view of open deals with that gap turns the rule into a short weekly list.

Add user properties for the solution architect and the delivery lead, so each deal names the people your company has committed. When one architect appears on four open bids at once, you've found a staffing limit before it costs you a deadline.

What this means for you: for every open deal in solution design or later, check that a Decision maker is on record. Then name the architect and delivery lead on each one.

How do you track presales hours and SOW versions in HubSpot?

Put presales effort on the deal record, starting with a bid or no-bid decision at the end of discovery. Record it as a required property with a short reason.

When a deal enters solution design, capture three facts:

• Architect assigned: the person scoping the work.

• Date joined: when presales time started.

• Estimated hours: the expected presales effort, updated with actual hours when the deal closes.

The simplest setup is a task assigned to the presales lead for each new request. A more structured option is a separate ticket pipeline or a custom object for presales requests, which shows the whole queue across all deals.

Proposals and SOWs need version tracking in the CRM, not only in a shared drive. Keep a version number property for each one and update it with every revision you send, with a short note on what changed. When a deal reaches its fourth SOW version, a manager can see the rework without opening a file.

Presales effort is spent long before any revenue is booked, so a deal record that leaves it out understates what each IT services deal costs to win.

What this means for you: add a bid decision, an assigned architect and presales hours to your deal properties this quarter. Make the first two required at the stages where they apply.

Which HubSpot reports show where IT services bids are won or lost?

Build one dashboard around four views, using the date HubSpot records each time a deal enters a stage:

• Solution design to proposal: how much presales work reaches a priced offer.

• SOW review to closed won: how often an agreed scope becomes a signed contract.

• Days in solution design and SOW review: where deals wait, and whether rework is the cause.

• Presales hours on won versus lost deals: what a lost bid costs your architects.

Next to them, count open proposals with no Decision maker on record. Review the dashboard monthly with the sales, presales and delivery leads. Each of them controls a different part of these numbers.

Questions to ask: Which stage holds the most presales hours on deals we later lose? How many open proposals have no Decision maker on record right now?

The Bottom Line

The facts that decide an IT services deal already sit in architects' estimates, delivery reviews and proposal folders. Stages for solution design, internal review, proposal and SOW give those facts a home on the deal. Required properties make sure each field is filled. Workflow alerts and the pipeline meeting decide whether the answers are good enough to move the deal forward.

The Markivis Approach

Replaying one lost bid is where we begin. With your sales, presales and delivery leads, we walk through it from the first scoping call to the final decision. Along the way we mark every point where information left the CRM for an inbox or a drive. The stages and entry rules come from that walkthrough, and the people who will follow them help write them.

We have no published case study from an IT services company. The closest proof is the HubSpot, CRM and lifecycle work in the Slimstock case study, done for a software company. You can see what else we configure on our HubSpot implementation page.

FAQ

Q: Can HubSpot handle complex IT services sales cycles?

A: HubSpot can hold every stage, stakeholder and document version an IT services deal involves. The default pipeline won't, so the value comes from designing stages, buyer roles and presales fields around how your deals actually move.

Q: Should managed services and project deals share one pipeline?

A: Split them if their stages or entry rules differ in a real way. Managed services deals often add transition planning, while project deals center on scope, so two pipelines keep each forecast honest.

Q: How should RFP-driven deals fit into this pipeline?

A: Record a bid or no-bid decision as soon as the RFP arrives, and enter the deal at solution design if you bid. Store the submission deadline and clarification dates as properties beside the stage.

Q: Who should own the IT services pipeline design?

A: Sales operations or the CRM owner should own it, with sales, presales and delivery leads signing off on stage definitions. A pipeline designed by one function tends to miss what the other two need.

Q: Should presales work in HubSpot or in a separate tool?

A: Presales can keep working documents elsewhere. The assignment, hours and bid decision should still sit on the HubSpot deal, or nobody can compare presales effort with the revenue it helped win.

 

Q: How do we migrate open deals into new stages?

A: Move each open deal to the stage its evidence supports, not the stage it held before. Fill in the newly required properties during that review, so your first reports start from accurate data.

Q: When should we avoid adding more pipeline stages?

A: Skip a new stage when it doesn't change what the buyer or your team must do next. Use a property or a task instead, and keep the stage list short enough to read on one screen.

Ready to Map Your IT Services Pipeline in HubSpot?

The best time to map an IT services pipeline is before your next large bid. The architects who scoped recent deals still remember how they unfolded.

Send us your current stage list and one SOW that went through several versions. In the review, we'll show where stages, buyer roles and presales fields would have captured that rework as it happened.

Book a Free IT Services Pipeline Review.

Last Updated: November 05, 2026