Your Calendar Already Knows Where PreSales Time Goes

This is the least glamorous integration a technical sales team can turn on and, in our experience, the one that changes the staffing conversation fastest — because it replaces an argument about perception with a table.

Why the usual answers do not work

• Timesheets. They require the person under time pressure to spend more time reporting on it. Compliance decays within a month and the resulting data is worse than none, because it looks authoritative.
• Activity counts. Demos delivered, RFPs completed. These rise when a team is overloaded, which makes them precisely the wrong evidence to bring to a headcount conversation.
• CRM logging. The opportunity record captures that an SE was involved, not for how long or on what. It was never designed to.

Meanwhile the actual record of where an engineer's week went is sitting in their calendar, already accurate, already maintained, and requiring nobody to do anything extra.

What connecting the calendar actually produces

WinIQ reads events from Google Calendar and Outlook Calendar, normalises them into one stream regardless of which provider each engineer uses, and then does the part that makes them useful — matching each event to a project and a customer:

The number that changes the conversation

Most capacity arguments stall because the two sides are describing different things. A leader sees deals per engineer; the engineer is experiencing concurrency — six evaluations in the same fortnight, each expecting responsiveness. Calendar data is what makes concurrency legible, because a week with four different customers in it looks different from a week with one, even when the deal count matches.

That is the input the ten-deal capacity calculation needs and the part that is usually estimated. Estimated non-deal time is always low; measured non-deal time is the number that ends the argument.

The convention: put the customer and the project in the title

Attribution reads the entry’s title and description. A customer name in the text is a strong signal; the project name is a stronger one. So the convention is three parts, in this order:

The first three attribute themselves to a customer and a deal without anyone doing anything else. The fourth attributes to nothing, and no amount of matching cleverness will rescue it — there is genuinely no information in it.

Block the preparation, not just the meetings

This is the half that changes the numbers most. An entry does not have to be a meeting. A two-hour block titled Contoso – Core Banking – RFP Response Preparation is effort, it is attributable, and once it is on the calendar it appears in two places at once: against the project, where it explains what the technical evaluation actually cost, and in the engineer’s own week, where it is the difference between a day that looks empty and a day that was full.

Most presales work is not meetings. Reading the RFP, scoring requirements, drafting the questionnaire, preparing the demo storyline — that is the majority of the hours and almost none of it gets booked. A team that blocks it is not doing admin; it is making the largest part of its own workload visible for the first time.

Where this can go wrong, and how we think about it

One honest limit remains, and it is conditional rather than fixed: a calendar records what you put on it. If a team only ever books meetings, then the RFP read on a Sunday evening and the two hours spent chasing an architect are invisible, and the resulting utilisation is a floor rather than a total. That is a real gap — and it is also the gap the practice below closes, because preparation blocked as an entry counts exactly like a meeting does.

Attribution depends on what the entry says, which is not something to apologise for — it is the point. See the section below.

What to do with it in the first month

• Agree the title convention first, and write it down: customer, project, what. Everything below depends on it, and it takes one team meeting rather than a rollout.
• Do not report on individuals. Start at team level. It removes the surveillance objection and it is where the staffing decision lives anyway.
• Look at the unmatched entries first. Some are genuine non-deal load — enablement, escalations, internal support — and that is usually the finding. The rest are badly titled, and they are the adoption backlog.
• Compare concurrency, not totals. Two engineers with the same meeting hours across different numbers of accounts are not carrying the same week.
• Bring one quarter to the staffing conversation, not a live dashboard. The argument is stronger when it is a period, and safer when it is not a screen someone can refresh.

The point is an argument you can make

technical sales leaders are routinely asked to justify headcount with evidence they do not have, and then given activity counts that argue against them. A measured picture of where the week actually went — including the part that has nothing to do with any deal — is a better starting position, and it costs one OAuth connection plus a title convention rather than a process nobody will follow. The reporting is the smaller half of the return. The larger half is that a team which writes down what each block is for starts noticing, in advance, which weeks were never going to work. It pairs with technical win rate: one says what the team is carrying, the other says whether the carrying is working.