The ChalkBlaster you'll eventually pull out of the box will be consistent — one unit the same as the next. That consistency exists because we did the slow, unglamorous thing first: we built the earliest batches ourselves, by hand, before letting anyone scale them. It taught us things about our own design that no factory would have told us.
The easy path we didn't take
On paper, the smart move for a small hardware team is to hand the design to a contract manufacturer and let them figure out assembly. It's faster and it frees you up. We didn't do that. We assembled the first two batches in-house, one unit at a time, on our own bench.
It was slow and tedious. It was also the most useful thing we've done for the product.
What building by hand forced us to see
Assembling a product yourself surfaces the problems most founders only meet after they've scaled — when it's expensive and slow to fix. We ran straight into a design that didn't want to be mass-assembled: steps that fought back, tolerances that were fine one at a time but a nightmare in a row. Quality control was impossible to standardise, and honestly, early on every unit had a slightly different defect. A factory would have simply reproduced all of that — at a thousand times the volume.
Outsource assembly on day one
Fast, and someone else's problem — until the design's assembly flaws get mass-produced into thousands of units. You discover the bottlenecks at scale, when they're expensive to unwind.
Build the first batches yourself
Slow and tedious — but every awkward step, loose tolerance and one-off defect shows up in your own hands first. You fix the design before volume makes the mistakes permanent.
2 batches
assembled by hand before we let anyone scale the ChalkBlaster
Why this matters before you scale
Now we walk into supplier and process decisions knowing exactly where the ChalkBlaster fights back on the line. We know which steps are the bottlenecks, which tolerances need tightening, and where a jig or a design change removes a whole class of defect. That's the difference between choosing a manufacturer from knowledge instead of hope. Designing for assembly only means something once you've done the assembling.
What this means for your ChalkBlaster
When the ChalkBlaster scales, it won't scale a pile of hidden assembly flaws with it. The design has already been through the one test a CAD file can't run — a human being building it, over and over, and getting annoyed at every part that didn't cooperate. You get the version that came out the other side of that. Consistent, on purpose.
From the comments
Hardware folks summed it up in two acronyms: Design for Assembly and Design for Manufacturing. You can't do either honestly until you've felt the design fight you on the bench.
A repeated theme: founders who assemble early solve problems faster later, because they already know exactly what breaks and where the line will jam.
SWEEP Climbing builds tools for climbers who take friction seriously.
