u/devneeddev

I’ve been building an AI language-learning platform with a slightly different approach: instead of giving everyone the same lessons, it creates a personalized curriculum based on what you want to learn and your current level.

The early results have been promising, but I’m mainly looking for people who are willing to actually use it and give me honest feedback. I’d much rather hear what doesn’t work than get polite feedback.

If you’re learning any language and would like to try it, I’m happy to give you free access for a month. It does cost me to run, so unfortunately I can’t offer unlimited free access.

I’m intentionally not mentioning the product name or posting a link here because I don’t want this to turn into a promotional post. If you’re genuinely interested, just comment or message me and I’ll send you the link privately.

Thanks!

I want to share this as constructive feedback, not as a "Claude vs. Codex" fight.

I have been a big fan of Claude Code and I really like the way it thinks, plans, and handles complex coding tasks. In many situations, I still prefer the quality of the output and the overall developer experience.

But recently, the speed has become a real issue for me.

I am on the $200 plan, and even when I use Dynamic Workflow, Claude Code has become slow enough that I sometimes cannot even fully use my limits anymore. The bottleneck is not the limit itself - it is the time it takes to get through work.

At the same time, I am also using Codex on the $200 plan. There, I can keep working continuously in Fast mode, and surprisingly, I still do not hit the limit as easily. The difference between Codex Fast and Claude Code's normal workflow feels much bigger than I expected.

Again, this is not meant as hate. I genuinely like Claude Code and I want it to stay competitive. But from a daily developer workflow perspective, speed matters a lot. When the tool is too slow, higher limits do not feel as valuable, because I cannot move through enough tasks to actually use them.

I would love to see Anthropic focus more on speed and responsiveness for Claude Code, especially for higher-tier users. The quality is great, but the workflow needs to feel faster and more fluid.

Curious if other Claude Code users are feeling the same thing, or if this is specific to my workflow.

It is eleven at night. I was going to fix one thing, the color of a button. I write the prompt, hit enter, and text starts streaming across the screen. That stream is a feeling all by itself. I have not seen the result yet, but my brain has already started collecting the reward, because I can see that something is happening. I can see movement. In the old editor the cursor just blinked and nothing happened. Now the screen is talking back to me. And before I have done anything, just by waiting, I slide into a kind of tension and anticipation. What is about to appear?

The output lands. The button is fixed, but along the way Claude noticed something else, "by the way, I cleaned up your state management too." I did not ask for that. But it is good. And right here the first hook fires: I asked for one thing and it gave me more than I asked for. The surprise feels like a small gift. And once you get a gift, you want one more. "Since you understood that so well, can you also do this?" I type. Eleven becomes eleven thirty.

What is happening here is a simple mechanic, but it is hard to describe. In old-school coding there were hours between an idea and a result. You write, you compile, you get an error, you fix it, you try again. The reward was far away and rare. Claude Code collapses that distance into seconds. Idea, prompt, result, all in one breath. And the more often the reward arrives, the faster the brain bonds to it. A slot machine works the same way: you pull the lever, a few seconds, a result. In Claude Code the lever is the prompt, a few seconds, a result. The only difference is that on a slot machine you mostly lose, and here you mostly produce something. But that word "mostly" is the danger itself.

Because the moment that hooks you is not the one where everything works perfectly. It is the one where it almost works. The button is fixed but something broke somewhere else. The page loads but the data does not come through. I got so close, it almost worked, one more prompt and it will resolve. And this is where I cannot get up. Because there is an open loop, an unfinished job, and the human brain cannot tolerate open loops. They call it the Zeigarnik effect, an unfinished task takes up space in your head and will not leave you alone. Walking away from working code is easy. Walking away from broken-but-almost-working code is torture. "I cannot go to bed until I solve this," I say. It is now one in the morning.

