Consulting engagements change every week. AUVY keeps each one current.

For consultancies, AUVY keeps every client engagement current. It reads the client's mail, your interview and workshop notes and the deliverables, flags requests that go beyond the proposal, and drafts the change note and the follow-up with a numbered source on every line. The partner signs off.

← Use casesFor: Partners, engagement managers, consultants, and the client team they work with

Consultancies

A week on an engagement.

The request arrives in a side sentence: “could you also look at the Nordic market?” at the end of a mail after the steering committee.
The proposal, the work plan and the team's picture drift apart, and the engagement manager rebuilds the status before every client meeting.
On fixed-fee work, the extra deliverable gets absorbed, and at the end nobody can show where the scope moved.

Use cases

What comes in, and what AUVY does with it.

When
The client adds “one more market” at the end of a mail.
AUVY
Marks the request in the mail, checks it against the proposal and the work plan, and names what it touches: interviews, the model, the final deck.
You get
A change note with two options, add it to the budget or swap it for something planned, ready for the partner to accept.
Reads Mail · Proposal v2 · Work plan
When
Twelve stakeholder interviews and three workshops are in.
AUVY
Answers questions across all of them with the passage each answer came from, and shows where two stakeholders say different things.
You get
Findings you can trace back to the interview, for the report and for the client's “who said that?”.
Reads Interview notes · Workshop transcripts
When
Version 7 of the operating-model deck goes to the client.
AUVY
Keeps every version and shows what changed since version 6, next to the client comments the changes answer.
You get
A straight answer to “what did we change since last week?”, with the versions to prove it.
Reads Deck versions · Client comments
When
A consultant rolls off on Friday and a new one starts on Monday.
AUVY
Answers the newcomer's questions from the engagement's own record: what was agreed, what is open, who decides what at the client.
You get
A newcomer who can work on the engagement from the first day.
Reads The whole engagement
When
A new name appears on the client's cc line.
AUVY
Adds the person to the project's People map from what is written: their role, who they report to, which open decisions they are part of.
You get
The client organisation on one map, kept current as the project moves.
Reads Mail · Minutes · Org charts you add
When
The client wants a weekly benefits tracker for the programme.
AUVY
Builds it as a small working tool inside the project from a plain-language request; the team fills and edits it together.
You get
The tracker sits in the engagement, and every version is kept.
Reads Your request · Project files

Sources

Every answer shows its work.

Before a partner puts an answer in front of a client, they want to know where it came from. In AUVY that takes one click.

What did we agree about the Munich site?

The client added Munich as a third site on 12 March.¹ It is covered in the revised offer, section 4.² The workshop date is still open.

2 of 3 sentences have a sourceNo source: “The workshop date is still open.”

Offer v3.docxSource 2 · section 4, lines 12–14

4 Scope, phase 2
4.1 Munich is added as a third site,
as requested by the client on 12 March.
4.2 One workshop and two site visits.
4.3 Dates follow the revised plan.

Example project, synthetic data.

Numbered sources: Every statement in an answer carries a small number. The number points to the file, the version AUVY read and the lines it used.
One click to the passage: Click the number and the file opens beside the conversation, scrolled to the passage and marked in the text. A deck turns to the slide; a spreadsheet selects the cited cells.
It checks itself: AUVY shows how much of an answer is backed by a source and names the sentences that are not, so you know what to verify before it goes out.
Every version kept: Files change during a project. Every version stays, so you can see the text an answer was based on and what has changed since.

Meetings

Steering committees, workshops, the weekly check-in.

AUVY prepares each meeting from the engagement's sources and follows it through from the minutes, notes or transcript you add.

MeetingsBeforeAfter

Steering committeeWhat changed since the last meeting, the decisions the committee has to take, and the change notes waiting for approval, each with its source.Decisions logged with the line of the minutes they came from, tasks with an owner and a date, and the follow-up mail drafted for the engagement manager to accept.

Client workshopWhat each participant has said so far, where they disagree, and the questions still open.Notes and board photos become findings with their source; new wishes are marked as changes against the scope.

Weekly team check-inOne view of what moved on the engagement this week and what needs whom.Tasks updated with owners and dates. Nothing goes to the client until someone accepts it.

How AUVY fits

How AUVY fits the way you have to work.

Client confidentiality: Each engagement is its own project. Consultants on other engagements don't see it unless they are invited; freelancers and partner firms are invited into one project, not your workspace.
The proposal is the baseline: New requests are checked against the proposal and statement of work you give the project, so the scope conversation starts from the documents.
Client sign-off by link: The client approves a change note or answers a question from a link, without an account. The answer is recorded in the engagement.
Deliverables stay yours: AUVY drafts from the engagement's sources and shows which sentences have none. A consultant decides what the client sees.

For every project

The same ground rules, whatever you deliver.

Only what you give it: Each project reads only the sources you give it: a folder, a mail thread, the Outlook, Teams and SharePoint places you connect.
One project, one room: Project content stays in its project. Personal notes stay yours. An outside partner is invited into one project, never into the workspace, and a read-only link shows one view and nothing else.
A person decides: AUVY prepares; a person accepts, edits or rejects. Nothing leaves until someone accepts it. When a step needs a person, AUVY stops and asks them by name.
Everything on record: Every answer cites the document and the exact version it read, and shows the sentences that have no source. Every version is kept, and a client's answer by link is recorded in the project.
Data in the EU, no training: Workspace and account data is stored in the EU (Helsinki); AI runs through approved providers in EU regions. Customer data is never used or designated for model training. Every subprocessor is listed in the trust center.
No one is scored: AUVY senses the project, not the people: no per-person performance views, no employee scoring. The AVV under Art. 28 GDPR is part of every order.

Questions

Can AUVY run several client engagements at once?

Yes. Each engagement is its own project with its own sources and people. When you link two projects, the approved work of one becomes context for the other, for example a method you reuse.

Does AUVY write our deliverables?

It drafts from the engagement's own sources, cites each line, and names the sentences without a source. A consultant decides what goes to the client.

How does AUVY handle scope creep on fixed-fee work?

It marks new requests in the mail or minutes they came from, checks them against the proposal you gave the project, and prepares a change note. A person decides whether to bill it or give it away on purpose.

Is client data used to train AI models?

No. AUVY does not designate customer data for model training, and workspace data is stored in the EU.

See it on one of your own projects.

Book a walkthrough Sign in

Consulting engagements change every week. AUVY keeps each one current.

A week on an engagement.

What comes in, and what AUVY does with it.

The client adds “one more market” at the end of a mail.

Twelve stakeholder interviews and three workshops are in.

Version 7 of the operating-model deck goes to the client.

A consultant rolls off on Friday and a new one starts on Monday.

A new name appears on the client's cc line.

The client wants a weekly benefits tracker for the programme.