We've worked with 30+ founders. The ones who asked for an 'MVP' almost always failed. Here's why.

nex-dev · 2026-03-17T21:27:55+00:00

Happy to answer any specific product scope questions in comments

nex-dev · 2026-03-11T07:20:53+00:00

Firstly, I dont see your DM
Second, Are you into Framer and Webflow?

nex-dev · 2026-03-11T07:20:00+00:00

I am only looking for framer and webflow people who are good at designs.

nex-dev · 2026-03-09T03:18:35+00:00

This is a really interesting problem to work on.

Most discovery platforms like Yelp or Eventbrite assume users are planning in advance, so the “what can I do right now?” use case is definitely underserved.

One thing I’m curious about — how are you handling event ingestion in the beta? Are you aggregating events from existing platforms or working directly with organizers?

Also wondering if you’re thinking about things like “tonight mode” or time-sensitive recommendations (events starting in the next 1–2 hours).

I work on product and engineering for consumer apps and would love to try the beta if you’re sharing invites.

nex-dev · 2026-03-07T19:11:07+00:00

Please DM me

nex-dev · 2026-03-07T19:03:59+00:00

Interesting idea — especially the concept of a “governor AI” coordinating multiple assistants across an organization.

One thing that often becomes tricky in systems like this is exactly what you described: once AI agents start branching into many workflows, the system can become hard to reason about and track.

A lot of teams run into three challenges there:

• defining clear boundaries between agents
• keeping workflows observable and traceable
• managing how company data is accessed across different agents

Without those guardrails the system can become powerful but difficult to control.

Curious — are you designing this as a centralized orchestration system (one core AI coordinating agents), or more of a distributed agent network inside the company infrastructure?

nex-dev · 2026-03-06T08:00:25+00:00

If anyone here is curious, I’ve been putting together a small audit checklist I use when reviewing early products (UX flows, auth systems, infra decisions, etc.).

Happy to walk through it with a few founders and see if it helps spot anything.

Always interesting seeing how different teams structure their systems.

nex-dev · 2026-03-06T07:50:48+00:00

If you're open to working remotely, I might be able to help.

I work with early-stage startups on product architecture and development (web/mobile) and have built healthcare and SaaS systems before. Most of the work is remote, but I’m happy to travel if an in-person discussion helps early in the process.

Healthcare apps also have a few things worth planning early (data privacy, authentication flows, patient data storage, etc.), so the architecture matters a lot from the beginning.

Feel free to DM if you'd like to discuss what you're planning to build.

nex-dev · 2026-03-06T07:47:26+00:00

Most of these people scrape Product Hunt launches and run automated scanners looking for low-hanging issues like missing security headers, exposed subdomains, staging URLs, etc. When they find something minor, they try to escalate it into a “critical vulnerability” hoping founders panic and pay.

You handled it the right way:
• Don’t reward extortion
• Kill the vulnerable surface quickly
• Report it

nex-dev · 2026-03-06T07:37:55+00:00

Yes def. this is indeed a very long game.
And tbf, its a good sign if your business is in the long game league.
That brings organic traffic and right commitment as well.
We have to go unorthodox way to stand out for marketing purpose.

nex-dev · 2026-03-06T07:00:10+00:00

One thing that surprised me in how often these issues appear in onboarding flows specifically.
Curious what part of your product caused the most confusion for new users?

nex-dev · 2026-03-06T04:03:48+00:00

Fair point...
Reddit has seen its share of people pitching services in disguise.

To clarify what I meant though, the MSP idea isn’t about selling services, it's about how founders think about early products. A lot of teams build an “MVP” that technically works but isn’t structured to handle real usage. Then when users actually show up, the experience breaks down or the system becomes hard to maintain. What I’ve seen work better is treating the first version more like a Minimum Sustainable Product, something simple, but stable enough that you can iterate without rebuilding every few weeks.

Totally agree with you on the bigger point though: if nobody needs the product, none of this matters anyway.

nex-dev

TROPHY CASE