The pre-transformation intelligence platform
Diagnose before you buy.Priorities before platforms.
Disruption rarely breaks an organisation all at once. It finds the vulnerability already sitting in the operating model and turns it into operational failure. MBT finds that vulnerability first: it measures each signal against how the business actually runs, isolates the root inside the operating model, and charts an evidence-grounded direction for both your business and technology transformation roadmaps — priorities your board can defend, before capital is committed.
The path MBT follows
- Signals
- Patterns
- Implications
- Priorities
- Decisions
The scientific lineage
Seventy years of published decision and systems science — not a generic answer engine. Select a name to see the rule it sets inside MBT.
Theorist names, theory titles and seminal works are cited for scholarly attribution and methodological lineage only, as permitted for nominative academic reference. The named authors, their estates and their affiliated institutions do not sponsor, certify, endorse or have any affiliation with MBT. All descriptions, wording and software are original works of MBT and are not authorised derivatives of the cited publications. To query any attribution, contact contact@hrmbt.com. Read the full attribution terms.
Diagnose the operating model before transforming.
- Workforce
- Business Dynamics
- Technology Pressure
- Market & Industry
- Regulation & Compliance
- Organizational Realities
Why pre-transformation intelligence
The costliest HR decisions are made before anyone buys anything.MBT is the intelligence layer for that phase.
Before a business case is written, the evidence that should shape it sits scattered across owners, formats and systems — and the real causes are rarely the ones in the complaint.
- Geopolitics
- Economy
- Labour regulation
- Industry
- Technology & AI
- Local events
- Company-specific signals
- Your own secure workspace documents and private enterprise files
What MBT does with them
You choose which signals to scan. MBT then helps you group them, work through what they could mean for your organisation, and turn the ones you confirm into a prioritised transformation view.
- Signals
- Patterns
- Implications
- Priorities
- Decisions
The pre-transformation deficit
Software gets chosen before the cause is understood.
- Workforce data
- HR systems
- Market research
- Business strategy
- Technology roadmaps
- Regulatory changes
- Industry signals
- Consulting reports
- Too many signals.
- Too many possible initiatives.
- Too much uncertainty.
What needs to change across the business — and how does technology enable it?
That is the question MBT answers before a platform is chosen — with evidence attached, scoped to your organisation, industry and geography, and with clear direction for both your business operating model and technology enablement roadmaps.
How MBT works
Eight steps from organisational context to a decision leadership can take.
Each step goes deeper than the complaint in front of you: what people experience day to day is traced back to what is really causing it, and forward to what it costs the business — so nothing is treated as a cause until it holds up against evidence. You stay in control at each step — MBT proposes, you confirm.
SSRN Working Paper
The Epistemic Standard: A Causal Hierarchy and Provenance Framework for Pre-Transformation Diagnostic Research
Available on SSRN · Abstract ID: 7613859
Author-deposited working paper. Listing on SSRN does not imply endorsement by SSRN or Elsevier.
Every finding sits on one seven-level ladder
- Root cause
- Problem
- Challenge
- Complexity
- Scenario
- Symptom
- Business impact
- 01
Scope
You set the organisation, industry classification, geographies, the situation in view and the research language — screens, your typed input and every export then stay in that one language.
- 02
Industry & geography findings
A sourced baseline of what is shaping your industry and the places your workforce sits.
- 03
Current affairs radar
You choose which current-affairs categories to scan, then keep only the sourced items you consider relevant.
- 04
Consolidated hierarchy
Findings are placed on one cause-to-impact ladder, so symptoms are never mistaken for causes.
- 05
Discover & relate
Plain-language questions — including ones designed to disprove — let you confirm or reject what applies to you.
- 06
Ops & capability clustering
Confirmed problems are grouped by the root cause they share, each with its own journey map.
- 07
Solution & priority
Transformation acts are mapped across business operations and technology enablement, scored against impact and effort, and sequenced into an actionable roadmap.
- 08
Export & share
A research dossier, transformation heatmap, analysis trees and requirements specification, built only from what you confirmed, in the study's research language.
What you get
From intelligence to action
Four deliverables come out of a single run — a full research dossier to defend the decision, a heatmap of the prioritised objectives, analysis trees that trace each problem to its root cause, and a requirements specification to hand to a vendor. Each is built only from what you confirmed, produced in the study's research language, carries the run reference and review dates, and lists the sources behind every claim.
Executive Research & Diagnostic Dossier
Can we defend this decision line by line?
A structured PDF with a clickable contents page: the bottom line up front, a chapter per confirmed problem with its causal chain, journey map, cost of inaction and solution, the priorities with reasons, every source cited, a verification seal showing which claims were checked against primary records, and — when the Workforce Sustainability lens is switched on — a Workforce Sustainability & Governance briefing.
In the workspace: the export stage — downloads as a PDF in the study's research language
Explore an exampleTransformation Heatmap
Where is the pressure greatest across the prioritised objectives?
A single heatmap of every prioritised objective with its ID, scored on impact and effort and grouped into priority tiers — ready to drop into a board pack or your own documents.
In the workspace: the export stage — downloads as SVG
Requirement Solution Analysis Trees
How does each problem connect to what causes it?
A tree for every confirmed problem, tracing it down to its root cause through the levels the research confirmed, and showing whether HR can fix it alone.
In the workspace: the export stage — downloads as SVG
Explore an exampleHR Tech Requirements Specification
What exactly do we hand to a vendor?
Every target outcome turned into phased business transformation acts and line-by-line functional requirements, with agentic AI scenarios and, when the Workforce Sustainability lens is on, a Workforce Sustainability & Governance sheet — capabilities described, never brand names. Delivered as an interactive HTML specification with search and filters, carrying the Excel workbook inside it.
In the workspace: the export stage — downloads as an interactive HTML file that also hands out the Excel workbook
Explore an exampleZero IT integration
Nothing to connect to your core HR systems.
No production system access and no connectors to configure. MBT adds no attack surface to your HR technology stack — you choose what, if anything, to upload.
Time to value
A board-ready diagnosis in hours, not months.
Go from organisational scope to a signed-off research dossier in a working session, instead of a discovery phase that typically runs for weeks.
Workforce Sustainability & Governance lens
Check the people side of a transformation before it reaches the board.
An optional workforce sustainability lens reviews each agentic AI scenario for workforce transition load and human-in-the-loop guardrails, and points to the reference frameworks that fit your scope — such as SEBI BRSR Core Principles 3 & 5 and the Indian Labour Codes, CSRD ESRS S1 and the EU AI Act, or GRI 401–405 and ILO standards. Every line is labelled a hypothesis to test. It covers people and decision governance only. It does not measure environmental impact, carbon or emissions, run employee surveys or green-skills training, or calculate sustainability ratings — MBT diagnoses causes before transformation, it is not a reporting or HR operations tool. It is pre-audit support, never a formal disclosure.
- Frameworks matched to your geography
- Human-in-the-loop guardrails
- Briefing in the dossier and workbook
Why MBT
Unconflicted, causal, evidence-led.
MBT sells no software and bills no implementation, so it gives unbiased direction for both your business operating model and technology transformation roadmap. It exists for one job: deciding what to change, and in what order, before the money is committed.
- 01
Contextual
Not generic HR trends.
Intelligence scoped to your organisation, industry and the geographies your workforce actually sits in.
- 02
Evidence-backed
MBT does not treat AI output as evidence.
MBT is designed around a proprietary research method; AI supports defined research tasks, not unchecked conclusions. Evidence comes from identified sources, and AI-generated analysis is labelled as interpretation, never as fact — findings carry their sources and an evidence-strength label, and say plainly where evidence is thin, contested or missing.
- 03
Vendor-neutral
Priorities before platforms.
Transformation priorities are established first, on the evidence. Technology and vendor choices are then assessed against those priorities — never the other way round, and never against a shortlist MBT has an interest in.
- 04
Decision-oriented
Not another research library.
Every output is designed to move a specific decision forward, in a format leadership can act on — with the reasoning, the sources and the open questions attached.
- 05
Hybrid Research Orchestration
Public evidence and your own files, together.
Simultaneously combines public web data with your own private, uploaded documents (PDFs, reports, benchmarks) with an automated AI Relevancy Guardrail to prevent noise — and your documents are cited by file name wherever they shape a conclusion.
The research standard
Five disciplines behind every MBT finding
Most pre-transformation research fails in three ways: repeated stories mistaken for consensus, symptoms mixed with causes, and diagnoses shaped by what can be sold next. MBT is built to avoid all three.
A causal chain, not a flat issue list
Every finding is placed on one level of a seven-level chain from root cause to business impact, so a symptom such as attrition is never mistaken for its cause.
Every claim carries its label
Findings are marked as fact, evidence, inference or hypothesis. Unsupported points stay labelled as inference, and no source is ever invented.
Origins counted, not articles
Ten articles repeating one survey count as one origin. Where sources disagree, the conflict is disclosed rather than averaged away.
Separated research roles
Finding evidence, synthesising it and reasoning over it are kept as distinct tasks, with reasoning run at a fixed setting for repeatable answers.
Technology honesty
A low or no technology contribution is a valid answer. Where the cause sits in structure, governance or leadership mandate, MBT says HR-led change alone will fail.
| Generic AI | Typical desk research | MBT | |
|---|---|---|---|
| How problems are structured | Flowing prose summary | Lists of pain points or challenges | Seven-level causal chain |
| How sources are weighed | Blended into one answer | Secondary research, analyst judgement | Independent origins counted; conflicts disclosed |
| How certainty is shown | Uniformly confident tone | Varies by author | Fact / evidence / inference / hypothesis labels |
| Technology stance | Often suggests tools | Can be shaped by implementation scope | No vendor names; low tech contribution accepted |
| Structural limits | Rarely raised | Depends on engagement scope | Explicit “HR-alone will fail” escalation |
The architectural difference
The guardrails MBT enforces on every study
Modern AI models can follow strict research rules when they are given them. MBT writes those rules into the workflow so they apply to every study. MBT is not an authoritative judge; it gives your leadership an evidence ledger to inspect before committing transformation capital.
Guardrail MBT enforces
What you see in the output
Separate research roles
GuardrailSource discovery, citation extraction, synthesis and diagnosis are run as separate, fixed steps in every study.
In the outputEach step is visible in the study record, so you can see where every finding came from.
Origin-based source counting
GuardrailSyndicated copies of one document are counted as one origin, not several.
In the outputCorroboration is reported as the number of independent origins, not the number of articles.
Mandatory claim labels
GuardrailEvery non-obvious claim must be labelled Fact, Evidence, Inference or Hypothesis.
In the outputUnsourced points appear as inferences, never as established facts.
Contested evidence disclosed
GuardrailConflicting or single-source findings must be disclosed, not quietly resolved.
In the outputWhere your own document overrides public evidence, the report says so in plain words.
Seven-level causal chain
GuardrailEvery finding is placed on one level: root cause, problem, challenge, complexity, scenario, symptom or business impact.
In the outputSymptoms are kept apart from root causes, and business impact is always included.
Locked study scope
GuardrailGeography, industry and HR stage are fixed when the study starts; inputs are checked for relevance against that scope.
In the outputOff-scope text and documents are flagged before they are used.
Technology honesty
GuardrailA technology rating of None or Low is an accepted answer; no vendor or product names are allowed.
In the outputAny technology suggestion must trace back to a researched problem.
HR-alone limit
GuardrailWhere a root cause sits in governance, funding, business model, structure or leadership mandate, the rule must be triggered.
In the outputThe output states that HR-led change alone will fail and names the wider prerequisite.
Dated, traceable output
GuardrailEvery output carries a run ID, a valid-as-of date and a re-check-after date.
In the outputYour leadership can inspect the evidence ledger and know when to refresh it.
Rules built in
GuardrailThese rules are part of the workflow, not something the user has to type into a prompt.
In the outputThe same standards apply to every study without writing or maintaining prompts.
Same rules, every study
The rules stay the same as the underlying AI models change.
No prompts to write.Every claim labelled.Every output dated.
Who it is for
Built for leaders making transformation decisions
Everyone works in the same workspace — there are no separate role-based views. Whoever has to defend the decision afterwards gets the reasoning, the sources and the evidence-strength labels with it.
- CHROUnderstand what matters most and make strategic transformation decisions with greater confidence.
- HR Transformation LeaderIdentify, prioritise and sequence transformation opportunities.
- COO / Transformation LeaderConnect workforce and HR transformation to broader business priorities.
- CIOUnderstand HR technology and transformation implications before major technology decisions.
When leaders use MBT
The business moments where the cause has to be known first.
Each scenario is researched as a possibility to confirm or reject in your organisation — never assumed to apply to you.
Growth & footprint
- Rapid headcount growthTest whether hiring pace is outrunning the processes, managers and systems meant to absorb it.Read the scenario
- Multi-country expansionSurface statutory, payroll and talent conditions in each new market before the entity opens.Read the scenario
- Manufacturing & blue-collar scale-upCheck whether shift, safety and frontline workforce practices can carry a larger operation.Read the scenario
- New plant or site launchExamine whether workforce readiness, local hiring and compliance are in place for go-live.Read the scenario
Deals, risk & continuity
- Merger or acquisition integrationIsolate policy, payroll and operating-model conflicts between combining entities before Day 1.Read the scenario
- Compliance or audit failureTrace an audit finding back to whether the cause sits in process, data, systems or governance.Read the scenario
- Leadership or succession gapTest how exposed critical leadership roles are, and what is really limiting the pipeline.Read the scenario
- High attrition in critical rolesSeparate the symptoms of attrition from the operating conditions that may be driving it.Read the scenario
- Employee experience declineFind out whether falling sentiment points to processes, managers, tools or the wider model.Read the scenario
Operating model & modernisation
- Cost reduction pressureDistinguish cost that can be removed safely from cost that protects critical capability.Read the scenario
- Shift to HR shared servicesCheck whether processes are standard and stable enough to centralise before the move.Read the scenario
- Digital & ERP-led modernisationEstablish what the operating model must change so a large system rollout does not automate today's problems.Read the scenario
- Before selecting HR technologyConfirm the requirements and priorities on evidence before a multi-year platform commitment.Read the scenario
- Troubled programme resetGive a stalled or over-budget programme an independent view of whether the cause is technology, governance or change load.Read the scenario
How enterprises engage
Three ways to bring MBT into a decision.
Every engagement starts with a private briefing. Access is approved for verified business email addresses, and nothing needs to be connected to your HR systems.
- 01
Pre-transformation diagnostic
Best for: a board paper, investment case or technology selection
A focused run on one decision. You set the scope, confirm or reject what the research finds, and leave with the dossier, transformation heatmap, analysis trees and requirements specification.
Typical scenarios
- Before selecting HR technology
- Merger or acquisition integration
- Multi-country expansion
- 02
Programme reset
Best for: a transformation that is stalled, over budget or resisted
An independent, vendor-neutral view for the steering committee of where the programme is really breaking down — and whether HR-led change alone can fix it.
Typical scenarios
- Troubled programme reset
- Digital & ERP-led modernisation
- Shift to HR shared services
- 03
Enterprise workspace
Best for: transformation and HR strategy teams running repeated diagnostics
An ongoing, administrator-approved workspace for your team to run studies across business units and geographies, with your uploaded documents kept private to your organisation.
Typical scenarios
- Cost reduction pressure
- High attrition in critical roles
- Leadership or succession gap
Enterprise governance manual
Enterprise Onboarding, Regional Data Center, Tenant Provisioning and Access
NDA, services agreement and data protection addendum before access; hosting region choice agreed in contract; tenant-isolated researcher approval; and data handover and deletion when the engagement ends.
Read the manualInside the platform
See the intelligence behind the decision.
MBT is a controlled-access platform, not a self-serve tool. Accounts are approved for verified business email addresses by an administrator, so the working product and its methodology are shown in a private walkthrough rather than published in full here.
- 01
Scope
You set the organisation, industry classification, geographies, the situation in view and the research language — screens, your typed input and every export then stay in that one language.
- 02
Industry & geography findings
A sourced baseline of what is shaping your industry and the places your workforce sits.
- 03
Current affairs radar
You choose which current-affairs categories to scan, then keep only the sourced items you consider relevant.
- 04
Consolidated hierarchy
Findings are placed on one cause-to-impact ladder, so symptoms are never mistaken for causes.
- 05
Discover & relate
Plain-language questions — including ones designed to disprove — let you confirm or reject what applies to you.
- 06
Ops & capability clustering
Confirmed problems are grouped by the root cause they share, each with its own journey map.
- 07
Solution & priority
Transformation acts are mapped across business operations and technology enablement, scored against impact and effort, and sequenced into an actionable roadmap.
- 08
Export & share
A research dossier, transformation heatmap, analysis trees and requirements specification, built only from what you confirmed, in the study's research language.
Walk through the real product
A private briefing walks through the live workspace and a worked example end to end, using your own organisational context rather than a canned demo.
Trust
Enterprise intelligence requires enterprise trust.
What follows is a summary. The published notices are the authoritative statements — no certification is claimed unless it has been formally obtained.
Data ownership
Your data is yours. It never trains our models.
Nothing you enter, upload or generate is used to train AI models, and nothing is sold or shared for marketing. Your research stays inside your account, is visible only to you and your approved colleagues, and can be exported or deleted at any time.
For sensitive work you can switch on a zero-retention run: the research run itself is not written to your browser or our database, no result is cached, and the session ends when you close the tab — you keep only what you export. Files you have uploaded to your secure workspace are held separately and stay until you remove them.
Secure workspace uploads: your files are private to your organisation, separated at the database level from every other customer, checked for relevance before they are used, and never sent to the public research engines. They are kept so you can reuse them across runs, and deleting a file or purging the workspace permanently removes it along with everything derived from it.
Business-email access, isolated per organisation, encrypted in transit, deletion on request. Read how we handle data.
Data handling
Your inputs and research outputs are stored against your own approved account and are not readable by other accounts, enforced by database-level access rules.
Access control
Access is granted by an administrator to verified business email addresses; there is no public sign-up, and access can be withdrawn at any time.
Sign-in codes
Sign-in uses single-use codes, valid for a limited time, sent to the approved business mailbox.
AI and data usage
How AI is used in research and what is sent to model providers is described in the data and security notice.
Privacy, retention and deletion
Retention and deletion practices, and applicable data-protection commitments, are set out in the privacy notice.
Know the cause before you commit the capital.
Move from competing priorities and vendor pitches to evidence-grounded direction for both your business and technology transformation roadmaps — what must change in the operating model, and how technology accelerates it.
Administrator-approved access