Choose the right first Maximo opportunity for Max Connect.
Max Connect is exploring where to enter the IBM Maximo and MAS market first. The Drive source room is now a live intake surface with 441 visible files; the NotebookLM discovery notebook has 357 sources after the 22 July upload intake. Treat the pack as an evolving discovery system: each new source should either strengthen, qualify or challenge the consulting-first Maximo/MAS discovery, readiness and ITT-support wedge.
The first founder interview turns source signal into a lead wedge
Use these as prompts for founder, partner, account and source-material follow-up now that the source room and first founder interview are available.
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 source room also supports optimisation and product/tooling gap conversations that should be tested beside it.
The Ant/Hadrian interview moves the lead wedge from broad “which lane?” exploration toward a consulting-first Maximo/MAS Discovery & ITT Readiness Sprint; AI should stay as internal delivery leverage for now, not the visible launch product.
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 should use different parts of the source room: Rich to test user-group/end-user reality; Andrew to test implementation, partner economics and product-gap reality.
Only buyer-backed claims should graduate into external positioning: named organisations, direct user language, price/rate proof, product-gap examples and inspectable source files.
The job is to choose the first opportunity, not to prove everything at once
Max Connect is using discovery to decide where to enter the Maximo / MAS 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 original NotebookLM export was converted into a reviewer source room, and the Drive room is now live as an intake surface: 441 files are visible in Drive and 357 sources are now in the Max Connect Discovery NotebookLM corpus after the 22 July intake.
That material changes the pack from a static first cut into an evolving discovery pack. New source files, survey responses, account lists, ITT proof and partner material should be ingested, classified, synthesized, and used to update the buyer, wedge and proof-gap view rather than treated as one-off attachments.
Treat strong claims as prompts to validate.
This pack separates researched product mechanics from commercial claims that still need named-account and partner proof.
Current state: the technical and product-material base is now substantial; the remaining gate is named-account, buyer, channel and price evidence before choosing the first offer.
The source room is live and evolving; commercial proof remains the gate
The pack now has an inspectable source base and a live intake path: 441 Drive-visible files, including July 22 uploads across MAS source material, commercial proof and MAS Unlocked event/community evidence; 357 sources are now in the NotebookLM discovery corpus.
Use the source room to support claims about platform mechanics, architecture, security, integration, data, performance, AI, community signal, named accounts and ITT/commercial proof. Do not use it as a substitute for Rich/Andrew/account evidence about what people will buy first.
NotebookLM categories now available in the shared Drive folder and /source-index/.
| Category | Sources | What it gives Max Connect | Commercial gap to test |
|---|---|---|---|
| MAS migration, upgrade and modernization | 11 | Migration-route context, support/EOS pressure, migration playbooks and upgrade paths. | Which named estates have urgent migration decisions now? |
| AppPoints licensing, commercial model and ROI | 8 | Licensing mechanics and AppPoint monitoring/entitlement material. | Actual budgets, package shapes, overage examples and price/rate proof. |
| OpenShift architecture, deployment and infrastructure | 122 | The densest technical base: installation, deployment, sizing, hosting, cloud and OpenShift operating requirements. | Which buyers see this as a board-level risk rather than implementation detail? |
| Security, identity, administration and governance | 57 | Security, admin, identity and governance implications of MAS operation. | Who owns this risk and what trigger makes them seek outside help? |
| Integration, extensibility, API and automation | 18 | Integration/change surface for customisation, APIs and automation. | Concrete broken integrations, custom classes, API rewrites and partner scope. |
| Data migration, backup, restore and reliability | 31 | Data, backup/restore and reliability material for routefinding and readiness. | Named data-quality failures, cutover constraints and support burden. |
| Performance, mobile operations and optimisation | 33 | Optimisation lane evidence: performance, mobile and operational usage. | Whether optimisation is a paid wedge or a later delivery module. |
| AI, Predict, Health Monitor and Visual Inspection | 91 | Product/tooling gap surface around analytics, prediction, inspection and asset-performance capability. | Which AI/analytics gaps users actually trust, need and would pay to solve. |
| User groups, events, community signal and training | 32 | Routes into GoMaximo/MUWG/SWMUG/CANMUG/community conversations and training/adoption evidence. | Which communities Rich can reach and what follow-up agenda they will accept. |
| Partners, vendors, market and competitive context | 17 | Partner/vendor landscape and competitive context. | Andrew-level partner economics, channel role and service-package reality. |
New Drive uploads added to NotebookLM and queued for synthesis into the evolving pack.
| Route | Files | What it adds | Next synthesis job |
|---|---|---|---|
| MAS source material | 6 new NotebookLM sources plus one duplicate already present | Current MAS collateral, March 2026 product update, Manage material, Maintec/Rich prep and Maximo links. | Update technical/product wedge claims and partner-interview prompts. |
| Commercial proof | 2 new NotebookLM sources | Market opportunity report and scanned Maximo UK & Ireland User Group member proof. | Extract named-account/market proof carefully before public-facing claims. |
| MAS Unlocked 2 event/community | 5 new NotebookLM PDF sources; Numbers survey file remains unsupported pending CSV/export | Named event/community respondent PDFs and an ITT file. | Synthesize community/account/pain evidence and convert/export survey responses if needed. |
Representative atoms remain useful, but should now be checked against the categorized source room. The full index remains at /atoms/ and the material index at /source-index/.
| ID | Description | Sources | Date |
|---|---|---|---|
| MAXCONNECT-TECH-001 | MAS is a platform shift from legacy Maximo Asset Management to Maximo Manage inside a broader suite. | RESEARCH | 2026-06-12 |
| MAXCONNECT-TECH-004 | MAS requires Red Hat OpenShift, changing the operating base for legacy customers. | RESEARCH | 2026-06-12 |
| MAXCONNECT-MONEY-002 | AppPoints create a buying risk because licensing uses a shared pool with role, access and overage implications. | RESEARCH | 2026-06-12 |
| MAXCONNECT-TECH-014 | Data, integrations, customisation and reliability risks turn migration into routefinding rather than a simple upgrade. | RESEARCH | 2026-06-12 |
| MAXCONNECT-TEAM-001 | Rich Barber and Andrew Carrie are the named validation route for Maximo relationships and account reality. | PRIMARY | 2026-06-13 |
| MAXCONNECT-OPP-011 | Named-account reachability is the main commercial unknown before any route becomes a sales motion. | SPECULATION | 2026-06-13 |
| MAXCONNECT-INTERVIEW-001 | Ant/Hadrian founder interview sharpens the first wedge: consulting-first Maximo/MAS discovery, readiness and ITT support, with AI as internal delivery leverage. | PRIMARY | 2026-07-20 |
The categorized source room is now the evidence layer
The Max Connect source room contains 420 categorized NotebookLM sources across ten folders. Use the web source index for orientation and the shared Drive folder for inspectable files and reviewer additions.
The pack should now be challenged against material, not against memory.
| Use case | Where to look | Question to answer |
|---|---|---|
| Validate technical claims | OpenShift, security, integration, data and AI/product categories | Does the pack say the right thing about MAS mechanics? |
| Prioritise wedges | Migration, optimisation, AI/product, AppPoints and community categories | Which category creates a first sellable wedge? |
| Find buyer proof gaps | Drive additions: account lists, call notes, survey exports, price/rate examples | What needs Rich, Andrew or a named account before we position it? |
| Keep evidence auditable | /source-index/ plus Drive source files | Can a reviewer inspect the exact source behind a claim? |
The lead wedge is now a consulting-first discovery 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: Max Connect should not lead with a visible AI product or generic software story on day one.
The founder-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 · Ant/Hadrian founder interviewThe thesis now has primary-founder signal, but still needs Rich/Andrew and named-account validation before external positioning.
Lead with one buyable sprint, then earn the wider offer
The source room widens the wedge list, but the first founder interview narrows the operating decision. 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 and community-led channels — remain valuable, but should become modules or follow-ons unless Rich, Andrew or named accounts prove they should lead.
Prioritisation after the Ant/Hadrian interview: 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 source-room categories | Validate £5k–£10k entry price, buyer language, artefact list and named first prospects with Rich/Andrew. |
| 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? |
| Data/integration risk map | Customisations, integrations, data quality, backup/restore and reliability are concrete migration blockers. | 18 integration + 31 data/reliability sources | Can Rich/Andrew name painful examples and reusable checklists? |
| 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 | Can Andrew provide rate/service evidence and price bands that sell? |
| 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 channel does Rich actually control and what is the follow-up agenda? |
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.
This section is now the working checklist for partner interviews and source-file review: ask which fields create buyer pain, which are routine implementation work, and which can become a differentiated Max Connect wedge.
The fields Max Connect needs to make legible for an account, now aligned to the source-room categories.
| 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 and competitive context. | 32 community/training sources plus 17 partner/market sources | Which introductions Rich/Andrew can actually unlock. |
Four buyer roles. Two validation candidates. Different pains, different channels.
The MAS buyer surface is not one audience. This pack separates economic, technical, operational and service-provider buyer roles, plus the partner/expert side that can validate the map. All personas below remain composite until Rich, Andrew or named accounts prove them.
The useful discovery move is to ask, for each role: what pain do they feel, what budget do they control, what channel reaches them, and what first Max Connect product would feel worth a conversation?
Founder 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.
Validation route — Rich Barber
Should produce named accounts, relationship owners, pain anecdotes, reachable intros and proof files. Not a light endorsement call.
Validation route — Andrew Carrie
Should pressure-test MAS blocker reality, buyer-map accuracy, partner dynamics and which routefinding offer can credibly be sold first.
Proper persona definition is part of discovery, not post-pack polish
The next discovery pass should create Max Connect personas in the same explicit style as the Smithfield buyer surface: named composite, role, estate shape, pain type, cost of miss, quote, what they buy, how to reach them, confidence state and atom links.
Current personas are strawman composites from secondary research and intake. They are useful only if the interviews turn them into named-account evidence.
Megan, the asset transformation sponsor
Economic owner of operational risk and MAS spend. Define AUM equivalent as asset estate scale, sites, downtime cost, budget line and approval path.
Raj, the CIO / platform owner
Responsible for OpenShift, integrations, security and cloud/on-prem constraints. Needs a credible route before partner selection.
Claire, the maintenance / reliability director
Sees dirty data, mobile adoption, daily-user resistance and reporting pain. Provides exact language for the routefinding offer.
Tom, the FM / service-provider operator
Runs Maximo under client SLAs and procurement constraints. Could need licensing, multi-tenant and service-provider route clarity.
Each persona needs these fields before the offer is chosen
- Role + estate shape: title, sector, sites/assets, Maximo footprint, MAS exposure.
- Pain type + cost of miss: sharp/slow-drip/continuous, downtime or budget consequence, quote language.
- What they buy: routefinder, readiness assessment, AppPoints review, integration risk map, training plan, partner matching or support audit.
- How to reach them: Rich/Andrew intro, IBM/partner route, events/user groups, LinkedIn/content, incumbent SI path.
- Evidence state: source file, account evidence, relationship owner, quote language and missing proof.
The next questions need context and role-specific agendas
The next questions should say what kind of answer is wanted and why it matters. Abstract feedback is less useful than named accounts, direct quotes, price evidence, product-gap examples and source files.
The shared question bank separates common evidence tests from role-specific work: Rich mines end-user, user-group, survey and account reality; Andrew mines implementation detail, consultancy economics, rates and product gaps.
These questions define the first partner discovery pass and the survey follow-up agenda.
| Test | Question | Evidence needed |
|---|---|---|
| Pack clarity | What is wrong, missing or too upgrade-led in this pack? | Corrections, missing context, claims to demote. |
| Source-room challenge | Which source-room categories actually matter to buyers, and which are just implementation background? | Category ranking, sources to ignore, sources to promote, missing source files. |
| Named organisation truth | Which Maximo-using organisations and survey respondents should be prioritised first? | Account list, survey response, relationship owner, urgency signal. |
| Rich agenda | What should Rich ask follow-up respondents from an end-user/user-group perspective? | Follow-up call agenda, Drax/user-group anecdotes, account pain. |
| Andrew agenda | What should Andrew answer from a consultant/configuration/implementation perspective? | Service/rate evidence, implementation patterns, product-gap ideas. |
| Opportunity truth | Which is the strongest first wedge: migration, optimisation, product gap, AppPoints/rates, partner selection, training/adoption or community route? | Wedge ranking with reason, account fit, timing and proof. |
| Product-gap truth | Where might Max Connect build software that bolts onto Maximo/MAS? | Mobile, AI/analytics, asset-performance data, reporting, integration, workflow evidence. |
| Price truth | What price points, day rates, packages or service shapes are in the right ball park? | Examples of services/rates that sell or fail. |
Capture these phrases verbatim where possible
- “The best first opportunity is…” Force the why, target prospect, timing and price/rate evidence.
- “That is too narrow because…” Separate migration, optimisation and product-gap corrections.
- “The organisations to call first are…” Write the account names, survey response, route and follow-up agenda.
- “Clients would actually pay for…” Capture service/rate/package evidence, not just interest.
- “Maximo/MAS does not do X well enough…” Turn product-gap comments into buildable hypotheses with proof requirements.
Use Drive as the shared source room, not just a drop box
The shared Google Drive folder now contains the categorized NotebookLM export. Treat Drive as the inspectable source room: reviewers can see the source categories and add account lists, call notes, survey exports, pricing examples and product-gap evidence beside the existing material.
NotebookLM remains the internal synthesis tool. The Drive source room and /source-index/ route are the reviewer-facing evidence layer.
/source-room-reviewable/00_SOURCE_INDEX/
Manifest, source checking guide, and sources-by-category index for all 420 NotebookLM sources.
02/01_MAS migration upgrade and modernization/
Migration route material: upgrade paths, EOS pressure, MAS transition playbooks and IBM migration guidance.
03/03_OpenShift architecture deployment and infrastructure/
The largest category: deployment, sizing, cloud/on-prem, OpenShift and operating-model material.
04/04_Security identity administration and governance/
Security, identity, administration and governance sources for regulated/operational risk conversations.
05/05 + /06 Integration, data and reliability/
Integration/API/customisation plus data migration, backup, restore and reliability sources.
06/07 + /08 Optimisation, mobile, AI and product capability/
Performance/mobile operations plus AI, Predict, Health, Monitor and Visual Inspection material for product-gap testing.
07/09 + /10 Community, partners and market/
User groups, events, training, community signal, partner/vendor and competitive context.
08New reviewer additions
Add account lists, call notes, survey exports, price/rate examples and product-gap proof into Drive beside the source-room categories.
Hadrian has narrowed the thesis; Rich and Andrew now validate route and delivery
The first founder interview should now be treated as ingested evidence, not just background conversation. It establishes a stronger internal thesis: consulting-first Maximo/MAS discovery, readiness and ITT support is the lead wedge; AI/tooling is delivery leverage; productisation waits until client patterns repeat.
The next interviews are not generic expert calls. Rich should validate buyer pain, user-group language, named organisations and willingness to pay. Andrew should validate delivery feasibility, artefact quality, scope boundaries, partner economics, rates and governance fit.
Use each partner for a different proof burden.
| Partner | What to prove | Evidence to capture |
|---|---|---|
| Hadrian — ingested | Shared proposition, market gap, operating model, consulting-first sequence, internal-AI posture. | NotebookLM source 8d9b797b-91a5-412a-9220-cacba9d1fa1c; atom MAXCONNECT-INTERVIEW-001; Drax/process and supplier-ecosystem examples. |
| Rich — next | User-group and product-owner pain: who is underserved, what language they use, which organisations are reachable, what would make them take a call. | Named accounts, survey respondents, direct quotes, user-group route, first-call agenda. |
| Andrew — next | Technical and delivery credibility: can the sprint be delivered well, what artefacts matter, what price/rate bands work, where product gaps are real. | Service package shape, rate examples, implementation failure modes, scope boundaries, MOU/equity implications. |
Use this as the working offer until contradicted
- Offer: Maximo/MAS Discovery & ITT Readiness Sprint.
- Buyer: Underserved mid-market or asset-heavy Maximo owner/product owner/operator who cannot get responsive, affordable support from big suppliers.
- Outputs: current-state map, pain/risk register, requirements brief, ITT/supplier support, upgrade/readiness options and next-step roadmap.
- Price hypothesis: £5k–£10k entry engagement; validate before external positioning.
- AI posture: invisible internal accelerator for quality/speed/repeatability, not the front-of-house product promise yet.