Insights
What a Fractional Data Architect Actually Does (and When You Need One)
When a mid-market company needs senior architecture judgment — but not a full-time executive hire — this is the role that fills the gap.
A fractional data architect gives a mid-market company senior architecture judgment without a full-time executive hire. They decide how your data should be structured, integrated, and governed so the business can trust and act on it — working part-time or per-project. You bring one in when your problem is architectural: reports that contradict each other, systems that don't talk, or a foundation that can't support the questions you need to ask.
Forty years in enterprise data has taught me that the hardest problems are almost always architecture, not technology. The tools are rarely the bottleneck. What decides whether a company's data works is how it's structured, sourced, and governed — and those are decisions that require senior judgment most mid-market companies can't justify hiring full-time.
Who do I hire to fix our data — a person, not another software vendor?
Not a platform, not a licence, not a team of juniors — a senior data architect, working with you directly. You call one in when the problem is the shape of your data, not its contents. In practice, here is what that person does:
- Designing the foundation — how data is consolidated, modeled, and stored so it can be trusted and reused.
- Integrating systems — connecting the tools you already run into one coherent environment instead of a pile of disconnected apps.
- Establishing governance — definitions, ownership, and access, so the same number means the same thing everywhere.
- Setting technical direction — choosing the approach and platform that fit the business, and knowing what not to build.
What's the difference between a data consultant, an analyst, and a fractional data architect?
An analyst works within your existing data to produce reports and insights. A consultant is usually sold as a project or a block of hours, staffed by whoever is free, and gone at the end. An architect decides how the data should exist in the first place — and a fractional one is a single senior person who owns those decisions and stays accountable for them. If your dashboards keep disagreeing, if every integration is a custom project, or if new questions trigger fire drills, no amount of analysis will fix it — the problem is upstream, in the architecture.
How do I know if I actually need one?
- Your reports contradict each other and no one trusts the numbers.
- Your systems don't talk, and integrations keep becoming multi-month projects.
- You're about to buy a platform and want to be sure you're solving the right problem.
- You're heading toward a sale and need your data house in order.
- You need senior judgment for a defined period — not a permanent six-figure hire.
The tools are rarely the bottleneck. The architecture is.
Can I hire a data architect part-time?
Fortune 500 companies employ teams of architects. Mid-market companies have the same architectural problems and a fraction of the budget — but the problems don't scale down just because the company is smaller. A fractional arrangement gives you access to senior architecture judgment for the weeks or months when the decisions are being made, then steps back. You pay for the judgment when it matters most, not for a permanent seat.
This is the spirit of the selective engagements I take on: a small number of projects where the problem is genuinely hard, the timeline is tight, and getting the architecture right changes what the business can do next.
More often than not, this hands-on architecture work is the companion to a broader fractional Chief Data Officer engagement — the same senior seat, with the executive ownership, governance, and board reporting layered on top. You can take the architecture work on its own, or as the delivery layer under the CDO role.
Free Resource
The Mid-Market Analytics Readiness Checklist
Twelve honest questions to tell you whether your data is ready to drive decisions — or whether you've quietly outgrown spreadsheets.
Get the checklist →Frequently asked questions
Who do I hire to fix our data — a software vendor, or a person?
A person. A licence is not an agreement about what your numbers mean. You bring in a senior data architect to decide how your data is structured, integrated, and governed, and then the tools serve that decision instead of standing in for it. That is the work I do.
What's the difference between a data consultant and a fractional data architect?
A consultant is often sold as a project or a block of hours, staffed by whoever is available, and gone at the end. A fractional data architect is one senior person, on a fixed arrangement, who owns the architectural decisions and stays accountable for them — typically a day or two a month, for the months it matters.
Can someone assess our data in a few weeks, not a few months?
Yes. A Data Readiness Assessment is a fixed-fee, three-week engagement I deliver myself — an honest read on whether your data can support the decision in front of you, with a plan you can act on. No open-ended discovery, no team of juniors learning on your time.
I want an independent opinion, not a sales pitch — is that what this is?
Yes, and sometimes the opinion is 'not yet.' If one person can still tell you where everything lives, you probably don't need me — and I would rather tell you that than sell you an engagement. That is the point of bringing in someone with no platform to push.
When do I need a data architect versus a data analyst?
An analyst works within the data you already have to produce reports. An architect decides how that data should exist in the first place. If your dashboards keep disagreeing, every integration becomes a project, or new questions trigger fire drills, that is an architecture problem — and no amount of analysis fixes it.