ServiceNow ITOM, ITAM, CMDB, custom apps, AI and managed services.
All services

Fractional ServiceNow Architect

Someone should own your ServiceNow architecture.

A fractional architect is a named architect who holds your platform's architecture role part-time: the roadmap, the design authority, the standards, and the oversight of whoever is building on it. The role is led by Brandon Wilson, ServiceNow Certified Technical Architect.

Start with a conversation

Fractional architect
Where a fractional architect sitsYour admins, developers, and partners build. The fractional ServiceNow architect holds the roadmap, the standards, and the decision record, and reviews designs before they are built. The architect reports to leadership on what was decided, what is at risk, and what needs a decision.01 / THE BUILDERSYour admins, developers, and partners02 / DESIGN AUTHORITYFractional architectRoadmap, standards, and a decision record03 / LEADERSHIPReporting to leadershipWhat was decided, what is at risk, what needs a decisionWhere a fractional architect sitsYour admins, developers, and partners build. The fractional ServiceNow architect holds the roadmap, the standards, and the decision record, and reviews designs before they are built. The architect reports to leadership on what was decided, what is at risk, and what needs a decision.01 / THE BUILDERSYour admins, developers,and partners02 / DESIGN AUTHORITYFractional architectRoadmap, standards, anda decision record03 / LEADERSHIPReporting to leadershipWhat was decided, what isat risk, what needsa decision

What a fractional architect is

Think of a fractional CFO. A company that does not need a full-time finance chief still needs someone who holds the role, makes the calls it exists to make, and is still there next quarter. It is not a block of hours, and it is not a project with a fixed scope. What we agree is what the role covers and which decisions it holds.

Who needs a fractional architect

For organizations that run ServiceNow with capable admins and developers, often with a partner or two, but no architect of their own. Someone in leadership is accountable for the platform; nobody is accountable for how it is built. Not for backlog hands (the managed services retainer), a single defined project (an entry engagement), a help desk, or general enterprise architecture.

Signs you need a fractional architect

  • Design decisions are made by whoever is building the request, or by the vendor quoting the work.
  • Nobody can explain why the instance is built the way it is, and nothing is written down.
  • Every project and partner brings its own conventions, and customizations pile up between them.
  • The roadmap is a list of requests, not a sequence with dependencies and owners.
  • Upgrades are deferred because nobody is sure what will break.
  • Device, discovery and telecom tools all write to the CMDB, and nobody has decided which source wins.
  • Leadership asks whether the platform is healthy and gets a ticket count.

What the architect holds

  • The roadmap

    One sequenced roadmap with dependencies and owners, tied to leadership's priorities.

  • Design authority

    Designs above an agreed threshold are reviewed before they are built, whoever builds them; each decision is recorded with its reasoning.

  • Standards and governance

    How the platform is extended, configure versus build, how data enters the CMDB, who approves an exception.

  • Partner and vendor oversight

    Proposals, statements of work and deliverables reviewed from your side of the table.

  • Upgrade and release decisions

    When to upgrade, what must be ready first, a recommendation leadership can act on.

  • Reporting to leadership

    A plain written report: what was decided, what is at risk, what needs a decision.

  • An escalation point

    Admins and developers have an architect for hard design questions.

Cadence

How often the architect works with you, and what happens
RhythmWhat happens
WeeklyDesign and decision session with the platform team
MonthlyWritten platform report for leadership; roadmap review with the platform owner
QuarterlyLeadership review of roadmap, risks and technical debt, and a review of the role itself
As neededUpgrade and release decisions, partner checkpoints, major design reviews
Between sessionsA direct channel for decisions that cannot wait; handling agreed at the start, no response time published

Artifacts you keep: a decision-rights table, an architecture baseline, target architecture and standards, a decision record, a sequenced roadmap, a technical debt and risk register, monthly reports, upgrade recommendations, and a handover pack if the role ends. Platform ownership and the business decisions stay with you.

The fee

A monthly fee, agreed by scope and accountability and set in writing before the role starts. It is not an hourly rate, and hours are not what you are buying.

How it starts

A first conversation at no cost; a short written role definition (scope, decisions held, cadence, reporting line, fee); first weeks with read access to review the platform and set up the decision record; then the standing cadence, reviewed each quarter.

A team mid-project with a partner can start with a design review.

Led by

Brandon Wilson

Founder & Chief Architect

ServiceNow Certified Technical Architect (CTA)

verify on Credly (opens in a new tab)

Compare

Which one do you need?

Fractional ServiceNow Architect compared with the managed services retainer
QuestionFractional ServiceNow ArchitectManaged services retainer
What you buyA role, held by a named architectCapacity: architecture and delivery hours
UnitScope and accountabilityHours per month, in three tiers
Who sets the agendaThe architect, with your platform ownerYou: the backlog in the order you set
What comes outDecisions, standards, a roadmap, reviews, reportsCompleted backlog items, health checks, fixes
Who buildsYour team, your partner, or Emetrix retainer hoursEmetrix
How it startsA conversation, then a written role definitionA Platform Health Baseline
PriceMonthly fee by scope; not publishedPublished tiers

Fractional architect questions

We have admins and developers. Why an architect?

They build what is asked for. An architect decides what should be built, how it fits, and what should not be built at all.

Our implementation partner provides an architect.

A partner's architect answers to the partner's project and leaves when it ends. A fractional architect answers to you, stays between projects, and reviews the partner's designs on your behalf.

Why not hire full-time?

If the platform needs one full-time, you should. Many need architectural judgment every week but not a full week of it. The role can also cover the gap while you hire.

How is this different from the managed services retainer?

The retainer is delivery capacity. The fractional architect is a role that holds the roadmap and design authority. Many teams use both.

Is this a block of hours with a new name?

No. Hours are not the unit. The fee follows what the role covers and which decisions it holds.

What does the architect actually decide?

That is agreed at the start in a decision-rights table. Your platform owner and leadership stay accountable for the platform.

Will the architect steer work to Emetrix?

You choose who builds: your team, your partner, or Emetrix. Recommendations are recorded with their reasoning so you can test them, and the architect can oversee work delivered by anyone.

What if the architect is unavailable?

The architecture does not live in one person's head: decisions, standards and the roadmap are written down and are yours. Cover during absence is set in the agreement.

Does it cover tools other than ServiceNow?

ServiceNow and the tools connected to it, not general enterprise architecture.

Cost and commitment?

A monthly fee agreed by scope and accountability and set in writing before the role starts. Month to month. No price is published.

Admin access?

The role starts with read access; changes are made by your team, your partner, or a separate delivery agreement.

Scope note. Decision rights, cadence and fee are agreed in writing before the role starts. This page describes a role and how it works, not a guaranteed outcome.

Who decides how your platform is built?

If the honest answer is whoever is building it this month, start with a conversation.

Start with a conversation We reply within 24 hours on business days.