u/Gallegos_Daniel

I'm building Meridian, and I noticed something: it's surprisingly hard to find founders who are genuinely deep in the fundraising grind — not just "building a startup," but actively pitching, negotiating term sheets, chasing warm intros.

I mean people who:

Are raising pre-seed or seed from VCs right now.
Talk about pitch decks, cap tables, and investor strategy like it's actually interesting.
Would rather get real feedback than another "great idea!" comment.
Are willing to help each other get to a signed term sheet.

My goal isn't to sell anything or build a paid community. Just a small, curated Discord of founders who are actively fundraising and want to share pitch feedback, VC intros, and keep each other accountable.

If that sounds like you, comment what you're raising for or DM me. If enough people are interested, I'll get you the invite.

I'm building Meridian, and I noticed something: it's surprisingly hard to find founders who are genuinely deep in the fundraising grind, not just "building a startup," but actively pitching, negotiating term sheets, chasing warm intros.

I mean people who:

Are raising pre-seed or seed from VCs right now.

Talk about pitch decks, cap tables, and investor strategy like it's actually interesting.

Would rather get real feedback than another "great idea!" comment.

Are willing to help each other get to a signed term sheet.

My goal isn't to sell anything or build a paid community. Just a small, curated Discord of founders who are actively fundraising and want to share pitch feedback, VC intros, and keep each other accountable.

If that sounds like you, comment what you're raising for or DM me. If enough people are interested, I'll get you the invite.

I've been thinking about doing something similar for a while. Apparently, this is becoming pretty popular as a fixed or secondary income. I was working on my startup and saw a YouTube post that said CalBubby reached $80k MRR in 12 months, another example of this is Stella, which crossed $300k MRR in 2 months, reaching 12k customers.

There are ways to distribute these, with UGC you can test, or with Ads. AI told me that starting with $300–500 is a good starting point for testing ads. Another method I mentioned and that worked was rev share + creators promoting it.The niche usually seems easy, although after researching the market a little, it seems pretty saturated with vibecoded apps.

I'm doing this as a side project. My idea was to start in trading/crypto, although they're pretty messed up legally. AI told me that I need a permit to run ads, and there are also the typical legal problems with trading. Although I'm still just exploring.

So, in your opinion: is this a good business to experiment with? How much capital do you think you would need to start, and how would you do it?

There isn't just one type of investor. There are two:

Venture scout → Analyzes your startup and helps you prep for the fund's process — basically filters startups and expands the fund's network in places they don't usually reach directly.

Investor → The one who actually writes the check and evaluates you directly.

I learned this the hard way while raising interest for Synathic. (Verification layer for AI Agents) Someone reached out, asked sharp questions, seemed genuinely engaged, I assumed I was talking to a potential investor. Turns out they were a scout. Not a bad thing at all, just a different conversation than I thought I was having.

What I'd tell earlier-me: ask directly, early, "are you evaluating this for your own check, or passing it along to a fund?" Saves both sides time, and changes what you send them (a scout wants your sharpest one-pager to forward; an investor wants the full picture).

Curious, anyone else mixed these up early on?

I've been thinking about this for a while, and I want to run an experiment.

The idea: a tight-knit community for founders who are actively raising — or preparing to raise — venture capital.

Not another generic "founder" Discord.

Think of it as the opposite of Indie Hackers: instead of optimizing for $1K MRR and bootstrapping forever, we obsess over term sheets, warm intros, pitch narratives, investor strategy, and getting from the first meeting to a signed term sheet.

What I want to build:

• A small, curated community — first 50–100 people max

• Weekly pitch roasts

• Term sheet / deal breakdowns

• Warm-intro matching

• Fundraising strategy discussions

• Radical candor — no "great hustle!" comments, just useful feedback

• Eventually: investor AMAs, office hours, founder dinners, etc.

The goal isn't to create another noisy startup Discord.

I want to build a community where you can drop your pitch, fundraising strategy, or investor situation and get genuinely useful feedback from people who understand the game.

Why I'm doing this:

I'm a founder myself, and I've noticed how fragmented the fundraising ecosystem is for early-stage founders.

I also want to build something that creates genuine value and eventually becomes a recognized name in the fundraising space.

This isn't about building a huge Discord just for the sake of having 10,000 members. I'd rather have 100 people who actually know each other and actively help each other.

