The problem
Why project-based revenue is difficult to forecast
A product sale has one commercial decision. A services sale has that decision plus a scope, an estimate, a delivery start date and a staffing implication — and each of those can move independently while everyone involved is being perfectly honest.
- The close date is a function of the buyer’s procurement calendar, not the seller’s quarter.
- Scope changes during the sale, so the value in the pipeline is a number about a proposal that no longer exists.
- The buying committee grows: a technical evaluator, a security reviewer, a legal reviewer, a procurement lead and a budget holder, most of whom appear late.
- Revenue recognition depends on a start date that slips quietly after the signature.
- A won deal creates a staffing obligation, so a wrong forecast costs bench cost as well as revenue.
Committees
Stakeholder and committee complexity
The most reliable predictor of an integration deal slipping is a name that has not appeared yet. Klosure records every person who shows up on a thread or a meeting, including anyone added on a CC line, and flags the roles a deal of this shape should have but does not.
| Gate | Who usually owns it | What Klosure watches |
|---|---|---|
| Technical validation | An architect or lead engineer | Whether they have joined a call, and whether their questions were answered |
| Security review | An information-security reviewer | Whether a questionnaire arrived, and whether it is still open |
| Commercial approval | Procurement | Whether procurement has appeared at all — most often they have not |
| Legal | In-house or external counsel | Whether a contract is in review, and how long it has been there |
| Executive sponsorship | The budget holder | Whether signing authority is identified — unknown against a near deadline caps confidence |
The gates a services deal passes through, and what an unstaffed gate does to confidence.
Scope
Proposal revisions and scope changes
A third revision of an estimate is normally read as engagement. Sometimes it is. It is also what happens when a buyer is assembling a comparison for someone who has not been in a single conversation with you — and the two cases look identical from the seller’s side.
What separates them is whose questions are driving the revisions and whether those people have been in the room. Klosure keeps the stakeholder map and the open questions against the same deal record, so the second case shows up as a widening gap between the number of revisions and the number of buyer-side participants.
Procurement
Security, procurement and legal gates
This is the work that stalls deals after the buyer has already said yes, and it is largely invisible to a CRM because none of it looks like selling.
Klo drafts security-questionnaire answers from the team’s own prior responses — a corpus that compounds every time a rep promotes an answer back into it. Grounding is strict: answers come only from the corpus, and anything it does not cover is flagged as needing input, never fabricated, because Klosure will not invent a security claim or a certification.
Inbound contracts get a first-pass commercial review against the team’s own red lines with proposed redlines. Only clauses actually present in the document are flagged, and the raw contract text is never stored.
Delivery
What forecast confidence means for staffing
In a services business, forecast confidence is a resourcing input, not just a revenue number. Klosure carries build and staffing views alongside the forecast, so the same capped confidence that decides whether a deal is in Commit is the number the bench decision is made against — rather than a separate optimistic figure kept in a spreadsheet.
Worked example
A systems-integrator deal, gate by gate
Product example
A managed-services engagement with a quarter-end close date
Invented but realistic sample data, used to show how the gates interact. This is not a customer.
- Discovery with a head of infrastructure. The stated deadline is quarter-end. Klosure marks it tentative, because no budget cycle has been confirmed.
- Solution design adds an architect and a second engineer. Coverage improves; signing authority is still unknown, so the confidence ceiling holds.
- The estimate goes out. It is revised twice in ten days, both times against questions from a name that has never joined a call.
- A security questionnaire arrives from an information-security reviewer nobody has met. Klo drafts answers from the team’s own corpus and flags two items the corpus does not cover, for a human to answer.
- Procurement has still not appeared. The deadline is now 26 days away and signing authority is unknown, so the 35% cap fires. The deal leaves Commit.
- The removal names what would clear it: identify the approver and get them into a conversation. That is a specific action, not "work the deal harder".
- The approver joins a call and confirms the route: legal review, then a procurement cycle their own team estimates at eight weeks. The close date is reset on evidence, and the staffing plan moves with it.
The deal in this example was not lost. It was mis-dated by a quarter, which in a services business is a bench cost as well as a miss.
FAQ
Frequently asked questions
What sales forecasting software suits IT services and system integrators?
Forecasting software for IT services has to handle a close date set by the buyer’s procurement process, scope that changes during the sale, and a buying committee that grows late. Klosure forecasts these deals from observed buyer behaviour, caps confidence when a gate such as signing authority has no identified owner, and tests close dates against realistic time-to-signature floors by market.
How do you forecast project revenue when start dates keep moving?
Forecast the signature and the start date as separate facts, and treat both as tentative until the buyer confirms them. Klosure marks deal value and deadline as definite or tentative on the deal record, and rebuilds expected timing from what the buying process still has to complete rather than from the date originally typed in.
Can Klosure help with security questionnaires?
Yes. Klo drafts answers from your team’s own prior responses, and every answer a rep promotes back into the corpus compounds it. Grounding is strict: anything the corpus does not cover is flagged as needing input rather than fabricated, because Klosure will not invent a security claim or a certification on your behalf.
Does Klosure work for project-based revenue outside IT services?
Yes, where the deal shape is similar: multi-stakeholder, proposal-driven, with procurement and legal gates and a delivery commitment behind the signature. What Klosure needs is a process that runs through email and scheduled meetings; a deal negotiated mainly by phone or WhatsApp shows less signal.
Bring one deal. See what Klosure would read.
A 20-minute walkthrough against a real opportunity from your own pipeline — not a canned demo. Bring a deal you are not sure about.