Spaces

Message workload planner for software and IT firms

This planner works out how many hours a week a software or IT firm spends answering client messages, from your own figures for messages a day and minutes per reply. It suits support leads and owners.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Client messages at a software firm rarely look like much work, one at a time. A status question takes three minutes. A fault report takes fifteen, once you gather the details. But they arrive in the middle of coding, deployments and calls, and every switch costs more than the minutes on the clock.

Enter your own figures below, using a typical week. Count every message, from clients, prospects and your own team's questions in the chat. The total may surprise you, and it shows what answering really costs, even before the interruptions are counted.

Every starting figure is an example. Change each one to your own.

Under your figures

Hours a week spent answering15
Hours a month (4.3 weeks)65
Working days a month (8-hour days)8.1

This is an estimate based on the figures you enter, not a measurement of your firm.

Reading your result

If the total is a few hours a week, a good shared inbox and clear habits may be enough. If it is a day or more, someone at {business} is probably losing a large part of their week to messages, and it is likely an engineer, not a support specialist.

Remember that interruptions cost more than the reply time. Switching from code to a chat and back can cost far more than the minutes you counted.

Where the minutes go

Look at what takes the time before you decide what to change.

  • Asking again for the page, time and error that were missing.
  • Searching for the ticket or the release notes.
  • Answering the same ten questions in slightly different words.
  • Deciding who should pick up the message.

FAQ

How do I count messages if they arrive in several places?

Add them together for a typical week and divide by the days you work. A rough figure is fine, since the result is an estimate and not an exact figure.

Should I include time spent on the fix itself?

No. Count only time spent reading and replying to messages. The engineering work to fix a fault is a separate matter, and belongs in your project hours.

What is a normal workload for a small firm?

It varies widely. A small firm with a few retained clients may spend five hours a week, while a managed IT provider may spend most of a person's week. Your own figures matter most.

More free tools for software and tech support firms

Read the guide: Answer client messages at your software and IT firm, from outages to scoping.