9
11 Comments

I'm 58 and built a "debugger" for human psychology (Next.js + Clerk). How can I improve my conversion?

I’ve been a developer for years, but this is my first solo SaaS project.

The Concept: I realized my relationship patterns were just "legacy code" from childhood. So I built Origin Code—an app that maps your "Shadow Archetype" (like The Fixer or The Ghost) and helps you debug it.

The Stack:

  • Next.js 14 (App Router)

  • Clerk (Auth)

  • Vercel KV (Database)

  • Stripe (Payments)

The Problem: I have a "Freemium" model. The diagnosis is free, but the "User Manual" is $19. I'm trying to figure out if my "Paywall" is too aggressive or not aggressive enough.

The Ask: Could you guys roast my result page flow? Does the "cliffhanger" make you want to buy, or does it just annoy you?

Link: https://origincode.app

posted toAvatar for product Origin Code
Origin Code
  1. 2

    Shipping a solo SaaS at 58 is already a win. Respect.

    The “legacy code from childhood” metaphor works well, especially for a dev audience — it’s clear and differentiated. The free diagnosis feels real, not fake-freemium.

    On conversion: the cliffhanger does create curiosity, but it also feels slightly abrupt. I wanted one concrete example of what actually changes after I pay — not more theory, but a tangible “here’s how this shows up in your relationships / decisions.”

    I don’t think the paywall is too aggressive. If anything, it might be under-justified. A short preview of the manual (headings, sample paragraph, or a before/after scenario) would likely convert better than pure suspense.

    Overall, this feels like a legit product looking for sharper framing, not a pricing problem. I’d optimize clarity before experimenting with price or gating.

  2. 2

    Respect for shipping this solo. One thing that stood out to me is conversion often drops when users understand what they’re seeing but not why it matters right now. On your result page, do you explicitly anchor the diagnosis to a recent real decision or behavior they recognize, or does that context live mostly in their head? That gap alone can kill urgency.

  3. 2

    I am psychologist with IT background. Really interesting idea. How do you do your marketing?

  4. 1

    Just want to say: nice going. I'm slightly older than you, and I'm sure a lot of people assume that people our age are just phoning things in at this point and not trying to do things like launch a solo business. Not true, though!

  5. 1

    This is a really interesting concept — the “legacy code” framing clicked for me immediately. From a user POV, the free diagnosis feels valuable, but the jump to the paid manual might land better if I saw one concrete outcome first (even a small, actionable insight). Cliffhangers work best when users feel progress, not just curiosity.

    Curious: have you tested giving a tiny win before the paywall to build trust?

  6. 1

    the 'legacy code' analogy for relationship patterns is actually sick. as an mis student building an automation saas on the side, i totally get the 'debugging' mindset.

    ​about your paywall: the $19 jump might feel a bit steep if the free diagnosis is too generic. here’s my roast: if you give them the 'what' (the archetype) for free, you gotta make sure the manual is 100% about the 'how' (the fix). if the manual is just more theory, users will feel baited.

    ​maybe try a 'preview' of one specific fix? like showing them one line of the 'new code' they need to write. also, nextjs 14 + vercel kv is a vibe for a fast mvp, love the stack choices. good luck with the launch!

  7. 1

    This is a genuinely strong concept, especially the “legacy code from childhood” framing — that lands.

    One thought on conversion: the cliffhanger itself isn’t the issue. The question is whether the free result creates emotional specificity.

    If users clearly recognize “oh, this explains why I did that last week”, the $19 feels small. If the result stays more abstract or archetypal, curiosity alone usually isn’t enough to push them over the line.

    You might experiment with anchoring the diagnosis to a concrete recent behavior (relationships, conflict, avoidance, over-functioning) before introducing the manual. That tends to turn insight into urgency.

    Respect for shipping this solo — that alone puts you ahead of 99%.

  8. 1

    Really interesting concept. Framing psychology as something you can debug is a powerful mental model. Have you found that users respond better to this framing compared to more traditional self-help language?

  9. 1

    The idea itself is compelling, but I don’t think conversion comes down to the paywall. ~

    What you’re really selling isn’t a “User Manual.” It’s relief—the moment someone recognizes a painful pattern and believes there’s a way out.

    If the free diagnosis clearly names the problem but stops just short of emotional resolution, the paywall feels earned.

    If it already feels complete, people bounce. That line matters more than how aggressive the cliffhanger is.

  10. 1

    For me personally I'm not into psychology. I did try it out and found that some of the questions I couldn't answer accurately, or did not fit for my upbringing making it a bit confusing. Sometimes I would rather have the option to choose or specify "Other" or "Does not apply". The number of questions did test my attention span a tad. The cliffhanger I could see being tempting, I'm definitely not the target audience so take that with a grain of salt :)

  11. 1

    Hi there, great product! I love the idea, it made me think about a therapeutic chatbot like you answer questions and get AI therapy sessions based on that.
    Good luck with the project!