Clarity over jargon
If a recommendation needs a glossary to be understood, it's not ready for a client meeting yet. We push toward plain, direct language in every deliverable we look at, including this website.
What shapes the program
The values behind how we teach this
None of this is complicated, which is sort of the point. Good advisory work is mostly clarity, restraint, and doing real things instead of talking about them.
Real work, not hypotheticals
Case studies with made-up numbers are easy. Feedback on the proposal you're actually sending next Tuesday is harder, and more useful. That's what the async submissions are built around.
Small groups, on purpose
Cohorts stay small enough that facilitators can actually engage with each person's material. That's a constraint we keep deliberately rather than opening every seat available.
Positioning over tricks
We're not teaching a script for sounding more senior on a call. We're working on the underlying structure of how you scope, price, and frame your work so the shift holds after week eight ends.
Honesty about fit
This program isn't built for every analyst at every stage. We'd rather say plainly who it suits and who might want to wait than fill every seat regardless of fit.
Why this exists
Built by someone who did the execution work too
The program grew out of a fairly ordinary observation: a lot of freelance and independent analysts are excellent at the technical side and genuinely uncomfortable with the business side. Pricing conversations feel awkward. Recommendation memos turn into ten-tab spreadsheets nobody opens. Scope creeps because nobody wrote down where the engagement was supposed to end.
None of that is a skills gap in the traditional sense. It's a different discipline, one that usually gets learned the hard way, through a few uncomfortable client conversations and a couple of underpriced projects. This program is an attempt to shorten that path a little, with structure and feedback instead of trial and error alone.
Ground rules
A few things we ask of every cohort
01
Bring real material. Feedback on hypothetical projects is fine in week one, but by week five we're working on your actual pipeline.
02
Show up for both weekly sessions when you can. The format depends on continuity, not just consuming recordings later.
03
Give feedback as generously as you take it. Cohorts work because analysts are willing to critique each other's drafts honestly.
04
Expect to feel a little exposed. Sharing a real proposal with strangers is uncomfortable at first. That discomfort tends to fade by week three.