You’ve probably noticed it: that admin task that should take 15 minutes somehow eats up 45. Or the “quick email” that turns into a chain. Or the booking that involves three back-and-forths because nobody captured the right detail upfront.
At eDivert, we’ve been watching this pattern for years. And we’ve learned something important: the problem isn’t that you’re slow. It’s that the task wasn’t clearly defined in the first place.
The hidden cost of fuzzy scope
When you bill by time (like we do), fuzzy scope becomes a real problem. Not because you’re trying to overcharge — you’re not. But because unclear tasks expand to fill the time available.
A “quick follow-up email” becomes:
- read history
- interpret context
- draft
- confirm details
- send
- log
That’s not one task. That’s five.
The same happens with bookings, quotes, chasing invoices, and CRM updates. Each one has invisible steps that don’t get counted until they’ve already happened.
The result? You’re delivering more value than you’re charging for. Which feels good in the moment. But it’s not sustainable — and it hides the real cost of serving different clients and different task types.
What we see most often (the patterns)
When we break admin down properly, a few patterns show up again and again:
- Small tasks that are rarely smallA “standard” follow-up should be one 15-minute block. Without a template or a clear brief, it becomes two or three.
- Rework driven by missing intake infoIf the initial call/chat doesn’t capture the right details, the admin task expands. You end up chasing clarification instead of just doing the work.
- Some client types cost more to serve (and that’s OK)Not because they’re bad clients. Because their work is inherently more complex: more stakeholders, more precision, more back-and-forth.
- Context switching has a hidden taxA task done during peak comms windows costs more in real strain than the same task at a quiet time.
The fix: define “standard” vs “non-standard”
Here’s the simple fix that changes everything: define what “standard” looks like for each task type.
A standard booking might be:
- client calls
- You confirm details from a template
- You log itThat’s one block.
Anything beyond that — multiple reschedules, unusual requirements, stakeholder coordination — is considered “non-standard” and billed accordingly.
Still fair. Still transparent. But now everyone knows the rules.
This isn’t about charging more. It’s about clarity. When clients understand what “standard” means, they can:
- plan their requests better
- avoid scope creep
- predict their costs more accurately
And you can:
- protect margin
- deliver consistently
- Stop subsidising hidden complexity
Templates, checklists, and category-based minimums
Once “standard” is defined, the next steps are practical:
- Micro-templates: checklists for “standard booking”, “standard follow-up email”, “standard supplier call”.
- Category-based minimums (not blanket minimums): e.g., supplier coordination often involves hold time and multiple attempts, so it’s realistically a 2-block minimum.
- Workflow bundles: if a client triggers six separate “tiny” tasks that are really one workflow, bundle it so it’s clearer for them and sustainable for you.
Why this matters (especially for eDivert clients)
You’ve built a service on trust and reliability. (Your renewal rate after the first three months is extremely strong — that only happens when clients feel looked after.) A clear scope doesn’t damage trust. It protects it because it keeps expectations and costs predictable.
Clarity isn’t cold. It’s kind. It means you can keep serving clients well without burning out your team or quietly eroding margins.