My clients build impressive things for other businesses. But when I ask them to describe their most recent project in plain English, they immediately reach for technical terms their clients would never understand.
A custom inventory system becomes "a full-stack application with a database backend." A client-facing booking tool becomes "an API-connected web application." The work is real, the results matter — but the words make it sound like homework.
Portfolio blog posts are how service professionals prove their value to the next client before a sales call ever happens. The challenge is translating the work into language that a business owner actually cares about. No generic AI tool solved this well. They either produced flat, corporate-sounding summaries or repeated the technical details back in slightly different words. What I needed was a writing partner who would ask the right questions first, pull out the human story behind the project, and then write a post that spoke to a decision-maker — not a developer.
So I built one.
How the System Works
The Blog Writing Assistant is a subscription-based AI tool built for service professionals who need to keep their portfolio current without spending hours rewriting technical notes into business language.
- Guided Discovery First: Before writing a single word, the assistant asks structured questions about the project — who the client is, what problem they were actually trying to solve, where the build got difficult, and what the concrete results looked like. It never asks about the tech stack.
- Writes for the Right Audience: The assistant is built to speak to regional business owners and municipal partners — the exact decision-makers who hire service professionals. It avoids software jargon entirely and translates every technical detail into a plain business result.
- A Conversation, Not a Form: Users describe their project naturally, in their own words. The assistant asks follow-up questions, steers toward the most compelling details, and tells you when it has enough to write a strong draft.
- Structured Output Every Time: Every post follows the same proven structure — a real-world problem introduction, a plain-English system overview, the honest friction from the build, and the concrete business win. No filler, no generic preamble.
Overcoming the Friction
Keeping the AI On-Voice
The biggest challenge was consistency. A standard AI assistant, given the same project notes, will default to bullet points full of buzzwords and hedged language. The assistant needed a strict ruleset — a list of banned phrases, required structures, and a specific voice — that it would follow every single time without slipping into corporate-speak. Several rounds of testing against real client projects were needed before the output was reliable enough to publish without heavy editing.
Protecting the Recipe
The tool is built on a detailed set of writing instructions that took considerable time to develop and refine. A critical requirement was that those instructions never be visible to subscribers. Anyone with enough curiosity can inspect what a website sends and receives behind the scenes. The system had to be structured so the writing instructions stay entirely on the server — subscribers interact with the result, not the ruleset that produces it.
Teaching Discovery Before Writing
Early versions jumped to writing too quickly. The draft read like a summary of whatever the user typed first, rather than a real story. The assistant needed to learn to ask before it wrote — to slow down, gather the human details that make a post memorable, and only offer to draft once it had the right raw material. Shifting from "instant output" to "guided conversation then draft" made the final posts significantly stronger and required far less editing.
The Business Win
The tool produces a complete, publication-ready blog post in a single conversation — typically under twenty minutes. Users arrive with rough project notes and leave with a polished draft written in the voice their clients actually respond to.
No Blank Page: The biggest reason service professionals do not blog regularly is the time and mental overhead of starting from nothing. The assistant removes both problems by leading the conversation and handling the structure.
No Rewrite Cycle: Because the assistant gathers the story details before writing, the first draft is structurally sound. Subscribers report making minor adjustments to personalize the tone — not wholesale rewrites.
Consistent Portfolio Growth: A steady publishing cadence matters for attracting new clients. Removing the blank-page problem means users can close a project and document it the same week, while the details are still fresh.
The next step is adding industry-specific discovery templates for common project types — municipal technology, retail operations, and commercial construction — so the assistant can ask even more targeted questions from the very first message.
Top comments (0)