$9M ARR in 8 Weeks: Inside Muse's Hypergrowth Playbook

Chapter 1 · Narration: WOW Mentor

$9M ARR in 8 Weeks: Inside Muse's Hypergrowth Playbook

WOW Mentor breaks down the hypergrowth strategy of the founder of Muse, who contracted $9M in annual recurring revenue across 2,000 locations just eight weeks after rebranding. He hires only on proof built by hand, rebuilds a deliberately vague landing page into a funnel an ordinary decision-maker can understand, routes around App Store bureaucracy, and scales his team toward eight engineers. Underneath it all sits a single premise — that SaaS is dead — and a bet that the product is not a screen but an ontology layer holding each business's data.

Today, WOW Mentor breaks down the story of a startup that got to say the number $9 million just eight weeks after rebranding. At the center is the young founder of a company called Muse. On camera, worn out, he admits the days are really getting to him now, and that the team has already been in the office since 7 a.m. And yet he cannot hide his excitement: it is absolutely crazy, he says, that just eight weeks ago they started this new company and are already contracted to $9 million a year. What WOW Mentor flags first is the tension that runs through the entire video. On one side sits the explosive growth number; on the other, his honest exhaustion — the admission that it is really stressful, but in a good way. Today we take the whole thing apart in the third person: the true nature of that number, how he decides whom to hire, how he sells the product, and the single biggest bet he has placed. The two numbers he keeps returning to are these: $9 million in annual recurring revenue, and 2,000 locations. But there is something WOW Mentor has to underline. He never calls it simply revenue; every time, precisely, he says contracted ARR. In other words, this is not cash in the bank, but the annualized value of one-year agreements signed with 2,000 locations. They are contracted to 2,000 locations for the year at $9 million right now, just eight weeks in, and if everything goes to plan they could get up to 5,000 over the next month. The reason WOW Mentor stresses this is that the faster a founder claims to be growing, the more precisely they must name what kind of number their metric actually is. Contracted ARR and recognized revenue are not the same. He did not blur that distinction, which is exactly why the boast reads less like hype and more like a report. That is today's first lesson: the bigger the number you cite, the more you owe the listener a clear name for what that number is. The pressure of that growth flows straight into hiring. He says they have calls a couple of times a week about new POCs, enterprise contracts, and new locations that all want their solution. To support that, he figures they need at least eight developers, so he's started hiring for a couple of roles in the Toronto office. And he threw up a post on his own LinkedIn announcing the $9 million ARR contracted. The result was explosive. By his account, in just eighteen hours his inbox had been flooded with well over a hundred applications — and that from a single job posting. What WOW Mentor observes is what this means for an applicant. The moment a hundred applications land, a job posting stops being a place to fill a seat and becomes a litmus test for effort. So he puts it coldly: unless you put in at least a little extra effort — in the message you send, or by tailoring your application even a bit — you are never going to stand out. In the flood, what he scans for is not a glittering résumé but one signal: did this person try even slightly harder? So what does he look at before he will trust someone? His answer is simple and consistent: something they built with their own hands, or having been part of a successful project with a real user base. Being a software engineer, he says, means being able to build a solution that can scale — and if you cannot show that you can do that with how AI works these days, he is simply never going to hire you. He offers two examples. The first is an applicant named Nikita. A couple of years ago, when he was practically a kid, Nikita was already part of a founding team; go back further and he was part of another startup that got acqui-hired, and then he successfully exited again. Doing all that so young, the founder says, showed him before they had even spoken that Nikita would be technically capable enough. The second is a candidate he interviewed that very day, likely to be hired for mobile app engineering. His application was strikingly bare — nothing but his LinkedIn and a short couple of paragraphs, clearly not AI-generated. It said, in effect: I solo-built this app, live on the App Store, 7,000 users and $1,000 MRR in a year and a half — and I was in the news for it. The founder says he just clicked through the app and immediately saw the person was obviously good enough for the role.

The insight WOW Mentor draws from these two cases is this. What he looked at was not a degree, not a famous company name, not a long personal statement. It was purely the thing they had built and shipped into the world on their own. He says letting your work speak for itself is the best way to get a job, and then adds a sharper line: you can't really complain about the job market when you're not willing to put in that kind of effort. WOW Mentor reads that not as cynicism but as a standard. In an era where AI writes the code for you, the place a hirer anchors their trust has shifted — from what you know to what you have actually made. Nikita's repeated exits and the mobile candidate's 7,000 users are, in the end, the same kind of evidence: a shipped product rather than a claim, a mark left by hand rather than a line on a résumé. That is today's second big lesson, and it inverts cleanly for the applicant, too: all you truly need is one piece of work that speaks for you. Now the story turns to the face of the product — the landing page. He says they're upgrading it right now: concepts that show ontology, a few sketches, even a little pixel animation. But a viewer is entitled to be puzzled. In the previous vlog he pulled an all-nighter on that very page, sitting there at 1 a.m. announcing they'd finally finished the hero and marveling at how beautiful it looked. So why tear it up already? His answer becomes today's third lesson. He confesses the earlier landing page was intentionally vague and ambiguous. In fact, he says, even viewers who checked it out would have thought, what the hell do they even do — what is Muse? And he doesn't blame them, because it was done that way on purpose. What WOW Mentor stresses here is that in an early-stage startup, ambiguity can genuinely be a deliberate strategy. Before the market and the product have set, an overly specific promise can become a shackle around your own ankle: nail down what you do, and the moment you pivot, that sentence becomes a lie. But every strategy has a shelf life. He says the landing page is now becoming a funnel — people are clicking on it. Just that morning he had a call that went really well. And yet the person on that call, who was quite technical, told him: I really liked what was on that page, but even I struggled to understand it. That one sentence moved him. He and the team reasoned it out: it is one thing if a senior data engineer can maybe follow you, but if a random QSR CEO — the head of a fast-food chain — can't understand your value, you are losing a lot of clients. So he decides to completely redo the page, for the last time, he promises; the ROI is there, so they have to do it right, once and for all. The question WOW Mentor puts to you is this: is your value proposition validated against the most technical person you can find, or the most ordinary decision-maker? The Muse lesson is that the instant the latter fails to understand, revenue starts leaking out. The scene WOW Mentor finds most vivid on the product side is the commotion around shipping the app. Their app finally lands on the Google Play Store, and the team jokes that everyone should go download it and rate it. Then, literally five minutes later, an email arrives from the Apple App Store: we noticed an issue with your submission that requires your attention. He complains that Apple is anal with everything, and that it takes something like seven days to review every single small change. The issue itself was trivial: he simply hadn't removed or outlined the account-registration features for businesses. The team's response is thoroughly pragmatic — strip out the whole onboarding flow to get past review, and once they're allowed on, add that feature back. What WOW Mentor stresses is his refusal to fight the platform's bureaucracy head-on. Rather than railing about how unfair it is, he designs the fastest route that will pass. If you can't change the rule, find the quickest path inside it — existence over completeness, speed over principle. For a startup at this pace, that is a small-looking but decisive piece of operational instinct.

… The rest of this chapter continues in the full edition, available with a subscription.

Listen to this chapter