Before starting a project, you need a budget, but above all a framework: duration, pace, and how the handover will work. Here's how I operate
My benchmarks for sizing an engagement, before putting a number on anything
That's my benchmark, whatever the pace. Beyond that, we redefine the project together, to keep the topics clearly separate
Never more than a year. A project that runs longer is no longer about building, it's about running. And that's not what I do
The engagement sets a pace that stays adjustable within the month for maximum flexibility: say 3 days one week, 1 day the next
If the project ends earlier, you only pay for the days used: the budget is a framework, not a minimum to fund. And if one month runs over, we can adjust by mutual agreement
I bring expertise and a method, which go hand in hand. Without real decision-making power, I can't move forward efficiently or deliver the best possible result
I work remotely by default, on site when it makes sense and geography allows. If needed, we discuss it at scoping to check feasibility
Pick a pace and a duration, the calculator adapts
The day rate is of course open to discussion, depending on the length and pace of the engagement
It's the cornerstone of any build project, not the last box to tick
A project where nobody can name the end or the successor isn't a defined project yet. If that's your case, that's where we start, and it's already a good chunk of the work
I'm not here to create one more dependency, but to build something that runs on its own, once I'm gone: tools your teams master, processes they own, and know-how that stays in the company
So from the scoping stage, we answer three questions
3 forms, usually combined
Skills transfer to whoever will run things day to day: training their team, handing over the documentation, and a supported transition
I have partners I can recommend, if needed
Hiring one or more people to handle day-to-day operations, so the know-how stays in-house
I can define the role, run the technical interviews, then handle the upskilling until they're fully autonomous
It's a key part of my model: your processes written down, organized, and above all kept up to date by your teams over time. A shared brain for the company, so nobody is left high and dry when someone leaves
The framework above follows directly from them
An official mandate, and a role announced to the teams
Full delegation over the agreed scope
A 1 to 12-month project, with a clear objective
An end date or final deliverable, with a successor
The first conversation is free and with no commitment, to talk about your project and discuss the framework 🙂