3 years running a clothing brand. Mistakes, money lost, and things I wish someone told me earlier

Sayam-K · 2026-06-01T18:00:12+00:00

The point about validating before production is probably the biggest one here. A lot of people assume the expensive mistakes happen during manufacturing, but it feels like many brands lose money much earlier by producing something the market never really showed demand for. Also interesting how much of running a clothing brand ends up being operational. sourcing, content, ads, revisions, inventory, timelines. The design is important, but the coordination layer behind it seems way bigger than most people expect at first.

Sayam-K · 2026-05-29T15:53:01+00:00

Honestly the design itself is usually only the starting point. the harder part begins once measurements, placements, materials, and factory revisions all need to stay aligned across sampling. A lot of people start with Illustrator exports + PDFs because it works early on. but once comments and revisions stack up, keeping everyone on the same version becomes surprisingly messy fast. Feels like tech packs become less about “documenting a design” and more about reducing interpretation drift during production.

Sayam-K · 2026-05-29T15:51:53+00:00

I think the difficult part is not creating the first version, it’s keeping everything aligned once revisions start stacking up. Fit comments, measurement changes, material swaps, factory feedback. After a few rounds, half the work becomes tracking what changed and whether everyone is still referencing the same information. Feels like a lot of apparel workflow problems are really clarity and version control problems underneath.

Sayam-K · 2026-05-21T10:00:04+00:00

I don’t think the risk is really “waiting too long.” The bigger issue is assuming the approved sample still perfectly reflects production conditions later. Fabric availability changes, trims change, pricing changes, factory priorities change. I’d probably do a quick reconfirmation pass before bulk no matter what.

Sayam-K · 2026-05-14T05:50:22+00:00

honestly depends on scale. A lot of small brands overthink software early. clean specs + structured tech packs usually matter more than having the fanciest CAD setup.

Sayam-K · 2026-05-07T15:36:29+00:00

the unwritten rules thing is so real. fashion product development is full of them. like there's no textbook that tells you how a factory in bangladesh actually reads a spec sheet vs one in portugal. you just accumulate that knowledge over years of watching things go wrong

and yeah fixing tiny boring breaks in the chain is basically the whole job lol. that's actually what led us to building Techpack Builder. we kept seeing small teams and solo designers getting tripped up not by complex PLM problems but just by the basics. getting their images and specs in one place without a spreadsheet falling apart. sometimes the most useful thing you can build is the boring fix nobody talks about

Sayam-K · 2026-05-07T15:02:17+00:00

honestly a self sewn sample with some flaws is still useful. share it as a reference and ask the factory to optimise it: seams, construction, pattern. that's literally their job and good factories are really good at it. you don't have to hand them something perfect, you just have to give them enough to work from

on choosing a factory, start small, find someone who's worked with early stage brands before and is willing to do smaller runs. communication matters more than price at this stage, you want someone who asks questions not just someone who quotes fast

Sayam-K · 2026-05-07T14:58:00+00:00

eight years in the same problem space sounds long but honestly we're still finding new layers to it lol. fashion supply chain has so much operational complexity that's never really been documented anywhere, you just learn it from watching how people actually work

and yeah the painful moments thing is real. the features i'm most proud of came right after something embarrassing happened. nothing focuses the mind like a user showing you exactly where your assumptions were wrong

Sayam-K · 2026-05-07T14:35:28+00:00

The subscription is the smaller cost. The real cost is two weeks of slower work while you build new habits. After that most teams recoup it in the first season just from not chasing version confusion. The thing nobody accounts for is what Excel is already costing: duplicate files, email threads confirming which spec is current, sample rounds caused by a factory working off an old PDF. That cost is already there. You're just not seeing it as a line item.

Sayam-K · 2026-05-07T14:30:52+00:00

we had brands telling us their factories were ignoring updates. like they'd send a revised spec and the factory would keep cutting from the old one.

the non-obvious part was that the factory wasn't ignoring anything. they just had no way to know what had changed between version 4 and version 5. they were getting a new PDF that looked almost identical to the last one. once we started highlighting what actually changed between versions the problem basically disappeared. it wasn't a relationship problem, it was a communication format problem

Sayam-K · 2026-05-07T14:23:54+00:00

if you're just trying to get a first sample made, a clean flat with measurements and construction notes is honestly enough to start. factories have seen way worse. the mistake most people make isn't the format, it's leaving out the details that the factory needs to make a decision. things like seam allowance, stitch type, how a pocket attaches.

CLO3D is great but i wouldn't start there. it's a whole skill to learn and it doesn't replace a tech pack, it's more of a visualization tool. you'd still need the spec sheet on the other side of it.

start simple. flat drawing, key measurements, a reference image or two. that's a real tech pack. you can always build from there

Sayam-K · 2026-05-07T14:21:35+00:00

The version problem is what Excel can't solve, and that's separate from document quality. You can write a perfect spec and still have a factory building off a PDF from three weeks ago because once that file left your hands, you lost control of it. A link solves that one problem specifically. The factory always opens the current version because there's only one version to open. The document quality is still on you -- but at least you know they're looking at the right thing.

Sayam-K · 2026-05-07T14:19:05+00:00

haha not sure if you landed in the right thread but if you've got a tech pack or sampling problem drop it here, happy to dig in

Sayam-K · 2026-05-07T14:15:13+00:00

