1
0 Comments

Kindness isn't data

Hi. First post here. I'm Fabri — three months building solo, full-time, no co-founder, no team. I'm Italian and writing in English, so please be patient with the rough edges.

Here's what's real, so this isn't abstract. The thing is live: a SaaS, a Chrome extension, a paid tier already running. I built all of it alone in those three months. I'm not saying that to impress anyone — half of it still scares me — but so you know I'm not asking from the idea stage. It exists. People can pay for it.

For the technical sliver of you: running a multi-agent orchestration solo is about as smooth as a cat in trousers. I'm taming it well enough, but it's the kind of work where every fix surfaces two more questions you didn't know you had.

That's exactly what makes my question harder, not easier.

Because it's the one I think every solo founder hits at least once, usually around 2am — I suppose:

What exactly have I gotten myself into?

Mine has a twist now. It's not "will this ever work" — it works, it's out there. It's "I built it, it's real, and I'm not sure I'm building it for the right people."

What I'm building is niche enough that explaining it to a normal person takes longer than they want to listen. There are early users — the founder pricing exists for a reason — but few, and the signal I get from them is the warm, encouraging kind.

Kindness isn't data.

What I'm watching for is different: a stranger I've never spoken to, using it, writing back unprompted because something in it worked. I haven't seen that yet. The only honest way I've found to know whether the work matters is to put it somewhere people are free to ignore it, and watch what they do.

The part I underestimated wasn't the technical work. It's deciding everything alone. You make ten calls a day with half the information and nobody to push back. You read your own landing page so many times that the familiarity starts to feel like clarity — it isn't. You go invisible for weeks behind a monitor, friends ask what happened to you, and you don't have a good answer, because you're still here. Just not where they can see.

For years my work has been about how people learn together — peer-learning, at Pyragogy. Then to ship this I did the exact opposite: shut myself in a room and decided everything alone. I notice the contradiction. I don't love it.

Someone reading this might ask: you built a tool that adds friction and depth to drafts before they go out — why are you asking other founders to do what your product is supposed to do?

Fair question. Obliqo works on the text, not on the founder. It runs four voices over what I write, from different angles, and hands back what doesn't hold — I ran this post through it before publishing, and it found a contradiction I hadn't seen. But it doesn't tell me which product to build, who it's for, or whether the bet is the right one. That kind of friction doesn't live in a draft. It lives in conversation with people who've been where you are.

I built a tool for pressure on drafts. What I'm missing now is pressure on direction.

So I'm not here for product feedback. I'm asking for something I think is more useful: how did you get through your first months building solo? Not the success story — the muddy middle. The part where you still weren't sure the thing mattered.

Who did you talk to? What kept you from mistaking isolation for focus? Did you ever find, or build, a small group of founders who audited each other's work honestly?

That last one is what I'd want most. Numbers come later. Right now what I'm missing is a few people who get it from the inside.

I'll be in the comments. I'm here to listen more than to talk.

(For the curious: Obliqo, at obliqo.pyragogy.org — four AI voices read your draft before you publish, each from a different angle, and hand back what doesn't hold. It pushes back; it doesn't rewrite. Built out of the peer-learning work at pyragogy.org. Happy to get into it in the comments — but that's not why I'm posting.)

posted to Icon for group Building in Public
Building in Public
on June 1, 2026
Trending on Indie Hackers
Your build-in-public audience is not your market. I learned the difference the slow way. User Avatar 182 comments I built a WhatsApp AI bot for doctors in Peru — launched 3 weeks ago, 0 paying customers, and stuck waiting for Meta to approve my app User Avatar 61 comments Built a "stocks as football cards" thing. 5 days in, my launch tweet got 7 views. What am I missing? User Avatar 33 comments From broke and burned out as a PM, to launching my SaaS and optimizing my health User Avatar 32 comments Why Claude Skills Are Becoming Important for Tech Careers User Avatar 24 comments I kept starting projects and dropping them. So I built a system that wouldn’t let me User Avatar 23 comments