And there is this too: now it is my code. Maybe Claude wrote it, but I steered it, I prompted it, I shaped it. With every prompt I invested a little more of myself in this project. Half an hour ago it was a throwaway experiment, now it is "my project." And the more effort, attention, and time you put into something, the harder it becomes to give it up. I know it is not rational. Half of this prototype is junk, I will probably delete it when I look in the morning. But right now, at one thirty in the morning, this is my creation and I cannot abandon it. Ownership crushes logic.

I pick up my phone. On Twitter someone has posted "I shipped an entire SaaS solo this weekend with Claude Code." Underneath, dozens of people saying "same," "incredible," "I wrote 70k lines." And I go back to the screen. I am not actually competing with anyone, but I absorb the pace. If everyone is moving this fast, then stopping means falling behind. The social pressure is invisible but real. Even the people at the very top of the industry admit this feeling. The CEO of Y Combinator tweeted "So addicted to Claude Code, I stayed up 19 hours yesterday," and nearly a million people saw it. Strangely, that comforts me, it means I am not alone.

Then a warning: your token limit is running low. The window will reset in a few hours. And here a completely different feeling enters. Now I am not just saying "let me finish this," I am saying "let me not waste this window." Because the tokens I do not use will evaporate into thin air. This is not scarcity, it is something more insidious than scarcity, "use it or lose it." Like airline miles with an expiration date, if you do not use them they burn. And I paid for my subscription, those tokens are mine by right, if I do not spend them I feel like I am throwing my own money in the trash. The reason Garry Tan sleeps four hours is probably this, not for the output but to optimize the window. The product is now designing my sleep schedule.

The bitter part is that when I wake up in the morning I will see that half the code I produced overnight does not work. There were green checks, the tests passed, everything on screen looked successful. But Claude used a library that reached end of life, or built a structure that will be impossible to refactor in three months. Everything I thought I won that night was actually deferred debt. In gambling they call it a loss disguised as a win, the machine flashes its lights and congratulates you, but you have actually lost. In Stack Overflow's survey two thirds of developers say they lose time to "almost right" code, and half say debugging AI code takes longer than writing it themselves. So this is not just happening to me, this is the mechanic itself.

And here is what I understood: Claude Code did not do this on purpose. Nobody sat down and designed "how do we make developers addicted." They just chased the right things, fast feedback, visible progress, broad capability. But when those right things came together, all the parts of a game accidentally appeared. Fast reward, variable outcome, ownership, social pressure, scarcity, open loops. If a game designer had assembled these on purpose we would call it great gamification. Claude Code arrived at them by accident, and the result is stronger than anything I deliberately tried to build in the last year.

It is two in the morning. I look at the screen, my fingers hovering over the keyboard to write one more prompt. And for the first time, I see what I am doing. This feeling is not a flaw, it is a design. I sell gamification infrastructure, which means I teach people exactly how to put this feeling into their products. But Claude Code taught me a lesson in my own field. And I realized this: the point is not creating this feeling, it is which half of it you create. The creativity and progress side, or the fear of loss and sunk cost side. Claude Code does both, the early hours are the top half, after midnight the bottom half. I close the laptop. I will delete that code tomorrow, but I will write this piece, because a tool I could not put down for one afternoon is no longer just a tool.

If you read this, you clearly see that Claude Code has implemented almost every point of the Octalysis framework created by Yu-kai Chou, a gamification and behavioral design framework that analyzes and drives human motivation, and that is why you told your wife five more minutes. That was four hours ago.

It is eleven at night. I was going to fix one thing, the color of a button. I write the prompt, hit enter, and text starts streaming across the screen. That stream is a feeling all by itself. I have not seen the result yet, but my brain has already started collecting the reward, because I can see that something is happening. I can see movement. In the old editor the cursor just blinked and nothing happened. Now the screen is talking back to me. And before I have done anything, just by waiting, I slide into a kind of tension and anticipation. What is about to appear?

