DEGet started

Your client signs off from a link, and the whole project sees it.

An approval buried in a reply-all thread is hard to find when the invoice is disputed. Once someone on your team decides a change request, a confirmation or a deliverable goes out, your client gets it as a link. They approve, decline or answer without an account, and the answer lands in the project with the version it applies to, so everyone works from it.

← Use casesFor: Project leads, account managers, and the clients who approve their work

How approvals go today.

  1. A client approves version 3 on the phone, and the team delivers version 4.
  2. At the final invoice, nobody can show who approved the extra work, or when.

What comes in, and what AUVY does with it.

  1. When

    A change request needs the client's decision.

    AUVY

    Sends it as a link, and the client approves or declines without an account.

    You get

    The decision recorded in the project with the change request it applies to.

    Reads Change request

  2. When

    A date moved in a meeting.

    AUVY

    Drafts a short confirmation for the client, with the minutes as the source.

    You get

    The new date confirmed in writing by the client.

    Reads Minutes

  3. When

    A deliverable is ready for sign-off.

    AUVY

    Sends that version for approval by link and keeps any question and your answer with it.

    You get

    Approval tied to exactly that version.

    Reads Deliverable version

  4. When

    The final invoice is due.

    AUVY

    Lists every approval with its date, version and source.

    You get

    Every approved change, with where it came from.

    Reads The project's approvals

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.1 It is covered in the revised offer, section 4.2 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 to 14

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

Many approvals are given in a meeting, so AUVY gets them confirmed in writing.

MeetingsBeforeAfter
Client meetingApprovals still open, with what each one is for.Verbal agreements drafted as confirmations for the client to approve by link.
Steering committeeChange requests waiting for a decision.Decisions recorded and confirmations drafted.

How AUVY fits the way your trade works.

No account for the client
The client answers from a link and sees nothing else in your workspace.
Tied to the version
Every approval, question and answer stays in the project with the version it applies to.
A person sends it
Nothing goes to the client until someone on your team accepts it.

At a glance

Walkthrough
40 minutes on one of your own projects, free.
Price
€59 per person a month, billed yearly, with every project, team and bot included.
Your data
Stored on our own servers in Helsinki, never used to train AI, and deleted within 30 days after the contract ends.
Contract
Every order includes the data processing agreement under Art. 28 GDPR, German text binding.
Checked

Questions

Does the client need an AUVY account to approve?

No. The client approves, declines or answers from a link.

What can a client approve?

A change request, a confirmation or a deliverable version. They can also answer a question.

Does AUVY send approval requests on its own?

No. It drafts them, and a person on your team accepts before anything goes out.

Also read

All use cases →

More revenue with the same team.

Book a walkthroughSign in