If you have an idea but haven't started building yet — what's the actual block?
I've been talking to non-tech folks who have an idea sitting in their head (or in a Notion doc) for months — but haven't started building. The
reasons they give me aren't "I don't know how to code." It's more often:
- "I don't know if it's even possible with AI tools today"
- "I don't trust myself to pick the right tool to start with"
- "I'm scared the first attempt will fail and confirm I'm not cut out for this"
- "Every time I sit down to start, I open YouTube and lose 3 hours"
If you've been in this spot — even briefly — what was the actual block for you? Was it tool overwhelm, fear of failing publicly, lack of a small
enough first step, or something else entirely?
Trying to map the real shape of this before I assume.
Trending on Indie Hackers
For me, it’s usually not the technical side. It’s uncertainty around distribution. Building feels predictable; finding the first customers often doesn’t.
For me the block was never the idea — it was not knowing if my architecture decision was correct before I started. I'd spend weeks planning instead of building. What broke it was deciding to just ship something broken and fix it in production. My OTT app DramaHub has been live for 18 months now and I've fixed more real problems from real users than I ever would have caught in planning. The fear of the first attempt failing is actually the right instinct — just let it fail with real users instead of in your head.
the reframe from "fail in your head" to "fail with real users" is the actual unlock — most people stay in the first mode because the failure feels lower-stakes there (only your own self-image is exposed, not the work). but the cost shows up later as months of unbuilt projects.
curious about the moment of the shift for you specifically. did "ship something broken and fix in production" come from a particular bad experience (something stalled too long, an idea you watched die), or was it a deliberate decision triggered by something external — a deadline, a co-founder, a customer ask? trying to figure out whether founders who escape this loop tend to fall into a similar trigger pattern, or whether each one is genuinely idiosyncratic.
The "YouTube and 3 hours later" line hit home. That's not a time management problem, that's an environment problem.
What I see with founders (including myself) is that the block isn't the idea itself. It's the default environment. You wake up, open the laptop, check email, check analytics, check messages, check Reddit, check YouTube, and suddenly it's 2pm and nothing was built.
I've started testing a different approach: removing the choice entirely. For the last few weeks I'm running week-long deep work retreats in Zanzibar where folks literally cannot access their normal distractions. The result is almost always that people ship in 3 days what they couldn't in 3 months at home.
That tells me the actual block for most people isn't motivation or knowledge. It's the absence of an environment that makes starting the default state.
Curious: when you mapped the real shape of this for the folks you talked to, did any of them mention environment as a factor? Or was it mostly tool overwhelm and fear?
that's the right diagnostic — short-term forcing function works on almost anyone, durability is the real question. if you ever publish the post-retreat shipping data (even informally), would love to read it. that "did the unlock stick?" follow-up is the part most environment-based interventions never measure.
Honest answer: environment came up once or twice but not as the dominant block. The pattern I'm hearing more often is uncertainty about where the first concrete attempt even starts — people stay in research/comparison mode because that feels like progress while not requiring them to commit to anything testable. Your Zanzibar setup might be solving that indirectly though — removing the comparison-loop entirely is environment-as-forcing-function.
Curious about your retreat data: of the people who "ship in 3 days what they couldn't in 3 months", do they continue shipping when they get home, or does the pattern reset? That'd tell us whether you're solving the block or just bypassing it temporarily.
Still early data. I'm observing for now. The retreat definitely forces action in the moment, but long-term shipping behaviour after people return to their normal environment is what I'm tracking.
Yeah, this is the trap. The blocker usually isn’t coding, it’s the jump from a half-formed thought to something you can actually work on. People turn that into a research project, comparing tools and rewriting the idea in Notion instead of just getting a rough first sentence down. I built DictaFlow for exactly that, getting the thought out fast enough so you can sort it later.
The "research-project trap" framing is sharp — half-formed thought → comparison research → never built. That's exactly the loop I'm trying to understand.
When you built DictaFlow, was it because you saw this pattern in yourself first, or in users? Asking because the founders who solve this kind of block usually have a very specific memory of being stuck in it.
Money and data is the problem, planning to build one ai tool which will help retailer to purchase stuff based on whats selling providing subscription otherwise free assistence on basic stuff what to buy with qty specially for general stores eventually the game is bigger and profitable for both b2c and b2b
"Money and data" — both real blocks for AI tools. Curious which one is currently the bigger weight for you: is the money block stopping you from accessing the data (e.g. you'd need to pay for an API), or is the data block stopping you from validating whether the money problem matters yet?
Also — for your retailer assistant idea: have you already talked to any actual retailers about whether they'd use something like this? That conversation often resets which block is the real one.
This question is relatable because the block is often not the idea, it is uncertainty around where to start or what to build first. Validation fear, perfectionism, and overthinking stop more products than lack of effort.
Foundersbar helps startups turn early ideas into structured MVP plans so founders can move from thinking to building faster.
Honestly I think the biggest blocker is not coding anymore. It’s uncertainty.
People don’t know:
“am I even starting the right way?”
So they keep researching, watching tutorials, comparing tools, rewriting ideas in Notion… because that feels productive without risking failure.
AI tools also created a weird situation where people now feel like they should be able to build something, which makes the hesitation even worse psychologically.
Most people are not blocked by lack of ideas.
They’re blocked by fear of wasting months on the wrong first step.
Yogya — this is sharp, especially the framing that AI made the hesitation worse psychologically ("I should be able to build this").
Curious — are you describing this from your own pattern, or from people you've observed? Either way, can you take me to one specific moment when you (or someone you saw) actually broke that "research → tutorials → notion → reset" loop? What concretely tipped them over to "today I'm trying something even if it's wrong"?
Honestly for me the shift happened when I realized I was using “learning” to delay contact with reality.
I’d keep refining ideas, changing direction, researching tools, redesigning plans — but none of it forced me to answer the uncomfortable question:
“does anybody actually care about this?”
The thing that broke the loop was lowering the importance of the first version completely.
Instead of thinking:
“this needs to become a real startup”
I started thinking:
“let me see if I can get even 5 real people interested.”
That changed everything because suddenly the goal was not perfection anymore.
It was exposure to reality.
And weirdly, once I stopped treating the first attempt like a life-defining decision, shipping became much easier.
This is the cleanest articulation of the breakthrough I've heard so far — "using learning to delay contact with reality" + "lowering the importance of the first version" + "5 real people interested instead of becoming a startup".
The reframe from "real startup" to "5 real people" sounds like the actual hinge. Curious how you defined what counted as "interested" though. Was there a specific signal you were looking for (someone replied, someone asked a follow-up question, someone offered to pay), or were you reading the room more loosely? Asking because most people I talk to get stuck inventing that signal — they can't tell if "they liked it" means anything.
If you'd ever be up for trading notes on a quick call (I'm doing 20-min research interviews on exactly this), I'd love to. No pitch — your framing is sharper than most.
This was me for the longest time until I found the right person that was able to push me past the edge. I believe it's really about surrounding yourself with the right people and allowing yourself to fail
"Until I found the right person who pushed me past the edge" — that's a moment most people gloss over. Can you take me to the specific conversation? What did they say or do that actually shifted you? Was it permission to fail, a deadline, a side-by-side session, or something else entirely?
Trying to understand if these breakthroughs share a shape, or if they're all uniquely personal.
For me, I always loved sharing business ideas with certain friends. We'd talk about them, strategize, laugh over them, then forget about them in a week. When I began BrewChat, it was different. I brought the idea to my cofounder, we talked about it, strategized dropped it. But in a week, he called me back up and said, "so when are we doing this". That hit something inside me that told me we had an idea of something real and to not let the opportunity slip.
So, we had no idea what we were doing but began working and telling the idea to anyone willing to listen.
that's such a clean example — the unlock wasn't the idea, it was your cofounder calling back with "so when are we doing this?" — that one line turned another fun conversation into a commitment you couldn't quietly drop. the accountability of one specific person seems to do what months of solo motivation can't. did BrewChat stay "real" on its own after that, or did you need that kind of nudge to repeat? i'm mapping these breakthrough moments across a bunch of people right now — would you be up for a quick 15–20 min call to walk through the BrewChat story properly? small $25 thank-you for your time, and i'll send back the patterns i find. no pressure.
Happy to chat! If you go on BrewChat.co you will be able to find and book me right in the platform!
I have a Trello list called projects. When a "brilliant" idea comes to my mind, I add a card to this list. Some ideas I turn into projects, and some of them are too complicated or not interesting enough to start building. The main reason I don't start some projects is that I don't know how to monetize them, so I return to them from time to time to rethink options.
"Don't know how to monetize" is a category I hadn't framed in the post — most people I talk to stop at "can I build it" before they even get to "should anyone pay for it." Yours sounds like the inverse — execution is solvable, but the path from working thing to revenue is the unsticker.
Curious — of the ones you DID turn into projects, was there a specific monetization signal that made you commit (someone offered to pay, you tried something similar before, etc.), or did you commit anyway and figure it out later? The decision logic between "stays on the Trello card" vs "becomes a project" sounds like it might be the actual research question here.
The only signal I consider is that I would buy it myself. My projects are small ones, mostly Google Chrome extensions or Trello power-ups, which I create mainly for myself.
One more curiosity if you have a moment: was there ever a Trello card where you DID want it yourself, but it still stayed on the card? If yes — what was the actual block that one time (skill gap, time, doubt about ROI even for personal use)? Trying to figure out if "I'd buy it" is a sufficient signal or if there's still a second filter underneath.
Just looked through the list; there are some items I could characterize as "too much hassle" and "I'm not interested in this solution rn." Also, there are some "technically impossible" things.
"too much hassle" is the category i'm most curious about — it's the closest to the block i'm trying to map. "not interested rn" is honest, "technically impossible" is real, but "too much hassle" lives in this weird middle ground where you actually want it but the cost-of-starting outweighs the cost-of-not-having-it.
if you can, pick one specific card from that bucket — what was the thing, and what specifically made it feel like hassle? was it the unknowns at the start (don't know which tool, which stack), the projected total time, or something that happened the moment you actually sat down to try? asking because "hassle" usually breaks down into 2-3 distinct sub-blocks once you press on it.
For example, I wanted to create a tech support agent that has access to SaaS databases, logs, etc., so it could provide L2 technical support to customers. It would indeed be too much hassle, as it requires testing on real SaaS infrastructure, which I don't have access to. btw i wanted to create it before agents were introduced.