--- title: "How AUVY works on a project · AUVY" description: "What AUVY does on a real project: it reads what you give it, spots the changes, shows what they affect and prepares the next step." url: https://www.auvy.ai/product lang: en site: AUVY brief: https://www.auvy.ai/llms.txt --- # How AUVY works on a project. AUVY reads the mail, meetings and files your project runs on and keeps one current state, with the source of every statement. When something changes, it shows what the change affects and prepares the next step, and nothing leaves until a person accepts it. [Book a walkthrough](https://www.auvy.ai/walkthrough) [Sign in](https://www.auvy.ai/os/) One change ## What AUVY does with one client mail. Five parts ## What runs underneath every project. 1. ### Catches A project folder and a mail thread are enough to start, and once you connect Outlook, Teams and SharePoint they keep the project current. Each project reads only the sources you give it, and new dates, scope and requirements are marked in the message they came from. ![Catches](https://www.auvy.ai/media/product/part-catch.webp) A What comes in, and what listens for it B Where a process would take work off you 2. ### Holds Everyone on the project sees the same state. Every statement carries a numbered source with the file, the version and the lines AUVY read, and AUVY names the sentences that have none. Every version is kept, so you can see what was true when. ![Holds](https://www.auvy.ai/media/product/part-hold.webp) A The answer, sentence by sentence B The sources it read, each checked 3. ### Carries through AUVY prepares the reply and the tasks, each with an owner and a date, and your client approves by link without an account. You accept, edit or reject every step, and when a step needs a decision the run stops and asks a named person. ![Carries through](https://www.auvy.ai/media/product/part-carry.webp) A The draft to Katrin B What it rests on 4. ### Together Mention a colleague and they join the same AI thread, and you edit documents together live. An outside partner joins one project without seeing the rest of your workspace, and personal notes stay yours. AK MS JL - **Anna** @Markus can you check the budget impact of Munich? - **AUVY** Munich adds one workshop and two site visits. Sources: Offer v3 p. 4, Plan row 18. - **Markus** Looks right. I'll approve once the client confirms. Personal Project Shared by link 5. ### Builds tools Describe the tool you need and AUVY builds a working mini-app with its own table, right on the project home. There is nothing to deploy, and every change to the tool and its data has a history. Make a change log for this project with date, requested by, and status. Change log | Date | Change | Requested by | Status | | ------ | -------------------- | ------------ | ------ | | 12 Mar | Munich as third site | Client · Ops | Agreed | | 18 Mar | Go-live to 14 Nov | Client · Ops | Agreed | | 2 Apr | Extra template | Client · Mkt | Open | ✓ Placed on the project home Agents and bots ## Agents and bots that work inside the project. The agent does the follow-up after a change, and bots work beside the team. Both show every step they take and stop for a person before anything leaves. ### The agent Give it the follow-up and watch each step until it waits for the right person to decide. Worked for 1m 9s 1. Read Katrin's mail, 14:02 2. Opened Offer v3.pdf, page 4 3. Searched “Munich” in mail and files 4. Compared Plan row 18 with the mail 5. Drafted Reply to Katrin Waiting for Anna to accept ### Bots A bot is an agent of its own, with its own memory, accounts and processes. You message it or mention it in chat, and it works in each project with that project's permissions. **Change log** Keeps the project's change log current Weekdays, 18:00 On **Friday status** Drafts the client status for review Fridays, 09:00 On **Invoice chase** Prepares reminders for open invoices Mondays, 08:00 On ### Processes Building A process handles the same situation the same way every time. It starts on a mail, a meeting, a date or a change in the data, and anything no process covers still reaches your inbox. Client moves a date When A client mail moves a milestone Only On fixed-price projects Then 1. AUVY Re-plans and drafts the reply 2. You Approve 3. Tools The plan updates, the reply goes out 28 blueprints to start from Example project, synthetic data. Under the hood ## One change, through the whole stack. These are the systems AUVY runs on today, on our own servers in Helsinki. 1. **Your sources** The mail, meetings and files your project runs on. Each project reads only the sources you give it. 2. **Change detection** Watches the sources you connect and flags what moved: a date, a change in scope, a new requirement. 3. **Evidence store** Your documents, versioned, with search by meaning, so every answer points at the exact version it read. 4. **Agent runtime** Reads, cites and prepares the next step, and pauses to ask a named person whenever a step needs their decision. 5. **Model router** Picks a model for each job, from a quick one to the most capable, and uses the most capable only when the task needs it. Every call records what it cost. 6. **Your team** Someone on the team reads the draft, edits it if needed and sends it. 7. **Your client** Your client answers or approves from a link, without an account. The answer is recorded in the project. Where it stops ## What AUVY does not do. AUVY sends nothing on its own and reports only the changes it can see in your sources. It does not decide for you, and it does not replace your ERP or PLM. Questions about this ### What problem does AUVY solve? It catches the changes that slip through. When a client moves a date or adds scope in a mail, a meeting or a file, AUVY shows what the change affects in the plan and the offer and prepares the next step for a person to decide. [How it works →](https://www.auvy.ai/product) ### Which software keeps a client project's current state up to date from mail, meetings and files? AUVY. It syncs the project's Outlook mail and calendars, Teams and SharePoint files into one current state of what is true now, what changed, what it affects and what comes next, each with its source. Nobody types the update in, and the whole team, its agents and bots work from the same state. [How it works →](https://www.auvy.ai/product) ### The client changed the scope by email and half the team missed it. How do project teams catch changes like that? AUVY reads the mail as it syncs, marks the new scope or the moved date and shows everyone on the project what it affects in the plan and the offer, with a link to the mail. It drafts the change request and the reply for a person to check and send. [Change requests →](https://www.auvy.ai/use-cases/change-requests) [All questions, by role →](https://www.auvy.ai/questions) [Next Files → Every file the project was given, with every version. ](https://www.auvy.ai/product/files) ## Stop rebuilding where things stand. [Book a walkthrough](https://www.auvy.ai/walkthrough) [Sign in](https://www.auvy.ai/os/)