Built for the Extension scenario — when an acquirer buys a company to extend its product line and must fold the acquired entity’s SAP landscape into its own. This intake profiles that incoming landscape end-to-end, giving the consolidation programme (and ODIN’s agents) the ground truth needed to plan the merge with confidence.
Due diligence content is sensitive. Before you start, here is exactly where your answers live and what leaves your device.
Everything you type into the questionnaire is held in your browser’s local storage only. There is no database, no server-side persistence, and no user account. Close the tab and the content stays on your machine — by design.
The export buttons generate the JSON or Word file directly in your browser. Nothing is transmitted to Tarento or anyone else unless you choose to share that file.
The .docx and JSON exports are produced entirely in-browser and downloaded straight to your machine. You decide who receives them — over your own email, secure file share, or deal-room — exactly as you would any other diligence artefact.
Clearing your browser storage (or using a private window) removes all locally saved answers. Export first if you need to keep them.
This page is served as a static web app. The host can see that someone visited the URL, as any web server would. It has no visibility into the answers you enter, select, or export.
Your questionnaire content never reaches the hosting infrastructure. The only outbound requests on load are for the page assets themselves.
Ten domains structured so the acquired entity can route sections to the right SMEs — surfacing everything the consolidation team needs to merge the incoming landscape into the acquirer’s. Three areas receive deeper coverage based on common consolidation risk: data modelling, process harmonization and integration architecture.
Basic information about the target entity and engagement scope. Seeds the agentic M&A framework — feeds the Engagement Context Agent and ODIN orchestrator.
Inventory of SAP products, versions, and deployment models. Consumed by the Landscape Discovery Agent to build the source-side knowledge graph.
Underlying infrastructure, sizing, HA/DR, and technical operations. Feeds the Infrastructure & Sizing Agent in the agentic framework.
SAP modules and business processes in productive use. Feeds the Functional Footprint Agent and seeds the Gap Register against the acquirer's S/4HANA template.
Focus on master data structures, harmonization state, and custom data model. Primary input to the Data Model Mapper Agent — drives the harmonization plan in the agentic framework.
Process maturity, standardization, and variation across the organization. Feeds the Process Harmonization Agent — variants and RICEFW signals seed the Fit-to-Standard agent.
Integration patterns, middleware, interfaces, and APIs. Feeds the Integration Architecture Agent — drives the target integration blueprint in the agentic framework.
Identity, authorizations, GRC, and regulatory posture. Feeds the Security & Compliance Agent in the agentic framework.
Run model, vendors, and SAP organization. Feeds the Run-Model Agent for Day-1 / Day-2 operating model design.
In-flight initiatives, technical debt, and known risks. Feeds the Risk & Roadmap Agent — outputs converge into ODIN's phase agents for the integration plan.
The intake is the front door to Tarento’s agentic M&A framework: Agentic AI as the engine, ODIN as the vehicle that makes it enterprise-safe and compounding. Every acquisition processed through ODIN makes the next one faster.
Every M&A phase has a defined methodology — what to ask, how to decide, what good looks like. Injected directly into every agent, at every step.
Gap analysis, data model mapping, configuration precedent retrieval and custom-code classification — months of consultant hours produced in weeks as a validated starting point.
Clean handoffs between phases, real-time programme health, and an institutional memory that compounds with every subsequent engagement.
The agentic org chart
Layer 1
Master Orchestrator
Holds program state. Routes work. Escalates to humans when it matters.
Layer 2
Phase Agents
One per M&A block. Domain-specific. Produce machine-readable handoff packets.
Layer 3
Skill Agents
Narrow, reusable capabilities — where Tarento’s IP compounds across acquisitions.
Foundational assumption: one known (the source organisation’s S/4HANA template), one unknown (the acquired entity’s landscape). This questionnaire is how the unknown becomes known — the knowledge graph the Assessment Agent, Gap Register Builder and Data Model Mapper work against.
Open the interactive form to capture answers in-app, or download the Word version to send to the acquired entity ahead of consolidation planning.