@MdrBwl

20 • Compound Context • Shit Post • Building Things

Joined September 2024
Pinned Tweet
since you all loved her male anatomy. here's i made Female anatomy using GPT 6 Astra with 3,004 modeled pieces.
since you guys loved the exploding tesla.. I used GPT-6 Astra to create a 3D website that pulls apart the male anatomy into 2,234 modeled pieces! we are in a renaissance of learning
15
32
7
374
48,857
It took me 2 years to grow from 0 to 150 followers. It took me 3 days to grow from 150 to 400 followers. Let's #connect and grow together 🚀
3
4
116
What's one thing about building a SaaS that you wish someone had told you earlier? Not the glamorous stuff. The frustrating, boring, unexpectedly difficult part nobody mentions in launch threads. Let's hear the lessons that only come from actually building.
3
3
115
Sometimes the hardest startup decision isn't what to build next. It's deciding what NOT to build. Every feature costs time. Every new direction divides attention. Every unnecessary improvement delays learning from customers. Focus is a product decision, too.
2
2
106
I just crossed 400 mark on X in just 3 days. Congratulate me!
1
64
Your MVP isn't supposed to prove that you can build software. It's supposed to help you learn whether people want the solution. Keep the scope small enough to launch quickly. Get feedback before you polish everything. You can improve a real product. You can't learn much from an unfinished one.
33
Indie hackers, when you find a competitor doing exactly what you planned to build, what's your first reaction? A. Abandon the idea B. Study what they're doing C. Find an underserved audience D. Build a better alternative I'm curious how other builders think about competition.
1
1
56
Spent 4 hours building a feature. Nobody noticed. Spent 20 minutes fixing a tiny bug. Suddenly everything works and I feel like I deserve a standing ovation. Software development is a weird way to experience happiness 😂
31
People visit your website but don't sign up. Before redesigning the entire landing page, ask: Do they understand the product? Is the value obvious? Is the next step clear? Do they trust you enough to try it? Don't guess at the problem. Investigate it.
40
Building in public isn't a performance where you pretend everything is going well. It's showing the actual process. The decisions you got wrong. The assumptions that failed. The things you're still figuring out. You don't need to look successful to be worth following.
2
130
Using AI to build a bad idea faster doesn't make it a good business. It just helps you reach the wrong destination sooner. Validate the problem first. Then use AI to reduce the time between learning what customers need and delivering it.
1
82
Imagine you have a working SaaS, zero customers and no marketing budget. You have 7 days to get your first paying user. What's your move? Direct outreach Content on X Relevant online communities Personal network I'd love to hear the reasoning behind your choice.
2
2
130
A hard truth about SaaS: You can build something technically impressive and still have no business. Because customers don't care how complicated your backend is. They care whether your product solves a problem worth paying to solve. Build for the outcome, not the applause.
1
2
81
What's the most underrated skill for an indie hacker? Coding gets you a product. Writing helps you explain it. Sales helps you get customers. But listening helps you figure out what to build in the first place. Which skill are you working on improving right now?
3
4
178
Sometimes you don't need another productivity system. You need to stop switching between 4 startup ideas and finish one thing. The next idea will always look exciting. But the boring work of getting your current idea in front of customers is where you learn what it's worth.
1
2
59
A useful exercise for anyone building a SaaS: Ask 5 potential customers to try your product without explaining how it works. Watch where they get stuck. Listen to the questions they ask. Their confusion might reveal what your next feature should actually be.
2
2
127
Your landing page shouldn't make people think: "This looks cool." It should make them think: "This solves my problem." Explain who it's for, what it does, and why it matters. Clarity beats clever copy when customers don't understand what you're selling.
2
63
AI has made building an MVP ridiculously accessible. But here's what I find interesting: If building becomes easier for everyone, how do you stand out? Better distribution. Deeper customer understanding. A sharper problem to solve. The code is only one piece of the puzzle.
2
63
If you could go back to the day you started your current SaaS, what would you do differently? Talk to customers sooner? Validate the idea first? Start marketing earlier? Build a smaller MVP? Your biggest mistake might save someone else months.
1
45
You don't need $10k MRR to have something valuable to share. Maybe you learned why your landing page wasn't converting. Maybe your first user misunderstood your product. Maybe you wasted a week building the wrong feature. Share the lesson. That's progress too.
3
49
Launching a SaaS is basically: Day 1: This is going to be huge. Day 2: Let's check the analytics. Day 3: Maybe analytics is broken. Day 4: Let's post about it on X. Day 5: Refresh analytics again 💀
2
111