For AI-Assisted Inbox & Follow-Up
AI-Assisted Inbox & Follow-Up
For solo operators whose clients’ inboxes outpace their attention — AI-assisted triage, decision-grade categorization, drafted replies, and a follow-up cadence that keeps threads alive without burning your week.
Four operating pillars
What the engagement actually looks like.
Four operating commitments that distinguish solo-direct AI-triage from a generic shared inbox bolted onto a CRM.
Every inbound is sorted into urgent / wait / escalate before the senior opens it — what lands, what waits, what gets pushed to the top so a paying client is never buried under a vendor update.
Decision-grade labeling of inbound vs. async vs. billing vs. follow-up, so the inbox is readable at a glance and the close at month-end does not surprise you with unmapped threads that changed scope.
Pre-written responses drafted against the standing engagement — every draft reviewed by the senior before it leaves. You stay in the loop on tone, the keyboard never gets ahead of the relationship.
A persistent rhythm of nudges — open proposals get reminded, unbilled threads get pinged at the right interval, stale deals get re-litigated. Threads do not die silently because nobody watched the inbox that week.
How this differs
Solo-direct AI-triage, instead of a generic shared inbox.
Generic shared inbox
Sandomenico AI-triage
Ad-hoc scan of a shared inbox once or twice a week, sorted by whoever had time.
Triage SLA surfaced every morning so the senior sees what matters first.
A single "needs reply" tag that flattens everything into the same queue.
Categorization across inbound, async, billing, and follow-up buckets — held consistent across engagements.
Auto-replies that ship in your voice without a single human review pass.
Drafted replies reviewed by the senior before send, so tone stays yours.
Follow-up that lives in a sticky-note or a flag nobody re-checks after Friday.
A persistent cadence log so follow-up never depends on remembering who owes what.
Inbox that runs hot from 9-to-5 and goes cold the moment the laptop closes.
Coverage across declared working hours — evenings and weekends are scheduled, not ad-hoc.
Monthly deliverables
Five recurring artifacts, every engagement.
The same five artifacts ship every month against the published scope — no separate invoice for the cadence log or the quarterly snapshot.
Weekly inbox triage report
Categorization matrix
Drafted-reply queue (approved before send)
Follow-up cadence log
Quarterly attention-cost snapshot
Monthly cadence — five recurring artifacts an inbox-management engagement receives, no extra invoices layered on top.
Solo-direct AI-triage, in your words
Common questions a solo operator asks before signing.
The four decisions a solo operator makes before signing an inbox-management engagement — and why the solo-direct AI-triage model answers each one without a generic shared inbox in the loop.
What does AI triage actually replace in a solo inbox?
It replaces the ad-hoc scan that runs once or twice a week when the inbox finally feels heavy. The triage SLA surfaces every morning sorts inbound into urgent, wait, and escalate before the senior opens anything, and the categorization matrix holds inbound, async, billing, and follow-up buckets consistent across weeks. Drafted replies sit in a queue the senior reviews before send, and a follow-up cadence log keeps open proposals reminded, unbilled threads pinged, and stale deals re-litigated at the right interval. The published flat retainer absorbs the four pillars (triage, categorization, drafted replies, cadence), so a paying client is never buried under a vendor update and a thread never dies silently because nobody watched the inbox that week.
How does the flat retainer cover inbox volume — don't you bill per message?
No per-message meter. The published flat monthly retainer is written down against a written scope before kickoff, and the only thing that moves the price is a written scope change, also written down before any additional work begins. Five recurring artifacts ship every month against that retainer — the weekly inbox triage report, the categorization matrix, the drafted-reply queue, the follow-up cadence log, and the quarterly attention-cost snapshot — so the billable headline does not compound when the inbox does. The flat structure is what lets solo-direct AI-triage absorb inbox volume without turning every missed reply into a separate invoice layered on top.
What do you actually deliver each month on an AI-inbox engagement?
Five recurring artifacts ship every month at the published flat price, no separate invoice layered on: a weekly inbox triage report sorting urgent, wait, and escalate before the senior opens anything; a categorization matrix holding inbound, async, billing, and follow-up buckets consistent across weeks; a drafted-reply queue the senior reviews before send; a follow-up cadence log keeping open proposals reminded, unbilled threads pinged, and stale deals re-litigated at the right interval; and a quarterly attention-cost snapshot surfacing what the inbox actually cost in attention across the engagement window. Those are the recurring deliverables priced into the flat retainer — anything outside them is a written scope change, written down before any additional work begins.