Now: CEO @proxon_ai Previously: CSO @newrelic CEO @teamcodestream CEO @glip CEO Multiply Founder https://xitter.cf/t.co/3ujsh8FsDL
San Francisco
Joined March 2007
- Tweets1.7K
- Following2.2K
- Followers2K
- Likes2.7K
Pinned Tweet
we're live on Product Hunt today. an upvote goes a long way: producthunt.com/products/pro…
full story here: proxon.ai
Peter Pezaris 💻 retweeted
In 2026, code is written faster than we can physically read it.
25 PRs before lunch. Your whole app rewritten in Rust in 18 hours.
But reliability hasn't kept up. Monitors are an afterthought, alerts pile up ignored, and when prod breaks, your customers notice first.
That's why we're launching Struct: the AI Production Engineer.
It reads every PR you ship, creates monitors for each one, and fixes things when they break. (Humans optional.)
Keep moving at AI speed and never think about monitoring again.
Thank you @katiebindley and @wsj for a piece that captured this moment better than I could. Yes, I did promise my wife I'd retire this year. The agents had other plans.
wsj.com/tech/ai/ai-agents-st…
Peter Pezaris 💻 retweeted
This is the one I've been quiet about for months.
We're live on Product Hunt today. I built this because I was tired of losing leads in the gaps between demo, onboarding, and support.
Take a look and tell me what you think 🦆
Here it is 👇
producthunt.com/products/pee…
everyone you work with just got promoted.
every employee using AI became a manager: assigning tasks to agents, reviewing output, deciding what ships. the software to manage that workforce didn't exist, so we built it.
today we're launching @proxon_ai, the management layer for the AI workforce.
Peter Pezaris 💻 retweeted
asked my coding agent what TypeScript would look like if it were designed for code mostly written by machines. two hours later, BotScript exists.
playground + a one-shot prompt that scaffolds a full-stack app: github.com/marcelofarias/bot…
Early stage truth:
Your startup feels like a needy parasite.
You give time. You get nothing back. No signal it’s working.
Most quit here.
the cost of starting a company has collapsed. AI writes your deck, your prototype, your marketing in a weekend.
For 3 years I wrote myself a $200,000 check every month to keep Glip alive. No outside investors. Just me, burning $7.2M of my own money.
First few months felt fine. Year two the pen got heavy. Year three I was asking what I was doing.
We sold the company. Got it all back and more.
Now building @tryvortex.
Office floor. $10K/year. 3 years.
Sold the company. Now I spend my days fixing the dumbest leak in SaaS: free users who never become teams. Vortex turns that into revenue. No engineering required.
$17 in my bank account. That was the low point.
CodeStream eventually exited to New Relic for $46M.
What changed things: figuring out how free trials turned into paying teams faster and more often.
That's the hardest problem in PLG. It's also what Vortex solves.
Team activation and invitation flows. 29% uplift in new user conversion.
Early in my career, I started having some success with my first business, and I had a few exits for about $350 million. free-trail-to-paid-team conversion was paramount and became our secret sauce.
Stay away from @BankofAmerica. Their online account management not only allows you to change the password for other people, it makes it probable that you do that by mistake. This is the worst security I have ever experienced in an online product, and it is "working as designed".
we switched to @mercury and couldn't be happier so far. it's the difference between a modern system and walking with dinosaurs.
Fell asleep at my desk with toilet paper on my face because we couldn't figure out why trial users weren't converting.
Turned out we were chasing all of them. No signal AT ALL.
Fixed that. Sold for $46M.
If your free trials aren't converting, I've been there.
@BankofAmerica the following is "working as designed" according to your reps:
1. I create an online business account with sub-owner
2. Sub-owner signs in and resets his password
3. Is asked to confirm identity by providing EIN or SSN
4. He enters EIN
5. Changes his password
Result?
It changed MY password to the one he chose.
So any sub-owner who knows the EIN can overwrite the primary owner’s login credentials.
That’s intentional?
There are, quite obviously, two problems with this design:
1) it allows one online user account to change the password of another online user account with no confirmation
2) the design is confusing enough that he did this *by accident*
It shouldn't be possible at all, but certainly not by accident.
Peggy I already spoke to multiple reps. They assure me it is working as designed.