Async advisory: what works, what doesn't, and how it fits between calls

The default shape of paid advice is the scheduled call. Thirty minutes, sixty minutes, weekly or monthly, on the advisor's calendar. It's the shape because it's legible. It feels like work. It's easy to invoice for. On its own, it misses a lot of what happens between sessions.

The problem with the scheduled call is that founder questions don't arrive on a schedule. A customer sends an email Tuesday afternoon that you can't parse and you have to decide by Wednesday morning whether to keep building what you're building. A call on Friday doesn't help. By Friday you've already made the decision, you've spent three days circling it, and the cost wasn't the decision itself but the three days of being stuck.

Async between calls fixes that. You bring the question the moment it appears, in the channel you already live in, and you get a thoughtful written answer in hours instead of days. The answer is in writing, which means you can re-read it, forward it to a cofounder, paste it next to the customer email and actually compare. Above all, the cost of asking is low, which means you ask the small things that you'd never schedule a call for and the small things are usually where founders get stuck.

Async also strips away the meeting overhead. No video, no small talk, no calendar Tetris, no preparing notes for a 30-minute window. The relationship shows up where the work is happening.

Async breaks down in three places. First, when the question is genuinely a conversation, when you need to think out loud and have someone redirect you in real time. Second, when emotional weight is high and writing it down would take longer than saying it. Third, when the founder is the type who needs the appointment to actually do the work; the discipline of a scheduled call is what forces them to bring the question in the first place. For those three cases a call helps, which is why The Practice combines biweekly 1:1 calls with Slack access between calls, transcript reviews, and work on the MVP and spec over 3 months.

Between those calls, async does the rest. Lower friction, faster turnaround, a written record, and it fits the cadence of building. The calls give the work structure, and Slack keeps it moving in between.