The author
Jimenez Julien, the person who builds and answers for StitchPattern
I write the code, run the support inbox and sit on the walkthrough calls. If something in StitchPattern is wrong, it is mine to fix.
Why I built a release tool for pattern designers
I did not come to sewing patterns through sewing. I came to them through a support inbox. In 2022 I was helping a small digital publisher untangle why their customers kept receiving outdated files, and the answer turned out to be simple and awful: the corrected file existed, but nobody had a reliable way to hand it to the people who had already paid. That publisher sold recipe collections. A few months later I heard the identical complaint from a knitwear designer in Vermont, then from a sewing pattern label in Ohio, and the shape of the problem never changed.
What was different in this trade was how much craft sat on top of the mess. A pattern designer holds an enormous amount of precise information: eleven graded sizes, finished measurements with ease, a construction order that has to survive being read at eleven at night by someone with a seam ripper in her hand, print tiling for three paper formats, and a chart where one repeated decrease can cost a knitter a whole evening. All of that is engineering. Yet the tools designers were handed for managing it were a shared folder, a spreadsheet and a social media group. The care went into the drafting and evaporated the moment the file left the studio.
So I built StitchPattern around the one thing that folder and that spreadsheet could never do together: keep the chain intact from a tester note to a numbered errata entry to a corrected PDF sitting in the inbox of every person who bought version 1.0. Everything else in the product exists to serve that chain. If a feature does not help a correction reach a buyer, or does not help a designer see what her testers actually found, it does not get built.
What working with this trade taught me
Three things, mostly by being wrong first. The first is that designers do not need to be taught version control; they already think in versions, they just do not have a place to put them. My earliest interface tried to explain the concept and it was insulting. The version screen now assumes you know exactly what you changed and simply asks you to say it in a sentence your buyer can read.
The second is that tester rounds fail on coverage, not on enthusiasm. Twenty testers who all sew a size medium tell you almost nothing about the grade. The size coverage view exists because a designer in Michigan showed me a spreadsheet where she had been color coding this by hand for six years.
The third is about tone. Errata carries shame for a lot of designers, and a product that treats a correction as a failure makes people publish fewer of them. StitchPattern deliberately treats an errata entry as ordinary maintenance, because a pattern that gets corrected in public is a better pattern, and buyers behave accordingly.
Experience and expertise
- Fourteen years building software for small operators who run a business alone or with one or two colleagues, mostly in publishing, digital goods and craft retail.
- Direct work with 214 US pattern businesses using StitchPattern, from single designers with six patterns to studios maintaining catalogs of more than a hundred.
- Hands on experience with the shop platforms this trade actually uses: Shopify, Payhip, Gumroad, Etsy and Ravelry, including the awkward parts of their buyer exports.
- Ongoing conversations with technical editors and graders, who taught me more about what belongs in a release record than any product research ever did.
- Founder of MLJ, SASU, the company that publishes StitchPattern and a small number of other tools for independent operators.
How this product is built and maintained
StitchPattern ships small changes weekly and publishes what changed in plain language. Every feature starts from a real support conversation, and I keep the original message attached to the work so the reason survives longer than my memory does. Nothing goes out without being used first on a real catalog with a designer's permission.
The editorial standard for this site is the same as the product standard. Every number on these pages comes from platform data or from a customer who agreed to it being published, and the three testimonials are from named designers who read their quote before it went up. If a figure changes materially, the page changes with it. I do not publish rounded estimates dressed as measurements, and I do not use a customer's business as a marketing prop without asking.
On the technical side: pattern files live in encrypted storage in US regions, buyer data is never sold or shared, and access to production data is limited to me and logged. Backups run daily with a thirty five day retention window. When something breaks, I write to affected accounts before they write to me, because in this trade a broken download link on launch day is a real financial event.
Published articles
These are the nine pieces I have written for The Grading Table, the StitchPattern magazine, all published on September 4, 2026 and revised whenever the trade practice behind them changes.
- How do I run a tester round for a new sewing pattern without losing three months?
- Should I sell my knitting patterns on Ravelry, on my own site, or on both at once?
- What are the most common grading errors that only show up in the largest sizes?
- Do I have to collect sales tax on a PDF pattern sold to a buyer in another state?
- How did one designer fix a sizing error after two thousand people already bought the pattern?
- Is the market for printed paper patterns actually coming back, or is that wishful thinking?
- What exactly should I check in a pattern PDF before I put it up for sale?
- How should I price a PDF pattern when the tech editor costs more than the pattern earns?
- What does a tech editor actually do to a knitting pattern before it goes out the door?
Contact the author
Write to me at jimenezjulien42@gmail.com. I read everything and answer within one business day, and I would rather have your hard question than your polite one. If you want to see the software running on your own catalog, use the walkthrough form and pick a time.