The output lands. The button is fixed, but along the way Claude noticed something else, "by the way, I cleaned up your state management too." I did not ask for that. But it is good. And right here the first hook fires: I asked for one thing and it gave me more than I asked for. The surprise feels like a small gift. And once you get a gift, you want one more. "Since you understood that so well, can you also do this?" I type. Eleven becomes eleven thirty.

What is happening here is a simple mechanic, but it is hard to describe. In old-school coding there were hours between an idea and a result. You write, you compile, you get an error, you fix it, you try again. The reward was far away and rare. Claude Code collapses that distance into seconds. Idea, prompt, result, all in one breath. And the more often the reward arrives, the faster the brain bonds to it. A slot machine works the same way: you pull the lever, a few seconds, a result. In Claude Code the lever is the prompt, a few seconds, a result. The only difference is that on a slot machine you mostly lose, and here you mostly produce something. But that word "mostly" is the danger itself.

Because the moment that hooks you is not the one where everything works perfectly. It is the one where it almost works. The button is fixed but something broke somewhere else. The page loads but the data does not come through. I got so close, it almost worked, one more prompt and it will resolve. And this is where I cannot get up. Because there is an open loop, an unfinished job, and the human brain cannot tolerate open loops. They call it the Zeigarnik effect, an unfinished task takes up space in your head and will not leave you alone. Walking away from working code is easy. Walking away from broken-but-almost-working code is torture. "I cannot go to bed until I solve this," I say. It is now one in the morning.

And there is this too: now it is my code. Maybe Claude wrote it, but I steered it, I prompted it, I shaped it. With every prompt I invested a little more of myself in this project. Half an hour ago it was a throwaway experiment, now it is "my project." And the more effort, attention, and time you put into something, the harder it becomes to give it up. I know it is not rational. Half of this prototype is junk, I will probably delete it when I look in the morning. But right now, at one thirty in the morning, this is my creation and I cannot abandon it. Ownership crushes logic.

I pick up my phone. On Twitter someone has posted "I shipped an entire SaaS solo this weekend with Claude Code." Underneath, dozens of people saying "same," "incredible," "I wrote 70k lines." And I go back to the screen. I am not actually competing with anyone, but I absorb the pace. If everyone is moving this fast, then stopping means falling behind. The social pressure is invisible but real. Even the people at the very top of the industry admit this feeling. The CEO of Y Combinator tweeted "So addicted to Claude Code, I stayed up 19 hours yesterday," and nearly a million people saw it. Strangely, that comforts me, it means I am not alone.

Then a warning: your token limit is running low. The window will reset in a few hours. And here a completely different feeling enters. Now I am not just saying "let me finish this," I am saying "let me not waste this window." Because the tokens I do not use will evaporate into thin air. This is not scarcity, it is something more insidious than scarcity, "use it or lose it." Like airline miles with an expiration date, if you do not use them they burn. And I paid for my subscription, those tokens are mine by right, if I do not spend them I feel like I am throwing my own money in the trash. The reason Garry Tan sleeps four hours is probably this, not for the output but to optimize the window. The product is now designing my sleep schedule.

The bitter part is that when I wake up in the morning I will see that half the code I produced overnight does not work. There were green checks, the tests passed, everything on screen looked successful. But Claude used a library that reached end of life, or built a structure that will be impossible to refactor in three months. Everything I thought I won that night was actually deferred debt. In gambling they call it a loss disguised as a win, the machine flashes its lights and congratulates you, but you have actually lost. In Stack Overflow's survey two thirds of developers say they lose time to "almost right" code, and half say debugging AI code takes longer than writing it themselves. So this is not just happening to me, this is the mechanic itself.

And here is what I understood: Claude Code did not do this on purpose. Nobody sat down and designed "how do we make developers addicted." They just chased the right things, fast feedback, visible progress, broad capability. But when those right things came together, all the parts of a game accidentally appeared. Fast reward, variable outcome, ownership, social pressure, scarcity, open loops. If a game designer had assembled these on purpose we would call it great gamification. Claude Code arrived at them by accident, and the result is stronger than anything I deliberately tried to build in the last year.

