A timed workflow test is a benchmark. You simulate a real user task (like "create a new contact from an email") and measure exactly how long it takes from start to finish. It's not about synthetic API load; it's about real UI interaction time.
You do it because marketing claims are useless. You need data. Example: you might find that CRM A takes 8 clicks and 45 seconds for a task that CRM B does in 3 clicks and 12 seconds. At scale, that's massive productivity loss.
A basic test structure:
```yaml
Task: Convert email to support ticket
Steps:
1. Open email in CRM inbox view
2. Click "Create Ticket"
3. Fill required fields (Subject, Priority)
4. Assign to queue
5. Save
Measurement: Page load times, client-side rendering delay, total clock time.
```
Why this matters:
* Exposes poor UI/UX that synthetic tests miss.
* Quantifies training cost and daily friction.
* Directly ties platform choice to business throughput.
Without timed workflows, you're just guessing.