3 min read
Inside Brightfold's content engine: four times the output, one voice
Brightfold's six-person marketing team now publishes four times as much as it did a year ago. How they set up brand voice, review and Library so quality went up, not down.
Grace Mensah and Divya Menon
On this page
A year ago, Brightfold’s marketing team published one long article a week, a newsletter every other Friday and whatever social posts they could fit around launches. Today the same six people publish four times as much, in three languages, and their editor says the writing is better than it was.
We spent a day with the team to understand how. The short version: they didn’t ask Pilot to write more. They asked it to take over the parts of writing that weren’t really writing.
Where the time was going
Before Pilot, Brightfold’s head of content, Mira, tracked a week of the team’s hours. Drafting took less time than anyone expected. The rest went to work around the draft:
- Finding the right product facts, customer quotes and previous posts to reference
- Rewriting drafts that drifted off brand, especially from freelancers
- Turning one article into a newsletter section, three social posts and a sales email
- Chasing reviewers and reconciling their comments
“We thought we had a writing problem,” Mira told us. “We had a finding-things problem and a reformatting problem.”
Step one: a voice guide Pilot could follow
The team’s old style guide was a 30-page PDF that nobody opened. Divya worked with them to turn it into a Pilot brand voice: around forty short, testable rules, each with an example.
A few of Brightfold’s rules:
- Say “customers”, never “users”
- No exclamation marks, and no “we’re excited to announce”
- Lead with the customer’s problem, not the feature
- Write at a grade 8 reading level for anything public
Rules like these work because Pilot can check them sentence by sentence. “Sound warm but professional” can’t be checked. “Use first names for customers in case studies” can. We wrote more about this in Writing a brand voice guide Pilot can actually follow.
Step two: one source of truth in Library
Next, the team moved everything a writer needs into Library: the product fact sheet, approved customer quotes, the messaging framework and every post they had published.
Now a writer can ask what did we say about the spring release in March? and get an answer with links, instead of searching three drives. More importantly, Pilot drafts from these sources, so a new post doesn’t contradict an old one.
The first month, the biggest change wasn’t speed. It was that the freelancers’ drafts finally sounded like us.
Step three: one article, many formats
Brightfold’s biggest gain came from repurposing. Each long article is now the source for a set of smaller pieces, generated from a saved template and reviewed by one person:
| From one article | Before Pilot | With Pilot |
|---|---|---|
| Newsletter section | 45 min | 10 min |
| Three social posts | 1 hr | 15 min |
| Sales follow-up email | Rarely written | 10 min |
| German and French versions | Agency, 5 days | Same day, reviewed by a native speaker |
The team still edits every piece. But editing a good draft is a different job from writing from a blank page, and it’s one they can do between meetings.
What they’d tell another team
We asked what they’d do differently if they started again. Three answers came up more than once.
Start with the voice, not the volume. Spend the first week on brand rules and examples. Every draft after that is better.
Give review a single owner. Brightfold has one editor who approves everything public. Faster drafting only helps if review keeps up.
Measure what you publish, not what you generate. It’s easy to produce drafts. The number that matters is pieces that shipped and performed.
The numbers
Over twelve months Brightfold went from about 9 published pieces a month to 37, without new hires. Organic traffic grew 62%, and the newsletter’s open rate rose from 31% to 38%, which the team attributes to more consistent sending.
You can read the full Brightfold customer story, including their template library and review workflow.

Written by
Grace Mensah
VP of Customer Success
Sets up Library and brand voice with every new team on the Enterprise plan.

With
Divya Menon
Head of Content
Edits the blog and writes the style guide Pilot learns from first.

