The date's in the diary. Dev says six weeks. Marketing says the assets land next month. Sales is waiting on a price list nobody's approved. Everyone's working hard, and nobody has the one list.
The offer, so you don't have to scroll: one owner, one plan, one date that holds.
Monday, 8:47am.
The launch date was announced at the away day. It felt real then. That was eleven weeks ago, and the date hasn't moved, but everything around it has.
Dev is “80% confident.” The agency has sent the assets as a PDF of screenshots with “final_v4_REAL” in the filename. Compliance saw the onboarding flow for the first time on Tuesday and has, politely, opened fire. Nobody is doing anything wrong. Everybody is doing their own list.
Wednesday's standup, when someone asks who owns the app-store submission, and the silence lasts exactly long enough for everyone to realise the answer is “the founder, presumably, at the weekend.”
And the worst part: the product is good. The demos land. The early users get it. The machine is fine; it's the coordination that's a full-time job, being done in the gaps between everyone's real job.
A launch isn't a milestone. It's a commitment with a supply chain, and it needs one owner.
It's almost never the product. It's the three weeks before the date, when coordination becomes the whole job, and everyone's still doing their old one. A launch needs one owner. Not a hero: an owner.
Twenty years of projects, told honestly. The Receipt stories are mine and verifiable. The Pattern stories are composites: details changed, lessons intact.
Four months, 232 sales. I built the whole thing (platform, emails, checkout) so launch morning I had nobody to blame. I checked the cart on my phone, my laptop and a borrowed iPad before the first email went out. Twice. Paranoia, scheduled. It's the only kind that helps.
A pattern, not a client: the founder who submitted the app herself at 2am on launch eve, because the dev agency's scope said “client to create developer account” and nobody had read the appendix. The app was perfect. The paperwork wasn't. Details changed; the Thursday-before scramble hasn't.
My largest single deal at BT (biggest in the division's history) didn't close on charm. It closed because one list existed: every dependency, every signer, every date. When someone asked “what's left?”, the answer fit on a page. That page took a fortnight to build and saved three months.
Appvocado is a partner: a digital agency building apps, streaming (OTT) platforms and websites. This is work I've been part of start to finish, from kickoff to live.
The portfolio includes
Twenty years running enterprise programmes at BT scale. £1.5m largest single deal; critical paths, steering groups and real dates, held for a full year at 100% of target.
I've run the whole launch myself (platform, emails, ads, checkout): 232 course sales in four months. I know what every week of that calendar feels like from the inside.
I've held the £2m programme budget on the other side of the table: writing the scopes, choosing the suppliers, cancelling the ones who drift. I know what "nearly there" means from both chairs.
Projects end in decisions: sign-off, buy-in, adoption. Twenty years of getting to yes without pressure means the decision actually gets made, in writing, and stays made.
"I run projects the way I wanted them run when I held the budget. That's not a slogan; it's a specification, learned from the most expensive seat in the room."
Everything that's left, in order, with an owner and a date on every line. One page: if it doesn't fit, the plan isn't finished. Everyone can see what "done" means, including you.
Every line has a name against it, mostly mine. Status is offered before it's asked for, so nobody spends their week chasing updates that never arrive.
Red, amber, green, without the politics. Bad news travels in 24 hours; good news waits for the weekly. A plan nobody trusts is worse than no plan at all.
Go-live is the midpoint, not the finish line. Handover pack, walkthrough, and a team that knows exactly what happens on day 31, because delivery that doesn't stick isn't delivery.
The numbers above, the launches behind them, and a public ledger of the whole journey: applications, rejections, results, lessons. The highlight reel is boring; the delivery is the evidence.
You bring the product and the date; I'll tell you where the launch is actually leaking, which dependency will bite first, and the first three moves. If I can't help, I'll say so and point you somewhere better.
A pitch. There's nothing to buy on the call except a decision, and you'll know inside ten minutes whether I'm the person to run this.
Start to finish: how the client was found, the need proved, the option proposed, the work delivered.
One owner, one page, one weekly report. Your team does what they're brilliant at, and the launch happens on the day you told the board.
Book the 20-minute callYou'll know inside ten minutes. · Every number on this page is verifiable.