If it can be automated, I’ll find a way.

Twenty-four years in sales, thirteen of them inside sales. I've been the rep on the phone with a dialer and a quota, and the person the reporting was supposedly built for. Almost all of it was lead generation and lead sales — building the pipeline and selling the pipeline. Plus a stretch of consultative selling in solar — its own education in long cycles and buyers who need to be walked through a decision.

Then I ran it — sales manager, then operations manager, carrying a P&L and standing up a dozen direct-to-consumer pilots. I've had to justify spend, kill what wasn't working, and answer for the number at the end of the month.

Then I measured it. I taught myself SQL because I got tired of waiting on someone else to answer questions about my own pipeline. I worked as a data analyst and a product analyst, and built reporting in Periscope and Sisense.

Now I build it. I've sold the product, run the operation behind it, analysed the numbers and specced the roadmap — there isn't a part of a revenue system I haven't sat on the wrong side of. That's why the work below looks the way it does. A lead distribution platform, a CRM, an affiliate program, call analysis — the tooling I spent a career using and wishing were better.

Industry depth

• Residential solar
• Residential real estate
• Title & closing
• Construction & remodeling
• D2C
• SaaS

I don't hand-write most of what I ship. I direct Claude Code, review what comes back, and own every architectural decision in the system. I'd rather say that plainly than have you work it out later.

What you're paying for is the judgment around it: knowing what to build, catching the output that's wrong before it reaches production, and insisting on the parts nobody asks for until they're missing — reconciled billing, row-level security, retention rules, an audit trail.

The part I'm actually good at is seeing where a system will break before it does. Where the data model won't hold. Where the manual step quietly becomes someone's full-time job. Where the thing that works at a hundred records falls over at a hundred thousand. The same instinct turns up the requirement nobody wrote down — the report they'll need at quarter end, the state the workflow can get stuck in. I raise those while we're scoping and build the seams in early. Adapter layers so a vendor can be swapped, kill switches on anything that touches money, validation that fails at build time — not in front of a customer. It costs a little more in week one and saves the rewrite in month nine.

The reporting goes in from the start. If you can't see what a system is doing, you don't really have it yet.

A career of cold calling teaches you there is always another path to the same outcome. I build the same way — scrapers, queues, integrations, whatever the problem needs. If it can be automated, I'll find a way.