I built Eclipse because more content was never the answer
I didn’t set out to build a software company. I was consulting, had built myself a website, and needed the right people to find it. Paying for attention through Google Ads was never on my radar, so I stitched together ChatGPT, Zapier, and a few forms to see whether visitors could be earned organically instead.
The first version was a hack, but it worked. A few people asked to use it. Then they were willing to pay for it. That was when Eclipse stopped being a private workflow and became a business.
But a hack was never going to be safe enough to hold other people’s client work, and I knew it. So I threw the first version away and built Eclipse properly, from scratch. Everything underneath it today was engineered as one system. Secure, isolated for every client, and built to hold serious work at the volume real GTM teams run.
That machinery is deliberately invisible. The person using Eclipse sets the standard, makes the editorial call, and approves what goes out. The system does the heavy, complicated work beneath them, so producing world-class content at scale feels simple on the surface, even though almost nothing about it is.
From the beginning, I was wary of what AI was making easy. It could produce more content, more quickly, without giving much thought to why any of it should exist.
“CONTENT FOR EVERYONE IS CONTENT FOR NO ONE.”
Before anything is written, you should know who it is for, why it matters to them, what you want them to understand, and what should happen next. That principle still sits underneath everything in Eclipse today.
The company was built in much the same way. There is no large team hidden behind the website, and there doesn’t need to be.
It keeps me close to the product, the customers, and the problems we are solving. It also holds me to a simple standard: if Eclipse cannot help me build and run Eclipse, I have no business asking other founders to trust it.




