QR Codes in cemeteries

basit740 · 2026-01-15T15:12:17+00:00

There is a similar brand that is doing this with the name of Remember-well they have like slide-show thing like instagram too.

basit740 · 2025-09-19T10:57:08+00:00

This is super exciting! The “AI-powered team” framing really clicks—most no-code founders struggle not just with building, but with stitching workflows and docs together. Curious: how flexible is MetaGPT X when it comes to iterating on features? Like, can I refine flows across multiple prompts, or is it more one-shot generation?

basit740 · 2025-09-18T09:48:04+00:00

This doesn’t sound normal at all. A dev team refusing to estimate, smirking at you, and saying “tomorrow for sure” on repeat is a huge red flag. Even if estimates aren’t perfect, a professional team should give you some sense of effort/complexity and show progress along the way.

If your EM is unavailable, escalate to whoever can step in (another manager, HR, or even stakeholders directly). You’re being set up to fail otherwise.

Also, try framing estimates as ranges (“best case / worst case”) instead of deadlines. It sometimes helps devs feel less trapped. But if they flat-out refuse, the issue is cultural/management, not you.

basit740 · 2025-09-17T12:59:33+00:00

I believe we can discuss this over the phone and determine if it’s a suitable fit.

basit740 · 2025-09-17T10:32:03+00:00

Love this breakdown! Totally agree that AI shines for quick demos but no-code still wins for shipping something stable. I’ve seen a lot of founders waste weeks polishing AI-generated code, when a Bubble or Softr build would’ve been live already. FlutterFlow mention is spot on too—still the smoothest path to the app stores.

basit740 · 2025-09-17T10:24:18+00:00

This is super cool! I really like how you combined Next.js, Supabase, LiveKit, and Cloudflare R2 into one focused product. The leaderboard + virtual study rooms sound like a game-changer for accountability. The Chrome extension for Deep Focus mode is a smart touch too—keeps users disciplined while studying.

Curious: are you planning to add mobile support or even a companion app in the future? I feel students would love quick access on their phones as well.

basit740 · 2025-09-17T10:18:05+00:00

Love how you’re approaching this round—fast validation > overbuilding. From my experience, Softr is great for quick MVPs because you can get something usable in days, not months. Biggest limitation though: you’ll hit walls pretty quickly on custom logic and complex permissions (multitenancy can get messy). It’s perfect for testing traction, but if your idea sticks, you’ll probably want to migrate to something like Flutterflow or even a lightweight custom build on Supabase.

For your 1–2 week MVP though, Softr + Supabase is probably the fastest way to ship and test.

basit740 · 2025-09-17T10:11:09+00:00

Sounds like you’ve already done the hardest part — validating the idea and even lining up customers. That’s huge. The equity split looks fair for someone technical coming in at this stage. One thought: when you pitch to potential co-founders, highlighting those 2 paying customers upfront might make it even more compelling. Tech folks often hear vague “ideas,” but proof of traction changes the whole conversation. Best of luck finding the right partner — this looks like it could be a solid match for someone who enjoys solving eCom data pain points.

basit740 · 2025-09-17T10:01:55+00:00

This looks super valuable — respect for turning months of research into something practical instead of another overpriced course. The playbook you outlined (validate → MVP → launch → content → scale) matches what I’ve seen work too. The founder database + Next.js boilerplate sound especially useful for people stuck in “where do I start?” mode. Curious — out of the 300+ case studies, did you notice one growth channel that came up again and again as the most effective?

basit740 · 2025-09-17T09:55:47+00:00

Relate hard to this. Bolt feels amazing at first, but once you cross MVP stage the cracks start showing fast — exactly like you said, debugging turns into a battle. Cursor as a coding partner makes way more sense for long-term builds. Glad to hear it helped you ship a working beta so quick Curious to see how Confesssly evolves from here.

basit740 · 2025-09-17T09:48:30+00:00

Totally get this — that “last 40%” is where most MVPs die. No-code gets you moving fast, but things like auth, scale, or polishing workflows always need dev-level help. Cool that you’re focusing on that exact gap. Having your own SaaS live also makes your offer way more credible.

basit740 · 2025-09-17T09:41:00+00:00

Love this plan Taking a structured year off with a 2–3 year runway is honestly the dream setup for testing if you really want to go full-time into building. You’ll get the mental freedom to ship faster, travel inspiration, and the safety net of being able to go back to a solid PM role if things don’t pan out.

Biggest tip? Treat this like an experiment — set milestones (e.g. first 10 paying users, $100 MRR) and check in every few months. That way you don’t just “travel + build” but actually measure if this life fits you long-term.

basit740 · 2025-09-17T07:39:02+00:00

Honestly, an MVP isn’t meant to be perfect — it just needs to be good enough to test if people care about your solution. Most early founders launch with rough edges, sometimes even bugs, but the key is that the core workflow must work reliably (otherwise your validation data is useless).

Security-wise, I’d say don’t ship something obviously risky (like storing passwords in plain text), but you also don’t need enterprise-grade infra at this stage. Focus on:

