Week 12: Building the Machine Was the Easy Part

Week 12 of Shipping Every Week: last week I set Powr down and said I was picking up a web design studio. This week I had to actually do it. And I learned something I half-knew already but had managed to avoid for fifteen months.

The hard part was never the building.

What I built this week

I went from a decision to a working operation in about six days. The receipts:

I built demos for real LA businesses I've never met. The play is simple: find an established local business with a website that's dated or doesn't work on a phone, rebuild it as a free, mobile-first demo, put it on a live URL, and send the owner a short note that says "I redesigned your site, here's the link, no strings." This week that meant a 1969 wholesale food supplier in downtown LA, a fastener distributor in San Dimas that's been around since 1947, a packaging supplier in South El Monte, a solo optometrist in Long Beach, plus about ten local-booking businesses: salons, nail and lash studios, trainers, a boxing gym. Each one is a real redesign of their actual site, live and ready to look at.

To make that repeatable instead of bespoke, I built a design token system: a set of per-vertical themes where re-skinning a site for a new salon or a new distributor is mostly swapping variables and fonts, not rebuilding from scratch. That's the whole bet of the studio. Every site is a variation on a reusable template.

I built a little CRM web app to track who I've reached out to and where each conversation stands, because a markdown file stopped being enough the moment there were twenty names in it. I wired up a job that goes looking for new prospects every Monday morning so I always have a list to work. And I gave this series a real home: the blog you're reading is new this week, generated straight from the repo and living on my own site instead of inside one platform.

That's a lot of machine for one week. And none of it was the hard part.

The part I kept avoiding

All of that building is comfortable for me. I'm an engineer. Give me a problem I can solve by typing and I'll happily do it for ten hours and feel productive the whole time. Building the pitching machine was a place to hide.

The actual job this week was to send cold emails to strangers about their websites. And that is scary in a way shipping code is not. When I push code, the worst case is a bug. When I send a stranger an unsolicited note saying "I redesigned your business's website," the worst case is they think I'm presumptuous, or they ignore me, or they reply with something unkind. There's a person on the other end, and they didn't ask for this.

So I caught myself avoiding it. Polishing the CRM, refining the templates, making the demos a little nicer. All real work, and all a convenient reason not to open Gmail and hit send.

This week I finally started. I sent ten outreach messages, real notes to real owners, each with a demo of their own site attached. Not every demo I built went out, but ten did, and the sky didn't fall. A few haven't replied. That's fine. For eleven weeks I counted what I built. This week I counted what I actually put in front of a person: ten.

Outreaches sent this week: 10. I'm going to put that line at the bottom of every one of these from now on, because the audience is a better commitment device than my willpower has been.

Why this is the opposite of the Powr trap

With Powr, I built and built and built, and the market never pulled the product out of my hands. I mistook shipping for traction for a very long time. The work was real and the revenue was flat, and I wrote about that last week.

The risk this week was doing the exact same thing in a new outfit: spend the studio's first week building a beautiful pitching machine, feel productive, and never sell anything. Same trap, new logo. The tell would be a gorgeous CRM full of prospects I never emailed.

The difference this time is that the scary thing and the important thing are the same thing, and I can't code my way around it. A demo on a server does nothing until a person reads it and decides to write back. So the discipline I'm taking into week 13 is dumb and simple: the machine is done enough. From here the only number that counts is how many real people I send this to.

If you're a business owner in LA who needs a website, to take bookings or sell something or host a blog like this one, hit me up. Getting less afraid to ask is the whole point this week, so you'd be doing me a favor.

This week taught me I'll build infrastructure forever to avoid the one conversation that actually moves the business. If you've ever caught yourself perfecting the tool instead of doing the scary thing the tool was for, I'd like to hear how you broke the pattern.

What did you ship this week?