Multi-location franchise · the forecast that assumes capacity

Your forecast says 80% likely to close. The crew that would do the job is already booked solid.

Sales forecasting predicts close probability from deal stage and historical conversion. It almost never checks whether the servicing location has the capacity to deliver on schedule if the deal actually closes.

The desire, and the forecast blind to delivery

Nobody searching “sales forecasting software” wants a probability score. They want a forecast that reflects revenue the business can actually deliver, not just revenue a deal-stage model predicts will close.

1. 1. The model — deal stage and conversion history. Every CRM forecasting tool does this well: stage, deal age, and historical win rate produce a close-probability score. This is the well-known half.
2. 2. The gap — capacity lives in a different system. Whether the servicing location can actually deliver the job on schedule sits in the field-service or dispatch platform, unread by the forecast — the same blind spot /franchise-crm-software found in lead routing.
3. 3. The close — weight the forecast by delivery capacity. A high-probability deal at a fully booked location gets flagged differently from the same deal at a location with open slots — the forecast reflects what can actually be delivered, not just what is likely to be signed.

This is the same capacity signal missing from a second CRM function — not a new discovery, a deeper application of one already proven on this site.

Which platform this runs on

• CRM and marketing automation, by scale — the platform whose forecast should weight by capacity.
• Franchise CRM software: the capacity signal it never sees — the same signal, read by lead routing instead of forecasting.
• Field-service software, by scale — where the actual capacity data the forecast needs already lives.

Some links on the recommendation page are partner links: the vendor pays us if you sign up, your price does not change, and each button says which.

How to build it yourself, end to end

Five steps. Each names the vendor touchpoint from the picks above.

1. 1. Pull a capacity metric per location from the field-service platform. Open slots in the promised delivery window — the same metric /franchise-crm-software already argued lead routing should read.
2. 2. Attach it to each open deal by servicing location. The forecast needs to know which location would deliver each deal, not just that a deal exists somewhere in the pipeline.
3. 3. Flag high-probability deals at low-capacity locations. Not to lower the close probability itself — the deal may well close — but to flag a delivery-timing risk the raw forecast does not show.
4. 4. Route the flag to whoever plans staffing, not just sales leadership. A capacity conflict is an operations decision as much as a sales one — both sides need to see it before the deal closes, not after.
5. 5. Track forecast accuracy against actual delivery timing. The real test is whether capacity-weighted forecasts predict on-time delivery better than deal-stage alone did before.

Step 2 is the one to get right first — a forecast that cannot tie a deal to the location that would deliver it has nothing to weight capacity against.

Or have it scoped and built

Wiring field-service capacity into CRM forecasting is scoped work against your specific platforms — the readiness assessment is where that gets mapped out before anything is built.