About
They fail because nobody owns the whole thing. I've spent nearly 20 years on almost every side of that problem.
I started as a web designer. Then I moved into front-end development, then JavaScript engineering, then brand and marketing leadership. The work kept pulling me across those lines, because the problems I cared about didn't respect them.
At Fleetio, I grew from web designer to Director of Brand Marketing while the company went from Series A to Series D. I led the website function inside a broader marketing team, including rebuilding a 1,000+ page site on a modern Next.js stack. Build times dropped from more than 20 minutes to seconds, key pages got about 50% faster, and marketers could publish without touching GitHub. Inbound became a major source of pipeline during that time. That was a team result, and it taught me how much the website depends on content, demand gen, sales, and measurement working together.
I started Plerom because I saw how many B2B websites don't have a full-time owner building them into the engine they should be. Now I do that work for other teams, with current client work keeping my view calibrated against new tools and new ways of working.
Having led design, development, strategy, and messaging doesn't mean I should do all of them for every client. It means I can see how they affect each other, and step in where the gap actually is.
Sometimes that's rewriting the message. Sometimes it's rebuilding the tracking. Sometimes it's directing your designer and staying out of the way. Most website problems aren't purely strategic or purely technical. They live between the two, which is exactly where I'm most useful.
Agencies can do great work. They also tend to add layers exactly where continuity matters: the strategist who pitched you hands off to a team you've never met.
With Plerom, you work with me. The person who diagnoses the problem stays with it through launch and after. When a job needs more depth, I bring in specialists directly, without account managers or agency margin in between.
This isn't task-based production. The work has to connect to something that matters to the business: clarity, conversion, speed to launch, measurement, or steady site growth.
That's also why I take on a small number of clients at a time. The model only works with focus.
What I believe
A marketing website deserves the same seriousness as the product. It should have a clear architecture, reusable components, tracking you can trust, and a CMS your team can actually use.
Most B2B SaaS websites don't fail because nobody cared. They fail because nobody owned the whole system.
That's fixable.
Personal note
I'm based in Austin, Texas. I have four kids, a record collection that keeps growing, and a strong preference for plain language, clean systems, and work that earns trust over time.