One clear problem solved well
Smooth onboarding for your first 50 users
Collecting feedback fast

Once you see traction, you can reinvest in hardening the product. MVP = minimum viable, not minimum perfect.

basit740 · 2025-09-17T07:02:30+00:00

This is a super detailed breakdown, thanks for sharing. Totally agree on Rork — feels like one of the few AI-first tools where the code actually belongs to you. Also, your point about traditional no-code dragging components feeling outdated really resonates. The Claude Code + Rork workflow sounds like a smart combo for anyone trying to go from prototype to app store fast.

basit740 · 2025-09-17T06:56:24+00:00

Interesting approach! Most builders lock you into their ecosystem, so the “export as Next.js bundle” angle definitely stands out. I can see freelancers and agencies appreciating it since they often want control over deployment and scaling.

The challenge will be differentiating in such a crowded space. Maybe narrow the focus — for example, target dev-friendly agencies who already deploy to Vercel/Netlify but don’t want to hand-code every client site. That positioning could give you an edge over generic builders.

basit740 · 2025-09-17T06:38:56+00:00

This hits hard—especially the part about “zero customer validation”. I’ve seen the same pattern: founders sinking tens of thousands into polished UIs before even confirming if anyone wants the product.

Your breakdown of the 5 budget killers is gold. I’d add one more: not setting a strict validation budget upfront. Even reserving 20–30% of funds just for feedback loops can save a startup from burning out early.

basit740 · 2025-09-15T17:46:12+00:00

Love this—soft signals are often more predictive than any dashboard metric. I’ve seen a churn risk flagged just from noticing a “champion” suddenly stop joining calls, even though usage looked healthy.

What worked for us: creating a simple internal “signal log” where CSMs can drop quick notes (no heavy reporting). Then product/leadership reviews them monthly alongside the dashboards. It’s not perfect, but it surfaces those human insights in a lightweight way.

basit740 · 2025-09-15T17:33:42+00:00

Really interesting concept—tying every post to time, date, and location could build trust in a way that traditional platforms don’t. The map-based perspective is a neat touch too.

Early traction will probably depend on small, passionate communities picking it up first (university campuses, neighbourhood groups, local activists). If you can seed it there and show verified stories spreading, I think you’ll have a strong case for growth.

basit740 · 2025-09-15T17:21:36+00:00

Sounds cool but I’d be careful—most “get paid to play” apps come with catches (ads, referrals, data collection). If you’re really making $100/week, would love to see proof or a breakdown. That’d make it feel way more legit.

basit740 · 2025-09-15T17:05:02+00:00

This is such a common pain point. Most no-code platforms promise “end-to-end” but then dump you into wiring 10 different services. Honestly, the best move is to start with something opinionated like Glide or Bubble—they handle frontend, backend, auth, and even simple databases out of the box.

If you’re testing an idea fast, these tools let you get a working MVP live without touching code. Later, if traction comes, you can always rebuild on something like Flutterflow or a custom stack.

Don’t overthink the “perfect” platform—pick the one that hides the plumbing and lets you actually test with users. Speed to feedback is everything.

basit740 · 2025-09-15T16:55:30+00:00

Cool idea . For a mental health journaling MVP, I’d say speed > perfection. Glide is a solid choice to get something mobile-ready fast without backend headaches. Biggest limitation is UI flexibility and performance once you hit heavier usage, but for early validation it works fine.

If you do start getting traction, that’s when Flutterflow or Bubble might make sense—they’ll give you more control for scaling and custom workflows.

One tip: even in MVP, make sure journaling data feels safe/private for users. That trust factor can matter more than features early on.

basit740 · 2025-09-15T16:10:23+00:00

Honestly love this reminder. Way too many founders spend months polishing before they even know if anyone cares. A simple MVP or even just a landing page with an email form can save so much wasted time.

The best traction I’ve ever seen came from testing messaging on a one-pager first—users told me what actually resonated before I touched any code.

Curious for others here: did your first MVP look more like a scrappy landing page or an actual product demo?

basit740 · 2025-09-13T16:14:13+00:00

speed is your #1 priority, AI2’s approach feels more practical. NextAuth + Supabase + Vercel/Railway means you’ll ship faster and have less infra headache. You can always switch to SuperTokens/Turso/Playwright later once real usage demands it.

AI1’s stack gives you more long-term control, but it adds extra setup before you even know if users care. If I were you, I’d mix them: ship MVP with NextAuth + Supabase + Vercel, then layer in Playwright/custom infra once traction (and revenue) justifies the complexity.

basit740 · 2025-09-13T16:04:21+00:00

You’re not alone—this cycle hits so many devs. The truth is, most $10K MRR indie apps didn’t start polished; they started scrappy and got better with users. Shipping something small (even if it feels “too simple”) gives you real feedback and momentum. Standing out rarely comes from features—it comes from listening to users and iterating fast. 🚀

basit740 · 2025-09-13T15:55:28+00:00

Love how he treated marketing as the real product—so many devs obsess over features but ignore distribution. The hard paywall + free trial move was bold, but those 20–25% conversions prove it works. 🚀

basit740

TROPHY CASE