Working in public
Real transformations. Ongoing.
These are active engagements, not case studies. The work is still in progress, the messiness is still present, and the patterns are universal. We share them because the honest picture is more useful than a polished one.
The organizations are real. The challenges are universal. None of these are finished — that's the point.
Case studies are written when the work is clean. These aren't case studies. They're snapshots of engagements in motion — with the friction visible, the what's-still-messy documented, and the pattern named honestly. We show you the real picture because the real picture is what's useful.
Every story on this page carries a universal pattern — a recurring shape of how organizations get stuck, and what it looks like to start getting unstuck. The industry changes. The team sizes vary. The pattern holds. If you see your situation in one of these, that recognition is itself something worth paying attention to.
You are not alone in this. The complexity you're feeling isn't a sign that something is uniquely wrong with your organization. It's a sign that you're running a real organization with real operational weight. The question is whether you're ready to do something about it.
What changes when the work is rebuilt.
These come from active engagements, anonymized by function. Some are capabilities already in place. Two — the scheduling and invoicing figures below — are the outcomes we're building toward in a transformation still underway: targets the new system is designed to hit, not results we're claiming yet. We'd rather show you the real target and the real starting point than dress up a number that isn't in yet.
Weekly scheduling coordination
Projected — in build15+ hoursTarget: under 2 hoursField operations, 50+ daily jobs. The new system is designed for this; not yet measured in production.
Invoice creation
Projected — in build15-20 minutes per invoiceTarget: under 1 minuteManual copy/paste eliminated by design; the under-1-minute figure is the target, not a measured result yet.
Sales proposal building
Capability liveContext-switching between 4 systemsBuilt inside a single deal recordInventory, maps, and contract data unified — this exists today.
Revenue attribution
Capability liveChannel revenue a guessAttribution visible in dashboardsEvent revenue validated within $10K — the one measured proof point in this band.
Proactive sales outreach
Capability liveReactive — waiting for contractors to callTriggered by public permit activityIntelligence surfaced before competitors are called — this exists today.
Real engagements. Real patterns. None of them finished.
Each card below is an active engagement. Click through to see the full picture: what was happening, what the symptoms were, what's different now, and what's still messy. The quote at the top of each is real — said in a session, in the language of the person living it.
Fitness Equipment Manufacturing & Distribution
The Fitness Equipment Company
Three systems. No shared substrate. The CFO was running finance from a spreadsheet bridge.
~50 employees, 8 sales territories
active
Infrastructure Services (UK)
The Traffic Management Company
75% of their business ran on WhatsApp
50+ field operatives
active
Outdoor Advertising / Media
The Billboard Company
Real-time inventory from three different systems
Multi-market sales team
active
Wine & Hospitality
The Napa Winery
Multi-million dollar visibility problem
~30 employees
active
Sports Technology / SaaS
The Sports Tech Company
400-500 workflows with unclear dependencies
~20 employees, scaling 3-5x
active
Building Materials / Retail
The Lumber Company
Building permits as sales intelligence
Regional multi-location
active
B2B Consulting / AI Operations
The Consulting Team
Building the infrastructure while serving clients
Small team (2 principals + specialists)
active
The pattern underneath all of it.
Across every engagement on this page, the same dynamic shows up: a system that made sense when it was built, behavior that adapted around it over time, and a gap between how the work was supposed to happen and how it actually does. No organization is immune to this. The question isn't whether the pattern is present — it's whether you're ready to name it clearly and do something about it.
If something here resonates, that's the starting point. Not a form to fill out, not a scope to commit to — just a conversation about what you're seeing and whether we're the right fit to help you do something about it.
See your situation in one of these?
Start with a conversation. There's no scope to commit to before we both understand what you're working with.