It is two in the morning. I look at the screen, my fingers hovering over the keyboard to write one more prompt. And for the first time, I see what I am doing. This feeling is not a flaw, it is a design. I sell gamification infrastructure, which means I teach people exactly how to put this feeling into their products. But Claude Code taught me a lesson in my own field. And I realized this: the point is not creating this feeling, it is which half of it you create. The creativity and progress side, or the fear of loss and sunk cost side. Claude Code does both, the early hours are the top half, after midnight the bottom half. I close the laptop. I will delete that code tomorrow, but I will write this piece, because a tool I could not put down for one afternoon is no longer just a tool.

If you read this, you clearly see that Claude Code has implemented almost every point of the Octalysis framework created by Yu-kai Chou, a gamification and behavioral design framework that analyzes and drives human motivation, and that is why you told your wife five more minutes. That was four hours ago.

I lost many traffic after chatGPT and now trying to optimize my contents for GEO. I am using Microsoft Clarity and I think it is good for starting. But also for a peofessional approach, I tried SemRush but I think it is so expensive for a really limited query. What is the best tool that you are using? And sure what is the best tips for GEO?

Gamification lifts your retention the week you ship it. Then it dies in month three.

Most founders think the mechanics got stale and bolt on another badge. That is not the problem. The problem is there is no finish line anywhere in the system.

Classic gamification is a ladder with no top. Points, levels, badges, repeat. By month three the user stops and asks "what am I actually winning here?" and when there is no answer, they leave.

Look at how Duolingo solved it. The streak alone could have been that endless ladder. So they put leagues on top of it. Bronze, Silver, Diamond. Every league closes weekly, you get promoted or relegated, and a fresh week begins. The game never ends, but it gets split into weekly loops that actually complete and have a result. By grouping users into tiers with promotion and demotion, Duolingo built a repeatable weekly engagement cycle. It works: users who join a league spend 20 percent more time in the app.

That is what retention really is. Not an infinite ladder, but loops the user gets to finish.

So look at your own product. Does your gamification have a "weekend," a peak, a moment of completion? Or is it just a number going up forever? Because that is exactly where the churn leaks in.

Hey everyone,

I’m working on a tool that provides an API-first progression infrastructure, gamificiation engine and widgets (XP, streaks, badges, leaderboards) for established SaaS. It saves engineering teams and product managers weeks of building this logic and designing gamification from scratch.

Early startups won't pay for this, so I'm targeting PMs focused on retention. Be brutally honest:

1. Build vs. Buy: If you wanted to add retention hooks (like streaks or levels), would you allocate engineering sprints to build it in-house, or buy a scalable API? Or what makes to you buy decision?
2. Pricing: What pricing model actually fits a product budget? (Per MAU, tiered, or flat fee?)
3. The Dealbreaker: What’s the biggest blocker for you to adopt an external API for user state? (Security, UI flexibility, etc.)

Just trying to validate if this solves a real product headache. Thanks!

Solo founder here, building in public [I hide my product name to not promote anything], a gamification API for B2B SaaS. The idea is to give product teams an engagement layer that adapts to their users instead of bolting on generic points and badges.

Here is the thing keeping me up at night.

When I look at what I have shipped so far, it feels like a widget. A pretty one, but still a widget. Points, badges, streaks, leaderboards. Useful, but not a philosophy. The more I talk to PMs the more I realize the real question is not "which mechanics" but "which model of human motivation are you actually building on."

I spent the last few weeks going deep on the main frameworks and now I am genuinely torn.

Bartle is the classic, but calling a SaaS user a "Killer" is a hard sell in any B2B context.

Hexad (Marczewski) is my favorite on paper. Six player types, each tied to a specific intrinsic motivator, validated 24-item scale. Maps cleanly to discrete mechanics per type.

