Graftability: could a shared surface land here?

The first three axes assess a product on its own terms. This one asks a question that only exists because of who is buying: if you already have a working surface — an agent console, a review queue, a shared component set — could you install it in this product at all, or would installing it mean rebuilding it?

It is a different question from “is this code any good,” and the two come apart constantly. A carefully engineered application with every colour hardcoded, a bespoke session layer and one deploy artifact is close to ungraftable. A scrappier product that already sells white-labelled embeds has done most of the work by accident, because a customer paid it to.

Nothing published covers this. Here is what was looked at.

An absence claim is only worth making if the search could have found something, so here is the search. This course’s research read the published technical diligence material it could obtain — Bain, AKF, MEV, Papermark, Peony, Growth Shuttle, CTO on Demand, the Startup CTO field guide, a public GitHub checklist — and found that none of them names user experience, design systems, accessibility or front-end performance as a workstream at all. They dissolve the front end into “architecture,” “code quality” or “integration readiness.” Nothing in that body of work addresses installability of a shared surface as a distinct thing to assess. The term used on this page is this course’s own, and nobody you meet will recognise it.

Why the axis exists, without speculating about anyone

Vista Equity Partners publishes, on its own site, that it works with 85+ portfolio companies and 100+ operators as of June 30, 2026, serving over 250 million users as of December 31, 2025, and it names its Agentic Factory as the first of five value-creation pillars. That is the firm describing itself, which is the only thing about the firm this course will cite. There is no published methodology behind it and this lesson does not guess at one.

Worth noticing how the numbers behave, because reading a self-description carefully is the same skill as reading a target’s marketing site. A Vista press release from April 2026 states different figures — 90+ companies and 750 million users — on a different basis, with no reconciliation published. Neither is wrong. They are counts of different things at different dates, and quoting the larger one because it sounds better is exactly the habit this course exists to break.

The arithmetic is what matters. At that portfolio scale, a surface built once and installed in twenty products is a different economic object from a surface built twenty times. So the question of whether a given product can receive one stops being an architectural curiosity and becomes a number in the deal model. If you are not operating in that model, this axis does not belong on your page. Say that too, because a rubric that knows when it does not apply is more credible than one that applies everywhere.

The four questions, and what you can see

Is there a theming seam?

Fetch their stylesheet. If the computed styles resolve through CSS custom properties, there is a seam an installed surface could inherit. If every button carries a literal colour, there is not, and a grafted component will either look foreign or need a bespoke theme written for it.

The uniqueness ratio from css-analyzer is doing double duty here — the same measurement that reads as consistency debt on the maturity axis reads as theming risk on this one. A product with one hundred and forty unique colour values has no palette to inherit. And there is a strong positive signal available for free: if the product sells white-labelling or customer branding as a feature, the seam exists, has an owner, and has been tested by paying customers.

Where is the auth and session boundary?

The question is whether a new surface could sit inside the existing session rather than needing its own login. Outside evidence: published SSO or SAML documentation, an OIDC discovery endpoint, a documented service account or machine-token concept, subdomains that clearly share a session. A product with a documented enterprise SSO offering has an auth boundary somebody deliberately designed, which is most of what you need to know.

The red case is an application whose session is implicit and everywhere: no articulated boundary, every feature assuming the same monolithic context. Grafting into that means either inheriting the whole context or building a second identity path, and the second one is the expensive answer nobody wants to give in an integration meeting.

Can a piece of the UI be released independently?

The weakest of the four from outside, and mark it accordingly. Hints exist: a public status page that lists product components separately, a changelog that dates parts of the product independently, more than one versioned front-end artifact. A single bundle whose hash changes on every release is a hint in the other direction.

None of that is proof, so this question is usually not assessed pre-offer and belongs near the top of the list for the deep read. It also happens to be the question with the largest effect on the estimate: if every change to an installed surface requires a full application release on the target’s schedule, the thing you shipped once now moves at their cadence forever.

Is there an extension point already?

The strongest outside signal on the axis, because extension points get marketed. An app marketplace, a plugin API, embeddable widgets, an install script, an SDK that renders their UI inside somebody else’s product. Any one of those means the team has already fought the fight about where a foreign surface is allowed to run and what it is allowed to touch.

And the direction matters. A product that can be embedded elsewhere has solved a different problem from one that can host something else, and only the second one is what this axis is about. Read the direction before you score it green.

What this does not cover

All four axes now exist and every question has a threshold behind it, which means the instrument has content and no shape. What it does not have is a form: nineteen questions across four axes will not fit anywhere useful, and choosing what survives the cut is the work that makes the document readable by somebody who was in none of your meetings.

That is the next module. It opens with the one-page argument, then the red/amber/green test that decides whether your thresholds actually reproduce in another reader’s hands, then the remediation estimate with its assumptions printed, the finding management will dispute, and finally running the whole thing end to end against a real product. The questions that run breaks are the deliverable.