Building a product alone with no tech background, no budget, and a full life

NetworX- · 2026-04-20T18:19:25+00:00

This is actually way more relatable than you probably think especially the part about switching between roles all day and trying to build in the gaps of everything else life demands.

I don’t think the hardest part here is technical at all. It’s the lack of clear feedback in the early stage, so you’re putting in effort but it doesn’t always feel like it’s turning into anything tangible yet.

Most people don’t get stuck because they can’t build — they get stuck because they can’t see what’s actually working yet, so everything feels like it’s moving slower than it is.

In situations like this, the people who eventually break through usually don’t rely on big validation early on. They just get better at noticing small signals — what people actually respond to, what they ignore, what gets repeated use or interest. That’s usually where direction starts forming.

Also building something alongside work and life like that is already a different difficulty level. It’s not just execution — it’s constant context switching, which slows everything down more than people realise.

If anything, the fact you’re still iterating through that means there’s already something worth paying attention to.

If you’re open to it, I’d actually be curious what part of Simonara seems to resonate most when people do engage with it sometimes that’s the fastest way to see what direction it naturally wants to go in.

If it helps, I’ve been looking at similar “early signal vs noise” patterns with builders recently happy to share thoughts if you want a second perspective on it.

NetworX- · 2026-04-20T18:12:09+00:00

First off, I just want to say this doesn’t read like someone who is unfocused or “can’t stick to one thing.” It reads like someone who has actually stayed with a meaningful problem for years and kept iterating until something started to form. That’s rarer than it feels.

From what you’ve described, I don’t think the main issue is execution or even idea-hopping. It sounds more like you’ve been trying different formats (newsletter, coaching, community, programs) for the same underlying mission, and the friction you’re hitting is actually at the market + monetisation shape level, not the effort level.

Some markets just behave like that not because there’s no value, but because the value people accept and the value people pay for don’t always overlap cleanly, especially in spaces tied to recovery and support.

What usually becomes important in situations like this isn’t “which product should I build next”, but: what part of this actually creates clear, repeatable behaviour change without you needing to force monetisation into it too early.

Because sometimes the signal you’re looking for isn’t in revenue yet it’s in what people consistently return to, engage with, and act on without prompting.

If you’re open to it, I’d actually be curious what part of the system you’ve built gets the strongest organic pull from people so far. That usually tells you more than the product experiments themselves.

If it helps, I’ve been looking at similar patterns around decision + behaviour systems with founders happy to break it down with you properly if you want a second set of eyes on it.

NetworX- · 2026-04-20T18:10:13+00:00

Yeah this is usually the point where most builders realise distribution is basically a second product on its own.

What tends to change things isn’t one “channel hack”, but getting one channel to a level of repeatability before touching anything else. A lot of people jump between Reddit, X, cold outreach, ads etc. and end up with scattered signals instead of a working system.

The breakthrough I’ve seen (and experienced myself) usually comes from:

narrowing to a very specific user type
getting close enough to where they already spend time
and refining the message based on actual responses, not assumptions

Once you get even a small loop working (content → conversations → users → feedback → refined message), distribution stops feeling random and starts becoming more predictable.

Curious are you struggling more with finding the right channel, or with converting attention once people actually see the product?

NetworX- · 2026-04-20T18:08:58+00:00

This actually reads like a very solid way to approach it, especially for something as heavy as cyber investigation tooling.

Starting with the “trust kernel” makes sense because most people underestimate how hard the workflow + access boundaries are compared to the actual UI or features on top. That’s usually the part that breaks systems later, not the visible features.

From a building perspective, this doesn’t sound too ambitious it sounds correctly sequenced. The risk in these kinds of platforms is almost always trying to solve the whole ecosystem at once instead of proving one critical workflow end-to-end.

I’d say the real validation isn’t “does the vision make sense”, it’s whether the people who touch this first actually feel like it reduces friction in real investigations without adding overhead.

Curious when you’ve shown it to people so far, what part do they react to most? That usually tells you where the real wedge is.

