After Henry Poydar's first exit, he built a portfolio of micro-SaaS products until one got traction. Then he doubled down, pivoted, and grew Steady into a 7-figure ARR business.
Here's Henry on how he did it. 👇
I've been building software and leading teams for over 25 years, working across everything from small bootstrapped startups to large enterprise teams at places like Sapient.
After I sold my last company, where I was cofounder and CTO, and did my time at the acquiring company, I wanted to try something different. I built a slew of micro SaaS apps across things I was interested in — some B2C, some B2B. It was a great period of experimentation and learning what sticks.
One of those B2B apps was near and dear to my heart: Status Hero. It solved a problem I'd experienced over and over as a manager — I wanted a lightweight way to ask people for their intentions. Not micromanage them, but give them agency and ownership over their work while giving me, as a leader, a chance to course-correct early. I built it into a tool and it took off during the pandemic, largely because it met teams where they already worked — Slack, and then Microsoft Teams.
As we grew to a few hundred paying teams, we evolved Status Hero into Steady — a lightweight teamwork OS focused on keeping teams coordinated. When AI started maturing, we discovered that pattern matching around coordination best practices worked remarkably well. Things like surfacing blockers, identifying misalignment, nudging teams toward proven rhythms — AI was a natural fit. So we went all-in and rebuilt Steady as an AI-native product.
Then agents came along, and the thesis got even stronger. If humans already struggle to stay coordinated, autonomous agents make that exponentially harder. So we evolved again. Today, Steady uses purpose-built AI agents to deliver coordination intelligence, and where we're headed, agents and humans participate in the same coordination loops side by side.
The founding team includes people from Basecamp, GitLab, and Sapient — organizations doing distributed work before it was trendy. We also co-created an open framework called Continuous Coordination that underpins how Steady works.
Today, we're a small, lean team with hundreds of customers and no dedicated sales staff. Everything has been organic growth. And we're at seven-figure ARR.

