I've been advising a small SaaS startup on their website copy, and we hit a snag on the "About Us" page. The founder wanted something that balanced professionalism with their unique team culture. To get a feel for the current landscape, I ran the exact same prompt through five popular AI writing tools.
The prompt was straightforward:
> "Write an 'About Us' page for a B2B SaaS company named 'NexusFlow'. We provide intelligent workflow automation for mid-sized financial firms. Our tone should be professional yet approachable. Key points to include: founded by ex-industry experts who saw a gap in affordable, intuitive tools; our platform turns complex processes into simple, visual workflows; we believe technology should empower teams, not replace them; and we value deep partnerships with our clients. Aim for 250-300 words."
The outputs were fascinating in their divergence. One tool produced a bloated, 500-word essay full of generic phrases like "leverage synergistic solutions." Another gave a crisp 200-word draft that nailed the key points but felt a bit sterile. A third surprisingly injected a subtle, welcoming warmth that aligned perfectly with "approachable," while a fourth got the facts right but the voice sounded like a stiff press release.
The main differences weren't in factual coverage—they all hit the bullet points—but in **voice, conciseness, and how they framed the core message**. The one that performed best required the least editing to match the desired tone. The others needed significant rewrites, either to cut jargon, inject more humanity, or tighten the structure.
It's a useful reminder that the tool choice isn't just about generating text; it's about which one starts you closer to your specific voice and audience. The "best" tool completely depends on the brand's personality.
—daniel
That's a really interesting experiment. I've seen similar variation when using AI to generate config files or CI/CD pipeline YAML. You give the same spec to GitHub Copilot, ChatGPT, and a CLI tool, and you get three different structures that all technically work.
The "bloated, 500-word essay full of generic phrases" sounds painfully familiar. It's like when a tool over-engineers a simple deployment script, adding unnecessary complexity.
Which tool gave you the sterile but crisp draft? That's the kind I'd probably end up using as a first draft, then trying to manually inject the "approachable" tone afterward. I wonder if the results would be more consistent if you added a single, very specific instruction like "avoid the phrase 'leverage' and use 'use' instead."
Learning by breaking
Absolutely. That "sterile but crisp" one came from the tool that's basically a GPT wrapper with a minimalist UI - it tends to do exactly what you ask, then stops. No extra fluff. It's useful as a skeleton, but you're right, you then have to spend time adding the warmth back in.
Your point about a single, specific instruction is spot on and something I preach to clients. We did a similar test with marketing email copy and found that adding "replace all instances of 'leverage' with 'use'" dramatically cut down on the corporate jargon across every tool. The consistency improved, but the *style* still varied wildly.
It's the classic automation paradox: sometimes the tweak needed to make the output perfect is more work than writing the first draft from scratch. Been there with workflow builders too - you can spend an hour debugging a flow that would've taken 10 minutes to do manually.
Implementation is 80% process, 20% tool.