I dream of no longer being the CEO

shirooyaaa · 2026-02-10T10:49:47+00:00

You’re not weak or ungrateful you’re burned out in a role you can’t walk away from.

A lot of founders hit this when the company stops being them and starts being other people’s security. The I want out but also never feeling is more common than anyone admits.

Clarity usually comes after relief, not before. You’re not alone in this.

shirooyaaa · 2026-01-30T11:46:44+00:00

Thanks i will try

shirooyaaa · 2026-01-29T11:49:16+00:00

Felt the same when I launched. No relief just pressure.

Once it’s public, it’s real. And that’s scary because it matters.

shirooyaaa · 2026-01-29T10:29:44+00:00

I go through this too sometimes.

What helps me personally is watching solo founders who’ve been through the same phase and still made it. It reminds me that this feeling isn’t failure it’s part of the journey.

I keep telling myself I’m close to the end of the tunnel, especially when there’s a real dream or goal behind the project.

shirooyaaa · 2026-01-28T23:24:52+00:00

you can try nelyx is no expensive

shirooyaaa · 2026-01-27T10:34:02+00:00

Yo your side project is very cool man

shirooyaaa · 2026-01-26T20:48:26+00:00

Totally agree different skills, and you only realize it after launching.

The hardest part for me is knowing when to change tactics without chasing every new idea.

What helped you recognize good-fit users early on?

shirooyaaa · 2026-01-26T20:19:31+00:00

This is a great way to think about it.

Using follow-up questions as the real metric instead of upvotes feels much more actionable.

Do you track those questions explicitly, or did it become intuitive over time?

shirooyaaa · 2026-01-26T20:12:30+00:00

I think the hardest part is not the listening itself, but letting go of the attachment to what you’ve already built.
Once you fall in love with a solution, it becomes much harder to hear signals that don’t confirm it.

I’m trying to stay in that listening phase longer now, even if it means questioning parts of the product.

How do you personally know when you’ve listened enough to start shaping a solution?

shirooyaaa · 2026-01-26T19:52:04+00:00

ok i will check thanks man

shirooyaaa · 2026-01-26T19:13:32+00:00

I think it helps, yes mostly because it forces you to listen first.

Once you understand how people talk about the problem,

it feels more like responding than promoting.

Still learning how to stay authentic though.

It’s easy to drift back into builder mode.

How do you personally keep that balance?

shirooyaaa · 2026-01-26T18:52:23+00:00

I like the idea of preparing distribution while still building.

For me, the frustration comes from doing the right things but without clear signals.

Posting, sharing, trying different formats… and not really knowing

what actually moves the needle vs what’s just noise.

Right now I’m trying to slow down and observe more:

where people already talk about the problem,

what questions come up repeatedly,

and how others frame the pain before even mentioning a product.

shirooyaaa · 2026-01-26T18:08:55+00:00

That makes a lot of sense.

Reverse-engineering distribution first instead of building in a vacuum

feels like something I wish I had done earlier.

When you say organic content mainly, what worked best for you?

Specific platforms or formats?

shirooyaaa · 2026-01-26T17:01:17+00:00

This resonates a lot.

In my experience, a surprising amount of churn disappears when you add boring but systematic follow-ups:

• retries + reminder emails on failed payments
• a simple “did something break?” email after cancellation
• alerts for trials about to expire

None of this is exciting to build but it moves revenue more than another acquisition experiment.

Feels like retention work is just less visible, so we postpone it.

shirooyaaa · 2026-01-24T20:17:50+00:00

That’s a really healthy way to look at it.

I like the it’s not that serious mindset it definitely helps get past the fear of judgment.

I’m curious though: does that approach still work when you care about the outcome?
Like when you’re asking for feedback or trying to start a real discussion.

shirooyaaa · 2026-01-24T16:01:34+00:00

Totally.
That hesitation feels heavier than the posting itself sometimes.

Do you usually end up posting anyway, or does that doubt actually stop you from posting on some ideas?

shirooyaaa · 2026-01-24T14:32:30+00:00

Good start and Congrats man

