Send it however it comes out of your head

The channels are the contract

Everything arrives through channels that capture on arrival: WhatsApp — text, voice notes, images, calls — email, meetings (recorded and transcribed, with your agreement), documents and screenshots.

That list is not a preference. It is the reason the rest of this page is true: work I can’t capture is work that depends on someone remembering, and remembering is the thing that fails.

What happens next, in order

1. 01

   It gets captured — usually within minutes.

   Transcribed if spoken, read if it's an image, filed against the thread it belongs to.

2. 02

   It becomes a tracked item, cited back to your message.

   Not a note I made about what you said — a row that points at the thing you actually sent, with its timestamp. So “did you get my message about…” stops being a conversation we have.

3. 03

   You get a first version fast.

   Built on stated assumptions, imperfect on purpose. You point at what's wrong; the next version is closer. Correcting a draft is faster than writing a specification.

4. 04

   Corrections are captured too, and they compound.

   The second month is cheaper than the first, because the system knows what you meant last time.

5. 05

   Nothing irreversible happens without your yes.

   Drafts, analysis, builds, proposals — machine speed. Sending in your name, spending, deleting, publishing — those wait. Speed lives in the drafts, never in the risks.

Answers come back the way you can actually take them

Some things you want to read. Some you want to hear — while driving, between meetings, at the end of a day when reading one more document is not happening. So the answer sometimes arrives as a short spoken brief, with the text on screen and each word lit as it’s said. Listen, read, or skim: same artifact, three speeds.

This is what surprises people about working asynchronously: it doesn’t feel asynchronous. You are not writing into a void and waiting for a status report on Friday.

Where the human hours actually go

Not into producing any of this. Into deciding what it should say. Reading, searching, drafting, building a working version, chasing something across three systems — that runs continuously and doesn’t need me awake. What needs me is judgment: what matters, what’s wrong, what you actually meant, and what should not be done at all.

The shape of an engagement

Every engagement starts the same way: one paid month. Paid, because a trial is not free work — you are buying a month of output, not an audition. Bounded, at a fixed price with an agreed scope. Two-way: at the end, either of us renews or walks. Not a marriage. And yours — every tracker, workflow and document I build stays with you, whatever you decide.

Onboarding me costs one conversation, not a week: minimal system access to start, and first deliverables built from your own documents and exports.

Audit week$3,000

Your workflows read closely; three automations built and working before the week ends; a written map of what to do next that ends in fixed prices rather than a pitch.

Bridge monthpriced against the seat

You're hiring for an ops role. While you search, I carry the urgent core — and your eventual hire inherits a documented, running setup instead of a cold start. Roughly a third of what the empty seat costs you per month.

Retainerfrom $6,000/mo

Your operations, run. Asks in, work out.

Who this fits

• You want output, not presence — trackers current, follow-ups chased, answers delivered; not a body in meetings.
• Your asks arrive in whatever form they arrive. Voice notes count; they're captured too.
• You'd rather correct a draft than write a specification.

Not a fit: work that needs someone live in the room all day, on-demand real-time availability, or managing people. If I think we’re not a match, I’ll say so in one email.

What this has produced

One line of work became three engagements — each one referred the next.

People extend work like this from one business to the next only when it holds.