I'm looking for a co-organizer who:

• Has raised VC before OR has strong access to the investor ecosystem

• Actually enjoys community building

• Can commit to the first 90 days of recruitment and running weekly rituals

• Is comfortable building in public and experimenting

This doesn't need to start as a formal company. I want to find someone who genuinely wants to build this with me and see where it goes.

If this sounds interesting, DM me with:

1. One sentence about your fundraising/community experience

2. One weekly ritual you'd want to run

3. Your timezone

Let's see if this idea has legs.

Building Synathic — verifying that AI agents actually did what they claimed (silent failures: agent says "done," DB row is missing). Validated the problem with 40+ devs, no funding, no cofounder yet, MVP scoped for September.

Not looking for equity/advisor formality right now — genuinely just want to talk to someone who's shipped production systems in this space (observability, policy engines, agent infra, distributed systems) and is willing to give feedback occasionally. Even one call would help.

I'm 15, based in El Salvador, doing this solo for now. Happy to share the architecture doc, what I've learned from customer discovery, or just trade war stories if you've built something similar.

Discord: itzdanigg (works better than Reddit DMs for me)

I've been running a LangGraph agent in staging that handles customer onboarding. Last week it reported "account created successfully," the tool returned 200, logs were clean.

I only found out the row was missing because I manually checked the DB 2 days later.

Not a prompt failure. Not an API error. The agent believed it succeeded. The tool reported success. But the side effect never happened.

Since then I've been paranoid about every 200 response. I've started adding manual DB checks after critical runs, but it feels like I'm duct-taping something that should be infrastructure.

For those running agents in production: do you verify the actual database state after your agent runs? Or do you trust the tool's response code and the agent's "success" message?

And if you've been burned by this before, how did you catch it?

Not selling anything. Just trying to figure out if I'm solving my own problem or if this is a shared gap.

Hey everyone,

I'm researching how developers and teams are handling AI agents in production.

A question I keep thinking about:

When an AI agent fails, how long does it usually take you to understand what actually happened?

For example:

\- Was it the prompt?

\- The model?

\- A tool/API failure?

\- Bad context retrieval?

\- A workflow/handoff issue?

\- Something else?

How do you debug these issues today?

Are you using tools like LangSmith, custom logging, dashboards, or just digging through logs?

I'm curious about the real workflow:

1. An agent fails.

2. What is the first thing you check?

3. How long does finding the root cause usually take?

4. What part is the most frustrating?

Not selling anything, just trying to understand how people are dealing with this.

Hey everyone,

I'm researching how developers and teams are handling AI agents in production.

A question I keep thinking about:

When an AI agent fails, how long does it usually take you to understand what actually happened?

For example:

- Was it the prompt?

- The model?

- A tool/API failure?

- Bad context retrieval?

- A workflow/handoff issue?

- Something else?

How do you debug these issues today?

Are you using tools like LangSmith, custom logging, dashboards, or just digging through logs?

I'm curious about the real workflow:

1. An agent fails.

2. What is the first thing you check?

3. How long does finding the root cause usually take?

4. What part is the most frustrating?

Not selling anything, just trying to understand how people are dealing with this.

I've been talking to founders about their accelerator application process. Common complaints:

Finding deadlines scattered across Twitter, newsletters, and program sites

Not knowing what "ready" looks like for a given program

Losing track of which version of their deck they submitted where

I'm thinking of building something that centralizes deadlines, breaks down prep by program, and tracks application status.

But before I write code: what's the problem with this idea? What would you actually use vs. what sounds nice in theory?

Brutal honesty appreciated. What should I NOT build?

Is anyone actually orchestrating multi-agent workflows well, or are we all duct-taping?

Every demo shows "Agent A talks to Agent B, magic happens."

In production, it's:

\- Agent A fails silently

\- Agent B waits forever

\- Agent C retries 47 times and burns $50

\- No one knows the workflow is broken until a human checks

Are people actually running reliable multi-agent orchestration in production? Or is the state of the art still "hope and monitor"?

If you've solved this, what does your stack look like? If you haven't, what's the biggest blocker?

Every demo shows "Agent A talks to Agent B, magic happens."

In production, it's:

\- Agent A fails silently

