A solo consultant's business model has an unforgiving property: the same person sells the work, does the work, and administers the work. Every hour of email is subtracted from one of the first two, which means inbox overhead isn't an annoyance; it's the margin. Fractional operators running three or four clients feel it hardest, because each client reasonably expects the responsiveness of a full-time hire.
State your standard once
The pressure to be always-on is mostly self-inflicted; the research on response expectations shows clients anticipate same-day, not same-hour. So say it once, visibly: "I process email mid-morning and late afternoon and reply the same business day; call for anything urgent." A stated rhythm converts silence-anxiety into predictability, and predictability is what clients actually rate as professional. Then batch to that rhythm; the method here, fitted around client blocks instead of meetings.
The proposal that chases itself
For a solo practice, the most expensive email failure is the sent proposal aging in silence. Not rejected: unattended. Every proposal, invoice, and scoping question you send should become a dated waiting-for entry the moment it leaves, with a chase cadence attached: a two-line nudge at three business days, a value-adding second touch at a week, then a graceful close-out that keeps the door open. The scripts are here; the discipline is just the list.
Can a one-person business justify an AI email assistant?
The economics run opposite to intuition: automation pays most where there's no staff to absorb the admin. Every message sorted, every routine reply drafted, every invoice chased automatically converts directly into billable or sellable hours, because there was never anyone else to do it. Pidgy plays the assistant role on Gmail or Outlook: sorts the inbox, drafts replies in your voice, keeps the waiting-for list, and queues the chasers, with you approving every send. The unbilled hour count drops toward the only number a solo practice wants it at: near zero. The one-person setup in detail: the solo consultants use case.
