u/Wise_Attorney4757

I used to work customer support for a small software company. We were measured almost entirely on how many tickets we closed each day. Customer satisfaction and actually solving the issue were supposedly important too, but the numbers on the dashboard always seemed to matter more.

One Monday, management announced a new rule.

No ticket was allowed to stay open overnight unless a supervisor approved it. They said seeing old tickets on the board "looked bad" during executive meetings.

I asked what we should do with the complicated issues that required the development team. Sometimes we'd be waiting two or three days for an answer.

The response was, "Close the ticket. If the customer still needs help, they can open a new one."

I confirmed that was the expectation, and my manager said yes.

So that's exactly what I did.

Every issue that depended on another team got a polite message explaining that the current request was being closed and that they should contact us again if they still needed assistance after the developers reviewed the problem.

By the end of the week, my numbers looked fantastic. I had the highest ticket closure rate on the team, and the dashboard had almost no old tickets left.

The following week, support volume suddenly exploded.

Customers were opening second, third, and sometimes fourth tickets for the exact same issue because each previous one had been closed before anyone could actually fix it. Reporting became useless because one problem now appeared as multiple unrelated cases. The developers were confused because they kept getting duplicate reports from different ticket numbers.

Management called a meeting to figure out why ticket volume had nearly doubled.

I reminded them that I had simply followed the new policy exactly as instructed.

After a rather awkward silence, the rule was quietly changed. Tickets waiting on another department could stay open again, provided we added an internal note explaining why.

My ticket closure rate dropped back to normal.

Strangely enough, so did the number of support tickets.

One thing I underestimated when working on an apparel business was how much of the risk sits in operations, not the idea itself. Product and branding got all my attention early on, but sourcing and production quickly became the real bottleneck.

The hard part wasn’t just finding manufacturers, it was coordinating everything: sampling, quality expectations, timelines, payment risk, shipping. It felt like managing five separate businesses just to get one product made. For small founders without industry connections, that layer alone can kill momentum.

Recently I’ve been looking into models that try to solve this structurally rather than treating it as “just go find a factory.” One example I came across was Greige, which seems less like a marketplace and more like managed production infrastructure, helping take a clothing idea through sourcing, sampling, manufacturing, QC, and delivery.

What interested me wasn’t the fashion angle, but the business model itself. It feels like “manufacturing-as-a-service,” which got me thinking about whether this is a broader startup pattern: wrapping fragmented legacy industries in managed-service layers instead of pure software.

Some things I’ve been thinking about:

• Is this a scalable venture model, or just a service business packaged well?
• Do founders prefer full-stack operational partners, or direct supplier relationships once they scale?
• In messy industries like manufacturing, is execution support a stronger moat than software?

Curious what people here think, especially anyone building in marketplaces, vertical SaaS, or service-enabled software. Is this the kind of model you’d consider venture-backable, or does it stay consultancy with better branding?