Case studies

Finding leverage in how a business already runs

Case studies in growth, GTM, and operations — using data and AI to find what's slowing a business down and fix it. Details are shown by industry rather than by name to protect confidentiality; the situations, builds, and results are real.

Enterprise Software

Building a Retention Function From Zero to 31% NRR Growth

Retention
Growth
Leadership

The situation: A global software platform with 200,000+ customers across 190 countries had no dedicated retention function and was quietly leaking revenue.
The problem: Without anyone owning retention, churn wasn't being diagnosed or addressed — it was just absorbed as a cost of doing business.
What I built: Built a retention team from scratch — playbooks, an objection-handling framework, a commercial terms dictionary, and a redesigned customer lifecycle from onboarding through renewal.
The result: A 31% increase in Net Revenue Retention within 9 months, with the team scaled to 17 people.

Enterprise SaaS

Turning Monday's Commitments Into Friday's Accountability

Workflow Automation
Growth

The situation: A Sales VP at a large SaaS organization ran a dozen-plus reps through a standard weekly rhythm — a Monday pipeline call to set commitments, a Friday check-out call to review them.
The problem: No one can actively listen, coach, and take accurate notes on a call at the same time. By Friday, the specifics had faded, and the check-out call had quietly turned into a status ritual instead of real accountability.
What I built: Two scheduled agents bookending the week — one that pulls Monday's call transcript and logs every rep's commitments, one that resurfaces that exact list Friday morning with coaching prompts already attached.
The result: Friday stopped being a status update and became a real coaching conversation — no new software, no retraining, just closing a memory gap.

Read the full case study

Enterprise Networking

Owning One Customer Relationship Across Three Roles, Three Years

Retention
Growth
Leadership

The situation: An enterprise network-visibility product needed someone who could grow with the customer relationship as it matured from onboarding into a strategic account.
The problem: Most account handoffs lose context at every transition — the person managing renewal isn't the person who ran onboarding, and the customer feels it.
What I built: Owned the full relationship arc directly — Customer Success Manager, then Global Account Management, then Sales Manager — across three years on the same product line.
The result: Continuity the customer could actually feel, instead of getting handed off between strangers at every stage of the relationship.

Investor Research

Finding the Investors Standard Directories Miss

Data & Research
Growth

The situation: A team looking for family office investors was relying on the same directories and lists everyone else already knows about.
The problem: The obvious sources are crowded — directories and conference lists don't surface the family offices that haven't shown up everywhere else yet.
What I built: Three parallel research pipelines — directory scraping, conference attendee lists, and SEC EDGAR filings — feeding one combined lead list.
The result: A lead list built from sources most people never check, not just the ones everyone already has.

Web3 Infrastructure

Scaling a Company From 8 to 120 During a Leadership Transition

Growth
GTM
Leadership

The situation: An infrastructure company lost its CEO mid-growth, leaving sales, marketing, customer success, and demand-gen without a clear owner.
The problem: A company can't grow through a leadership gap — someone has to own the whole commercial engine, not just their own function, or growth stalls.
What I built: Stepped in to run sales, marketing, customer success, and demand-gen as the de facto executive, including new cloud partnerships that generated co-sell revenue.
The result: The company grew from 8 to 120 people with 500% ARR growth in a single year.

Personal Automation

From Slack Message to Polished Draft, Automatically

Workflow Automation
Content

The situation: Good content ideas kept surfacing in the middle of other work, with no system to catch them before they disappeared.
The problem: An idea that isn't captured immediately doesn't get written — and manually organizing scattered ideas takes almost as long as writing the post.
What I built: Gave an agent its own Slack account. It reads a dedicated ideas channel, organizes everything into a running Notion canvas, and drafts a ready-to-tweak post in a trained voice.
The result: A one-line idea dropped into Slack comes back as an organized, near-finished draft — no separate writing session required.

Content Skills

Writing That Sounds Like You From the First Draft

Skill Creation
Content

The situation: Every piece of content required re-explaining tone and style from scratch before anything useful got written.
The problem: Re-teaching an AI tool your own voice every single time is slower than just writing it yourself — which defeats the point of using AI at all.
What I built: A skill trained on a sample of real posts, emails, and messages, so a draft starts sounding like the author instead of a generic assistant.
The result: Drafts now start at a "7" instead of zero — this exact skill is what runs the copy on this homepage.

Decision Support

A Five-Person Advisory Board for Solo Founders

Skill Creation
Leadership

The situation: A solo founder making a high-stakes call has no exec team in the room to pressure-test the decision before it ships.
The problem: Big decisions made alone, without pushback from different angles, are exactly the decisions most likely to have a blind spot nobody catches until it's too late.
What I built: A skill that spins up five expert personas in parallel to weigh in on any decision or piece of content, then a "chairman" synthesizes it into one clear recommendation.
The result: A founder gets a boardroom's worth of perspective on a decision, without needing to hire a boardroom.

