Runneth/Customer Stories/Open English

Open English · Signal to brief

The weekly meeting, replaced with a pipeline

Nina gave Runneth her problem in plain language on a Sunday and walked away with a pipeline that runs the entire creative operation in Slack.

1 Sunday
from problem to pipeline
Slack
where the operation runs
Org-wide
adoption beyond paid
Customer story
The situation

Nina was stuck.

Open English runs its entire creative operation in Slack on Runneth, replacing a weekly meeting with rapid voting on ideas and a smooth signal-to-brief production process.

She knew their team could go from idea to briefing faster, but things got bogged down with meetings, conflicting ideas of what would work, and back-and-forth between the growth and brand team.

The bottleneck wasn't talent or ideas. It was the process between the idea and the brief, and the meetings that kept the two teams out of sync.

The turn

A pipeline that runs the whole creative operation.

Nina sat down with Runneth on a Sunday, gave it her problem in plain language, and walked away with a pipeline that now runs the entire creative operation in Slack.

They replaced a weekly meeting with rapid voting on creative ideas right in Slack and a smooth signal-to-brief production process.

What started as a paid-team workflow has spread across the org. Copy, brand, email, and organic all pulling Runneth into how they work.
1

Sunday from plain-language problem to live pipeline

Nina described the problem in her own words and Runneth built the workflow. Now copy, brand, email, and organic are all pulling it into how they work.

What Nina built with Runneth

From a paid-team workflow to a marketing-wide operating system.

Signal-to-brief pipeline

Signal-to-brief pipeline

Rapid voting on creative ideas in Slack feeds a smooth production process that turns signal into briefs, no weekly meeting required.

Marketing-wide AI adoption

Marketing-wide AI adoption

What started on the paid team spread to copy, brand, email, and organic, all working through Runneth.

Brand-team reports

Brand-team reports

The brand team gets the reporting it needs from the same system, keeping growth and brand in sync instead of in meetings.

More customer stories

See how other teams put Runneth to work.

Everyday Dose

The pipeline, replaced with a URL

Travis swapped manual insight decks for one live dashboard and daily Slack alerts on what's winning.

Read the story →
Cozy Earth

QA that runs without her

Katie taught Runneth her video ad QA standards. The first pass now runs in Slack, even on vacation.

Read the story →
Available now on Motion

Put Runneth to work on your creative operation

Give Runneth your context in plain language and watch it turn signal into briefs, reports, and live workflows.

Activate RunnethTalk to an Expert
FAQ

Frequently asked questions

How does Open English use Runneth for creative production?

Open English runs its creative operation in Slack on Runneth. A weekly meeting was replaced with rapid voting on creative ideas, feeding a smooth signal-to-brief production process that gets the team from idea to brief faster.

How long did it take Open English to set up Runneth?

Nina sat down with Runneth on a Sunday, described the problem in plain language, and walked away with a working pipeline. There was no long implementation project, the workflow came out of one conversation.

Can Runneth keep growth and brand teams in sync?

Yes. Open English replaced the back-and-forth between growth and brand with rapid voting in Slack and shared brand-team reports, so both teams work from the same process instead of conflicting meetings.

Does Runneth adoption spread beyond the paid team?

At Open English it did. What started as a paid-team workflow spread across the org, with copy, brand, email, and organic all pulling Runneth into how they work.