SaaS

Lumenly

Sample story

How Lumenly cut article production from nine days to four

Lumenly ships product stories, comparisons, and thought leadership from a small team. Writto trained a voice on published posts so editing started closer to done.

58%
Less Production Time

Figures on this page come from the stories below. They are not a blended average of every Writto account.

Company

Overview

Lumenly is a 40-person B2B analytics company. Marketing is three people. They own the blog, comparison pages, and launch posts, and they cannot afford a two-week cycle on every piece.

The challenge

Every article moved from a Notion brief to a generic model, then to a humanizer, then to Yoast. The calendar filled with handoffs. Shipping slipped whenever someone was out.

How they used Writto

Lumenly trained a Writto voice on two years of published posts. Writers draft in that voice, score the page in the same document, and send it to review without a rewrite pass for tone.

Previous workflow

PMs wrote briefs in Notion. Marketers drafted in a chatbot. Editors ran detection and an SEO plugin in sequence, often on Friday afternoon.

Workflow

Before Writto

  1. 01Keyword research
  2. 02Multiple research tools
  3. 03Writer
  4. 04AI writing tool
  5. 05Editing
  6. 06AI detection/humanization
  7. 07SEO optimization
  8. 08Publishing

With Writto

  1. 01Research
  2. 02Write
  3. 03Humanize
  4. 04Optimize
  5. 05Publish

Results

Average time from brief to published post fell from nine days to four. The team published 11 more comparison pages in a quarter without hiring. Review comments shifted from 'this doesn't sound like us' to notes on the claim.

We were rewriting every first draft just to sound like us. Once the voice sat in the document, we spent the time on the argument instead of the tone.

Jordan HaleProduct Marketing ManagerLumenly

Key takeaways

  • A trained voice removes a rewrite pass the team had accepted as normal.
  • Optimization in the document is faster than a separate SEO stage at the end.