Content Skills

Catching AI Tells Before Your Audience Does

Skill Creation
Content

The situation: People using AI to help draft content had no way to know how "AI" their finished writing actually sounded before publishing it.
The problem: Content that reads as obviously AI-generated undermines trust with an audience, even when the substance is solid.
What I built: A diagnostic skill that scans a piece of writing, flags the specific "AI tells," and returns a letter grade — no automatic rewriting, just a clear read.
The result: Writers can check their own work before it goes out, instead of finding out from a comment section.

Content Skills

Turning Corporate Copy Into Something a Person Would Say

Skill Creation
Content

The situation: Content coming back from AI tools often reads technically correct but stiff — too corporate, too generic, not like an actual person wrote it.
The problem: Technically accurate writing that sounds like nobody in particular doesn't build trust or connection with a reader.
What I built: A skill purpose-built to take overly technical or corporate-sounding content and rewrite it to sound like an actual human said it.
The result: Content that reads like it came from a person, not a policy document.

Meta / Process

Why a Personal Skill Library Compounds Over Time

Skill Creation

The situation: Every new task meant re-explaining context, tone, and process to an AI tool from a standing start.
The problem: Re-explaining yourself every single time is a hidden tax on every AI-assisted task — it adds up fast and never gets easier.
What I built: A personal library of reusable skills — for voice, decision-making, content auditing, and more — each one teaching the tool something once instead of every time.
The result: A toolkit that compounds: each new skill makes the next task faster, not just this one.

Field Services

From Field Notes to Branded Estimates in Minutes

Workflow Automation
Operations

The situation: A fence installation company's reps were writing up every job by hand, translating field notes into a customer-facing estimate after the fact.
The problem: Turning raw field notes into a branded, accurate estimate took hours per job and varied by which rep wrote it — slow quotes lose jobs.
What I built: An AI extraction tool that reads field notes and generates a branded estimate automatically, plus a full job-flow CRM prototype covering the pipeline from lead to install.
The result: Field notes now become a client-ready estimate in minutes instead of days — the estimate goes out while the interest is still hot.

Trade Services

An AI Assistant That Actually Knows the Business

Skill Creation
Operations

The situation: A welding and fabrication shop wanted an AI tool of their own but had no discovery process, brief, or instructions to hand off to it.
The problem: Without a documented process, any AI tool built for the shop would only be as good as whatever the shop happened to remember to explain that day.
What I built: A ready-to-use Claude Project: a discovery checklist, project instructions, and a website brief packaged so the shop's knowledge is captured once and reused every time.
The result: The shop now has a standing AI assistant that already knows their business, instead of starting from zero in every new conversation.

Watersports / Rentals

Turning Ad-Hoc Pricing Into a Repeatable System

Workflow Automation
Operations

The situation: A watersports rental company priced inventory manually, without a system to track what should change and when.
The problem: Pricing decisions lived in someone's head, not in a tool — no consistent way to test, adjust, or defend a price.
What I built: A pricing management prototype with an AI assistant, "Casti," to help reason through pricing changes and keep them consistent.
The result: Pricing decisions are on paper for the first time — a working prototype ready to move from testing to daily use.

Data Tools

Query Your Own Data Without Writing SQL

Workflow Automation
Data & Research

The situation: A team had useful data sitting in raw files, but getting an answer out of it meant asking someone who knew SQL — or waiting.
The problem: Simple questions about a team's own data required a technical middleman, which slows down every decision that needs an answer today.
What I built: A tool that lets anyone drop in a dataset and query it directly, in plain language, no SQL or spreadsheet wrangling required.
The result: Anyone on the team can get an answer from the data themselves, the moment they need it.

Client Deliverables

Same-Day Leave-Behinds From Raw Meeting Notes

Workflow Automation
Operations

The situation: After a discovery call, whoever ran the meeting had to sit down and manually turn scratch notes into something client-ready.
The problem: Good discovery notes are useless to a client on their own — they need a polished, professional leave-behind, and building one by hand eats the time you just saved by having a good conversation.
What I built: A tool that turns raw meeting or discovery notes directly into a polished, client-ready leave-behind document.
The result: The leave-behind goes out the same day as the meeting, while the conversation is still fresh for the client.

Music / Entertainment

A Website Rebuilt Around What Actually Drives Revenue

Growth
GTM

The situation: A touring band had a website that hadn't been built around any real understanding of how they actually make money or grow their fanbase.
The problem: A site built without knowing the brand, the goals, or the revenue model ends up decorative — it doesn't move anyone toward the actions that matter.
What I built: Ran a discovery conversation covering brand, goals, revenue streams, and community growth, then reorganized the site around what actually drives conversions.
The result: A site built around the band's real goals instead of assumptions about what a band site should look like.

Yours would be the next one.

Book a callTodo: [BOOKING LINK — E.G. CALENDLY URL] — paste the real URL and this button goes live.