Fieldnote
A content system a team of three can actually maintain
Publishing had stalled at two posts a quarter. We replaced a bespoke CMS with a block-based system and a weekly editorial rhythm.
- Client
- Fieldnote
- Industry
- B2B SaaS
- Role
- Delivery consultant
- Timeline
- 6 weeks
Process designCMS migrationEditorial ops
4x
Publishing volume
2 hrs
Average time to publish
0
Developer tickets per post
Every article needed a developer. That single fact explained the entire content backlog.
Approach
Blocks, not templates
We catalogued every layout the marketing team had ever asked for, reduced it to eleven reusable blocks, and gave them a weekly slot to draft, review and ship. The technical work was the small half.
What made it stick
- A named owner for the weekly slot
- Blocks constrained enough to stay on brand
- Publishing with no engineering dependency