Ten core responsibilities of the role. For each: what it takes today, and the deliverable Vera hands you. She meets all ten. Most candidates stop at four.
Map the landscape: ERP, CRM, integrations, custom apps and the processes they run.
Months of interviews and spreadsheets that are out of date on delivery.
Atlas map of your whole estate, linking code in every system to the process it serves. Plus Vera Wiki, rewritten every refresh.
Process mapping →Review designs and change requests before they go ahead.
Senior developers trace callers by hand. Impact is found in testing.
An impact analysis for any change: callers, processes, reports, and the risks, each with a source.
Change impact →Define where the architecture is going and the roadmap to get there.
Scope set in workshops, based on whoever is still around.
Migration readiness assessment for S/4HANA, cloud moves or platform consolidation: what to bring across, retire or rebuild.
Migration scoping →Make sure what's written down matches what runs.
Docs drift. Nobody knows which version to trust.
Reconciliation report: every rule labelled agree, disagree or gap, with both sources side by side.
Reconciliation →Know what depends on what before anything moves.
Undocumented interfaces surface when they break.
Dependency and interface maps, including the integrations no document mentions.
Dependency tracing →Decide which applications and customisations to keep, consolidate or retire.
Overlapping apps and custom code nobody can link to a business need.
A rationalisation list: overlapping capabilities across systems, and code with no business process behind it.
Rationalisation →Make sure AI tools give answers the business can rely on.
Every copilot builds its own partial picture. None cite sources.
Knowledge layer: one governed model your copilots and agents query, with citations and declared gaps.
Grounding AI →Keep what the organisation knows when people move on.
Knowledge walks out with the developer or the partner.
A living model of what the system does and why, that any new joiner can ask.
Knowledge retention →Answer leaders' questions about systems, fast and accurately.
Questions take days and come back as opinions.
Plain-English answers in seconds, every sentence labelled and linked to source.
Ask Vera →Work out what goes with a business being separated.
Separation scoped late, under deal pressure.
A separation map: which code, interfaces and processes belong to each side.
Carve-outs →Start with one system and one deliverable: an Architecture Snapshot, at a fixed price. See the evidence before you commit.