Skip to content
eavantage

eavantage documentation

This is the working guide for consultants running an engagement in eavantage. It covers the workflow end to end — starting an engagement, bringing in a client’s material, reviewing what the AI proposes, designing the target state, and closing out — and what each person on the team can do.

It assumes your firm already has eavantage running (or a trial instance) and that you have an account in it. If you’re still deciding whether eavantage is right for your firm, the main site is the better starting point — start with How it works.

How eavantage works, in one paragraph

Section titled “How eavantage works, in one paragraph”

You give eavantage a client’s discovery material. The AI reads it and proposes candidate architecture elements — capabilities, processes, applications, the relationships between them. Nothing the AI proposes is authoritative until a person with the right permission approves it. Approved elements, and only approved elements, enter the model of record, which a single software component writes — nothing else can. Every proposal, edit, and approval is recorded. That is the whole product: AI does the reading and the drafting; your team keeps the judgement; the trail shows what happened.

What’s in this guide

Section titled “What’s in this guide”
  • Start here — the concepts you need before touching an engagement: the governed loop, the roles, and the six phases with their gates.
  • Running an engagement — the phase-by-phase tasks, from platform setup to closure.
  • Deliverables and standards — generating deliverables, exporting to EA tools, and the standards library.
  • The AI assistant and the client portal — the in-app assistant and what clients see.
  • Reference — file formats, the role-and-permission matrix, a glossary, and troubleshooting.

A note on honesty

Section titled “A note on honesty”

This guide describes what eavantage does today, including where a capability is partial. The Security & data handling and Capabilities pages on the main site are candid about the same things — the client portal is the least-developed area, fine-grained permissions are only partly wired, and there’s no at-rest encryption in the product. Where that affects how you should work, the relevant guide page says so.