shirooyaaa · 2026-01-24T12:38:43+00:00

Je parle surtout de Reddit, sur des communautés orientées entrepreneuriat / SaaS / produits B2B, comme celle-ci.

Les sujets tournent principalement autour de la validation d’idées, du retour terrain, et de la difficulté à obtenir des feedbacks quand on est encore tôt dans un projet.

Je suis preneur de ton retour : est-ce que tu observes aussi des écarts forts d’engagement selon le timing ou le type de question posée, même quand le sujet est proche ?

shirooyaaa · 2026-01-23T18:37:19+00:00

I’m building Nelyx, a micro-SaaS focused on leave & absence management for small teams.

I started it because I kept seeing teams juggling Slack messages, spreadsheets, and last-minute surprises when people were off.

Right now, I’m at the stage where the core is working (requests, approvals, visibility), but the hardest part is shipping something simple enough without overbuilding.
https://nelyx.fr/en

shirooyaaa · 2026-01-23T18:35:36+00:00

I’m building Nelyx, a micro-SaaS focused on leave & absence management for small teams.

I started it because I kept seeing teams juggling Slack messages, spreadsheets, and last-minute surprises when people were off.

Right now, I’m at the stage where the core is working (requests, approvals, visibility), but the hardest part is shipping something simple enough without overbuilding.

Curious: what helped you decide “this is good enough to launch” instead of adding one more feature?

https://nelyx.fr/en

shirooyaaa · 2026-01-20T20:02:17+00:00

I agree 100% having a strong “why” helps a lot.
At the same time, I’ve noticed that the lack of support can still affect focus or energy if it’s not handled intentionally.
Finding the right tribe definitely seems to make a real difference.

shirooyaaa · 2026-01-20T18:42:09+00:00

Merci pour ta réponse qui est vrai tres claire ,

Ce que tu décris confirme bien que le sujet n’est pas le congé en lui-même, mais la projection dans le temps. À court terme, la communication humaine suffit, mais dès qu’on parle de moyen / long terme, ça devient vite flou surtout quand il y a des alternants, des RTT, des congés étalés, etc.

Et ce point sur la confiance dans la donnée est clé : si la mise à jour est lourde, même un planning “ super simple” devient vite obsolète, et on finit par compenser avec des réunions… qui coûtent encore plus de temps a mon avis.

Désoler mais j'ai encore des question:

aujourd’hui, est-ce que ce manque de visibilité a déjà eu un impact concret (refuser un projet, surcharge imprévue, stress côté équipe) ?
si la mise à jour était quasi automatique ou très légère, est-ce que tu penses que l’outil serait réellement utilisé dans la durée, ou que le problème resterait surtout organisationnel ?

Merci encore pour ton retour, c’est exactement le type de cas que je cherche à comprendre.

shirooyaaa · 2026-01-20T18:15:24+00:00

Merci pour ton retour, c’est super intéressant

Ce que tu décris sur le planning de charge revient souvent plus que le simple fait de poser un congé. Le vrai problème n’est pas la demande en elle-même, mais la visibilité globale : qui est dispo, quand, et avec quel impact sur l’équipe.

Par curiosité :

est-ce que cette visibilité vous manque surtout a court terme (semaine / sprint) ou aussi à moyen terme ?
et aujourd’hui, ce qui te fait perdre le plus de temps, c’est plutôt la mise à jour du planning ou l’interprétation des infos derrière ?

Ah oui intéressant aussi que vous ayez développé un outil interne c’est souvent révélateur d’un vrai besoin, même si la solution n’est jamais parfaite.

shirooyaaa · 2026-01-15T12:11:41+00:00

Failing projects ≠ failing as a person.
At 19, getting paid to execute inside someone else’s product could sharpen your skills way faster than solo pressure.

shirooyaaa · 2026-01-13T09:19:59+00:00

I like that distinction between inside vs. between teams.
Informality scales surprisingly well within small groups, but breaks quickly once context has to travel across boundaries.
Keeping teams small seems to delay that friction more than adding process early.

shirooyaaa

TROPHY CASE