You have a digital project on the table, a website to rebuild, an integration between two tools or a product to launch, and nobody in-house to run it. Hiring would take months and an agency feels too heavy. So you look for a freelance digital project director, without knowing exactly what they will spend their days doing.
I do this work on my own, as SLX Management: I design and build things myself, in France and the United Kingdom. This piece describes the role as I practise it, the cases where a freelancer is the right arrangement and those where it is not, and the documents to ask for in the first week.
01What a digital project director actually does
The Project Management Institute defines project management as the application of knowledge, skills, tools and techniques to project activities to meet project requirements. It lists the basic moves: defining scope, identifying deliverables, managing risks, keeping communication flowing between teams. The Grow with Google video on the job, of which I could only read the description, sums up the same thing: plan, organise tasks, keep budget and costs in check so the project lands within the approved timeframe.
On a digital project, those moves take a specific shape. The project director holds three threads at once:
- the business thread, what the company wants to achieve and what users will actually do;
- the technical thread, what the tools allow, the integrations, the data, the go-live;
- the decision thread, who decides what, when, and where it is written down.
The difference from a project manager lies mostly in the third thread. A project manager moves a workstream forward; a project director gets scope, date and budget agreed with the leadership team, and coordinates several suppliers when there are several. In a small organisation it is often the same person, and that is fine.
02When a freelancer is the right choice, and when it is not
A freelance project director suits a project with clear limits in time: a start, a go-live and a handover. It also suits cases where you need someone who understands both marketing and engineering, so the two sides stop passing the problem back and forth.
It is a poor fit in three situations, and I would rather say so before anything is signed:
- The project needs a long presence, several months full time in your offices. That is a job, not an assignment, and hiring will be healthier.
- You need a production team (developers, designers, writers) rather than someone to run it. An agency or an integrator will serve you better.
- The system involved needs on-call cover or managed services. One person cannot promise to answer at night.
In my case, I do not do long-term staffing, SAP rebuilds, native mobile apps or managed services. Be wary of a freelancer who does not tell you what they do not do: they may say yes to everything.
03What an assignment looks like, from the first week to the handover
My assignments are short and follow the same structure. It is simple on purpose: at every stage you know what you will have in hand at the end.
The first week: the diagnosis
I spend a few days reading what exists and listening to the people who will build or live with the project. I come out of it with a short document: the problem as I understand it, the proposed scope, the risks I see, what I do not know yet and who needs to answer. If the diagnosis shows the project does not need me, I say so.
The build, live with you
Then I build, live, with you. I write the specification, put the prototype together, configure the tools and test. When there are suppliers, I coordinate them and review what they deliver. Keeping a tracking spreadsheet is not enough in my view: you have to get your hands into the project to see where it sticks.
I learnt this discipline early, in film and video production, where a budget, a schedule and a crew are held together by a date that does not move. You do not push back a shoot because a decision was not made: you get it made.
The handover: leaving without a gap
The last stage is the handover. Everything I have built is documented so your team can take it over: where the settings live, how to publish, who to call if something breaks. To me, a successful assignment is one after which you no longer need me.
I run my own projects the same way. For Moonworkers, my payroll software company, I rebuilt the marketing site in Next.js and Sanity in May 2026, with free calculators checked one by one against the official tools. The details are on the Moonworkers page.
04The documents that keep a project aligned
I judge a project director by their documents more than by their meetings. Here are the ones I put in place, and that you can ask any supplier for.
- A versioned specification. On an assignment for a client, an integration between an ERP and an online shop, the specification changed at almost every meeting. I updated it version after version, so everyone was talking about the same document. I describe the method in my piece on integration specifications.
- A decision log: one line per decision, with the date, who decided and why. It stops the same debates reopening every fortnight.
- A prototype or mock-ups before development. Showing several design directions at the same level of finish moves a decision forward faster than a long discussion. I cover this in the piece on clickable prototypes.
- A regular decision meeting. A report that goes out on its own every month and a committee that decides are worth more than a dashboard nobody reads. The format I use is in the piece on the monthly marketing committee.
- Acceptance tests written before go-live, and a check done as a visitor would. A site can look fine to the logged-in team and be broken for visitors, because of a cache for instance. My list is in the acceptance testing and go-live checklist.
On point 4, the Scrum Guide says two things I find useful even outside Scrum. The Product Owner is one person, not a committee. And the sprint review is a working session where you inspect the outcome to decide what comes next, not a presentation. So from the start I ask who, on your side, has the final say.
05What a freelance project director cannot replace
The first risk with a freelancer is dependency. One person means one diary and one memory. I deal with it by documenting from day one, but I do not claim to remove it: if I am ill for a week, the project slows down. Better to know that and plan who on your side can pick up the threads.
The second is decision-making. I can prepare a choice, set out the options and their consequences, but I cannot decide in place of management. A project where nobody decides does not move faster with an outside project director; it just has one more person watching it stall.
The third is contractual, and it is often forgotten. In France, above a certain contract value, the client must obtain a vigilance certificate from its supplier and renew it for the whole assignment, as the Service Public Entreprendre page explains (in French). In the UK, the IR35 rules cover contractors who work through their own company, and it is generally the medium or large client who determines their status, according to HMRC's page on GOV.UK. Giving legal advice is not my role, but a serious supplier hands you the relevant paperwork without being chased for it.
06Where to start if you are looking for someone
Before contacting anyone, write one page: what you want live and by when, what already exists, who will decide on your side, and what worries you most. It will serve you better than a long tender, and it will quickly show you whether the person in front of you asks the right questions or recites a sales pitch.
In the first conversation, ask for three things: an example of a document they produce (a specification, a decision record), what they do not do, and how they plan to leave. If the answers stay vague, move on, however good the profile looks.
If your project looks like what I describe here, you will find how I work on the SLX Management services page. Happy to talk it through.