You’re here because
I pay them a fortune and they don’t do what I ask.
It is your product, your money, and your roadmap. So why does it feel like the vendor decides what gets built? When the only people who understand the work are the ones building it, the vendor ends up steering, not you. The tail is wagging the dog. And without a written picture of what you need, their version quietly becomes the spec. This isn’t a tech problem. There’s a knack to giving orders. We’ll get you back in the captain’s chair.Start here
01
Write down what you need.
Plain English, outcomes not features. If it’s not written, the vendor’s version wins by default.
02
Sketch a picture.
Whether it's visual or a process, a picture is worth a thousand words. Go low-tech: Pencil, paper and take a photo with your phone.
03
When is it 'done'.
What you’re paying for, what’s in, what’s out, and what happens when something new comes up. On paper, before more money goes out the door.
Take this with you
Free tool
Your Technical Risk, in Ten Minutes
A free check-up that scores six areas of hidden technical risk, your people, backups, vendors, releases, data and ownership, then shows you on screen where to start. Save the report to keep or share.
Free guide
You’re Not Signing a Contract. You’re Saying “I Do.”
Every vendor you sign is a dependency wearing a vendor’s name tag. How to scope, sign and exit so a vendor going dark on a Friday can’t take you with it.
Recommended first step
Clarity Day
One day, a plain-English diagnosis and a prioritised plan your team can act on now.