Cloud Modernization Patterns Module 1 · Size It Up

Build vs Adopt vs Extend

Updated

Intermediate

What you'll learn

~20 min
  • Evaluate build, adopt, and extend options each on its own terms before comparing
  • Build a feature-parity disposition table with an explicit 'not needed' column
  • Recognize the honest limits of unweighted comparisons -- and add the weighting pass

FieldDesk’s three futures

Dana’s low-code stopgap became load-bearing, and now it has three possible futures:

  1. Adopt — take a mature open-source service-request product and configure it for Meridian
  2. Build — rebuild FieldDesk purpose-made on Meridian’s modern stack (Next.js, Entra ID for identity, a managed database)
  3. Extend — stay on the low-code platform and invest in doing it properly

The naive move is to pick a favorite in the first meeting and spend six weeks justifying it. The disciplined move is a rule: every option gets a full evaluation on its own terms before any comparison happens. If you evaluate “adopt” through the lens of the build you already want, you will find exactly the flaws you went looking for.

Prompt first: three advocates

Switch your workspace agent to Plan mode with your Lesson 1.2 assessment and candidate product notes, and ask for three separate advocacy plans (if you do not have live exports or files handy, ask it to generate a small Meridian practice sample from the lesson’s scenario first):

Using our FieldDesk assessment and candidate notes, plan three separate advocacy documents for Adopt, Build, and Extend. Make the strongest honest case for each option on its own terms without comparing them yet.

Check that the plan or draft covers:

  • Three independent advocacy documents: Option A (Adopt the open-source product), Option B (Build on Next.js, Entra ID, and managed Postgres), and Option C (Extend and remediate the existing low-code platform)
  • Architecture fit, 2-year cost profile, operational risks, and what 2-year success looks like for each option
  • Zero cross-option comparison or hedging inside the individual advocacy documents

If the draft starts ranking the options against each other inside the advocacy docs, follow up with: Keep each advocacy document focused strictly on its own best case; save cross-option comparison for the matrix.

Three documents, three genuine best cases. Only after all three exist do you build the comparison.

🔍Why advocate documents survive the decisionclick to expand

In one real evaluation this pattern came from, the incumbent product’s own deep-dive concluded pro-adoption — and the final cross-option decision overrode it and chose build. The advocate document was preserved unchanged, not retro-edited to agree. That is the process working: advocates argue the best case at component altitude; the decision happens at portfolio altitude, where factors like platform alignment live. If your advocacy documents all mysteriously agree with the final answer, someone edited history.

The comparison: a qualitative attribute matrix

With three advocates on the table, the comparison is a matrix of attributes — not scores:

AttributeAdopt (OSS product)Build (Next.js)Extend (low-code)
Architecture styleMonolith, Node 16-eraModern app, your patternsVendor runtime
IdentityPlugin-based SSOEntra ID nativePlatform connector
Type safetyNoneEnd-to-end TypeScriptN/A
Ops burdenYou patch a forkYou own an app on PaaSVendor owns runtime
Licensing/ownershipApache-2.0 fork driftFully ownedPer-user, rising
Team fitNew stack islandExisting portal skillsCitizen-dev ceiling

The table that wins schedules

The single most valuable artifact in this decision is the feature-parity disposition table. Take every capability the current FieldDesk has, and force each into one of four columns:

CapabilityMVPLaterNot neededDefer decision
Request intake + assignment✔
SLA timers✔
Storm-day bulk dispatch✔
Emailed CSV integrations✔ (replaced by API)
The reporting module✔ (moves to the data platform, Module 3)
Multi-language UI✔ (workforce is single-language)
Custom branding engine✔
Mobile offline mode✔

The “not needed” column is where the schedule is won. Every row you can honestly place there is scope the build option does not carry — and in real evaluations, discoveries like “we never migrated the legacy data anyway” or “authentication is IdP-only now” repeatedly shrink the build until it beats adoption. Scope discovery is not cheating; it is the evaluation doing its job.

What actually tips these decisions

Documented tipping factors from evaluations of exactly this shape, in weight order:

  1. Platform alignment — Meridian already runs a settled modern-web ecosystem. Adopting a divergent stack means maintaining a technology island forever.
  2. Remediation cost converges on build cost — with a worse endpoint: money spent modernizing a fork still leaves you on someone else’s architecture.
  3. Scope discoveries — the disposition table deletes the adopt option’s biggest advantage (all those features you turn out not to need).
  4. Security debt as entry cost — a customized fork can’t cleanly take upstream fixes; you inherit its vulnerability backlog on day one.
  5. Run-rate economics — a purpose-built app on PaaS versus per-user licensing that rises with headcount.

And one discipline for whatever wins: the loser becomes a functional reference spec. If build wins, the OSS product’s battle-tested feature set defines what to build — and none of its code comes along.

The honest caveat — and your exercise

A qualitative matrix has a real limit: with no criteria weighting, the trade-off between rows is not auditable. A reviewer who values ops burden over platform alignment could defensibly reach the other answer. So run the weighting pass yourself in your workspace agent:

Using our attribute matrix and disposition table, propose attribute weights from the perspectives of a cost-focused CIO, a security officer, and a field-operations director. Score all three options under each and show where the winner flips.

If the answer survives all three weightings, you have a robust decision. If it flips, you have found the actual disagreement to take to the steering committee — which is worth more than false consensus.

KNOWLEDGE CHECK

Why are the three options evaluated separately, each on its own terms, before any comparison is made?

Key takeaway

Evaluate each future on its own terms, compare with an attribute matrix, and force every existing capability into MVP / later / not needed / defer — the “not needed” column is where schedules are won. Then stress the answer with a weighting pass. Next lesson: turning the winner into a roadmap that survives contact with reality.

Search lessons