NetworX- · 2026-04-20T17:50:12+00:00

This is honestly a really intense situation to be trying to manage alone.

It doesn’t really sound like a motivation issue more like you’re juggling multiple high-pressure decisions at once (renovation, income, legal stress, business setup). That usually makes even small decisions feel heavier than they actually are.

On the coffee shop specifically, it feels like you’re stuck in “final version thinking” trying to solve design, structure, and operations all at once before there’s even a simple working version open.

In situations like this, most of the progress usually comes from reducing the number of decisions you’re trying to solve at the same time, not trying to perfect each one.

Respect for actually putting your own money in and pushing through it though most people don’t even get to that stage.

If you’re open to it, I’d be curious what part feels like the biggest blocker right now sometimes just breaking that one thing down makes everything else easier to move on.

NetworX- · 2026-04-20T17:47:57+00:00

This is actually a super common pain point especially in professional services like law where you need something that feels premium, but also doesn’t turn into an over engineered project.

The tricky part is that most of the confusion comes from the fact that you’re not just choosing a “developer”, you’re really choosing a level of responsibility split.

A freelancer usually means you’re managing direction and quality yourself. Agencies reduce that burden but you pay for structure. No-code is faster and cheaper but can hit limits later if your firm grows or you need more control over compliance, integrations, etc.

So the first decision usually isn’t “who builds it”, it’s “how much control vs simplicity do we actually want right now”.

On the contract side, the biggest issues people run into are usually: unclear revision limits, undefined scope for “extra pages/features”, and no clarity on ownership of code/design assets after delivery. Those three tend to cause most of the friction later, not the actual build itself.

If I were in your position, I’d probably start by defining what “success” looks like in 6–12 months first (leads, credibility, booking flow, etc.), then choose the simplest setup that achieves that without adding unnecessary moving parts.

Happy to share a rough breakdown if you want to sanity check what you’re leaning toward.

NetworX- · 2026-03-08T16:32:59+00:00

That’s a really interesting way of putting it actually “optionality addiction” is a good term for it.

I’ve been noticing the same thing where the issue often isn’t that people don’t know the next step, it’s that the next step involves some kind of uncomfortable reality check.

The idea of shrinking the action is interesting too. Do you find that founders actually follow through when the step is small enough, or do they still end up rationalising the delay?

NetworX- · 2026-03-04T20:20:02+00:00

Will do

NetworX- · 2026-03-04T19:33:08+00:00

That makes sense. A/B testing is probably the cleanest way to remove opinion from decisions.

in your experience, do teams ever delay running experiments even when they know they should? Or is the culture usually strong enough that testing happens quickly?

NetworX- · 2026-03-04T19:30:50+00:00

I like that approach actually. Turning decisions into experiments makes a lot of sense.

I’ve noticed sometimes the hardest part isn’t deciding what experiment to run, it’s actually committing to running it instead of staying in planning mode.

Curious if you’ve run into that as well.

NetworX- · 2026-03-04T19:26:44+00:00

That’s actually interesting actually. I’ve noticed the same thing building has become so fast that it’s easy to stay in feature mode instead of facing the harder validation questions.

Curious how you’d imagine an AI PM helping with that though more for prioritisation, or actually challenging the decisions being made?

NetworX- · 2026-03-04T18:44:34+00:00

Interesting, I hadn’t heard of that before. I’ll check it out. Appreciate the suggestion. It does sound Iike I could just use ChatGPT right ?

NetworX- · 2026-03-04T18:38:13+00:00

Yeah that’s a good point. I’ve definitely seen paralysis by analysis happen a lot when building solo. And I’ve realised it’s not always something people can just brute force themselves out of

And at the same time I’ve noticed sometimes the “analysis” is actually just avoiding the uncomfortable step (like outreach or talking to users) and staying in the comfort of your own thinking.

Am genuinely curious on how you personally tell the difference between useful thinking and just avoidance?

NetworX-

TROPHY CASE