F&T Technical pre-sales · Engineering roots

Presales leadership, still shipping code.

I lead the solutions architects who win the hardest enterprise deals: the ones where the customer’s whole outcome hinges on getting the data architecture right: AI and LLM workloads, vector search, RAG, and agentic systems, going into some of the largest companies in the country. I still build those systems myself, which is what keeps the advice sharp enough to be worth funding.

01 — Proof

The engineer never left the room.

From building software to leading the people who sell it

I’ve been the technical person in enterprise sales rooms since 2010: first as a startup’s founding pre-sales engineer, then a solutions architect at a major enterprise-software company, and for the last nine years at a leading data platform, where I went from senior architect to running a team of them on the largest strategic accounts. Financial services, healthcare, retail; engagements north of $60M; the deals where the customer’s success depends on getting the data architecture right. (The names are all on LinkedIn.)

I never put the keyboard down. I still run agentic AI workflows and infrastructure myself, not for show; it’s the only way to keep giving advice that survives contact with a real architect. When I tell a CTO an approach holds at their scale, or doesn’t, it’s because I’ve built it, not because a slide said so. The habit of owning the outcome goes back further, to leading logistics in the U.S. Army, where accountability wasn’t optional.

Flagship

An analytics tool that shows leaders where their architects’ time actually goes

This one is mine, end to end. I designed and built a leadership analytics tool that takes the raw signal of how solutions architects spend their days (the customer calls, the builds, the internal drag that never shows up on a forecast) and turns it into something a manager can coach against.

It is not a surveillance dashboard. The point is to see where a talented architect is being pulled off the work that makes them valuable, and to do something about it before they stall or burn out. It turns a gut-feeling conversation into one grounded in what the week actually looked like.

02 — Trail

Don’t take my word for it. Follow it.

Two destinations, both live. Between them they hold the full record: what I’ve claimed here, and the work behind it.

03 — Writing

Longform, starting soon.

This is where the essays will live: what technical pre-sales actually looks like when it works, the unglamorous reality of getting AI adopted inside a real org, and what engineering leaders keep getting wrong when they try to measure their teams. Argued pieces with a position, not status updates.

First pieces In draft

04 — Projects

Build write-ups, starting soon.

Tools and experiments, written up in full: the leadership analytics tool first, then the smaller things I build to learn a technology by actually using it. Each one gets the what, the why, and the parts that didn’t work, not a screenshot and a link.

First write-up In progress

05 — Contact

Reach me directly.

No form, no calendar link. If you’re sizing me up for a role or an engagement, the trail above will tell you more than an intro call. If you’ve read it and want to talk, email is the fastest way in.