From Sketch to Sample: The AI-Assisted Workflow
A walkthrough of how a mid-size apparel brand used Calico to take a new style from initial sketch to production-ready spec in under 48 hours.
The traditional path
Take a style from initial sketch to a production-ready specification in the traditional workflow, and you are looking at a process that typically consumes two to three weeks of calendar time — even when everyone is responsive, nothing is lost in translation, and the factory asks reasonable questions.
A designer hands off a sketch. The technical designer interprets it, makes construction decisions, and begins building a techpack — a process that, for a moderately complex style, takes a full day of focused work. The techpack goes to the factory with material requests. The factory comes back with questions. The technical designer answers them, revises the spec, and reissues. A sample is cut. Three to five weeks later, it arrives.
In most cases, it is not right. A measurement is off. A construction detail was misread. A material was substituted because the specified option wasn't available at the factory's supplier. Another round begins.
For a brand running 150 styles per season, this loop — repeated across every style, simultaneously — is not just slow. It is the primary reason why product creation calendars are structured the way they are. The timeline is built around the assumption that iteration takes time. But the assumption has never been tested against a different process.
The new workflow
A mid-size contemporary brand running a twelve-person product team set out to test that assumption. The question was specific: could a new style move from confirmed design intent to a production-ready specification — one a factory could cut a first sample from without asking clarifying questions — in under 48 hours?
The answer, using Calico's Tech Design product, was yes. But what made it work was not simply speed. It was the quality of the output at the end of those 48 hours.
The workflow starts with the designer uploading reference imagery — sketch, inspiration photo, and any existing material or construction references. Calico's Tech Design product interprets the design intent and generates a draft techpack: construction details, measurement table with grading, material callouts resolved to factory-readable specifications, care and compliance labeling, and a factory communication summary that surfaces the decisions the team needs to confirm before the document is issued.
The technical designer's role in this workflow shifts. Instead of building the techpack from scratch — a mechanical process that consumes most of the working day — they are reviewing, correcting, and approving a draft that is already 80 to 90 percent complete. Their expertise is applied to the decisions that require expertise: the construction calls that depend on seasonal direction, the fit choices that reflect brand standards, the material substitutions that require aesthetic judgment. The rest is handled.
What 48 hours actually looks like
Day one: design intent confirmed by noon. The technical designer works with the designer to align on the sketch, construction approach, and material direction. This conversation happens in Calico — references are uploaded, comments are attached to specific spec details, and the draft techpack begins generating in the background during the alignment meeting.
By end of day, the technical designer has reviewed the draft, made corrections on seven of the thirty-two spec points, approved the material callouts, and flagged two construction questions for the designer to resolve the following morning.
Day two: design responses in by 10am. The technical designer incorporates the feedback, runs a final completeness check — Calico surfaces two measurement callouts that are inconsistent with the grading table — corrects them, and issues the finalized techpack to the factory by early afternoon.
The factory receives a document that answers the questions it would typically ask. No clarification request comes back that day. A sample is confirmed for cutting.
Total technical designer time invested: under four hours across two days. Under the traditional workflow, this style would have consumed a full day on day one and intermittent hours across the following week as factory questions arrived.
What it changes for the team
The 48-hour capability changes something more significant than just the speed of any individual style. It changes the shape of the product creation calendar.
When a techpack takes a week to produce and two or three sample rounds to get right, the calendar is built around those constraints. Design lock dates are set to accommodate the process. The number of styles that can run in parallel is limited by technical designer capacity — not by creative ambition or commercial opportunity.
When a techpack takes 48 hours and the first sample is right, those constraints loosen. More styles can move simultaneously. Design lock can happen closer to the delivery window. Late creative decisions — the ones that respond to what is actually happening in the market — become feasible rather than disruptive.
For the brand in this case study, the practical result was that the team was able to add eleven late-stage styles to the season — styles that would not have been possible under the traditional calendar — without adding headcount or extending the production window. Several of those styles became top performers in the season. None of them would have existed under the old workflow.