Operating Analysis

01 — What it is

One company, every dimension that matters.

Most consulting deliverables cover a slice of what leadership actually needs to decide. A market study, but no take-share moves. A financial projection, but no operating cadence. A SWOT, but no decision gates. The Operating Analysis is the consolidated artifact — the kind of deliverable a senior consultant builds after one or two weeks of primary research, covering strategic, competitive, and operational depth in a single document.

The structure is industry-agnostic. The same ten sections work for premium services, healthcare, professional services, consumer goods, B2B software, and founder-led mid-market businesses. What changes is the specific data in each section — the market sizing, the regulatory exposure, the unit economics — calibrated to the engagement. The discipline stays constant.

The deliverable is a self-contained HTML dashboard. On request, the engagement upgrades to a Vite + React + Recharts application — the artifact graduates from a shareable PDF replacement to a tool the leadership team can navigate live in a meeting. Most engagements ship the HTML and never need the React version. Some need it on day one.

Strategy is only worth what it withstands when the buyer challenges it.

02 — Anatomy

Ten named sections.

The deliverable spine is ten sections, in this order. Sections are judged against the engagement's one strategic question — without that question, the output drifts into a generic deck. If a section doesn't help answer it, we cut the section.

01
Thesis The 90-second read. The strategic answer in one sentence. A four-stat hero row. A scope table covering eight to twelve analytical dimensions. Three forces, three risks, three opportunities calling out the next twenty-four months.
02
Market TAM, SAM, and SOM with explicit source citations. Growth rates by segment. Demographic and macro tailwinds. Charts of segment size and CAGR. Composition donuts where relevant.
03
Threats The two-to-four forces that could materially change the subject's economics in twenty-four months. Regulatory exposure named explicitly. A risk-by-severity table. Callouts that quote the regulator or the disrupter directly.
04
Competitors A tiered competitive map — local, regional, national, online, international. A service-offering matrix verified by primary fetches. Filterable competitor cards. Threat-tagged rows. Verified pricing and capability per competitor.
05
SWOT Rank-ordered, not alphabetical. Numbered so the rank is unambiguous. Each entry is a one-line claim plus, where relevant, the dollar value or the urgency window.
06
Initiatives A prioritized roster of ten to twenty initiatives. Each one carries a KPI, a budget range, an owner, and a decision gate. Bar chart of one-time investment per initiative. Recurring-cost overlay.
07
Financials Revenue projection by stream over thirty-six months. Subscription unit economics where applicable. CAC payback and retention/LTV sensitivity tables. The monthly KPI roll that closes the section.
08
100-Day Operating System Weekly cadence, RACI ownership, day-by-day tracker, and the named decision gates. The section that turns a strategy memo into something a team can actually run. Day 100 success cards: business protected, growth engines validated, management visibility live, market-facing proof started.
09
Take-Share Playbook Competitor-by-competitor moves. Each card pairs their weak flank with your move. One card per competitor, in the same order as the competitor map.
10
Evidence The source register. Every claim that materially affects strategy — labelled, sourced, and dated. A topic / verified-as-of / strategic-implication table. The audit trail that makes everything above defensible.

03 — Evidence discipline

Every claim, labelled.

An Operating Analysis is judged on whether its claims hold up under audit. Every material claim — market size, competitor pricing, regulatory exposure, financial projection — carries a label that tells the reader exactly how much weight to give it. Four labels, used consistently across every section.

VERIFIED

Directly observed in a primary source within the last thirty days — the subject's own site, a regulator's bulletin, a named filing. URL and date attached to the claim.

SOURCED

Drawn from a named third-party report — Mordor, IBISWorld, Astute, Grand View, Coherent, Nielsen, and so on. Publisher and date attached. Stronger than "industry analysts say" because the analyst is named.

SCENARIO

An explicit model assumption — a revenue projection, a unit-economics scenario, a market-share target. Shown alongside the assumption inputs so the reader can change them. Never presented as a forecast.

NEEDS_VERIFY

A claim from prior research that has not yet been re-verified. Flagged in the Evidence section so the user knows what to chase. The honest token, used freely, that prevents stale claims from being quoted as current.

Two follow-on rules underwrite the label system. No fabricated precision — "$5.2M revenue" implies verification; if the subject hasn't published revenue, we use a band ("$3–4M est.") and label it SCENARIO. And the three-strikes rule before asserting absence — we don't write "the subject has no MD on staff" until three independent checks have failed. Otherwise the finding reads not surfaced in this crawl, never doesn't exist.

04 — The section that earns its keep

The 100-Day Operating System.

A strategy memo without an operating system is a wish list. Section 08 is what turns the analysis into something a team can run on Monday morning. Five named components, all of them load-bearing.

01

Operating cadence

Five meetings — weekly command, weekly regulatory or governance, weekly growth sprint, weekly subscription or product beta review, monthly executive review. Each row names the owner, frequency, purpose, and output.

02

RACI ownership

One row per workstream, named accountable / responsible / consulted / informed. The accountable column is single-named, never a team or committee. The point of failure is named.

03

100-day tracker

Six columns — timeframe, workstream, action, owner, decision gate, success metric. Twelve to twenty rows covering Days 1 through 100. Row-tone coding signals urgency at a glance.

04

Decision gates

Five to eight named decisions with deadline, required evidence, and a recommended default. When the team can't gather the evidence in time, the default tells them what to do. This is what prevents the plan from stalling.

05

Day 100 success

Four cards — business protected, growth engines validated, management visibility live, market-facing proof started. Each card carries three to five concrete statements. The definition of what success actually looks like, written down before Day 1.

The gates are what turn the tracker into an operating system.

05 — Deliverables

What you receive.

A self-contained HTML dashboard delivered in the Aspiture Operations Design System, with the subject company as the H1 and Aspiture's chrome as the wrapper. File-named with a client code and a version number — {ClientCode}_Operating_Analysis_v1.html — so versions stay distinct across iterations.

01
Operating Analysis dashboard (HTML) The ten-section deliverable, populated against your engagement. Self-contained — opens in any browser, travels by attachment or link, prints to PDF. The default artifact.
02
React app upgrade (Vite + Recharts) On request. The same content reimplemented as a deployable web application with interactive charts and a shareable URL. The artifact graduates from a PDF replacement to a tool a leadership team can navigate live in a meeting.
03
Optional appendices When scope warrants — a customer journey map (stage-by-stage), a service catalog, a project glossary. Added as the engagement reveals which of them earns its place.

06 — Where it fits

Standalone, or as part of a study.

The Operating Analysis is one of Aspiture's three deep-research practices, alongside Competitive Analysis and the full Strategic Consulting engagement. They're related — the Operating Analysis subsumes a tiered competitor map and a take-share playbook — but they have different scopes.

The right engagement depends on the question. If the question is "how does this company run the next twelve months?", the Operating Analysis is sufficient on its own. If the question is "who do we actually compete with, defensibly?", the Competitive Analysis is the focused engagement that produces the canvas and the presenter guide. If the question is "give us the full system — pitch artifact, operating instrument, gap assessment, fact-check audit", that's the full consulting engagement.

We help you make the call in the initial conversation. The wrong engagement scope is more expensive than the right one.

Operating Analysis.