Built for everyone who models the business
Architects, consultants, process and data teams, supply-chain and simulation experts — each arrives with different tools and the same frustration. Find your role below, and the outcome Metapad unlocks for it.
Enterprise Architects & EA Teams
Prototype your architecture before you commit — on a metamodel you define yourself, in a model business stakeholders can actually read.
EA practitioners and enterprise architecture teams who already think in models — capabilities, processes, systems, dependencies. They need a flexible modeling tool that lets them define their own metamodel rather than conform to a vendor's pre-baked taxonomy, and they immediately understand "prototype your architecture before committing."
Where today's tools fall short
Static tools (PowerPoint, Visio) lose dependencies and go stale. Fixed-schema EA suites (LeanIX, Ardoq) force pre-baked taxonomies. Business stakeholders can't read EA diagrams without an architect translating them.
Management Consultants (Strategy & Operations)
Leave behind a living model, not a slide deck that decays — a deliverable the client keeps evolving, and an asset you reuse on the next engagement.
Strategy and operations consultants who build enterprise models for clients constantly — Big 4 advisory, boutique strategy firms, digital transformation consultancies. The prototype metaphor (analyze, redesign, recommend) maps directly to how they already work, and a living model is a far stickier deliverable than a slide deck.
Where today's tools fall short
Models live in slides and spreadsheets that decay the moment the engagement ends. Reusing assets across engagements is painful. The deliverable is not something the client can keep evolving.
Business Process & Operational Excellence Teams
Prove the reorganisation works before you touch the organisation — simulate the redesigned process on a model wired to the real systems behind it.
Teams mapping and redesigning processes, org structures, and value chains. Simulation is the killer differentiator — they can prototype the change before they implement it, dry-running a reorganization on the model rather than on the organization.
Where today's tools fall short
Whiteboarding tools (Miro, Visio) are too shallow for serious analysis. Specialized BPM tools are expensive, siloed, and disconnected from business architecture and IT systems.
Data Officers & Strategic Data Teams
Connect data to the business context that gives it meaning — and prove GDPR / AI Act compliance from a model that stays current instead of a catalog that locks you in.
CDOs, data governance leads, and data architects responsible for the data landscape — domains, ownership, lineage, policies, quality. Regulatory pressure (GDPR, AI Act, data mesh adoption) makes a flexible modeling substrate that connects data context with business context increasingly urgent.
Where today's tools fall short
Rigid catalogs (Collibra, Alation) lock you into their schema. Spreadsheets can't capture relationships. Data context is disconnected from the business context that makes it meaningful.
Strategic Supply Chain Management
See past tier-1 before risk materialises — model the whole supply network and satisfy LkSG / CSRD from the same graph, not a manual report.
Supply chain strategists, transparency officers, and risk managers. Supply chains are inherently graph structures — suppliers, facilities, products, flows, risks — and EU regulation (LkSG, CSRD) now demands documented supply-chain models. transentis already has strong relationships in this community through the beer distribution game and BPTK.
Where today's tools fall short
Visibility breaks down past tier-1 suppliers. Risk concentration is invisible until it materializes. Compliance reporting is manual and disconnected from operational data and contracts.
System Dynamics & Simulation Practitioners
Bring your simulations onto a collaborative, visual surface — and out of the silo, connected to the enterprise model that gives them context.
Practitioners already in the transentis / BPTK ecosystem who understand modeling deeply and want a visual collaborative IDE on top of simulation. Smallest segment numerically, but highest product-market fit — and a natural source of advocates and case studies.
Where today's tools fall short
Existing SD tools lack collaborative visual modeling surfaces and are hard to share with non-modelers. SD models tend to be siloed from the rest of the enterprise model that gives them context.