Michelle works in economic development. Her peers signed a $30,000 contract with an automation vendor to produce company briefs, the research documents an EDO builds before meeting a prospect or pitching a site. Michelle took a different route. She joined a cohort, learned the workflow logic, and built the system herself. Her cost: the training and a few afternoons of practice.
Before, one brief took her four to five hours. Research across a dozen sources, copy into a document, format, check, format again. Now the same brief takes about 20 minutes, and most of that is Michelle reading the draft and correcting what the system missed.
The math, in public
Run the numbers with me. Say Michelle produces one brief a week. At four and a half hours each, that is 234 hours a year. At 20 minutes each, it is 17 hours. She gets 217 hours back from a single workflow. Call it 27 working days.
The vendor version produces the same briefs for $30,000 up front, plus a maintenance line in next year's budget, plus a support ticket every time the output needs to change. You pay twice: once in dollars, once in waiting.
What the workflow is made of
No magic here. The system has four parts. An intake step captures what the brief is for and who will read it. A research pass pulls from the sources her office already trusts. A template formats the findings the way her director wants to read them. A human review closes it out, every time.
Michelle owns each part. When her director asks for a new section, she adds it that afternoon. When a data source changes, she swaps it. A vendor would quote her for both.
The question that saves you $30,000
Before you sign an automation contract, ask who owns the system after launch. If the answer is the vendor, you rented a workflow, and rent comes due with every change request. If the answer is your team, the workflow compounds. Michelle's briefs improve month over month because she keeps tuning the system, and the skill she built carries into the next workflow, and the one after that.
I teach this because I run four ventures with a team of two, on the same systems I hand my students. The build is the easy part. The decision to own it is the part that pays.