How to Forecast Sales Inquiry Volume by Season and Plan Your Team

BOTrento Team7 November 20267 min read

Why seasonal patterns matter more than averages

A monthly average hides the problem. If an event agency gets most of its enquiries in a few autumn weeks, an average tells you the team is fine. In practice, replies slip, quotes go out late and follow-ups get forgotten exactly when the most revenue is at stake.

Seasonality looks different in each business:

• Event and production firms: surges ahead of the year-end party season and before spring conferences, with quiet gaps between.
• Equipment rental: peaks that follow festivals, trade shows, and building or filming seasons.
• B2B services: enquiries often rise after budget planning and fall around main holiday periods.

Treat these as hypotheses. Your own data decides which ones are true for you.

Step-by-step: build your seasonal forecast

1. Export your enquiries. Pull them from your shared inbox, Gmail or Outlook folders, or from HubSpot or Pipedrive. You need at least the received date and a rough label for the type of request. Go back as far as your history is reliable, ideally two or three years.
2. Clean the list. Remove spam, supplier mail, duplicates and replies within the same thread. Count one enquiry once. Decide the rule and keep it the same every year.
3. Count by week or month. Weeks show peaks more sharply. Months are fine if you receive few enquiries. Put each year in its own column so you can compare the same period side by side.
4. Mark the pattern. Highlight the busiest and quietest periods in each year. If they land in the same place two years running, that's a seasonal pattern. If they move, look for a cause such as a one-off event, a campaign or a large customer.
5. Write the forecast as a range. For each month, note "high", "normal" or "low" and a likely range based on past years. Add a short note on what could shift it, such as a marketing push or a new product line.

If you want to go a level deeper on what the history says about price friction and demand timing, reading pricing patterns in your own enquiries uses the same export.

Separate volume from workload

Ten enquiries are not always ten units of work. A one-line price request takes minutes. A complex production brief can take hours of clarification and a custom quote.

Tag by effort

Add a simple column: quick, standard or complex. Then forecast both numbers. A month with fewer enquiries but more complex ones can be heavier than a month with plenty of quick ones.

Watch incomplete requests

Enquiries that can't be quoted yet create extra rounds of email. If your peak months are full of them, your real workload is higher than the count suggests. Counting the hours lost to clarification loops shows how to measure that.

Turn the forecast into staffing and scheduling decisions

A forecast is only useful if it changes a decision. Use it for four things:

• Holiday planning: avoid having several people away in your high-volume weeks. Agree cover for the inbox before the peak, not during it.
• Temporary help: decide early whether you need a freelancer, a part-timer or a shared rota for the busy period.
• Preparation work: update price lists, standard quote wording and question sets in the quiet weeks before a peak.
• Response targets: set a realistic reply window for peak weeks and measure it. Measuring enquiry response time gives you a number to watch while volume is high.

In slumps, use the time for the work you postpone otherwise: reviewing open quotes, following up older ones and cleaning your data. If follow-ups are your weak spot, the answer on how to stop forgetting quote follow-ups covers the basics.

Common mistakes when forecasting inquiries

• Using one year only. One year can be distorted by a big project or a campaign. Use two or three if you have them.
• Counting everything as an enquiry. Mixed-in newsletters and supplier emails inflate the peaks.
• Ignoring the source. A peak caused by one directory listing or one partner behaves differently from steady demand.
• Forecasting once and forgetting it. Compare forecast with actuals every month and adjust the ranges.
• Treating the forecast as a promise. It supports planning. It doesn't tell you how many orders you'll win.

To see what happens after enquiries arrive, calculating quote conversion rate is the natural next measure.

How BOTrento helps you keep the data and handle the peak

Forecasting needs a clean history, and peaks need a process that keeps working when everyone is busy. BOTrento Chief of Staff is a managed process for enquiries and quotes. It watches enquiries in your mailbox and in the data you upload, and every working morning it shows a "Today 1+3" overview in the app and by email.

It prepares draft replies, quotes and follow-ups in four languages, and it picks up promises such as "I'll get back to you by Friday" and reminds you of them. Nothing is sent without a person approving it. BOTrento doesn't replace your CRM or accounting, and it doesn't send anything on its own.

At the start of a trial, a "Lost money" report looks back at past enquiries, though only for a mailbox connected via IMAP. You can import a CSV or XLSX export from your CRM or spreadsheet. AI is included in the plan with a monthly usage limit, and an own API key is optional (currently Anthropic only). You can see a walkthrough of the process first. For plans, see pricing. If cost is your question, there's also a short answer on what an AI sales assistant costs a small business.

Our own internal pilot ran over 7 days on BOTrento's own processes: 35 enquiries, 18 emails, 24 quotes and 15 actions. It's not a client reference, just an indication of the kind of workload the process handles.