CommsOS Discovery & Support
Let's figure out what's broken.
You just made a smart move. Not because you hired me — because you decided to stop winging your communications and build actual infrastructure instead.
Most founders and nonprofit leaders spend years patching together one-off solutions: a freelancer here, a template there, a social media strategy that someone swore would work. None of it compounds. None of it survives the person who built it leaving.
CommsOS is different. It's an operating system — a permanent communications foundation that runs whether I'm involved or not.
Let's see if it's right for you.
What happens now
Step 1: Your diagnostic call
You'll receive an email within 24 hours to schedule your 60-minute 1-on-1 diagnostic. This is where we figure out if CommsOS actually solves your problem — honestly, not as a sales pitch.
In that call, I'll map:
- Where your communications currently break
- What's costing you the most time, money, or credibility
- Whether a CommsOS build is the right fix or whether something else would serve you better
You'll walk out with a clear gap analysis and a roadmap — regardless of whether we continue working together.
Step 2: Monthly group office hours
Once a month, active subscribers join a live group session where you can bring implementation questions, get feedback on what you're building, and hear how other organizations are solving similar problems. These are working sessions, not webinars. Recordings, transcripts and supporting content will be provided for those who couldn't make the live session.
Step 3: Async support
During weekly office hours, you have direct access to me for questions that come up between calls. Quick diagnostics, copy review, strategy gut-checks — the kind of support that prevents small problems from becoming expensive ones.
What CommsOS actually is
Most communications consulting gives you a deliverable — a brand guide, a content calendar, a messaging doc — and then leaves. You're back on your own in 90 days.
CommsOS gives you a system. A voice architecture, decision frameworks, forbidden patterns, and operational workflows that your team can run without a consultant in the room. It's built on AI (specifically Claude) so a team of two can operate with the communications capacity of a team of ten.
The 75% rule: AI gets your outputs to 75% fast. Your team edits for voice, accuracy, and the things only humans can catch. That's the methodology. It's being documented openly and will eventually be fully open-sourced.
Who this works for
This tier is right for you if:
- You're a founder, nonprofit leader, or small team (under 15 people)
- You have communications needs that outpace your current capacity
- You're tired of outputs that don't sound like you
- You want infrastructure that compounds, not deliverables that expire
- You're open to using AI as a tool without losing your authentic voice
This tier is probably not right for you if:
- You need someone to run your communications for you (that's a hire, not a system)
- You want a full CommsOS build with dedicated implementation support (→ click here to learn what's possible)
- You're not willing to invest time in learning the system your team will run
If the diagnostic call reveals this isn't the right fit, I'll tell you. And I'll point you toward what is.
One more thing
I've spent 25 years building communications infrastructure inside institutions — newsrooms, tech companies, nonprofits, DAOs. The pattern I kept seeing: organizations with brilliant work and terrible communications, not because they lacked talent, but because they lacked systems.
CommsOS is what I wished existed every time I walked into an organization and found a team of smart people reinventing the wheel every time they needed to write a grant, send a press release, or explain what they do.
Now it exists. You're one of the early ones using it.
Let's build yours.
Next steps:
- Watch for the scheduling email (within 24 hours)
- [Link to CommsOS overview or methodology page] — background reading before our call
- [Link to what to prepare] — optional, but if you want to make the diagnostic call maximally useful, gather: your current website, any existing brand/voice docs, and the last 3 pieces of communications you produced that you weren't happy with