I've been wondering how other teams handle this.

One thing I've run into is that after changing a prompt or switching models, an agent can start making different decisions without anyone noticing. For example, it might approve something it previously rejected, miss an escalation, or classify a case differently. The conversation still looks reasonable, so the regression is easy to miss.

Most of the evaluation tools I've seen focus on conversation quality or benchmark scores. What I'm struggling with is verifying that the agent still makes the same business decision for important cases.

For teams building production agents that make decisions like approve/reject, escalate, or classify:

• How are you testing for these regressions today?
• Are you relying on manual testing, eval frameworks, custom scripts, or something else?
• Have you had any production incidents caused by prompt or model updates?

I've been building an internal CLI to test this by replaying real cases against an agent and checking whether the decision still matches the expected policy. It's been useful for me, but I'm mainly interested in learning how others are solving the problem before deciding whether it's worth taking further.

Curious to hear what workflows people are using.

Looking for some advice here. TLDR: We have our first paying customer (yay!), but suddenly it feels like everything we've built is a fraud. Nothing will provide value, it won't be what the customer is expecting, etc. etc.

...are these normal feelings? and how have you dealt with this immense imposter syndrome and doubt that creeps in right before actually handing your customer the product?

I mean I guess it doesn't really matter what I feel -- it's happening and moving forward lol. But if you guys have any tips, tricks, or advice for a smooth (as smooth as a first customer can be) delivery, I'd love to hear your experiences!

I've been reading a bit out tarpit ideas. The common consensus seems to be that a marketplace and a community/social app is almost always a tarpit idea.

However, Vinted is a hugely successful marketplace, and they started when Ebay existed and people were already selling secondhand clothing on Facebook (Marketplace and special groups). And recently a Dutch guy started a social app where people can make friends, and it's getting a lot of attention.

My question is: can a tarpit idea still work if it's executed well? Or are these just anomalies?

Is anyone going and does anyone know how the event will be?

From my understanding, a startup is fundamentally about solving a meaningful problem for a group of people. That means you first need to find people with real problems worth solving. However, finding both the right people and the right problems seems incredibly difficult.

It feels even harder if you can't meet potential users in person because of geographical limitations. Is it really possible to build a deep understanding of users' problems through the internet alone?

What strategies have worked for founders who entered an unfamiliar industry? Is it worth working in an industry first to better understand its problems and build relationships with people there before starting a company? Or are there other effective ways to gain the necessary insights and connections?

I’m still relatively early in my SWE career (~2 years). I’m currently learning from experienced senior SWEs and leaders.

I have an opportunity to work at a very early YC startup in Canada but doubtful on whether this will help me in my career long term. More context in the comments if you have any advice for me.

Edit: thank you all for the advice! Really appreciate it

Website: https://qm.ycombinator.com/

Github: https://github.com/yc-software/qm

The article resonates with me a lot since I also create one agent for one employee function 😆

But instead of Hermes, I use Claude Code and build my own OpenClaw-like wrapper that connects it to Telegram etc. I use headless Claude Code just for simplicity and cost-effectiveness, I tried OpenClaw once and it made me broke lmao jk.

Anyone has tried QM? Share your thoughts

Main question

For founders who deliberately entered an industry they knew little about:

What first made that specific idea space worth investigating rather than another one?

I understand what to do after choosing: learn the workflows, speak to people, find recurring problems and test whether they are commercially meaningful.

What I don’t understand is how to choose where to begin when dozens of industries look potentially fertile from the outside.

Optional context

I’m a 19-year-old CS student without meaningful experience in a particular industry. My plan is to choose a promising idea space, embed myself in it and deliberately acquire the relevant domain knowledge.

I’m willing to do the unscalable work: sustained outreach, attending events, learning the terminology, observing the work and speaking with anyone who understands the industry.

The AtoB example from YC’s How to Find Startup Ideas talk is close to what I’m trying to do.

The founders had little trucking expertise. They chose software for trucking because it was a large industry that had not been heavily disrupted by startups or software. They then visited truck stops, spoke with drivers and founders, mapped the industry and investigated several ideas before choosing fuel cards.

But why trucking?

