People, not platforms.
A small UK team, a fixed fee, and your own people building alongside us. Here’s what a project looks like, from the first call to the day you take it over.
Before anything starts
A free conversation. Thirty minutes, and you’ll know by the end whether there’s anything here for you.
Agree what good looks like. We look at your data, your process and your reports, and agree goals you can measure – how long things take now, and how long you want them to take. Whoever signs off the spend sees those goals too, so nobody is surprised at the end.
A fixed fee. You get a scope and a number, and the number on the proposal is the number on the invoice. If the scope changes we talk about it first – nobody likes a surprise line item.
Your IT team, looked after. Before you sign, your IT team gets an IT impact assessment from us. It covers security, how much of their time we need (typically not much!), and our policy that we don’t log into or change any of your systems – apart from the new platform itself, and an automation account that you own.
How a project runs
Every project goes through the same five stages. Most have more than one phase, though, so different parts go live at different times.
Prepare. Once you’ve signed, we book a welcome call. We agree the timeline, and who on your side does what – the core team, the people who’ll test it, and the early adopters who’ll help bring everyone else along. You get a short guide to what you can get ready in the meantime.
Design. A kickoff workshop, once we’ve been through your materials – usually a full day at your offices, with everyone who has a stake in it. We set out how the project will run, when we’ll need each of you, and check we’ve properly understood what you need.
Build. We build in phases, starting with the quickest win – often reporting, which goes from a timesink to a few clicks. Your team builds alongside us as much as possible: it keeps the cost down, and it means you can run and extend it yourselves afterwards.
Test. We test our own work and check the numbers. But nobody knows your data like you do, so your team tests it too: that people can get in, see only what they should, and that everything works the way they expect. We’ll help you plan that, and plan how you tell everyone else it’s coming.
Launch. Each phase is signed off when you’re happy with it. Your team is trained on your own system, not a generic course.
After go-live
Some teams take it over completely, which is fine and is usually the plan. Others would rather not own the admin, and we can keep it ticking over instead.
We’re always here if you need us. Where required, we have a choice of support options; either simple packs of hours, or a set number of hours each month at a lower rate.
What’s true all the way through
A small UK team. Working directly with you – no offshore delivery arm and nobody you haven’t met.
Out in the open. Everything runs through Teamwork.com, which you have access to, so you can see exactly what’s left to do.
A weekly catch-up. A status call as often as once a week, or less if that suits you better.
Recorded and transcribed. Calls are recorded and transcribed, so decisions are written down rather than remembered. Including when we’re onsite together, with dedicated meeting room recording hardware from Plaud.
Mostly remote. Most of the work is done remotely to be flexible around your day to day. The kickoff workshop is the day we advise to be in person; that time sets us up for successful remote work together.
AI in our own work. Teamwork.com and our call notes are connected to the AI tools we use, so actions from a call are written up straight away.
What we’ll ask of you
Someone who owns it. One person on your side who keeps an eye on the project and on your side’s tasks, and can make decisions or knows who can.
Time, at the right moments. Timings depend on your availability, typically more than ours, so it helps to know early when your people are free – especially for testing.
Access, early. Logins and exports from the systems that feed the project, in the first week or two.
Honest answers. If a report is never read, or a number is always adjusted by hand, tell us. It’s much cheaper to fix in the plan than after the build.
Questions people ask
How do you price projects?
Fixed fee, agreed before anything starts. You get a scope and a number, and the number on the proposal is the number on the invoice. If the scope changes we talk about it first – nobody likes a surprise line item.
How long does a first phase take?
Usually weeks rather than quarters, but it’s a little bit “how long is a piece of string” until we know the state of your data, and what you want to do. What we do shoot for is something live and usable, quickly, to start getting you a return on your investment.
Do we need our data sorted out first?
No, and if you wait for that you will wait a long time. Getting the data usable is part of the work, and it is normally one of the biggest parts. What helps is knowing which system is the master for each thing – that conversation is worth having early.
Who actually does the work?
A small UK team, working directly with you – no offshore delivery arm and nobody you haven’t met. Everything is run through Teamwork.com, which lets you see exactly what’s left to do, and calls are recorded and transcribed so decisions are written down rather than remembered.
What happens after go-live?
Whatever you want to happen. Some teams take it over completely, which is fine and is usually the plan. Others would rather not own the admin, and we can keep the model, the integrations and the calendar ticking over instead. We’re always here if you need us.
Start with a conversation that has a scope.
Thirty minutes, free, and you’ll know by the end whether there’s anything here for you. Most of the organisations we speak with aren’t looking to buy anything right now – we’re happy to educate and inform, for when the time is right.