Voice for Newsletter Writing

Draft newsletter content by talking through your ideas. Turn a stream of thoughts into a structured, engaging newsletter that your audience will read.

The Problem

Newsletters are powerful for building audience relationships, but writing them consistently is a grind. The blank page is intimidating, the pressure to be insightful and engaging is high, and the weekly or monthly cadence makes it feel like a treadmill that never stops.

The Solution

Ummless lets you talk through your newsletter topic conversationally, as if you're explaining it to a friend. The Professional Email preset transforms your spoken thoughts into a polished, readable newsletter draft with clear structure and engaging prose.

Workflow

Choose your topic
Decide what you want to write about. Have a few notes or bullet points ready if it helps.
Open Ummless
Select "Professional Email" for polished, reader-friendly prose.
Talk through your content
Speak naturally about your topic. Share your perspective, include anecdotes or data points, and give your audience something actionable.
Structure the draft
Review the output and organize it into sections with a compelling opener, body, and conclusion.
Edit and send
Polish the draft in your newsletter tool, add images or links, and schedule for publishing.

Before & After

Raw Transcript

So this week I wanted to talk about how we reduced our build times by like 80 percent by switching to Turborepo. A lot of people don't realize that um the big win isn't just caching, it's that Turborepo understands the dependency graph and only rebuilds what actually changed. We went from 12 minute builds to about 2 minutes. The key was setting up the pipeline correctly in turbo.json and making sure our package boundaries were clean.

Refined Output

## How We Cut Build Times by 80% This week, I want to share a win from our engineering team: we reduced our CI build times from 12 minutes to just 2 minutes by adopting Turborepo. The common assumption is that Turborepo's main benefit is caching, and caching is significant, but the real win is dependency graph awareness. Turborepo analyzes your monorepo's package dependencies and only rebuilds packages that were actually affected by a change. No more rebuilding your entire codebase because of a typo in a README. The key to making this work was two things: a well-configured `turbo.json` pipeline that accurately describes task dependencies, and clean package boundaries that minimize unnecessary coupling between packages. **Takeaway:** If your monorepo builds are slow, the fix might not be faster hardware or more parallelism. It might be smarter builds that skip work that doesn't need to happen.

Suggested Presets

Professional Email

Frequently Asked Questions

How long should I speak for a newsletter?

2-5 minutes of speaking typically produces a 300-600 word newsletter draft, which is ideal for most audiences. Longer newsletters can be dictated in sections.

Can I dictate a multi-section newsletter?

Yes. Dictate each section separately for better focus and organization. Combine the refined outputs into a single newsletter in your publishing tool.

Ready to try it?

Download Ummless and start using voice for your workflow.