Start with the opportunity, then choose the first offer.
Rich and Andrew have already been interviewed. This pack is therefore not a prompt to run more generic discovery; it is the founding-team readout: what the evidence suggests, what offer to lead with, what remains to prove with named accounts, and what the team needs to decide next.
The interviews turn source signal into a team decision pack
Use these as the current decision basis now that Hadrian, Rich and Andrew interviews are already in the evidence base.
Foundry EAM / Max Connect now has enough categorized source material to stop treating MAS as a generic market and start choosing a first wedge.
The material is deepest around OpenShift, security/governance, AI/Health/Predict/Visual Inspection, performance/mobile/optimisation and data/reliability — not just migration.
Migration routefinding remains credible, but the evidence also supports optimisation and product/tooling-gap options that should be treated as modules or follow-ons unless named-account pull says otherwise.
The Hadrian/Rich/Andrew founder-partner sequence moves the lead wedge from broad “which lane?” exploration toward an independent asset-intelligence diagnostic and ITT-readiness sprint; AI/tooling should stay as internal delivery leverage until repeated client patterns justify product claims.
Commercial proof is still thinner than technical proof: AppPoints, ROI, partner economics and price/rate evidence need named examples before they become positioning.
Rich and Andrew evidence has already helped separate user/community pain from implementation and delivery economics; the remaining work is named-account proof and team agreement, not generic discovery.
Only buyer-backed claims should graduate into external positioning: named organisations, direct user language, price/rate proof, product-gap examples, community-governance boundaries and inspectable source files.
The Andrew/Rich interviews and MAS Unlocked 2 survey have produced the current founding-team view; the next gate is agreement on name/category, first wedge, price point, roles and first prospects before public copy moves.
The job is to choose the first opportunity, not browse the machinery
Foundry EAM / Max Connect is using discovery to decide where to enter the Maximo / MAS-adjacent asset-intelligence market first. The useful output is a focused first offer, reachable target conversations, and a clear evidence trail for why that wedge should move before the others.
The evidence base now includes NotebookLM-exported research, Drive-visible source files, MAS Unlocked 2 customer/community material, and Hadrian/Rich/Andrew interview notes.
New proof should update the buyer, wedge and proof-gap view only when it affects the first-offer decision, not become more material for the team to browse.
The evidence base is there to support the judgement, not to become the reader journey. The founding-team job is narrower: choose the first offer, the first prospects, the price/scope boundary and who owns each next move.
Technical/source evidence is strongest. Named-account proof, buyer language, first-call agenda and price confidence are the practical gates before external positioning.
The evidence base is there to support the judgement, not to become the reader journey. The founding-team job is narrower: choose the first offer, the first prospects, the price/scope boundary and who owns each next move.
Technical/source evidence is strongest. Named-account proof, buyer language, first-call agenda and price confidence are the practical gates before external positioning.
The lead wedge is now an independent diagnostic and ITT-readiness sprint
Legacy Maximo to MAS still creates hosting, integration, licensing, data-readiness and adoption risk, but the Ant/Hadrian interview changes the sequencing: Foundry EAM / Max Connect should not lead with a visible AI product or generic software story on day one.
The founding-team-facing thesis is now sharper: start with a paid Maximo/MAS Discovery & ITT Readiness Sprint for underserved mid-market or asset-heavy organisations, using AI/tooling internally to make delivery faster, clearer and more repeatable. Product/tooling opportunities remain real, but should be earned from delivery patterns and named account pull.
“The first offer should be boring enough to buy and sharp enough to open the account: discovery, readiness and ITT support before visible AI productisation.”
MAXCONNECT-INTERVIEW-001 + MAXCONNECT-TEAM-004 · founding-team/name evidenceThe thesis now has founder/partner signal, but still needs named-account buyer validation, community-governance safeguards and price proof before external positioning.
Lead with one buyable sprint, then earn the wider offer
The evidence widens the wedge list, but the founder interviews narrow the operating decision. Foundry EAM / Max Connect should test one buyable service first: a Maximo/MAS Discovery & ITT Readiness Sprint for organisations that are underserved by the consolidated Maximo supplier market.
Other lanes — optimisation, AI/analytics tooling, AppPoints review, MREF/TRIRIGA, GIS integration and community-led channels — remain valuable, but should become modules or follow-ons unless named accounts prove they should lead; generic directory/community-media mechanics are now cautioned rather than promoted.
Prioritisation after the founder interviews: lead with a small, credible consulting wedge; keep productisation behind the delivery method until evidence improves.
| Wedge | Why it might work | Atom basis | Decision needed |
|---|---|---|---|
| Discovery & ITT Readiness Sprint | Small enough to buy, concrete enough to sell, and directly aligned with underserved product owners who need current-state clarity, requirements, supplier/ITT support and next-step roadmap. | MAXCONNECT-INTERVIEW-001 + migration/platform/data/commercial evidence categories | Validate £5k–£10k diagnostic hook fee, buyer language, artefact list, governance boundaries and named first prospects using Rich/Andrew evidence plus named-account follow-up. |
| Post-migration footprint / MREF health check | New customer/community evidence says large public-sector, university and facilities accounts may own enterprise suites but under-use them, including TRIRIGA-to-MREF transition pressure. | MAXCONNECT-OPP-001 + MAXCONNECT-OPP-012 + MAXCONNECT-PERSONA-008 | Validate MREF technical authority, reachable accounts and whether this expands or distracts from the initial readiness sprint. |
| MAS migration routefinding | The original routefinding thesis: help clients choose the next MAS move before implementation spend. | 11 migration sources + IBM migration docs | Which named accounts have urgent migration pressure now? |
| OpenShift / platform readiness | The source room is densest here; clients may need a plain-English route through architecture, hosting and operating-model choices. | 122 OpenShift/infrastructure sources | Is this sold to CIO/platform owners or bundled into migration readiness? |
| Security / governance readiness | Security, identity and admin material may create a risk-led route for regulated estates. | 57 security/governance sources | Who feels this pain and what compliance/operational trigger funds it? |
| GIS / ArcGIS integration strategy | Dispersed assets, facilities and public-sector estates may need a vanilla-friendly route between ESRI/GIS systems and Maximo/MAS. | MAXCONNECT-TECH-015 | Confirm repeatability and buyer urgency with technical practitioners. |
| Data/integration risk map | Customisations, integrations, data quality, backup/restore and reliability are concrete migration blockers. | 18 integration + 31 data/reliability sources | Which painful examples and reusable checklists are already evidenced, and what named-account proof is still missing? |
| Optimisation assessment | Assess current ways of working against newer-platform capabilities, performance and mobile operations. | 33 performance/mobile/optimisation sources | Do clients feel enough pain to pay before or after migration? |
| AI/analytics/product-gap exploration | Predict, Health, Monitor, Visual Inspection and analytics material gives product/tooling hypotheses beyond services. | 91 AI/Health/Predict/Visual Inspection sources | Which gap is painful, trusted, common and buildable enough to prototype? |
| AppPoints / commercial model review | Licensing and consultancy economics give finance/procurement a concrete reason to engage. | 8 AppPoints/commercial sources | What rate/service evidence and price bands are strong enough to test with named buyers? |
| Community / user-group route | Survey respondents and UK/Ireland/global user-group routes may create trust without cold sales. | 32 community/training sources + Rich route | Which channels are actually available and what is the first-account agenda? |
| Virtual strategic advisor for isolated platform leads | Team-of-one Maximo/MREF owners need roadmap, business-case, vendor-governance and adoption support beyond one-off implementation. | MAXCONNECT-PERSONA-008 + MAXCONNECT-OPP-017 + MAXCONNECT-PAIN-007 | Test willingness to pay, cadence, procurement route and whether this follows a diagnostic workshop. |
What the MAS decision actually contains
The source material makes the MAS decision map more specific. It is not only “upgrade to MAS”: it is platform route, OpenShift operations, integration and customisation change, data/reliability, security/governance, AppPoints, mobile/performance, AI/analytics capability, partner route and user adoption together.
Use this as a decision map: which fields create buyer pain, which are routine implementation work, and which can become a differentiated Foundry EAM wedge?
The fields Foundry EAM / Max Connect needs to make legible for an account.
| Decision field | What has to be understood | Known atom basis | Missing input |
|---|---|---|---|
| Platform / OpenShift route | Hosting model, OpenShift footprint, sizing, deployment model, cloud/on-prem constraints, operating skills. | 122 OpenShift/infrastructure sources; MAXCONNECT-TECH-004, 011, 012 | Current estate architecture and who owns platform risk. |
| Security / governance route | Identity, administration, permissions, governance, monitoring and support model. | 57 security/governance sources | Risk owner, compliance trigger and buyer language. |
| Integration route | Customisations, APIs, object structures, automation, authentication changes and integration inventory. | 18 integration/API/automation sources; MAXCONNECT-TECH-007, 008, 009 | Broken integrations, rewrite scope and implementation owner. |
| Data / reliability route | Data quality, backup/restore, cutover, attachments/doclinks and reliability risk. | 31 data/reliability sources; MAXCONNECT-PAIN-002, 005 | Migration defects, object counts, cutover constraints. |
| Commercial / AppPoints route | Entitlement, AppPoints, role tiers, monitoring, overage/lockout and ROI framing. | 8 AppPoints/licensing sources; MAXCONNECT-MONEY-002, 004, 005, 006 | Budget owner, procurement pain, price/rate examples. |
| Optimisation / product route | Performance, mobile operations, Health/Predict/Monitor/Visual Inspection, AI/analytics and workflow gaps. | 33 performance/mobile sources plus 91 AI/Health/Predict/Visual Inspection sources | Which gap is painful, common and buildable enough to test. |
| Community / partner route | User groups, events, training/adoption, vendors, partners, competitive context and customer frustration with black-box delivery. | 33 community/training sources plus 17 partner/market sources; MAXCONNECT-CHANNEL-004; MAXCONNECT-PAIN-007 | Which introductions and community routes are actually usable for first prospects. |
| Facilities / MREF / GIS route | TRIRIGA-to-MREF migration, facilities operations, lease/accounting compliance, GIS/ArcGIS location intelligence and public-sector footprint expansion. | MAXCONNECT-OPP-012; MAXCONNECT-OPP-016; MAXCONNECT-TECH-015; Stephanie Neves MAS Unlocked 2 intake | Validate buyer urgency, technical authority and whether this is a first-wave wedge or later account/event agenda. |
Four buyer roles, with Rich and Andrew already in the evidence base
The MAS buyer surface is not one audience. This pack separates economic, technical, operational and service-provider buyer roles, using the completed Rich and Andrew interviews as evidence behind the map rather than as future validation tasks.
The useful team move is to choose which role to pursue first, what pain to lead with, and what offer is concrete enough to test with a named account.
Founding-team signal — Ant/Hadrian interview
Primary founder discussion now points to underserved practical Maximo/MAS product owners and asset-heavy organisations who need discovery, ITT/readiness and supplier navigation more than a visible AI product pitch.
Economic buyer — asset / transformation owner
Owns business risk: downtime, asset life, transformation spend and the cost of a failed MAS route. Needs a board-level route map, not product detail.
Technical decision maker — CIO / platform owner
Owns OpenShift, integrations, security, data and cutover feasibility. Needs risk clarity before implementation commitments harden.
Operational owner — maintenance / reliability lead
Feels workflow disruption, mobile adoption, reporting gaps and daily-user resistance. Gives the pain language that makes the offer real.
Service-provider / FM buyer
May run Maximo for multiple client estates, with service-provider licensing, SLA and procurement complexity. Potential high-need niche; still unproved.
Isolated platform owner — team of one
Carries platform administration, roadmap, compliance, business-case and user-request load with limited internal backup. May buy retained strategic help if the artefact list and budget path are clear.
Interview evidence — Rich Barber
Interviewed; use his evidence for user/community language, reachable-account hypotheses and proof gaps. Follow up only for named accounts, direct quotes or specific first-call agendas.
Interview evidence — Andrew Carrie
Interviewed; use his evidence for delivery feasibility, partner economics, service shape and product-gap reality. Follow up only for price, artefact or scope proof.