I built Status Hero as a classic bootstrapped product. I did everything — Rails backend, frontend, integrations, support, billing, marketing. The advantage of solving your own problem is that you're also your first user, so the feedback loop is instant. I'd build something, use it, talk to a customer, feel the friction, and fix it.
I was obsessive about automation from day one. If I was going to be a team of one, I couldn't afford to spend time on anything a script could handle. I automated CI/CD, deployments, onboarding flows, and transactional emails early.
We still apply that discipline to how we operate at Steady. Four people running hundreds of accounts only works if the machine runs itself.
Our stack is Rails, PostgreSQL, Redis, and AWS. We use Electron for the desktop app and Google Vertex for our AI infrastructure.
The Ruby and Rails ecosystem is incredible for a solo founder — you get so much for free. I could move fast, ship features daily, and keep the codebase simple enough that one person could hold it all in their head.
I liked it. No microservices, no over-engineered infrastructure. Just a monolith that works. Cloudflare and Stripe were awesome too.
We recently moved from traditional per-seat SaaS pricing to credit-based pricing, and this has been a meaningful shift. Per-seat pricing ties your revenue to headcount, and it also reinforces this model where value only comes from humans sitting in front of a screen. That's not where things are going.
With credits, AI agents also consume resources — running coordination loops, synthesizing updates, and delivering intelligence. The value isn't locked behind a login screen anymore. Credits let us capture value from work that happens in the background, which is where most of Steady's value lives.
Growth has been slow and steady (pun intended). Status Hero was a bootstrapped product growing organically for years — mostly word of mouth and teams discovering us through Slack's app directory. The pandemic was an inflection point because, suddenly, every team needed async coordination tooling.
When we evolved into Steady, we kept that customer base and built on top of it. About a quarter of our current accounts are Status Hero conversions. The shift to credit-based pricing has been the biggest recent lever — mature accounts are spending meaningfully more than they did on per-seat plans because agents run coordination loops continuously, not just when someone opens the app.
The key factor is that we've never had to chase demand. Coordination is a universal pain point — one that I knew well. You must, must, have lived the problem you are solving.
We built something that works, kept showing up, and let compounding do its thing.
Our growth was earned, not bought. We grew by consistently showing up — writing, shipping visibly, and building in public.
A few things that have worked:
Meeting teams where they are. Steady integrates with Slack, Teams, and email. There's no migration, no new tool to log into. This removes the biggest friction point in B2B adoption.
Thought leadership around coordination. We co-created and openly published the Continuous Coordination framework. We write a weekly newsletter, The Steady Beat, and constantly discuss the problem space. When people search for answers to coordination problems, they find us.
Lateral expansion within accounts. One team adopts Steady, sees results, and other teams in the org want in. Some of our biggest accounts started as a single team.
Riding the agent wave. As AI agents become integral to how teams work, the coordination problem intensifies. We don't have to manufacture demand — the market creates it for us.
The common thread is our focus on being genuinely useful rather than loud. This compounds slowly but durably.
Paid acquisition doesn't work for us. We tried it. The economics never made sense for a product like ours — coordination tooling isn't an impulse buy, and the people who need it most don't find it through ads. Every dollar we spent on organic content and community outperformed paid by a wide margin.
And we don't have a sales team. Good salespeople are hard to find, especially at our stage. We learned you must first master founder-led sales — not just to close deals, but to deeply understand why people buy. You can't hand that off to someone else until you've internalized it yourself. And even then, keep doing it.
You have to listen hard. Always. Customers, teammates, stakeholders — everyone is telling you something if you're paying attention.
But remember that what customers say and what they want are different. This took me years to absorb.
People will tell you they want a feature, but they actually want an outcome. You have to dig into incentives — what's driving the request? What does their boss care about? What are they measured on? The answers to those questions are where the real product insights live.
From here, my goal is to continue building things. I'm really excited about what we're cooking up at Steady as agents make their way into every company.
You can follow along with our vision here: https://runsteady.com/next. Or connect with me on X and LinkedIn.
Leave a Comment
Really enjoyed this — especially how you kept things simple with a monolith and leaned hard into automation early. The shift from per-seat to credit-based pricing also feels very aligned with where AI products are going.
The biggest takeaway for me is your point about living the problem — you can feel that throughout the journey. Curious to see how coordination evolves as agents become more autonomous.
micro to 7-figure is usually a distribution unlock, not a product one. curious what flipped for you?
Most people see the result, not the iteration behind it.
Scaling usually looks obvious only in hindsight.
My big takeaway from this is the part where you pivoted from micro-SaaS to such a larger idea by following the pain instead of the idea you set out with. ~
You didn't scale the initial product out, you kept on morphing until you were addressing a bigger more universal problem.
Great breakdown, Henry. I love the 'monolith over microservices' approach. It’s a refreshing reminder that at 7-figure ARR, you don’t need a complex infrastructure—you just need a machine that runs itself. The shift from Status Hero to an AI-native 'Steady' feels like a masterclass in evolving with the market without losing the core utility. The credit-based pricing for AI agents is a smart move to future-proof the revenue model.
My big takeaway from this is the part where you pivoted from micro-SaaS to such a larger idea by following the pain instead of the idea you set out with. ~
WOW THAT IS POWERFUL I LOVE IT SO INSPIRING... THANKS
The credit-based pricing shift is the part of this I keep thinking about. Per-seat is so deeply ingrained in B2B SaaS that it's easy to treat it like a law of nature rather than a convention. But as agents start doing real work in the background - running coordination loops, surfacing blockers - without anyone logging in, the per-seat model starts looking like a mismatch between how value is created and how you capture it.
The part about customer requests resonates too. The "what happens if you don't solve this?" framing is a good one. Pay attention to what people do rather than what they say in support tickets - the features customers complain loudest about are rarely the ones that drive churn. It's usually silent friction, the thing they just worked around and never mentioned.
Also interesting that paid acquisition didn't work. Coordination tooling seems like a category that only makes sense once you've named the pain - you don't search for "async coordination software" unless you already know something is broken. That's a strong argument for the thought leadership approach: meet people when they're trying to understand the problem, not when they're already shopping for a solution.
Curious about the lateral expansion pattern - is that mostly word of mouth inside companies, or do you have any product-level triggers that encourage teams to invite others? That kind of expansion loop seems like it could compound significantly if there's a clear mechanism behind it.
the automation from day one thing is real. we're two people building the first agentic cooking app and the only way we keep up with content across platforms is automating the repetitive stuff and keeping creative work manual. you literally can't run lean without that
Henry's point about credit-based pricing resonates deeply with me. We're building an AI SaaS product and the per-seat model constantly feels like a ceiling — especially as more value starts getting generated by background AI processes rather than active user sessions.
The insight about customers saying what they want vs. what they actually need is also something I had to learn the hard way. Early on, I'd build exactly what a customer requested, ship it, and they'd still churn — because the feature solved the symptom, not the underlying problem. Now I always ask: "What happens if you don't solve this?" That question uncovers the real pain faster than anything.
The part about founder-led sales being non-negotiable before hiring anyone really stands out too. You can't delegate your ICP discovery. Great write-up — Henry's story is a great reminder that slow, compounding organic growth beats a growth-hacked launch any day.