payroll contingencies playbook for client concentration (before you need a “hero week”)

Published 2026-01-17. When client concentration and payroll contingencies show up together, it is rarely theoretical—it is a calendar problem colliding with family responsibilities. The goal is continuity that is honest about time: what can be delegated, what needs your judgment, and what should not live only in your inbox.

Turn payroll contingencies into a simple week-one plan

Start with client concentration: what it touches (cash, vendors, teams), what breaks if it stalls, and who is allowed to act. If you cannot name a backup for approvals, you have found the first line to write down.

Reduce “unknown unknowns” with one narrative pass

Most owners already know the risky corners. The hard part is writing them in language a loved one can follow—not internal shorthand. Stillago sections are structured for that translation.

• Devices and access: where 2FA codes should not become single-person bottlenecks.
• Money map: inbound, outbound, and the subscriptions you forget until they fail.
• Keep vs pause vs kill: pre-made decisions your household can respect under stress.

Stillago is built as a structured emergency operations manual—sections for people, devices, money, vendors, and narrative context—so answers exist in one place instead of across bookmarks, inboxes, and memory.

When revenue is concentrated, payroll risk is emotional too

Client concentration means a single customer delay can ripple to payroll confidence. Name the top customer’s payment cadence alongside payroll dates so backups understand why “everything is fine” might still feel tight.

• AR aging: who follows up when a large invoice slips.
• LOC or reserve: where liquidity lives if receivables wobble.
• Communication: what employees should never hear improvised.

Advisors often see this pattern early—see quiet owner signals for how portfolio triage surfaces it without shame.

Model a two-week customer delay, not only catastrophe

Concentration risk is often mundane: a PO stuck in legal, a net-90 that became net-120. Run the boring scenario so payroll conversations stay factual.

Separate “we are tight” from “we cannot pay” in internal language

Employees fill silence with their worst fears. Calibrated language in your manual prevents accidental panic.