About

The short version

‎‎I’m Ethan a GTM engineer in London who writes the software sales teams can’t buy .

‎‎I’m Ethan a GTM engineer in London who writes the software sales teams can’t buy .

‎‎I’m Ethan a GTM engineer in London who writes the software sales teams can’t buy .

I spend my days inside a live B2B sales team, building the systems it runs on. Account intelligence that reads call transcripts, emails and CRM history into a brief before every meeting. An AI assistant that answers security questionnaires from the company’s own policy docs. Custom apps living inside HubSpot. None of it was available to buy.

Before that I built and sold Ornn, a self-hosted outbound platform for GTM agencies. They deployed the full codebase on their own infrastructure and ran their clients on it. Several went further and built their own products on top — a post scheduler, a content generation layer, a white-labelled reporting dashboard. That part I’m proudest of: the architecture was good enough that other people built businesses on it.

Most GTM work is configuration: wiring together tools the company already pays for until they roughly fit. I write software instead. Real applications, deployed into the stack and owned outright by the people who paid for them.

a man (it's me)
that’s me

Most GTM problems get solved by wiring together tools someone already pays for. I reach for an editor instead. It usually takes about the same time and you end up owning the result.

Most GTM problems get solved by wiring together tools someone already pays for. I reach for an editor instead. It usually takes about the same time and you end up owning the result.

Ethan

How I work

Scope comes from watching

Before anything gets built I want to know what the team actually does on a Tuesday: where someone copies data between tabs, which spreadsheet gets rebuilt every week, what people gave up on asking the CRM for. The scope comes out of that, not out of a feature list.

scope first, build later.
no clean stacks here!

Building in messy stacks

Nobody has a clean stack. There are three sources of truth, a legacy field nobody dares delete, and an integration that half works. I’d rather build around what’s actually there than wait for a migration that never happens.

Shipped beats architected

A working system in two weeks teaches you more than a design document in four. I build the smallest version that does the real job, put it in front of the people who need it, and let what they do with it decide what comes next.

shipped beats perfect.
details build trust.

The unglamorous wins

The highest-value builds are rarely the impressive ones. A field that fills itself. A report that stops needing a human on Monday morning. An answer a rep would otherwise have waited two days for. Boring to demo, enormous in aggregate.

The story

A look at how I work

The work

Timeline

Offstack

Custom GTM engineering. Building the software sales teams can’t buy: native CRM apps, standalone internal tools, data layers and AI systems on their own records.

2026 - Current

GTM Engineer, B2B SaaS

In-house, inside a live sales team. Account intelligence from call transcripts and CRM history, a RAG assistant for security questionnaires, and custom HubSpot apps for the sales org.

2026 - Current

Ornn

Founded and sold a self-hosted outbound platform to GTM agencies. Full codebase, deployed on their own infrastructure. Several customers built their own products on top of it.

2025 - 2026

Events & Operations

Three years running events, plus logistics operations for freight forwarders. Where I learned how much of commercial work is still held together by spreadsheets and goodwill.

2021 - 2025

Let's Talk

Your first project is free. We build it in two weeks and you keep it. All we ask in return is a short video testimonial. After that, fixed prices agreed up front.

Comment

Ethan

Bring the workflow your tools can’t handle and the spreadsheet someone rebuilds every week. That’s the job.

1