The client's small tweak is a new feature. AUVY puts it next to the estimate.

For software studios and development agencies, AUVY reads the client's mail, call notes, specifications and estimates, flags requests that go beyond the agreed scope, and drafts the change request and the reply with the source attached. Your code and your ticket tool stay as they are. The project lead signs off.

← Use casesFor: Studio owners, project and delivery leads, product owners, and the client's product team

Software studios & development agencies

A week in a studio.

The client writes “one small tweak” under the demo invite, and it turns out to be a new integration.
The estimate, the tickets and what was said in the last call no longer match, and the delivery lead rebuilds the picture before every review.
On a fixed budget, the extra feature ships first and the conversation about paying for it comes afterwards.

Use cases

What comes in, and what AUVY does with it.

When
A client asks for a quick export to their ERP in a mail.
AUVY
Flags the request, checks it against the estimate and the statement of work, and shows which milestone it touches.
You get
A change request with the mail and the estimate line attached, for the client to approve by link.
Reads Mail · Estimate v3 · Statement of work
When
The specification comes back as version 4.
AUVY
Compares it with version 3 and names the requirements that were added, removed or reworded.
You get
The difference in one list, each change linked to the page it came from.
Reads Specification v3 ↔ v4
When
The sprint review is tomorrow.
AUVY
Lists what changed since the last review, which client requests are open and what is waiting for a decision, each with its source.
You get
A review agenda ready for the delivery lead to check.
Reads Mail · Call notes · Estimate
When
A developer asks why a feature was built this way.
AUVY
Answers from the record: the mail, the call notes and the decision that led to it, with the source for each.
You get
The reason behind the code, without asking around.
Reads The whole project
When
The client wants a simple status page for their stakeholders.
AUVY
Builds it as a small tool inside the project from your description and shares a read-only view by link.
You get
A status view the client can open, with nothing else in the project visible through it.
Reads Your request · Project files
When
A freelancer joins for two sprints.
AUVY
Invites them into this one project, where they see its documents and threads and nothing else.
You get
A quick start for the freelancer, and your other clients stay out of view.
Reads The project

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

Sprint reviews, client calls, the weekly check-in.

Prepared from the project's mail and files; followed up from the notes or transcript you add.

MeetingsBeforeAfter

Sprint reviewChanges since the last review, open client requests and decisions due.Accepted items and new requests logged against the scope; change requests drafted.

Client callWhat the client asked for since the last call and what the estimate covers.New wishes flagged as changes, tasks with owners and dates, the follow-up mail drafted.

Weekly check-inWhat moved this week and who is needed where.Tasks updated. Nothing goes to the client until someone accepts it.

How AUVY fits

How AUVY fits the way you have to work.

The estimate as the baseline: Requests are checked against the estimate and the statement of work you give the project, so the budget conversation starts from the documents.
Your code stays where it is: AUVY reads the documents and messages you give the project. It does not touch your repositories or your ticket tool.
Client approval by link: The client approves or declines a change request from a link, without an account; the answer is recorded in the project.
One client, one project: Each client's content stays in its project. Freelancers are invited into one project, never into your workspace.

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

Does AUVY replace Jira or Linear?

No. Keep them. They know what someone typed in; AUVY reads the mail and call notes where the change arrived and shows what the scope should now say.

Can AUVY read our specifications and estimates?

Yes, the documents you give the project, including earlier versions, so it can show what changed between them.

Does AUVY access our code?

No. It reads the documents, mails and notes you give the project.

How do clients approve change requests?

From a link, without an account. The answer is recorded in the project.

See it on one of your own projects.

Book a walkthrough Sign in

The client's small tweak is a new feature. AUVY puts it next to the estimate.

A week in a studio.

What comes in, and what AUVY does with it.

A client asks for a quick export to their ERP in a mail.

The specification comes back as version 4.

The sprint review is tomorrow.

A developer asks why a feature was built this way.

The client wants a simple status page for their stakeholders.

A freelancer joins for two sprints.