SDT and RAMP (Autonomy, Mastery, Relatedness, Purpose) is the psychology underneath almost everything good in this space. Strong defense against the overjustification trap that kills most naive PBL (Points/Badges/Leaderboards) systems.

MDA (Mechanics, Dynamics, Aesthetics) gives me the cleanest architectural lens. As a builder it maps almost 1:1 to how I would structure the platform layers.

Fogg's B=MAT plus Nir Eyal's Hook Model is operational gold for habit formation but ethically loaded. Hard to defend in front of an enterprise buyer without flinching.

Werbach's 6D is process-driven and easy to sell to stakeholders, but it feels like a workflow more than a worldview.

Octalysis is what I am currently centering the next version of Hatched on. Eight core drives, mixes black hat and white hat motivation, has a strong visual language that customers actually grasp in the first meeting. The downside is that it is not academically validated the way Hexad or SDT are, and the black hat drives (scarcity, loss aversion, unpredictability) feel manipulative when you put them in front of a serious enterprise buyer.

So my question to PMs and anyone who has shipped real gamification in production:

1. Did you pick one framework as the foundation, or did you treat them as a toolkit and pull from each layer?
2. If you went with one, which one and what made it stick over 12+ months?
3. For anyone who tried Octalysis specifically, did the black hat drives create friction in B2B contexts, or did you simply not use those quadrants?
4. Meta question: do your users and customers actually care about the underlying framework, or is it internal scaffolding for your own thinking while what they actually feel is just the Dynamics and Aesthetics layer?

I am asking because I would rather rebuild now while the new version is still pre-launch than ship something philosophically incoherent and patch it for a year. Any war stories from people who have been through this appreciated.

For a long time I had the same conversation with every product team I worked with. Retention was flat, engagement was bad, churn was creeping up, and somebody would say: "let's add gamification."

What they meant was: points, badges, leaderboards. PBL.

We did it. Again and again. Sometimes the metric moved 5% for two weeks. Sometimes it moved nothing. Sometimes it backfired and started attracting the wrong kind of behavior. I have been on both sides of this. I have shipped these things and watched them quietly fail.

Recently I sat down with Yu-kai Chou's "Actionable Gamification" and I want to share the thing that hit hardest, because I think a lot of product people are stuck in the same loop I was.

His core claim is that PBL is not gamification. PBL is a measurement skin. You can put it on top of any system, and the system keeps doing whatever it was already doing, just with progress bars on it. If your underlying loop is "mildly useful, slightly annoying to use," badges will not save it. They will just make the annoying part feel more transactional.

What he calls actual gamification is "Human-Focused Design." The argument is that every game that has ever held a person for thousands of hours is built on combinations of 8 psychological drives, not on PBL. He calls this Octalysis:

1. Epic Meaning and Calling. The sense that what you are doing matters beyond yourself.

2. Development and Accomplishment. Real progression toward something hard.

3. Empowerment of Creativity and Feedback. Meaningful choices, visible consequences.

4. Ownership and Possession. The feeling that something is yours.

5. Social Influence and Relatedness. People you care about being part of it.

6. Scarcity and Impatience. Wanting what you cannot immediately have.

7. Unpredictability and Curiosity. Not knowing what is around the corner.

8. Loss and Avoidance. The fear of losing something you already earned.

Look at any product that genuinely held you for years and you will count at least three or four of these. Look at any "gamified" SaaS that gave you a badge once and you will find one. Maybe two if you are generous.

What clicked for me is how completely we treat #2 (Accomplishment) and #8 (Loss Avoidance) as if they are the whole field. The 100-point badge is Accomplishment with the rest of the iceberg cut off. The 365-day streak is Loss Avoidance turned into a guilt loop. Neither one, alone, builds a product people love. They build a product people grudgingly return to until the cost of returning exceeds the cost of letting go.