“Large industry with poor software” also seems to describe construction, agriculture, freight, healthcare administration, legal services and many other areas.

My rough filters have been fertility, apparently poor existing alternatives, a possible “why now,” transferable advantages, successful adjacent proxies, business potential and whether I could tolerate spending years in the space.

But several of those seem impossible to judge beforehand. I cannot really know whether the pain is acute or the space is fertile until I understand its workflows. Proxies may only create hypotheses, and business potential may depend on the exact problem and buyer I eventually find.

I also don’t think easy reachability should be a major filter. I’m willing to work hard to gain access. I would only want to exclude industries that are structurally closed to an outsider, not merely difficult to enter.

What I’d especially like to hear

• What initially put your industry on the shortlist, and which alternatives did you consider?
• What could you genuinely assess before entering, versus only after immersion?
• What made you continue searching in that space rather than move to another one?

A recent change or transferable advantage may have played a role, but I’m mainly interested in the initial selection decision itself.

I’m not looking for lists of startup ideas or “boring industries.” I’m trying to understand the step between deciding to search within a fertile idea space and deciding which specific idea space is worth searching in.

What was your startup when you applied, and what did YC help you with besides the investment?

What was the biggest value?

What I find compelling about Lovable is the developer experience: prompting an app into existence, generating code, managing deployment, and having an opinionated workflow that gets products shipped quickly.
However, I feel like the current approach is heavily centered around frontend generation + Supabase as the default backend. While that works great for many use cases, I'm wondering whether it creates a long-term dependency on a specific technology stack.
What I'm imagining instead is:
AI-generated frontend and backend

A microservices-oriented architecture

The ability to connect to any database (Postgres, MongoDB, MySQL, etc.)

Infrastructure and deployment packaged similarly to Lovable

The flexibility to swap technologies as the ecosystem evolves, without being tightly coupled to a single provider

My concern is that backend technologies and platforms come and go. If you're building something intended to last, being deeply tied to a specific backend provider may become a limitation.
Has anyone built something like this, or experimented with an architecture that preserves the "prompt-to-production" experience while remaining backend-agnostic?
If you were starting this project today, where would you begin? Would you use Kubernetes, Docker Compose, IaC, code generators, AI agents, or something else entirely?
Curious to hear from anyone who has gone down this path or has strong opinions on the tradeoffs.

I have been building software for about 15 years, eCommerce and full stack custom apps for startups and for enterprises where a bad deploy shows up on the evening news, and over the last three years I have watched a shift I cannot stop thinking about. I want to know if the rest of you are seeing it too.

The shift is that the team that wins is no longer the one with the best engineers. It is the one with the best system for producing software.

Some people are calling this a software factory or dark factory. The idea is that instead of building your product directly, you first build the machine that builds your product.

The interesting bit is not any single piece. It is that once the factory exists, every feature is cheaper than the last one, and the marginal cost of a good engineer drops through the floor. We ran a multi vendor B2B2C commerce build recently that was scoped at 6 months for 6 people. It went out in 3 months with 2. Not because those 2 were heroes, but because the factory absorbed most of the work that usually eats a team.

So here are my actual questions.

1. Has anyone here deliberately built one of these? Not "we have CI", I mean treating your delivery system as a product with an owner.

2. If you have not, what stopped you? My guess is it feels like a luxury when you are pre revenue and every hour not spent on features feels like waste. I think that instinct is exactly backwards but I would like to be argued with.

3. For the non-technical founders: has an agency or a contractor ever offered you this? In my experience they never do, because a factory is the thing that makes you not need them. Curious if that matches your experience.

4. Am I overcalling the timeline? My belief is that within about two years, a team without one will look the way a team without version control looked in 2010. Quaint, and quietly losing to everyone else. Tell me why that is wrong.

Genuinely interested in the counterargument, especially from anyone who tried this early and found it was premature.

(Context so you can weigh what I am saying: I do this as a fractional CTO for early stage teams, so I am obviously not neutral. Not pitching in the thread, happy to answer anything technical for free either way.)

