**Read in one paragraph:** The piece is doing two things: telling a migration story and arguing a principle ("simpler is usually right at small scale"). The story works — it's specific and has texture. The principle doesn't, because you hand it to the reader before the story earns it. The voice is on target: plain, unhyped, recognizably a working dev. This is shippable after one structural fix and two cuts. **Structural notes:** You declare the conclusion in the first two sentences, then spend the rest of the piece on the evidence that would have produced it. The principle lands much harder as a finding than as a thesis. Open with the moment something broke — "I'd been using HubSpot for six months when I realized I was spending more time maintaining the CRM than talking to customers" — tell the migration, and let the lesson arrive at the end. **Section-by-section:** **Opening ("Simpler is usually right at small scale. That's the lesson I keep relearning."):** - Works: nothing yet. It's a slogan the reader has no reason to accept. - Weak: it states the conclusion with zero evidence behind it, which is exactly what makes a piece sound like a productivity influencer — the thing you said you're trying to avoid. - Specific change: cut both sentences. Start at "I'd been using HubSpot for six months..." **The migration ("I'd been using HubSpot..." through "It took an afternoon."):** - Works: this is the strongest part. "Six months," "an afternoon," "more time maintaining the CRM than talking to customers" — specific, concrete, earned. - Weak: the Notion sentence stops the story to give a feature tour. - Specific change: cut "Notion is a flexible workspace tool that lets you build databases, write docs, and organize information all in one place." The very next sentence already shows what you built, which is better than describing the tool. **Close ("Six months later..." through "...simplicity wins."):** - Works: "I haven't missed a single thing HubSpot did for me" is a real claim with a real time horizon. - Weak: the last sentence stacks three platitudes and undoes the plainness of everything before it. - Specific change: replace it with a statement scoped to what this story actually shows. **Line-level snags:** - "I spent way too long figuring out HubSpot's automation features before realizing I didn't need them." - Issue: "way too long" is vague in a piece whose power is specificity. Every other number here is real. - Rewrite: "I spent four hours in HubSpot's automation builder before realizing I had eight customers." (If those are the true numbers.) - "Notion is a flexible workspace tool that lets you build databases, write docs, and organize information all in one place." - Issue: an explainer sentence for a tool your reader already knows, and "all in one place" is marketing copy, not your voice. - Rewrite: cut it. - "At the end of the day, the lesson here is that simplicity wins." - Issue: "at the end of the day" + "the lesson here is" + "X wins" — three platitudes in one sentence. - Rewrite: "For eight customers and one person, the simple tool was the right one." **What to cut:** The opening two sentences and the Notion explainer, plus tightening the final line. That's roughly 60 words out of ~130 — the piece gets meaningfully shorter and the argument gets stronger, because the principle now arrives with evidence behind it. **What's missing:** The piece never says who *should* use a heavy CRM. One sentence — "If I had a sales team or a few hundred customers, HubSpot would be the right call" — preempts the obvious objection and is the difference between a considered take and a hot take. **Bottom line:** Ship after the structural fix (open with the break, not the principle) and the two cuts. The story is genuinely good. The fixes stop you from sounding like the thing you're trying not to sound like.