How Rally Built a Repeatable Content Process That Scales

Lauren Gibson had a lot on her plate when she was Content Marketing Manager at Rally UXR.

She was a one-woman content marketing team, juggling everything from content strategy to blog production. She was cobbling things together just to keep the content wheels turning.

No real system. Just a never-ending to-do list. Sound familiar?

The short version: Rally UXR published 3-4 blogs a month with a one-person content team, after replacing a spread of Notion, Google Drive, and Webflow with a single content hub. Setup took a week. Relato became the marketing team’s single source of truth inside a month. The headcount never changed.

The challenge: Make content sustainable, not just scrappy

Like most content marketers, Lauren was stuck using a Frankenstack. Some blogs lived in Notion, others in Google Drive, and a few were buried in Webflow. Ideas came from Slack threads, sticky notes, and passing thoughts.

She was repeating tasks, chasing down files, and drowning in busywork that should’ve been automated. And the patchwork setup? Not built to scale.

“I wanted to be more strategic and increase my actual impact,” Lauren said. “But I knew I needed a more organized system before I could scale anything.”

Her team had access to general project management tools, but none worked well (or were made) for content.

Notion felt clunky. Linear was built for engineers. Nothing stuck.

She needed a platform that was:

• Easy to use with minimal setup. With so much on her plate, Lauren did not have time for a steep learning curve. She needed the platform to get up and running quickly.
• Simple to share and scale. Freelancers, new hires, and cross-functional teammates needed to be able to jump in without hand-holding.
• Clear for stakeholders. Leadership needed visibility into content plans, progress, and outcomes.

Enter: Relato, a platform built for content teams

Lauren hadn’t heard of a “content ops platform” before Relato. But once she talked to David, Relato’s founder, it all clicked.

“I could tell he understood my challenges and built this tool for content teams. It was so easy to see how Relato would help me manage content strategy, production, and freelancers.”

That mattered. Lauren was skeptical about adding a new tool. She was choosing a system that could support Rally UXR’s growth. She didn’t want to bring something on board, only to abandon it a month later. And she needed to be confident it was the right fit before recommending it to the team.

And Relato delivered. Fast.

Within a week, Lauren was:

• Managing blog content
• Creating briefs
• Adding freelancers
• Looping in PMMs and stakeholders

“It was very quick,” she said. “That was such a relief. I could show that it was worth it to our leadership almost immediately.”

The tool-hopping and doc-chasing stopped. Everything finally had a home.

Within a month, Relato became the single source of truth for Rally’s marketing work.

Here’s how Rally uses Relato today:

• Freelancer management: assign, track, and review projects in one place
• Web content: plan and publish new site pages
• Email marketing: coordinate newsletters and nurture campaigns
• Event programming: organize outreach and logistics
• Repurposing: surface and reuse past content
• Strategy: capture ideas and shape long-term plans

From scrambling to scaling

Relato helped Lauren do more than organize. It helped her gain clarity and visibility, all while improving her ability to create great content.

With a platform built for how content teams actually work, she could hit Rally’s publishing goals (3-4 blogs a month) without burning out. The process became smoother. The content got better.

“Relato makes it so much easier to keep a record of what we’ve done and to move faster on what’s next. We can finally pause and ask: Is this working? What needs to change? What’s slowing us down? Before, we didn’t even have the time or structure to ask those questions.”

Collaboration improved across the board. Everyone, from freelancers to executive stakeholders, stayed in the loop without needing constant check-ins.

“It’s allowed me to operate like I’m part of a much bigger team. The briefs are clearer, and I’ve heard directly from freelancers that communication has improved.”

Now, Lauren has the headspace to think strategically. She’s no longer drowning in task-chasing or disconnected tools.

“There’s just more headspace now,” she said. “I feel like I’m finally leading content, not reacting to it.”

“Without Relato, my mind would break. My process would fall apart, communication would break down, and our content output would definitely suffer. I couldn’t be more thrilled with the tool and the collaboration we’ve had with the Relato team.”

Relato helped Rally turn scattered work into a scalable system.

What a repeatable content process actually looks like

The word people reach for is “process,” but what Rally really built was a repeatable content process: the same steps, in the same place, every time a piece moves from idea to publish. Strip away the tool names and the pattern underneath is simple enough to copy.

Capture ideas in one inbox. Every request, half-formed thought, and stakeholder ask lands in the same place instead of scattering across Slack, sticky notes, and passing hallway comments.

Turn the idea into a brief before anyone writes. A clear brief is the contract. Rally’s freelancers stopped guessing at scope because the brief traveled with the work.

Assign, then make status visible. Who owns it and where it stands both live on the project, so nobody schedules a meeting just to ask “is this done yet.” Assigning only works if the owner can actually decline a comment, which is why it pays to define what content ownership means before you start putting names on cards.

Keep feedback in context. Edits and approvals sit next to the draft, not buried in an email thread, which is what stops a review from stalling for days.

Publish, then reuse. Finished work stays findable, so the next quarter’s repurposing starts from a shelf instead of a search.

