Issue 1: the operations behind growth
Growth Ops Weekly covers the systems, data and tooling that growth runs on, and the people who keep them working.
By Growth Ops Weekly staff1 min read
Every growth number sits on top of an operation. A lead has to be routed before it can be worked. A field has to be filled before it can be reported. A sequence has to be connected to the CRM before anyone can say whether it worked. When the operation is wrong, the number is wrong, and nobody finds out until the quarterly review.
Growth Ops Weekly is for the people who run that operation.
What an issue covers
Systems: the CRM, the marketing platform, the data warehouse and how they talk to each other. Data: hygiene, enrichment, deduplication and the quiet decay of every field. Tooling: what connects what, what it costs, and what broke in the last release. Automation: the workflows that run without a person, and now the AI agents starting to take parts of the job. And careers, because this work is a career now and it helps to see how other people do it.
Something you can set up this week
Each issue has at least one thing an operator can set up before Friday: a routing rule, a report, a cleanup, a check. We describe it in enough detail to do it, with the tool named and the steps written out.
How we check
Against the tools' own documentation, in live accounts where we have them, and with the operators who do this every day. A vendor's claim is the vendor's claim until we have seen it work.
Who publishes this
Growth Ops Weekly is published by Good Standing Media. When an issue concerns a company the publisher has a stake in, it says so at the top.
Contact
hello@growthopsweekly.com. Tell us what broke this week.