The Lobbi Delivery Team
Operational Systems Engineering
Somewhere in your business right now, a customer-facing person is making a promise — a quote by Thursday, an installation next week, a resolution within two days. That promise depends on three or four internal handoffs. And not one of those handoffs has a committed turnaround.
This is the asymmetry nobody examines. Externally, your business runs on explicit commitments: quoted lead times, contracted response windows, delivery dates. Internally, the same business runs on hope. The estimating request will be answered when estimating gets to it. The approval will happen when the manager checks email. The customer promise is a chain whose links were never forged.
Why Internal Handoffs Default to Vague
No one decided that internal requests should have no deadlines. It happens because internal work arrives through channels designed for conversation, not commitment — chat messages, hallway asks, emails with no due date field. The requester hesitates to impose a deadline on a colleague. The receiver triages by recency and loudness. Both behave reasonably. The system they form behaves terribly.
The cost shows up in two places. First, in cycle time: every unpromised handoff is an unbounded queue, and unbounded queues stretch under load exactly when customers are most demanding. Second, in escalation culture: when the only way to get a turnaround is to mark something urgent or walk over to someone's desk, urgency inflates. Soon everything is urgent, which means nothing is, and your most conscientious people burn out absorbing the ambiguity.
What an Internal SLA Actually Is
The term sounds corporate. The thing itself is small: a visible, agreed answer to one question per handoff — when can the requester expect a response?
- Pricing requests: answered within 1 business day.
- Capacity checks: answered within 4 business hours.
- Document review: 2 business days.
- Internal IT requests: acknowledged same day, resolved or scheduled within 3.
Software teams formalized this years ago as service level objectives, and the operational insight transfers cleanly to any business: a target that is visible and measured changes behavior on both sides of the handoff. Requesters stop padding everything with false urgency because the default is trustworthy. Receivers gain a defensible way to sequence work — and a defensible way to say that demand has exceeded capacity.
That last point is the quiet payoff. When a team misses a visible 1-day commitment three weeks running, you have learned something real: the team is under-resourced, the demand is misrouted, or the commitment is wrong. Without the commitment, the same facts surface as interpersonal friction — that team is slow, that department never responds. Internal SLAs convert blame into data.
Setting Them Without the Bureaucracy
The failure mode to avoid is the 40-row SLA matrix nobody reads. Start with the handoffs that sit underneath your most important customer promise. There are usually three to five.
- Map one customer commitment back through every internal handoff it depends on.
- For each handoff, have the two teams agree on a turnaround they can hit 90 percent of the time — agreed, not imposed. A commitment set by the receiving team is a promise; one set for them is a quota.
- Make request age visible where the work lives — a shared view, a board column, anything with a timestamp.
- Review breaches weekly in ten minutes: which commitments were missed, and was the cause volume, routing, or the target itself?
| Handoff | Expectation | Measured how |
|---|---|---|
| Sales to estimating | Quote inputs within 1 business day | Request timestamp vs response |
| Ops to manager | Approval within 1 business day | Age of pending approvals |
| Field to office | Job paperwork same day | Submission time vs job completion |
| Any team to IT | Acknowledged same day | First-response time |
The Compounding Effect
Once internal turnarounds are explicit, something useful becomes possible: you can add them up. If a quote requires four sequential handoffs at one day each, the honest external promise is a week, not the optimistic Thursday that keeps getting missed. Either the business accepts that math and quotes honestly, or it redesigns the chain — parallelizes steps, pre-authorizes approvals, shortens a queue. Both outcomes beat the current one, where the gap between promise and process is absorbed by apology.
Customer trust is built on kept promises. Kept promises are built on internal ones. Make the internal ones exist, and the external ones stop being a gamble.
External promises are explicit. Internal promises do not exist. The customer deadline dies quietly in the gap between those two facts.
Sources
Topic clusters
Ready to see where the friction is?
The Lobbi's Operations Discovery maps your workflows, identifies your highest-impact bottlenecks, and gives you a clear picture of what's possible.