I connect strategy, operations, data, automation and AI to build revenue systems that work better—and keep improving.
Real operating problems.
Systems I designed and built to solve them.
A solo-built discovery platform that turns fragmented Indian specialty-coffee catalogues into structured, searchable data.
92 roasters represented in one discovery layerA time-boxed pipeline that turns an event attendee graph into prioritized, owned and personalized outreach.
12 qualified meetings from a single eventA current operating practice that makes pipeline rules, territory logic and forecast inputs legible to both people and agents.
Current operating work; confidential metrics and implementation detail are not publishedSales. Strategy. Marketing. Operations. Customer success. I’ve worked across the revenue system. Now I build the connective tissue.
How the experience adds upMake the priority clear. Decide where to focus, which customer problem matters, and what a useful outcome looks like.
A shared directionEvery decision feeds the next iteration.
The builds, the wrong turns,
and the things worth passing on.
Two redesigns changed the surface. Starting over finally changed the positioning, architecture and story underneath it.
A legacy-ID mismatch looked like a routine cleanup until the delete path exposed a second bug and 16 irreplaceable records.
GTBrain started as the lazy option: folders of text an agent could maintain. It became a durable argument for why files outlast models.
2 original resources, alongside the tools I use to build.
I’m also raising twins, teaching, brewing too much coffee and building things that begin with “Surely this should be easier.”
They rarely remain small.
Meet the human behind the systemsIf it involves GTM, AI, or an interesting operating problem, let’s talk.