How Wyra counts hours saved
Every Wyra dashboard shows a running Hours Saved total. This page is the formula behind it. The number is built from work Wyra completed, priced in minutes a person would need for the same task, with the time your team spent in Wyra taken off. Every input is listed below, so the number can be checked line by line.
Last reviewed: 26 August 2026 · Unit minutes are reviewed twice a year
The formula
Hours saved=Σ(work items completed × manual minutes per item)−hours your team spent in Wyra
Three rules
Only completed work counts.
An email that was sent. A research brief for a prospect who was engaged. An opportunity that reached AWS Partner Central. Wyra never counts capacity, and never counts work that could have been done.
Your team's time is subtracted.
Time spent in Wyra is logged per session and removed from the total. The Hours Saved number is net, not gross.
Every minute is published and conservative.
The unit minutes below sit deliberately at the low end of what sales teams report for each task. Under-counting is by design.
Unit minutes
| Work item Wyra completes | Manual minutes | Basis |
|---|---|---|
| Account research brief (company context, why now) | 15 | Low end of reported per-account research time¹ ⁴ |
| Contact qualified, scored, reason written | 3 | Reading a profile and recording a decision³ ⁴ |
| Personalized first-touch email | 8 | Writing only; research already complete⁴ |
| Follow-up email or social message | 4 | Derived: half of the first-touch figure; context already established |
| Send, sequence, and log one touch | 2 | Tool switching and CRM entry¹ ² |
| Direct phone number found | 5 | Wyra estimate; manual lookup across sources |
| Call preparation brief | 8 | Assembling context before a call⁴ |
| Reply drafted for a person to review and send | 5 | Derived: shorter than a first touch; thread already read |
| Opportunity created and shared with AWS through Partner Central | 15 | Manual form entry in Partner Central⁵ ⁶ |
| Opportunity update synced both ways (stage, status, closed outcome) | 3 | Re-keying a change in two systems² ⁶ ⁷ |
Unit minutes are reviewed twice a year. Changes are dated on this page and apply from the review date forward; historical totals are never restated.
A worked month
One seat — one AI SDR carrying 1,000 Active Prospects — produces roughly this in a typical month. Applying the table:
| Item | Count × min | Hours |
|---|---|---|
| Account research briefs | 400 × 15 | 100 |
| Contacts qualified, scored, reason written | 1,000 × 3 | 50 |
| Personalized first-touch emails | 1,000 × 8 | 133 |
| Follow-up messages | 2,000 × 4 | 133 |
| Touches sent, sequenced, and logged | 3,000 × 2 | 100 |
| Direct phone numbers found | 600 × 5 | 50 |
| Call preparation briefs | 20 × 8 | 3 |
| Replies drafted for review | 60 × 5 | 5 |
| Opportunities shared with AWS through Partner Central | 8 × 15 | 2 |
| Opportunity updates synced both ways | 24 × 3 | 1 |
| Work completed | ≈ 577 h | |
| Minus your team's time in Wyra | − 10 h | |
The figures above are an illustration of the arithmetic. Your dashboard uses your own counts.
From hours to cost
Hours Saved is shown in hours. If you record a loaded hourly rate and the monthly cost of tools Wyra replaced during onboarding, the dashboard also shows a cost figure:
Cost saved=hours saved × your loaded hourly rate + monthly tool spend you retired
Both inputs are yours. Wyra never estimates them for you.
What this number is not
It is a measure of work completed by Wyra, priced conservatively. It is not a forecast, not a pipeline figure, and not a guarantee of any outcome.
Sources
Each unit minute is anchored to a published source. Where a value is derived rather than measured, the derivation is stated. Sources last verified 26 August 2026.
- Salesforce, State of Sales, 7th edition (2026). Survey of 4,050 sales professionals, August–September 2025. salesforce.com
- Forrester, sales activity study: how reps spend time. forrester.com
- The Bridge Group, SDR Models, Motions & Metrics: 2025 Research Report, 10th edition. bridgegroupinc.com
- Gong, “Cold call preparation with AI insights,” March 2026. gong.io
- AWS Partner Network Blog, “Introducing AWS Partner Central agents,” June 2026. aws.amazon.com
- AWS Partner Network Blog, ACE CRM integration and opportunity referrals. aws.amazon.com
- AWS Partner Central documentation, CRM integration technical FAQ. docs.aws.amazon.com
| Row | Sources | Note |
|---|---|---|
| 1Account research brief | 1, 4 | 15 min sits below reported ranges |
| 2Contact qualified, reason written | 3, 4 | One step of a 10–15 minute per-prospect workflow |
| 3Personalized first-touch email | 4 | Below the reported figure |
| 4Follow-up message | Derived: half of row 3 | |
| 5Send, sequence, log | 1, 2 | |
| 6Direct phone number found | Wyra estimate | Published research measures contact-finding time in aggregate, not per number |
| 7Call preparation brief | 4 | Below the 10-minute floor Gong reports |
| 8Reply drafted | Derived: shorter than row 3 | Thread already read |
| 9Opportunity shared with AWS | 5, 6 | Multi-field manual form entry |
| 10Opportunity update synced | 2, 6, 7 | Re-keying one change in two systems |
Corroborating figures from practitioner sources are available on request.