Anagram

From the ground up

Anagram started with three people: me and my two co-founders. For the first two and a half years, I was the only engineer. I built the whole product.

But there wasn't a neat line around engineering. I drove product, designed the experience, talked to customers, hopped on sales calls, and helped with hiring. All of it was part of building Anagram.

I'm still here, still the primary builder and driver of product. We've grown to six-figure ARR and supported brands like Burton, 1st Phorm, and Armada. And plenty of fun ones: Yard Mastery, Vyper, and Stoke Shoes.

What we build

Will this work for me? Which one should I buy? Where can I try it? Those are real questions. A product page doesn't always have the answer, and a shopper shouldn't have to figure it all out alone.

A brand connects its catalog and product knowledge, sets up its agent, and puts it on its storefront. Shoppers can ask questions, get recommendations, and work out their next step.

Those conversations teach the brand something, too. What are people looking for? Where are they getting stuck? What do they keep asking that the site isn't answering?

I built both sides: what shoppers use and what brands need to configure, test, and understand it. That means keeping catalogs in sync, searching products, shaping agent behavior, and making it work on the storefront.

Then there's understanding the conversations and connecting them to purchases. We also help brands see how they show up in AI search. There's a lot behind a little chat window.

Wearing the hats

The hardest part? Balancing it all. You can do anything, but you can't do everything.

Some days, support needs all your attention. Other days, roadmapping. Other days, building. Other days, selling. I love writing code, but sometimes the thing that needs me isn't code.

I look back over the week and ask: was it a job well done across all the areas that needed me? That's a different question than how much I shipped. Building a company asks more of you than that.