Aha!

A company that sells clarity, sold no equity

Right now, somewhere, a product manager is dragging a feature card across a roadmap. The tool is Aha!.

Open a thousand product teams' browser tabs and you will keep landing on the same place. A roadmap with deadlines that move, ideas waiting to be scored, a whiteboard half-finished from yesterday's call. Aha! sits at the center of that mess on purpose. It is the software where strategy stops being a slide deck and becomes a plan with dates attached.

More than a million people now build products inside it. That is a strange sentence to write about a company with no headquarters, no venture backers on the cap table, and - for its first several years - no salespeople. Aha! grew up doing almost everything the standard Silicon Valley playbook tells you not to do. It worked anyway.

Four numbers, one quiet argument: you can grow large without ever holding a board meeting you didn't want.

Everyone has a strategy. Almost no one connects it to the work.

Here is the quiet failure that happens inside most companies. Leadership writes a strategy. Engineers write code. Between those two acts is a canyon, and into it falls every good intention. Features get built because someone shouted loudest. Roadmaps become wishlists. The word "priority" loses meaning the moment everything is one.

Brian de Haaff and Chris Waters had spent their careers on both edges of that canyon - at emerging startups and at large software companies that had been acquired by Aruba Networks and Citrix. They had felt the gap personally. People struggled to set a clear strategy and then connect it to the messy daily work of building things customers actually wanted.

The market was not short on project trackers. It was short on a place where the why and the what lived together - where a quarterly goal and a single user story could be traced to one another. That missing connective tissue is the tension Aha! was built to resolve, and it still runs through every product the company ships.

The canyon between "our strategy" and "today's standup" - Aha! sells the bridge, and charges per seat to cross it.

Two founders, one contrarian wager

In the spring of 2013, in Menlo Park, the two of them made a bet that sounded almost old-fashioned. Build something people will pay for. Charge money. Use the money to build more. Skip the part where you raise a fortune to lose for a decade.

Aha! was de Haaff's third company and the first he and Waters funded themselves. No office to sign a lease on. No investors to update. The plan was to be profitable early and stay that way - a plan so unremarkable it had become radical. De Haaff later argued the case publicly in Fortune and in his bestselling 2017 book, Lovability, where he laid out a people- and profit-first idea of what a software company could be.

That phrase - the Minimum Lovable Product - was a deliberate jab at the industry's favorite acronym, the Minimum Viable Product. Viable, de Haaff argued, sets the bar at "barely works." Lovable sets it at "worth caring about." It is a small rewording with a large attitude, and it became something close to a worldview at the company.

The bet held. Within four months of opening the beta gates, Aha! had signed 125 paying enterprise customers. Nobody on the team carried a sales quota.

Two people, no investors, a lease they never signed - and a customer list that started filling itself.

One place for the whole job of building

Aha! started as Roadmaps and kept refusing to stop. What began as a single tool is now a suite that maps onto the full arc of product work: have the idea, talk to customers, sketch it, plan it, document it, build it, ship it, prove it worked. Each piece can stand alone. Together they close the gap the founders set out to close.

Eight products that quietly insist your good idea and your shipped feature belong in the same sentence.

The receipts, for the skeptics

Mission statements are cheap. Here is the part that is harder to argue with. Aha! reports more than $100 million in recurring revenue and over a million product builders using its tools - reached without the venture fuel its competitors burned through. Third-party trackers estimate annual revenue closer to $45.8M, which tells you the exact figure is private; the direction is not in dispute.

The customer list reads like a directory of large institutions that do not adopt software on a whim: Dell, Siemens, Experian, Sage, LexisNexis, BAE Systems, Paycor, Blackbaud.

The accolades followed: #143 on the 2018 Inc. 5000 (and #13 among software companies), a spot on Deloitte's Technology Fast 500, and repeated "best workplace" honors from Inc. and the Best in Biz Awards. The company has also given away more than $1.5 million through its Aha! Cares program - profit, redirected.

A wall of enterprise logos assembled the slow way: by being useful, not by being everywhere at once.

See it move

Demos and interviews, for the people who would rather watch than read.

Build products people love. Run the company the same way.

The mission is not complicated and the company does not pretend otherwise: help people build products that customers love. What makes it more than a poster is that Aha! applied the idea to itself. Remote from day one - back when "no office" read as a warning, not a benefit. Profitable on purpose. Run by the framework de Haaff named The Responsive Method, which is mostly a long way of saying: be useful, quickly, to the people who depend on you.

There is a tidy logic to it. A company that tells its customers to obsess over what people love would look ridiculous building a workplace nobody did. So the internal culture and the external pitch are the same sentence, read in two directions.

A mission short enough to fit on a sticky note, stubborn enough to survive a decade of growth.

The roadmap, now drawing itself

The canyon Aha! set out to bridge is not going anywhere. If anything, AI widens it for a moment - teams can now generate ideas, drafts, and even working code faster than they can decide which ones deserve to exist. The bottleneck moves from making things to choosing things. That is, conveniently, the exact problem Aha! has spent thirteen years on.

Aha! Builder, shipped in January 2026, is the company's answer: let AI help plan, design, and develop custom software, but keep it anchored to a strategy and a roadmap so the speed actually points somewhere. The pitch is no longer just "organize your plan." It is "make sure all this new velocity is aimed at something worth building."

Return to that product manager from the top of this page, the one dragging a card across a roadmap. A decade ago that card was a guess in a spreadsheet, disconnected from any strategy, destined to be argued about in a meeting. Now it carries a goal it ladders up to, the customer interviews that justified it, the whiteboard it was born on, and the engineering ticket that will deliver it. Same gesture. Entirely different weight behind it.

That is the quiet thing Aha! changed. Not the existence of roadmaps - those always existed. The fact that the line on the roadmap finally means something. No office required.