Why Fractional?
Why not just hire a full-time data architect?
You might not need one yet. Senior data architects cost €150-250K+ fully loaded. If you need architecture direction but don’t have 40 hours of architecture work per week, fractional makes more sense.
Fractional also gives you:
- Faster start - No 3-6 month recruiting process
- Lower risk - If priorities shift, you’re not stuck with a full-time hire
- Cross-pollination - I bring patterns from other companies and industries
- No management overhead - No performance reviews, career development, or team dynamics to manage
Many clients eventually hire full-time. Fractional bridges the gap until that makes sense - and I can help you hire when you’re ready.
When should we hire full-time instead?
Hire full-time when:
- You have 40+ hours per week of architecture work
- You need someone deeply embedded in company culture and politics
- You’re building a large data org (10+ engineers) that needs full-time leadership
- You’ve stabilized your architecture and need long-term stewardship
If you’re not sure, start fractional. You’ll learn what you actually need.
How is this different from hiring a consultant?
Traditional consultants often work in isolation, deliver a report, and leave. I work with your team, not around them.
The goal is building your team’s capability, not creating dependency on external expertise. I’ll help you hire, train, and structure your team so you can continue without me.
How It Works
How much time do you typically spend with clients?
Most fractional engagements are 1-3 days per week. Some clients need more during intense periods (migrations, major incidents, funding rounds), less during stable periods.
Advisory clients might be a few hours per month for specific decisions.
Do you write code or just advise?
Both. I’m hands-on when it helps - reviewing PRs, pairing on complex problems, building proof-of-concepts. But the primary value is architecture decisions, team guidance, and stakeholder alignment.
I’m not a staff augmentation resource. If you need more engineering hours, I’ll help you hire.
Can you work with our existing team?
That’s the whole point. I work alongside your engineers, not instead of them. I’ll pair with them, review their work, help them level up, and gradually transfer knowledge so they can own the architecture.
What if we already have a data architect?
Then you might need advisory rather than fractional work. Or your architect might benefit from a senior sounding board - architecture can be lonely when you’re the only one thinking at that level.
How do you handle sensitive data and IP?
I sign NDAs and treat client information with the same confidentiality as an employee would. I don’t share specifics between clients, though I do bring patterns and approaches that work across contexts.
Getting Started
What does the first month look like?
Typically:
Week 1-2: Discovery and assessment. I learn your codebase, talk to your team, understand the pain points, and review your current architecture.
Week 3-4: Quick wins and roadmap. We address immediate issues while building a longer-term plan. You’ll see value fast, not after months of analysis.
By month end, we’ll have clarity on priorities and a working rhythm that fits your team.
Do we need to commit long-term?
No. Most engagements start with a focused piece of work - a platform review, an architecture sprint, or a specific problem. This builds context before either of us commits to ongoing work.
If ongoing fractional makes sense, great. If not, you’ve still gotten value from the initial engagement.
What if it’s not a good fit?
Then we stop. I’d rather end an engagement that isn’t working than drag it out. You’ll have learned something about what you need, and I’ll help you find the right resource even if it’s not me.
Pricing & Logistics
How much does this cost?
I work on a day-rate basis. Specific rates depend on:
- Type of engagement (fractional, project, advisory)
- Commitment level (more days = lower day rate)
- Scope and complexity
We’ll discuss specifics after the discovery call when I understand what you need. If budget is a constraint, we can usually find an engagement structure that works.
Where are you based?
Belgium (Hamme). I work:
- Belgium: Hybrid (on-site + remote)
- Europe: Remote, with occasional travel
- Global: Remote
Time zones matter for real-time collaboration. I can flex hours for US clients, but deep overlap works better than async-only.
How quickly can you start?
Usually within 1-2 weeks of agreeing to work together. I keep some buffer in my schedule for new engagements.
If you need someone tomorrow, I might not be the right fit - but I can often recommend alternatives.
Specific Situations
We’re a startup with limited budget. Can we still work together?
Possibly. Early-stage startups often benefit most from advisory rather than fractional - a few hours per month to sanity-check decisions and avoid expensive mistakes.
I also occasionally do smaller project-based work for startups I find interesting.
We’re preparing for due diligence / funding round. Can you help?
Yes. This is a common engagement pattern. I help you:
- Document your architecture clearly
- Address obvious red flags before investors see them
- Prepare technical answers for due diligence questions
- Build a credible data roadmap
We have a data emergency (outage, major incident, critical migration). Can you help fast?
Sometimes. If I have capacity and the problem is in my wheelhouse, I can often jump in quickly. Reach out and we’ll see what’s possible.
We’re a vendor. Can you help with technical content or pre-sales?
Yes - that’s what Thought Leadership and Technical Pre-Sales are for. I help data vendors create credible technical content and support sales conversations with independent practitioner perspective.
Still Have Questions?
Book a 30-minute call to discuss your specific situation. No pitch - just an honest conversation about whether I can help.
How I Work | Services | About