Run those five steps the same way each time and the process stops depending on any one person’s memory. That is the difference between a system and a to-do list, and it is the same foundation we describe in our guide to operationalizing your content strategy.

How to scale content output without hiring more writers

Rally’s goal was 3-4 blogs a month with a one-person core team. The instinct in that spot is to add freelancers until the numbers work. The cheaper lever is to scale the system so the people you already have spend their hours writing, not chasing files.

That is what the single hub did. Centralizing briefs, assignments, and feedback removed the busywork tax that quietly caps a small team’s output, so Lauren could grow production without growing headcount. It is the same principle behind scaling a content program without sacrificing quality: fix the workflow first, and the extra capacity is already sitting in your week. For distributed teams leaning on freelancers and agency partners, that visible, shared workflow is what keeps quality steady as more hands touch the work.

How do you scale content production without losing quality?

You protect the two places quality actually leaks: the brief and the review.

Most teams try to hold the line with a style guide and good intentions, then watch both give way quietly as volume rises. The brief gets thinner because writing it properly takes twenty minutes nobody has. The review gets skipped because the draft landed late and the slot is today. Neither failure announces itself. You just notice, two quarters later, that the blog reads like nine different people wrote it.

Rally’s answer was to make both steps unskippable by making them cheap. The brief lived on the project, so a freelancer opened the work and found the scope already written, which is most of what good freelance onboarding is trying to achieve anyway. Feedback sat next to the draft instead of in an email thread, so an edit cost a comment rather than a meeting, and the editorial feedback arrived while the writer still had the piece in their head. Lauren put it plainly: “The briefs are clearer, and I’ve heard directly from freelancers that communication has improved.”

Quality at volume depends less on talent than on whether your standards survive a busy week. If the brief is a chore, it gets skipped. If it is already half-written and sits where the work sits, it does not.

One caveat worth stating, because this is where the promise usually oversells itself. A repeatable process keeps quality steady. It does not raise a ceiling you never set. A clear brief written against a vague strategy produces consistent, on-time, forgettable articles. Decide what good looks like first, then use the system to hold it.

What a content production team looks like at this size

Lauren was the content production team. One person, a handful of freelancers, and a target of 3-4 posts a month.

That is worth spelling out, because “content production team” usually conjures a pod of specialists: a strategist, two writers, an editor, a designer. Most B2B teams do not look like that. They look like Rally did, with one owner holding the strategy and the calendar while contract writers do the drafting.

The roles still exist at that size. They are just not people. Somebody has to own what gets made, somebody has to write it, somebody has to edit it, and somebody has to press publish. When one person wears three of those four hats, the process carries the load that extra headcount would otherwise carry. That is why a written brief and a visible status matter more for a one-person team than for a nine-person one, not less.

If you are mapping this out for your own team, our breakdown of content team roles covers which hats merge safely and which ones fight each other when one person wears both. And if freelancers do most of your drafting, working with strategy-led freelancers changes what you can hand over, because a writer who understands the strategy needs a lighter brief than one who does not.

Frequently asked questions about building a repeatable content process

What is a repeatable content process?

A repeatable content process is a documented system where every step, from idea to brief to draft to review to publish, runs the same way each time in one place. For Rally UXR that meant moving briefs, freelancer assignments, and approvals out of scattered docs and into a single hub, so the team could produce 3-4 blogs a month without rebuilding the workflow for each piece.

How do you scale content output without hiring more writers?

You scale the system, not the headcount. Rally hit its publishing goals by centralizing requests, briefs, and feedback, so existing writers and freelancers spent less time chasing files and more time producing. Removing the busywork that caps output lets a small team ship more without adding people.

How do you standardize content production across a distributed team?

Give freelancers, new hires, and stakeholders one place to work with clear briefs and visible status. Rally used Relato so anyone could jump in without hand-holding, which kept quality consistent as more people touched the work.

How do you scale content production without losing quality?

Protect the brief and the review, because those are the two places quality leaks when volume rises. Rally kept both by making them cheap to do: the brief lived on the project so freelancers opened the work and found the scope already written, and feedback sat next to the draft rather than in an email thread. Quality at volume depends less on talent than on whether your standards survive a busy week. A clear brief written against a vague strategy still produces forgettable articles, so decide what good looks like before you scale the system that holds it.

How big does a content production team need to be?

Smaller than most teams assume. Rally UXR hit 3-4 blogs a month with one in-house content marketer and a handful of freelance writers. The roles of owner, writer, editor, and publisher all still exist at that size, they are just held by fewer people, which is why a documented process matters more for a one-person team than for a large one.

How long does it take to set up a repeatable content system?

Faster than most teams expect when the tool fits the work. Lauren was managing blog content, creating briefs, adding freelancers, and looping in stakeholders within a week, and Relato became Rally’s single source of truth within a month. If you are starting from scratch rather than migrating, our walkthrough on building a content system with AI and automation covers which stages to automate first and which to leave alone.

Try it yourself, and give your content team one less thing to juggle.