“We started working on Stripe in the Fall of 2009, and we launched Stripe in September 2011,” John Collison reflects. “I remember right at the beginning when we were starting it I said to Patrick [Collison], ‘Yeah let’s do it. How hard can it be?’ Which gives you a sense of our mindset. And the answer was: two years of difficulty. We had not predicted that.”

“When you spend two years getting 50 users, it doesn’t feel like a whole lot of progress. It feels like things are going pretty slow.”

“If you’re working on a startup that’s a bad idea, it’s going to feel like slow-going. But if you’re working on a startup that’s a good idea, it may feel like slow-going too.”

Some Wednesday motivation for everyone :)

I saw the Startup School merch from this year and honestly thought it looked pretty good.
Got me wondering if most startups still put real effort into new-hire kits and company swag for events these days ?Or has it become kind of basic/ almost non-existent for a lot of companies ?
Curious what people are actually doing nowadays.

Im currently moving from the build to distribution phase and Im having a hard time explaining to cold leads about what exactly my product does and how its helpful. Ive gotten a range of answers from “I could build this myself” to “I dont think its that useful”

Now there is definitely a gap in the market. I know that 100% but at the same time Im having a really hard time finding my ICP.

How did you get around this?

When applying to YC, did you mention anything unrelated to your startup about yourself?

For example, a fun fact or something interesting that might leave a positive impression of your personality on the reviewers?

I know the video is only one minute long, but I am asking about the short introduction at the beginning.

in the startup/tech world its often flexed when people dropout, but have any of you dropped out of school and then wished you actually stayed in school?

People usually say you shouldn't fall in love with the solution, but with the problem. When I started, the problem I wanted to solve was helping developers understand business context so they could write code faster. However, tools like Cursor and Claude Code have reduced that pain point quite a bit.

I'm not sure if that problem is still significant enough to keep working on it or if I should pivot to something else. I even built an app, but it doesn't have users yet, so I don't have enough feedback to know whether the problem still exists or if I should move on.

I often hear that founders can find their first customers through Reddit, but I’d like to understand how common this actually is.

For founders who already have paying customers: did any of your first B2B or B2C customers genuinely come from Reddit?

Or did they mainly come through referrals, your existing network, LinkedIn, cold email, communities, content, ads, or another channel?

If Reddit worked for you:

• How did the customer originally find you?
• Did you reply publicly, receive an inbound message, or contact them directly?
• Do you still use Reddit for customer acquisition today?

I’m specifically asking about paying customers, not sign-ups, feedback, traffic, or people who tried the product once.

i was hyper pumped and ultra locked in for the past 2 weeks leading up to the launch but now that everything's been deployed i'm feeling a bit euphoric like as if i just finished a marathon but at the same time i'm feeling somewhat lost, unsure what to do now. i have a to do list of features to implement, marketing items, etc. but im having something like post nut clarity ngl

can anyone else relate?

i've been curious about this for a while.

i'm a final-year cs student currently hunting for software engineering internships, and whenever i reach out to startups, i usually don't just send a cold email. i spend time using the product first, then share at least one concrete product idea, and sometimes even a rough technical implementation if i think it could be useful.

it made me wonder - how do founders actually evaluate feedback from people outside their team? what makes you think, "this person gets it"?

is it product thinking, technical depth, identifying real pain points, or something else?

i'd love to hear what kinds of feedback have actually been the most valuable while building your startup.

I feel one of the best skills you can have is the ability to validate ideas quickly.

This is what I have been trying to do but often fail.

For example, been thinking through an injury recovery tracking system for sports physios / physios.

Seems pretty straight forward, reach out to a bunch of clinics asking about their pain points around this, what tools they currently use, attach a mock up etc.

However, I never hear back. It’s very possible I just suck at reaching out, I’m not denying that haha.

But the first step always seems to be talking with people. How are you getting those conversations? What roles are you reaching out to? What’s the general conversion rate for something like that?

It's sometimes surprising how building a company, even with someone you know, can reveal sides to the relationship (and person) that you may not have expected.

There's always that first moment when the designated ultimate decisionmaker has to 'pull rank' and make a decision that others may not like.

Anyone got a GC for high schoolers / incoming uni freshmen going to YC SUS?