Skip to content
Menu

Sample report

Sample automation opportunities report

This is what an automation opportunities report from hey.space looks like: 38 people in 4 teams, measured over a 14-day pilot. It covers context switching, time in apps, repeated sequences of work and a ranked list of what to automate, with the hours and cost each automation would save.

Illustrative figures. This preview uses example numbers in the format of a real report. It will be replaced with anonymized data from TimeCamp’s own teams. How the figures are built

01

Summary: hours you could get back

198 h

a month the top 8 automation candidates would save

$9,306

a month in team time, at $47 per hour

10.9

app switches per hour, on average

38%

of the sales team’s time in communication tools

The largest single opportunity is in support: copying ticket details into Jira bug reports takes 38 hours a month and needs only a no-code workflow.

02

Context switching across tools

Support and sales switch apps the most, because their work spans a helpdesk or CRM, chat and email. Engineering switches least and keeps the longest blocks of focused work.

App switches per hour by teamSupport14.2Sales12.6Finance9.4Engineering7.9
App switches per hour of active time, average per person in each team.

03

Time in apps by team

Sales spends more time in communication tools than in its CRM. Finance spends more than a third of its time in spreadsheets, the clearest sign of manual data work.

SupportCore tool: Zendesk
SalesCore tool: Salesforce
FinanceCore tool: Billing and accounting
EngineeringCore tool: IDE and GitHub
  • Core work tool
  • Communication
  • Docs and spreadsheets
  • Browser, other
  • Other apps
Share of active time by app category. The table below has the same numbers.
TeamCore work toolCommunicationDocs and spreadsheetsBrowser, otherOther apps
Support46%27%9%12%6%
Sales31%38%14%12%5%
Finance34%18%35%8%5%
Engineering58%21%6%11%4%

04

Repetitive task sequences

The sequences of apps that repeat most often, with the time they take each month.

  • ZendeskJiraSlack

    Support · 41 times a week · 6.5 min each · about 19 h a month

  • SalesforceGmailSalesforce

    Sales · 63 times a week · 3 min each · about 14 h a month

  • Billing toolGoogle SheetsBilling tool

    Finance · 28 times a week · 9.5 min each · about 19 h a month

  • GitHubJiraSlack

    Engineering · 35 times a week · 4 min each · about 10 h a month

05

Time and cost per task, ticket and deal

With Asana, Zendesk, Salesforce and Jira connected, activity is matched to the work it belongs to, so each work type gets a real time and cost, including the time spent outside its own tool.

Work itemAverage timeAverage costNote
Content update task (Asana)2.1 h$9931% of the time spent outside Asana
Support ticket (Zendesk)0.4 h$191 in 5 tickets also touches Jira
Won opportunity (Salesforce)6.4 h$30142% of deal time in email and calls
Bug fix (Jira)3.2 h$150Plus 1.1 days waiting in review

06

Handoffs between tools

The most frequent paths work takes between tools. Each one that repeats with the same steps is a candidate for automation.

  • HelpdeskJiraSlack

    41 times a week

  • SalesforceGmailSalesforce

    63 times a week

  • GitHubJiraSlack

    35 times a week

  • Billing toolGoogle SheetsEmail

    28 times a week

07

Automation candidates ranked by hours saved

Automation candidates ranked by hours saved per month
#TaskTeamHours / monthCost / monthEffortTool type
1Copy ticket details from Zendesk into Jira bug reportsSupport38 h$1,786LowNo-code workflow
2Update Salesforce opportunities after sales callsSales34 h$1,598MediumAI agent
3Answer repeated “how do I” tickets with saved repliesSupport31 h$1,457MediumAI agent
4Match payments to invoices between billing and a spreadsheetFinance29 h$1,363MediumRPA
5Compile the weekly status report from Jira and SlackEngineering22 h$1,034LowAI agent
6Move new trial accounts from the CRM to the onboarding sheetSales18 h$846LowNo-code workflow
7Export monthly time and cost reports for clientsFinance14 h$658LowNo-code workflow
8Triage new GitHub issues into JiraEngineering12 h$564LowNo-code workflow

Cost uses $47 per hour. Effort is an estimate of the work to build and run the automation.

08

Methodology and privacy

  • Data sources. Activity from TimeCamp’s desktop app (apps, websites, time and switches between them) and tasks, tickets and deals imported from the team’s tools, matched by AI.
  • This report’s data. Illustrative figures that follow the same formulas as a real report. They will be replaced with anonymized data from TimeCamp’s own teams, collected with their consent.
  • Cost. Hours are valued at $47 an hour, the average U.S. private industry employer cost per hour worked (BLS, June 2026), rounded.
  • Privacy. Results are shown for teams, tasks and work types, never as scores for individuals. In a pilot, everyone is informed and gives consent before any data is collected.
Definitions and formulas behind every number

Get the full report by email

The full report has every section in detail, with the method behind each estimate and the steps of each automation candidate.

Want this report for your team?

30-minute call. We’ll show what a 2-week pilot on your team’s data would reveal.

Book a free automation assessment

We use your email to send the report and follow up about the assessment. See our privacy policy.