The piece that stayed with me most is his argument that the Endgame is what teams forget to design for. Most products design Discovery (a marketing problem), maybe Onboarding (a UX problem), and then everything past that is just "the product." Games design four phases, and the deepest one is Endgame: what does a power user do on day 600 that still feels meaningful? Almost no SaaS has an answer to this. We just hope churn comes slowly enough.

I want to be honest about something. When somebody on my team says "let's add a leaderboard," my first instinct is still to nod. It is the easiest thing to ship. It moves a number short term. It feels productive. But every time we do it without asking which of the eight drives we are actually serving and for which user, we are putting a costume on the same loop and hoping the loop will change.

What I am trying to do differently now:

Before shipping any "engagement" feature I ask, for the specific user persona, which of the eight drives the feature is actually built on, and which drive the product is weakest in right now. If the answer is the same drive twice (almost always Accomplishment), I push back and look for a feature that touches a weaker drive instead.

For activation, Empowerment (3) and Curiosity (7) tend to matter more than Accomplishment.

For long-term retention, Ownership (4), Social (5), and Epic Meaning (1) carry the weight.

For habit, Loss Avoidance (8) is the lever, but using it without anything from the right brain side of the framework gets you a guilt product, not a loved one.

A few questions I genuinely want answers to:

What is a product you stayed with for two-plus years, and which of the eight drives do you think actually held you?

For PMs who have shipped "gamification" features, which one moved a real retention metric and which one moved a vanity metric?

And if you have read the book, which drive do you think is most underused in B2B SaaS today? I keep landing on Ownership, but I am not sure.

(Not selling anything here, just thinking out loud after a book that genuinely changed how I look at a problem I have been stuck on for years.)

Für mich ist es ganz klar: Wenn man jemanden fragt: „Na, wie geht’s?“ und die Antwort einfach nur lautet: „Muss ja.“

Nicht gut, nicht schlecht, keine große Emotion, kein Drama. Einfach dieses Gefühl von: Man macht weiter, weil man halt muss.

Für mich steckt in „Muss ja“ irgendwie das komplette deutsche Lebensgefühl. Es klingt fast deutscher als jedes Klischee über Brot, Pünktlichkeit oder Stoßlüften.

Als ich jünger war, hieß es ständig: "Pass auf, was du ins Internet stellst." Keine privaten Fotos, keine persönlichen Informationen, nicht jedem vertrauen.

Aber inzwischen fühlt es sich so an, als hätten sich die Rollen komplett umgedreht. Mein Vater ist 66 und möchte gefühlt jedes Familienfoto auf Facebook posten. Neulich habe ich meiner Mutter ein kleines Geschenk gekauft, und bevor ich es ihr überhaupt richtig geben konnte, war schon ein Foto davon in der Familiengruppe. Ein paar Stunden später war es dann auch auf Facebook.

Urlaubspläne, Geburtstage, Krankenhausbesuche, private Familienmomente, manchmal sogar wer gerade wo ist alles wird ziemlich offen geteilt. Das Lustige ist: Wenn ich etwas poste, kommt trotzdem noch manchmal ein Kommentar wie "Musst du das wirklich ins Internet stellen?"

Früher wurden wir immer als die Generation dargestellt, die keine Privatsphäre mehr kennt. Aber in meinem Umfeld sind es mittlerweile oft eher die Älteren, die am meisten von ihrem Privatleben online teilen.

Ist das bei euch auch so, oder ist das nur in meiner Familie so stark umgedreht?

Hi r/gamification, long time reader, first real post here. Solo founder, looking for the kind of critique this sub does well.

Quick context: 6 years at Algolia and Salesforce Commerce Cloud building event pipelines, then co-founded, an English learning platform with ~130K students. At here we wired streaks, XP, learner companions, a marketplace and badges from scratch. Took us roughly 5 engineer-months and we got half of it wrong on the first try. Then I started seeing the exact same pattern at three companies I was advising. Same architecture mistakes, same shame spiral.

