Focus: Maximo configuration/development/implementation across industries, consultancy rates and service shapes, client demand patterns, and credible product-gap opportunities.
Andrew validates Max Connect from the practitioner/consultant side: configuration, development, implementation reality across industries, client demand patterns, rates and service shapes, and where Maximo/MAS may leave room for bolt-on products.
This is the asynchronous version. Fill it in at your own pace. Answers autosave in this browser only. This static page does not submit files or answers to the team. When complete, use Copy response or Download Markdown, then send the result and upload source files to the Max Connect Discovery shared Drive folders.
Prioritise implementation detail, consultancy economics and what clients repeatedly buy or reject.
Test migration, optimisation and product-enhancement ideas separately.
Mine for credible software-product gaps around mobile, AI/analytics, asset-performance data and workflow tooling.
Make the ask explicit: choose the best first opportunity, say why, and separate proof from opinion.
1. Which Max Connect opportunity should be tested first, and why? Choose from migration routefinding, optimisation, product add-ons, AppPoints/rates advice, partner selection, training/adoption, or another option.
2. What evidence makes that opportunity stronger than the others: named accounts, lived project experience, budget/rate evidence, survey response, user-group signal, or technical proof?
3. What are you certain about from direct work, what are you inferring, and what is only hearsay? Give one example in each bucket.
4. Which claims in the current pack feel too upgrade-led, too vague, or missing important context?
Account truth
02
Named account and survey follow-up
Use this section to turn known Maximo-using organisations, relationship knowledge and survey responses into a follow-up agenda.
1. From the known Maximo-using organisations and survey respondents, which names should be prioritised for follow-up calls first?
2. For each priority organisation, what do we know already: sector, Maximo/MAS state, current pain, relationship owner, warm intro path, and likely decision maker?
3. Which organisations are likely upgrade-led, which are optimisation-led, and which might expose product-gap opportunities?
4. What should Rich ask the survey respondents on a follow-up call so we learn what to target, how, why, when and at what price point?
Opportunity truth
03
Migration, optimisation and product gaps
Do not let MAS migration swallow the whole opportunity. Test migration, optimisation and bolt-on product ideas side by side.
1. Migration: where do clients need help moving from legacy Maximo to MAS — platform, data, integrations, AppPoints, change, testing, partner choice, or programme ownership?
2. Optimisation: where could clients improve current ways of working against the capabilities of the newer platform before or after migration?
3. Product gaps: where might IBM/Maximo leave room for Max Connect software add-ons — mobile workflows, analytics, AI-assisted asset-risk analysis, reporting, data quality, integrations, or planning tools?
4. For each opportunity, say whether it is likely a paid advisory/service wedge, a repeatable software-product idea, or a later-stage line of business.
Buyer truth
04
Buying committee and price reality
A good wedge needs a buyer, budget line, acceptable rate and reason to buy now.
1. Who owns the pain and budget for each opportunity: asset leader, CIO/IT owner, operations, finance/procurement, engineering/reliability, current SI, IBM contact, or service-provider lead?
2. What service/rate shapes do clients actually buy in this market, and which consultancy services or rates tend not to sell?
3. What price band would feel credible for a first paid conversation, diagnostic, workshop, assessment or product prototype?
4. What proof would a sceptical buyer need before approving the first paid step?
Market truth
05
Competitive, partner and channel reality
Positioning only works if current alternatives, partner boundaries and warm channels are named.
1. Who is already advising or delivering for these accounts: IBM, incumbent SI, reseller, independent consultant, internal team, or partner route?
2. Where are those alternatives strong, and where do users still feel exposed or underserved?
3. Which user-group, event, survey, partner or LinkedIn routes can create credible conversations without cold selling?
4. What should Max Connect avoid saying or selling because it would conflict with partners, overclaim delivery capacity, or sound like generic consultancy?
Close
06
Proof pack and first-wedge decision log
End with usable decisions: first wedge, first targets, missing proof, and what changes in the offer.
2. Name the first three target conversations and the exact reason each should be approached.
3. List source files, survey outputs, account lists, call notes, screenshots, pricing/rate notes or examples that should be added to Drive and the evidence corpus.
4. Promote, demote or kill the major assumptions. What should the offer say differently because of your answers?
Andrew lens
07
Andrew-specific: implementation detail, rates and product gaps
Use Andrew’s consultant/configuration/development/implementation experience across industries to test what can be sold and built.
1. Across industries, what do Maximo clients repeatedly need help configuring, developing, implementing or untangling?
2. Which consultancy services, day-rate/package shapes and price points sell in this market, and which ones fail to sell?
3. Where do clients ask for product capability that Maximo/MAS does not cover well enough: mobile, AI, analytics, asset-performance prediction, reporting, integrations, workflow UX, or data quality?
4. Which product add-on ideas are technically credible for Max Connect to explore first, and what proof or prototype would validate demand?
Autosave ready. Nothing is submitted from this page.
What good looks like
Every question has an answer, even if the answer is “unknown”.
Every strong answer names the supporting doc, source link, screenshot, account note or proof.
Five named accounts or a clear reason the account list is not ready.
Three account conversations ranked by reachability.
One first-offer recommendation with proof gaps.
Submission boundary
This is a static workbook. It saves to this browser only and does not sync across devices. Use Copy response or Download Markdown, then put the Markdown and source files into the Max Connect Discovery shared Drive folders. Files described here are evidence references until they are uploaded to Drive and absorbed into atoms.
