Project Advisory
You're managing a technical project. You didn't sign up to become a tech person.
Maybe you're a marketing manager who's been handed a website rebuild. A founder managing their first developer. Someone who approved a contract and now something feels off - but you can't quite name it.
You don't need someone to take over. You need someone experienced to think alongside you - to help you understand what you're hearing, ask the right questions, and make decisions without second-guessing yourself at every turn.
What You Get
Project Second Opinion
For a specific proposal, estimate, scope change, or technical decision you don't feel confident evaluating alone.
What this includes
- Review of the relevant proposal, estimate, or project material before we talk
- One focused conversation (60–75 min)
- A plain-language explanation of the trade-offs
- Questions worth asking before you proceed
- A short written assessment with risks and recommended next steps
An independent second opinion for one decision or situation - not a code audit, legal review, or guarantee that every technical detail is correct.
Advisory Cycle
For an active project where you want an experienced, independent perspective alongside you without adding another manager to the team.
What this looks like
- One kickoff conversation and three weekly check-ins
- Focused review of up to three important proposals, estimates, documents, or decisions
- Async questions between calls, answered within one business day
- Help preparing for important or difficult conversations with your delivery team
- A closing summary covering decisions, unresolved risks, and recommended next steps
Best suited for small-to-medium projects - a website build, a platform upgrade, or a first engagement with a freelancer or agency. Extend by 2 weeks for €500 if your project needs longer support.
Common Scenarios
"I've been asked to manage a web project and I don't really know where to start"
We start by getting oriented together - what's being built, who's involved, what decisions are coming. You don't need to figure out the right questions alone.
"A developer sent me a proposal and I'm not sure if it's reasonable"
We go through it together. I'm not a substitute for a deep technical audit, but I'll help you understand the trade-offs, spot the unanswered questions, and know what to clarify before you sign.
"Something feels off but I can't explain what"
That feeling is worth examining. We slow down, name what's bothering you, and figure out if it needs addressing - and how.
"The timeline keeps slipping and I don't know how to push back"
We work out what's actually happening and what a reasonable response looks like. Sometimes it's a conversation. Sometimes it's a scope decision. I help you figure out which.
"I need to explain a technical decision to my boss or stakeholders"
I can help you translate what's happening into language that makes sense to people who aren't close to the project.
"We built something with AI and don't know what state it is in"
We establish what you actually have, which questions can be answered from the available material, and where a specialist review may be needed. Then we decide on a sensible next step instead of continuing blindly.
What This Isn't
- Not project management
- Your team handles day-to-day. I'm your thinking partner, not their manager.
- Not a technical audit
- I can help you understand and question decisions, but I won't always have the definitive technical answer.
- Not crisis intervention
- This works best when engaged early, not when a project is already on fire.
- Not unlimited
- Focused scope, clear timeframe. Enough to be genuinely useful without becoming a dependency.
The goal isn't to make you a tech person. It's to make sure you're not alone in a room where everyone else speaks a language you don't.
We'll talk through your project and I'll tell you honestly whether I think I can help.
Ready to talk?
Tell me what you're working on. We'll figure out the rest.