Aaron Burton

I've spent the last decade in eCommerce and media buying, and for the past 8 months I've been building omnicheckout.app on top of an event tracking system I already had running. End result is a checkout platform that lets merchants take payments in environments where a processor ban would otherwise be a business-ending event, with world-class tracking built in underneath rather than bolted on. Stripe and Whop are the two processing partners live on it today, and merchants can either run their whole setup through us or plug in their own integration and let us just manage that connection.

I built this mostly by directing AI on architecture while learning TypeScript, terminal, and databases alongside it, which is enough for me to chase down real issues fast when they show up. Current focus is hardening the payment webhook logging so observability is airtight.

What I need now is someone who can actually sell and promote this, because that's not me. Looking for a co-founder or COO for that role. I'm also open to a UI/UX designer, since I can hold my own on design but not against someone who's built a career on it. Both are equity-only right now since we're not funded, the company is an LLC moving to a C corp shortly, and there's provisional patent coverage on identity resolution and edge technology, some of it close to expiring and already positioned to convert to utility patents cheaply.
If this sounds like something you'd want in on early, reach out and let's talk. Happy to walk through the platform, the tech, or the patent situation in more depth.

A couple weeks ago, Boris Cherny (the creator of Claude Code) shared a bunch of really useful tips on getting the most out of Claude Code. #1 at the top of the list: do more in parallel. He himself runs 10-15 Claude codes in parallel.

His advice and practice makes sense: coding agents give us the ability scale infinitely. At this point, the only real limiter is our own ability to manage all of these agents.

For as long as software has existed, the user has been a person. Someone sitting at a desk, poking at a phone, or calling an API. That assumption was so obvious it was never really a design principle, it was just common sense. Every decision about hierarchy, color, button placement, and error messaging was downstream of a single fact: a human being is going to see this.

With agents, that assumption is starting to fail.