The phone rings for status checks
None of those calls moves a file forward, and each interrupts someone who was moving another one. It's the least visible cost in any business that delivers over weeks.
A client portal only reduces calls if it shows information fresher than what a customer would get by phoning. That's the condition everything hangs on: a manually updated portal lags, so the customer calls anyway, and you've paid for a second thing to keep current.
None of those calls moves a file forward, and each interrupts someone who was moving another one. It's the least visible cost in any business that delivers over weeks.
Quotes, plans, approvals, photos. Three versions later nobody knows which one the client actually approved — and that's the one that matters in a dispute.
A client managing forty suppliers wants to check progress without emailing forty people. Increasingly, it's a selection criterion.
What the client sees is what your team sees, at the same second. No double entry, no lag — and therefore no reason to call and check.
A client doesn't need to see your margins, internal notes or the subcontractor's name. What's visible is decided with you, written down, and auditable.
Who approved which version, and when. It's often the portal's most concrete value, and it shows up on the day of a disagreement rather than day to day.
This isn't for you if your tracking information doesn't yet live in a system: the portal would then show emptiness, or force someone to fill it in — precisely the work it was meant to remove. In that case the right order is the system first, the portal second.
No sales page writes this section. That's precisely why it's here: it saves you a thirty-minute call, and saves us an engagement we'd decline anyway.
Only some of them, and that's enough. A portal absorbing half the status requests has paid for itself, and those who prefer to call will keep calling — the phone is never removed.
Not necessarily. For one-off file tracking, a time-limited private link avoids the friction of creating an account. For a recurring client consulting history, an account makes sense. The choice depends on frequency, not technology.
You leave with what we saw, in writing, even if we never work together.