Skip to content

Blog

Fractional Solution Architect: When It Makes Sense

What a fractional solution architect does, when part-time architecture beats a full-time hire or a one-off review, how the arrangement usually works, and what to expect.

3 min read · Dino Correia
solution-architecturefractionalhiring

TL;DR

  • A fractional solution architect is a senior architect who works part-time with your team over months, owning the design and the key decisions.
  • It fits teams without a senior architect who need one for a period of change, but not full-time or not yet.
  • It works best with a clear remit, a regular rhythm, and decisions written down where the team can find them.
  • It is the wrong fit if you need someone in every meeting every day, or if nobody will act on the decisions.

A fractional solution architect is a senior architect who works with your team part-time, typically a day or two a week over several months, and owns the design and the important technical decisions while the system is being built. It sits between a one-off review and a full-time hire: more continuity than a consultant who visits once, less cost and commitment than a permanent senior role.

When it makes sense

  • You’re about to build something significant and nobody on the team has designed a system of that size before.
  • You’re in a period of change, such as a migration, a replatform, or a run of integrations, that needs senior ownership for months, not years.
  • You need architecture before you can justify a full-time hire, or while you search for one.
  • Your senior engineers are stretched, and design decisions are being made in a hurry or not at all.
  • You’ve had a review and need someone to carry it through.

When it doesn’t

  • You need someone in every stand-up and every incident, every day. That’s a full-time role.
  • The decisions won’t be acted on, because nobody has the authority or the time.
  • The work is mostly building, not deciding. A contract engineer fits better.

What the role usually covers

ResponsibilityWhat it looks like in practice
Architecture ownershipKeeps the overall design coherent as features are added
DecisionsFrames the options, makes or recommends the call, and writes it down
Design reviewsReviews technical plans before they’re built, not after
Support for engineering leadsA sounding board for the people making day-to-day choices
Stakeholder communicationExplains trade-offs to non-technical leaders in their terms
RiskKeeps an eye on the things that would be expensive to discover late

How the arrangement usually works

  • A clear remit. One or two outcomes to own, such as “the migration off the old platform” or “the integration layer”, rather than “help with architecture”.
  • A regular rhythm. Fixed days each week, so the team knows when to bring questions, plus a way to reach them in between for urgent decisions.
  • Written decisions. Decision records in the team’s own docs, so the reasoning outlasts the engagement.
  • A defined end, or review point. Every few months, agree whether to continue, change the remit, or hand over.

It often starts well after a short, fixed-scope piece of work, such as an architecture review, because both sides then understand the problem before committing to months together.

Fractional, contract, or full-time?

Fractional architectContract architectFull-time hire
TimePart-time, ongoingFull-time, fixed termFull-time, permanent
Best forOwnership through a period of changeA large programme needing daily presenceLong-term ownership of the platform
CostLowest of the threeHigher, for a defined periodSalary, equity, and hiring time
Ramp-upDays to weeksDays to weeksMonths, including the search

If this sounds like your situation, the fractional or contract architect option is how I work in this shape, part-time alongside your team or on a full contract.

Where this leads

  1. If this is the situation you're in

    Fractional or Contract Architect →

    Your solutions architect for as long as the work needs one: part-time alongside your team, or on a full contract.

  2. Or skip ahead

    Let's talk: tell me about the problem →

Related articles

Blog

Architecture Review: What It Covers and When You Need One

What a software architecture review looks at, when it is worth doing, what you should get at the end, and how to prepare so it answers the questions you actually have.

· 3 min read
architecture-reviewsolution-architecturetechnical-decision-making
Read →

Blog

Technical Due Diligence Checklist: What to Look At

A technical due diligence checklist for investors and acquirers: architecture, code and delivery, data, security, infrastructure costs, third-party dependencies, and the team.

· 3 min read
architecture-reviewchecklisttechnical-decision-making
Read →

Blog

Solution Architecture Document: What to Include (+ Template)

What to include in a solution architecture document: problem, requirements, options, design, integrations, data, risks, and decisions. Template included.

· 7 min read
solution-architecturedocumentationdecision-records
Read →

Working through something similar?

I help untangle problems like this one.