So I built Hatched, an API-first progression infrastructure.

The thesis: modern products already emit the signals (lesson_completed, workout_kept, module_finished, feature_used). The hard part isn't producing the signal, it's wiring it into a coherent loop without your eng team quietly turning into a part-time game studio for two quarters.

How it works

One POST:

POST /v1/events
{
  type: "lesson_completed",
  externalUserId: "user_456",
  properties: { score: 92, skill: "grammar" }
}

You get back, in the same response, the full state delta: coins granted, XP routed to the right skill, streak kept (or grace day burned), badge unlocked, companion buddy evolution progress, path step completed.

Then embed live widgets in your product with one <script> tag (Preact, Shadow DOM, themed to your brand) or skip widgets entirely and render the state yourself.

What's in v1 right now:

• Skills and multi-currency coins
• Streaks with grace days and milestones
• Badges (manual and rule-based)
• Learning / onboarding paths
• Marketplace where users actually spend their coins
• Companion buddy with evolution stages (preset, AI-generated, or hybrid)
• Leaderboards (global, cohort, friends)
• Dashboard for the product team to tune rules and economy without redeploys
• Signed webhooks, idempotent events, typed SDK
• Analytics: streak active rate, badge earn rate, marketplace conversion, economy health

What I am explicitly trying NOT to be: another widget-first SaaS where you bolt a confetti banner onto checkout and pretend it moved D7. If the underlying event model is junk, no progression layer fixes that. Happy to be pushed back on this point.

Where I genuinely need this sub's brain:

1. Is "customer events in, progression out" actually clear to a non-engineer PM, or does it read like analytics jargon?
2. For people who design loops professionally, what is the dumbest thing I am almost certainly missing in the rule engine?
3. Companion buddy with evolution: useful retention primitive, or am I sliding into kid territory? It is optional, but I want a sanity check from people who've watched this play out at scale.

Design partner offer (first 5 only, then it closes):

• Free for 6 months
• Lifetime 70% off after that
• I personally wire your first event in a 30 min call
• Direct line to me, your feedback ships in the next sprint
• The goal is one beautifully working loop in your product, not a feature dump

If you ship something where retention is real money and any of this is interesting, comment or DM. I will send a demo link and we can decide together if it is a fit.

Roast welcome. Half the reason I am posting here instead of r/SaaS is that this sub will actually call BS on bad loop design.

https://preview.redd.it/oit9mghllx0h1.png?width=1254&format=png&auto=webp&s=132d1af4253f39e7934f5146a3c16e084f1cb3ff

Disclosure: I am the founder of Hatched.live

9 years, bootstrapped, mid 7-figure ARR in live-tutor language learning. Profitable. Growth flat for 18 months, AI reshaping the category.

While running it, I kept rebuilding the same internal gamification backend. Streaks, XP, badges, paths. Three times in five years. Eventually pulled it out as a standalone B2B API product. Solo on the new one.

Now I'm running both and I have to pick.

The EdTech has revenue and a co-founder who can carry it without me. The new product has my conviction and no revenue yet. If I half-commit to the solo one, it dies from neglect, not from being a bad idea.

For anyone who's done a version of this: how did you actually break the tie?

(Happy to share more details in the comments or over DM.)

9 years, bootstrapped, mid 7-figure ARR in live-tutor language learning. Profitable. Growth flat for 18 months, AI reshaping the category.

While running it, I kept rebuilding the same internal gamification backend. Streaks, XP, badges, paths. Three times in five years. Eventually pulled it out as a standalone B2B API product. Solo on the new one.

Now I'm running both and I have to pick.

The EdTech has revenue and a co-founder who can carry it without me. The new product has my conviction and no revenue yet. If I half-commit to the solo one, it dies from neglect, not from being a bad idea.

For anyone who's done a version of this: how did you actually break the tie?

(Happy to share more details in the comments or over DM.)