Start a mission
What to send. Then the first month.
Team, stack, constraint, 90-day outcome. The form lives on Contact — this page is the brief, not a second inbox.
The brief
Four things. One conversation.
01
Team
Who owns the channel today. Who can kill a send or a post without a workshop. Who legal actually is. If that list is empty, say so.
02
Stack
What you already pay for — ESP, social suite, analytics. Fluency is the point. A tool you plan to buy next year is not a stack.
03
Constraint
What is broken, missing, or colliding. Duplicate sends. A relaunch with no week. Three agencies and no calendar. One sentence is better than a war room.
04
90-day outcome
What “held” looks like. A living booking path. An editorial seat that survives a quiet month. A weekly the team can run. Independence is a valid outcome.
First month
Four weeks. An operating floor.
Week 1
Brief and access
Constraint named. Logins, domains, calendars. Who can change the week. No chemistry lunch.
Week 2
Diagnose
Kill list. Which journeys, posts, and queues are theatre. The number the VP already believes.
Week 3
Install
Architecture, calendar, stop rules. Legal path named. The first artefacts the weekly can use.
Week 4
First operating week
Something ships under the new rules. A readout that is an operating room, not a slide tour. Then the rest of the mission has a floor.
Next
The form is on Contact. Use it.
Name, company, and the four things above. It sends to hello@mbxconsult.com via Web3Forms. There is not a second form here.