--- title: "AUVY for software studios: scope and estimates on record" description: "AUVY checks client requests from mail and calls against the estimate and the statement of work, and drafts change requests with their sources." url: https://www.auvy.ai/use-cases/software-studios lang: en site: AUVY brief: https://www.auvy.ai/llms.txt --- # The client's small tweak is a new feature. AUVY puts it next to the estimate. On a fixed budget, the extra feature usually ships first and the talk about paying for it comes afterwards. AUVY reads the client's mail, call notes, specifications and estimates, flags requests beyond the agreed scope and drafts the change request with its source, for the project lead to sign off. Your code and your ticket tool stay as they are. [← Use cases](https://www.auvy.ai/use-cases) For: 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 the last call no longer match, so the delivery lead rebuilds the picture before every review. Use cases ## What comes in, and what AUVY does with it. 1. When ### A client asks in a mail for a quick export to their ERP. 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 2. When ### The specification comes back as version 4. AUVY Names the requirements added, removed or reworded since version 3. You get The difference in one list, each change linked to its page. Reads Specification v3 ↔ v4 3. When ### The sprint review is tomorrow. AUVY Lists what changed since the last review, which client requests are open and what waits for a decision, each with its source. You get A review agenda for the delivery lead to check. Reads Mail · Call notes · Estimate 4. When ### A developer asks why a feature was built this way. AUVY Answers from the record, with the mail, the call notes and the decision that led to it. You get The reason behind the code, without asking around. Reads The whole 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.1 It is covered in the revised offer, section 4.2 The workshop date is still open. 2 of 3 sentences have a source No source: “The workshop date is still open.” **Offer v3.docx** Source 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. Meetings ## Sprint reviews, client calls, the weekly check-in. Meetings Before After Sprint review Changes since the last review, open client requests and decisions due. Accepted items and new requests logged against the scope, with change requests drafted. Client call What the client has asked for since the last call and what the estimate covers. New wishes flagged as changes, tasks with owners and dates, and the follow-up mail drafted. Weekly check-in What moved this week and who is needed where. Tasks updated with owners and dates. Rules ## How AUVY fits the way your trade works. 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 and never touches your repositories or your ticket tool. One client, one project Each client's content stays in its project, and a freelancer is invited into one project, never into your workspace. 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](https://eur-lex.europa.eu/eli/reg/2016/679/oj) , German text binding. Checked 30 September 2026 Questions ### Does AUVY replace Jira or Linear? No. Keep them. They know what someone typed in, while AUVY reads the mail and call notes where the change arrived and shows what the scope should now say. ### 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. Also read - [IT services & implementation partners Scope moves in the steering committee. AUVY checks it against the statement of work. ](https://www.auvy.ai/use-cases/it-services) - [Agencies & creative production “Could you also…” is a new deliverable. AUVY makes sure you decide that on purpose. ](https://www.auvy.ai/use-cases/agencies) - [Change requests Every change you catch is a change you can price. ](https://www.auvy.ai/use-cases/change-requests) [All use cases →](https://www.auvy.ai/use-cases) ## See it on one of your own projects. [Book a walkthrough](https://www.auvy.ai/walkthrough) [Sign in](https://www.auvy.ai/os/)