\- Agent B waits forever

\- Agent C retries 47 times and burns $50

\- No one knows the workflow is broken until a human checks

Are people actually running reliable multi-agent orchestration in production? Or is the state of the art still "hope and monitor"?

If you've solved this, what does your stack look like? If you haven't, what's the biggest blocker?

Every demo shows "Agent A talks to Agent B, magic happens."

In production, it's:

Agent A fails silently

Agent B waits forever

Agent C retries 47 times and burns $50

No one knows the workflow is broken until a human checks

Are people actually running reliable multi-agent orchestration in production? Or is the state of the art still "hope and monitor"?

If you've solved this, what does your stack look like? If you haven't, what's the biggest blocker?

Every demo shows "Agent A talks to Agent B, magic happens."

In production, it's:

- Agent A fails silently

- Agent B waits forever

- Agent C retries 47 times and burns $50

- No one knows the workflow is broken until a human checks

Are people actually running reliable multi-agent orchestration in production? Or is the state of the art still "hope and monitor"?

If you've solved this, what does your stack look like? If you haven't, what's the biggest blocker?

I've been talking to more people who are running multiple AI agents (coding, customer support, lead qualification, research, content, etc.), and one thing that keeps coming up is that failures often go unnoticed until they've already caused real damage.

I'm curious what the worst case you've experienced was.

Was it a prompt issue? An API failure? A workflow that silently stopped? An agent doing the wrong thing without anyone noticing?

How long did it take you to discover it, and what did you change afterward to prevent it from happening again?

I'd love to hear real stories instead of theoretical problems.

Not promoting anything, just looking for honest feedback.

I'm validating a startup that helps founders discover and keep track of opportunities like accelerators, grants, competitions, and fellowships.

Instead of waiting until the app is finished, I'm thinking about building an audience first.

The idea is:

X → Discord community → Waitlist → Mobile app

The Discord wouldn't just be a placeholder. I'd actively share relevant startup opportunities, answer questions, collect feedback, and learn what founders actually need before building more features.

The goal is to make the community valuable on its own while the product is still being built.

Do you think this is a good approach, or would you rather wait until the app exists?

I'd love honest criticism, especially if you think there's a flaw in this funnel.

Not promoting anything, just looking for honest feedback.

I'm validating a startup that helps founders discover and keep track of opportunities like accelerators, grants, competitions, and fellowships.

Instead of waiting until the app is finished, I'm thinking about building an audience first.

The idea is:

X → Discord community → Waitlist → Mobile app

The Discord wouldn't just be a placeholder. I'd actively share relevant startup opportunities, answer questions, collect feedback, and learn what founders actually need before building more features.

The goal is to make the community valuable on its own while the product is still being built.

Do you think this is a good approach, or would you rather wait until the app exists?

I'd love honest criticism, especially if you think there's a flaw in this funnel.

Do you think creating content (YouTube videos, Shorts, tutorials, educational content, etc.) is necessary for a SaaS to grow?

For founders who have built SaaS products:

Did content help you get your first users?

Was it worth the time investment compared to other growth channels?

Can a SaaS grow successfully without creating content?

I'm interested in learning how different founders approached this.

Not promoting anything, just looking for experiences and discussion.

I'm curious how other founders approach user acquisition before having a finished product.

I'm currently building a SaaS and I'm trying to focus on providing value before launch, rather than just asking people to wait for the MVP.

For those who have launched before:

How did you find your first users?

Did you build a community, newsletter, waitlist, or something else?

What worked and what completely failed?

Not promoting anything, just trying to learn from other founders.

Hi everyone!

I'm a young founder currently building my first SaaS, and before continuing development I'd like to validate whether this problem is real for other people.

I realized that I often found grants, accelerators, competitions and startup programs too late, forgot deadlines, or had dozens of links scattered across different websites and bookmarks.

I'm exploring a product that helps people discover opportunities, organize them, track deadlines and manage applications in one place.

I'd love to hear about your experience:

How do you currently find startup opportunities?

Have you ever missed an opportunity because you found it too late or forgot about it?

What's the most frustrating part of the process?

If you could improve one thing, what would it be?

I'm not promoting anything and I don't even have a public launch yet. I'm simply trying to understand whether I'm solving a real problem before investing more time into development.

Thanks!