The Hidden Cost of "Just Emailing the Client": A Time Audit for Swiss SMEs

Ask any Swiss SME owner how they share files, invoices, or project updates with clients, and you'll likely hear some version of: "we email it." It sounds efficient. It rarely is. Multiply the small frictions — a status update here, a resent PDF there — across a week, and you get a surprising number of hours that never show up on any invoice.

Where the hours actually go

None of these tasks look expensive in isolation. That's exactly why they add up unnoticed:

• "What's the status?" emails and calls: a handful of clients asking for a quick update, each interrupting focused work for 5-10 minutes once you factor in the context switch.
• Re-sending invoices: "Can you resend that, I can't find it" — a two-minute task that also breaks your concentration and often happens right before a payment deadline.
• Chasing signed documents: emailing an NDA or agreement, waiting, following up, then manually filing the version that comes back.
• Explaining project scope to new stakeholders: every time a client adds a colleague to a project, someone on your side has to re-brief them from scratch.
• Sorting who should see what: making sure the client's junior staff don't see the invoice thread, or that a subcontractor doesn't see unrelated financial data.

For a small team of two or three people handling client-facing work, this easily totals several hours per week — not because any single task is hard, but because each one pulls someone out of deep work and back into email triage. At a blended rate of CHF 80-120 per hour for skilled staff, a conservative 4-5 hours a week of this kind of admin adds up to real money over a month, and it's time that never appears as billable client value.

The fix isn't "answer emails faster" — it's removing the emails

The recurring problem isn't a communication skills issue. It's that clients have no self-serve place to look. Every question becomes a message because there's nowhere else to check. A customer portal solves this by giving each client a private, branded space where they can find things themselves — invoices, files, project status, and a direct chat — without waiting on you to reply.

How the setup actually removes the friction

The mechanics matter here, because a portal only saves time if it's genuinely easy to hand out and control:

• Magic-link invites: you send an email, the client sets a password, they're in. No onboarding call, no shared login spreadsheet.
• Per-user feature toggles: choose exactly what each person sees — Work, Chat, Invoices, Files, AI Assistant — in any combination. The client's project manager and their accounts payable contact don't need the same view.
• Collaboration without chaos: customer collaborators can comment and edit on Work tickets directly, so status questions get answered inside the ticket instead of in a separate email thread. Moving or deleting tickets stays reserved for your team, so the board doesn't get accidentally reorganized.
• Invoices reach the right eyes only: billing-contact users automatically see shared invoices; other collaborators never see financial data at all. No more worrying about who's cc'd.
• Drag-and-drop files per customer record: NDAs, signed agreements, deliverables — uploaded once, findable by the client whenever they need it, instead of buried in an inbox.
• A scoped AI assistant: clients can ask "what's the status of our project?" and get an answer immediately, without a message ever reaching your team — and without any risk of seeing another client's data.

What this is worth, in practice

If even half of the routine status-check and resend traffic disappears because clients can self-serve, a small team recovers a meaningful block of focused hours every week — hours that go back into billable work, sales follow-up, or simply leaving the office on time. The per-user access controls also remove a quieter cost: the mental overhead of remembering who's allowed to see what. That's not something you can put a franc figure on directly, but it's the kind of background stress that eats into decision-making all day.

There's also a growth angle built in. When a client relationship outgrows a simple portal — say they want their own instance to manage their own team — they can become their own Flitz tenant in one click and keep collaborating with you. No migration project, no lost history.

Start with the biggest time drain

You don't need to roll this out to every client at once. Start with the two or three accounts generating the most "can you resend / what's the status" traffic, invite them in, and set their access to match how you already work with them. The time saved in the first week is usually enough to show whether it's worth expanding further.