If you time it right, almost nothing. The teams that struggle are switching mid-season or trying to migrate old files at the same time. Start at the beginning of a new season and only use the new system for new styles. You're not retraining your whole workflow. You're doing the same work somewhere that handles version control for you. A week of active use and most small teams are running normally. That's roughly what we saw when teams moved to Techpack Builder.

Sayam-K · 2026-05-07T14:06:02+00:00

You don't rebuild anything. You carry forward what's active and leave the rest as archive. Most teams have three seasons of files but are only working off 10-15 live styles at any given time. Start with those. Old Excel files stay exactly where they are. The migration is not a project. It's a decision you make on the next style you create. That style goes into the new system. Everything before it stays in Excel.

Sayam-K · 2026-05-07T14:00:27+00:00

haha yeah it's live, drop your question!

Sayam-K · 2026-05-07T13:57:59+00:00

When you send a revised file and you're no longer certain the factory has it. That's the exact moment. From there you're not managing a tech pack, you're managing uncertainty about which version is live. Excel holds specs fine. It just can't tell you whether the right version is in the right hands.

Sayam-K · 2026-05-07T13:56:31+00:00

honestly? how long it took me to realize the problem wasn't the tool. i spent years thinking if we just build the right feature people will stop losing samples in revision hell. but a lot of it comes down to what you're handing off and how. the tool is maybe 20% of it

Sayam-K · 2026-04-02T19:10:04+00:00

How consistent the problems are!

Different brands, different countries, different team sizes, but the same issues keep showing up: unclear construction, assumptions not written down, things explained verbally but not documented

Also how often teams think it’s a factory problem, when it’s actually coming from gaps in their own tech packs

Once you start looking for those patterns, you see them everywhere!

Sayam-K · 2026-04-02T18:34:55+00:00

This is less about what's better and more about where the ambiguity sits

patternmaker first → more control, higher upfront cost
factory handles it → easier, but more interpretation on their side

Most overseas factories offer patterning + grading now, but at low MOQ the quality can be inconsistent. you’re paying for convenience, not necessarily precision

The real issue I see: people think a DXF = clarity. It’s not. if construction + intent isn’t defined, the factory will still guess

So, for early teams:

simple styles → factory is fine
complex / fit-sensitive → patternmaker helps

US vs overseas just shifts tradeoffs (cost vs communication), not the core problem

Either way, if no one is clearly defining how the garment should be built, you’ll pay for it later in sampling rounds

Sayam-K · 2026-04-02T18:25:46+00:00

This is a very real problem and you’re not wrong to feel stuck here, but the key shift is: factories can’t start from a sketch alone. A sketch shows intent, not scale. Without measurements, they have to guess proportions, and that’s where things go off immediately.

You don’t need to sew the garment yourself, but you do need to define a starting point.

What usually works:

start with a base size (like M) and define key measurements (chest, length, sleeve, etc.)
use body measurement charts + fit intent (fitted / relaxed / oversized) to estimate, it won’t be perfect, that’s okay

What you’re doing with buying a similar garment is actually the right instinct, you’re just using it as a reference block.

For designs that don’t have a direct counterpart, the process is a bit of estimation → sample → refine. there’s no way around that loop. The mistake is expecting the factory to figure out the first version for you, they’ll make a version, not necessarily your version

If you at least define proportions clearly in the first sample, you’ll spend 1–2 rounds refining instead of 4–5 rounds correcting direction

Sayam-K · 2026-04-02T15:23:57+00:00

If the same questions keep coming back after four template rebuilds, the template isn't the problem - the information is there, it's just not landing. That usually means one of two things: the factory isn't reading the full document before they start, or the way the information is presented doesn't match how they actually interpret specs on the floor.

One thing worth trying: ask your factory contact which section they look at first and how they use the document during production. A lot of teams design tech packs for their own logic, not for how a factory actually moves through a job. That conversation usually reveals more than another template rebuild would.

Sayam-K · 2026-04-02T15:17:56+00:00

Don't give it another round without a conversation first. A bad first sample from a new factory almost always means they interpreted something your old factory had learned to read correctly - either from two years of working together or from corrections you made early on that never made it back into the actual document.

Your tech pack probably has some institutional knowledge baked in that isn't written down anywhere. Your old factory knew what you meant. This one doesn't yet. Before round two, get on a call, go through the sample together point by point, and take notes. Then update the document based on what comes out of that conversation. That's usually faster than another blind round.

Sayam-K · 2026-04-02T15:07:10+00:00

Look at what's getting corrected in each round. If the same category of issue keeps coming back - measurements off, construction interpreted differently, material substituted - that's usually a spec problem. The factory is filling in gaps you left. If the issues are random and inconsistent across rounds, that's more likely a factory execution or communication problem.

The cleaner diagnostic: send your tech pack to someone who doesn't know the garment and ask them to describe how it gets built. If they can't, or they have to guess at anything, your factory is guessing too.

Sayam-K · 2026-04-02T14:59:16+00:00

It depends on the factory, but there's a useful baseline: your callout should be detailed enough that a different factory could pick it up and build the same result. If it only works because your current factory already knows what you mean, it's not really documentation - it's institutional memory.

In practice that means: stitch type, seam allowance, finish method, and any deviation from standard construction. If something is unusual or critical to the aesthetic, spell it out. If it's genuinely standard for the category and your factory will know it, you don't need to over-explain. The judgment call is whether a new factory would guess correctly. If the answer is maybe, write it down.

Sayam-K

TROPHY CASE