Help CentreContactLogin
Lean teams

Four requests, four people, one week: why small teams drift

When whoever is free writes it, the one-pager and the campaign stop matching. The fix is upstream of the writing.

Aug 11, 20262 min readBy the Swiftly team
All posts

Here's the week on a lean marketing team. Monday: sales needs three vertical one-pagers by Thursday. Tuesday: the CEO wants a deck for the board on Friday. Wednesday: next week's social calendar is empty. Thursday: the blog hasn't published in a month and someone noticed.

Four requests, the same four people, one week. So the team does what every small team does. It triages. The one-pagers go to whoever has a window. The deck goes to whoever the CEO asked. Social gets squeezed in Friday afternoon. The blog slips again.

The cost isn't the delay

The delay is visible, so it gets managed. The real cost is what happens to the work when whoever is free writes it.

The one-pager says one thing about the product. The deck says something slightly different, because it was written by someone else from memory. The social posts don't mention the thing sales is leading with. Nobody's wrong, exactly. They just weren't working from the same strategy, because on a small team the strategy lives in three people's heads and a deck from last quarter.

One sourcepositioning · messages · proof points · voice
Sales one-pager
Leadership deck
Social posts
Three writers, three memories of the positioning. Then the same three, drafted from one source.

Why more headcount doesn't fix it

The instinct is to hire. But the problem isn't hands — it's that every request starts from a blank page, and every blank page is a chance to say something new. Add a fifth writer and you get a fifth version of the positioning.

The fix is upstream. Every request should start from the same place: the same positioning, the same key messages, the same proof points, the same voice. If that source exists and every draft reads it first, the one-pager and the deck and the post all say the same thing, regardless of who's free.

What that looks like in practice

Swiftly gives a team a Context Binder: one living record of the company's positioning, products, audiences, key messages, and voice. Every request — a campaign or a single one-pager — reads it before anything gets drafted. Campaigns come back as research and a plan the same day; single requests come back as drafts built from that same strategy.

Requestfrom sales, the CEO, the calendar
Binderread first, every time
Draftbuilt from the strategy
Reviewthe team’s actual job
Outin one voice
Every request passes through the same source before anyone writes. That’s what stops the drift.

The team's week changes shape. Monday's four requests are all drafted by Monday afternoon. The rest of the week is review and polish — the work that actually needs a human who knows the company — instead of four people starting four blank documents.

Whoever is free still reviews it. They just don't have to write it from nothing.

Put Swiftly on your next campaign.

Plans start at $199 a month.