Most people think of AI blog writing as one thing: you give it a topic, it gives you a draft.
What we found building Blogboat is that the topic is only half the question. The other half is: what kind of voice should this be in?
The same topic — say, "why developers should write more" — reads completely differently depending on whether you want it to sound authoritative, conversational, persuasive, like a story, or like advice from a friend. The content can be nearly identical. The reader's experience of it is not.
That's why we built tone selection into Blogboat as a distinct, first-class step before AI writing begins.
The five tones we support (and when to use each)
Professional is the default for most work content. Clean, confident, direct. No hedging, no filler. Best for: technical documentation, company blogs, LinkedIn posts where you want to be taken seriously.
Casual drops the formality without dropping the intelligence. Shorter sentences. Contractions. Feels like a smart colleague explaining something. Best for: developer communities, Discord-style audiences, situations where stiffness would read as disconnected.
Friendly adds warmth. It's approachable, encouraging, assumes the best about the reader. Best for: onboarding posts, tutorials, anything where you want the reader to feel welcomed rather than tested.
Persuasive is structured to build a case. It leads with a problem, introduces a claim, supports it, and closes with a call to think differently. Best for: opinion posts, change-my-mind content, marketing-adjacent writing where you want the reader to shift a position.
Storytelling opens with a scene or moment rather than a thesis. It earns the insight by showing it in action. Best for: personal essays, "how we built this" posts, case studies with a human arc.
Why this matters more than most people expect
The biggest mistake in AI writing isn't the topic. It's publishing content that's technically correct but tonally wrong for the platform or the audience.
A well-researched post written in Professional tone performs differently on Dev.to than the same information written in Casual tone — because Dev.to readers respond to peers sharing experience, not to brands publishing advice. A Friendly-tone tutorial does better for beginners than a Professional-tone one, even if the content is identical, because the tone itself signals safety.
Tone is the first thing a reader feels before they process any actual information. It determines whether they trust you, stay reading, or bounce.
How it works in Blogboat
When you open the AI writing panel, you choose a tone before you generate. The AI doesn't add the tone as a veneer afterward — it writes the entire draft in that register from the first sentence. The structure, the vocabulary, the sentence rhythm, and the calls to action all shift together.
You can also regenerate in a different tone without losing your topic or outline. If the Professional version feels too stiff for where you're publishing, switch to Casual and generate again. The topic stays the same; the voice adapts.
The bigger point
Blogboat was built by the team at twRty Software Services to solve the full publishing workflow, not just the drafting step. Tone selection exists because we wanted the output to be publishable — not just generated.
A draft that needs to be entirely rewritten for voice is not a useful draft. We wanted the first draft to be close enough to your actual intended voice that editing it is a matter of precision, not reconstruction.
Try it at twrty.org/blogboat, on iOS, or on Android.
