Tenants, investors and planners all change something. AUVY keeps the development on one record.
For real estate developers and project management firms, AUVY reads the mail, minutes, briefs, budgets and planner files of each development, flags changes from tenants, investors and planners, checks them against the brief and the budget, and drafts the confirmation and the change request, each with its source. The project manager signs off.
← Use casesFor: Developers, project managers, cost planners, and the tenants, investors and planners around them
Real estate developers & project management
A week on a development.
- A future tenant asks for a second staircase in a fit-out mail.
- The architect sends a revised plan set in the same week the cost planner updates the budget, and nobody is sure which version the other used.
- Decisions are spread across the minutes of four different meetings.
Use cases
What comes in, and what AUVY does with it.
- When
A tenant asks for changes to their fit-out.
AUVYFlags the request, checks it against the tenant brief and the lease scope, and shows the plans and cost lines it affects.
You getA confirmation or a change request for the tenant, with the evidence attached.
Reads Mail · Tenant brief · Budget
- When
The architect sends a new plan revision.
AUVYCompares it with the previous revision, names what changed and which budget lines still rely on the old one.
You getTasks for the cost planner and the planners, each with an owner and a date.
Reads Plan revisions · Budget
- When
The investor asks why costs went up.
AUVYAnswers with the decisions behind each increase and the mail or meeting each came from.
You getAn explanation the investor can follow line by line.
Reads Budget versions · Minutes · Mails
- When
Minutes from planning, tenant and site meetings pile up.
AUVYPulls every decision out of them, each with the line it came from.
You getOne decision log for the development, shareable as a read-only view.
Reads Minutes
- When
The building authority asks for more documents.
AUVYLists what is requested and what already exists in the project, with the source for each.
You getA checklist and a reply drafted for review.
Reads Authority letter · Project files
- When
A new project manager takes over a development.
AUVYAnswers from the record: decisions, open changes, current plan versions.
You getA handover the new manager can check against the sources.
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
2 of 3 sentences have a sourceNo source: “The workshop date is still open.”
- 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.
- 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
Planning meetings, tenant meetings, investor updates.
Prepared from the development's sources; followed up from the minutes you add.
How AUVY fits
How AUVY fits the way you have to work.
- Brief and budget as the baseline
- Requests are checked against the briefs and the budget you give the project.
- Every party in its place
- Tenants, planners and investors see only what you share: a project they are invited into, or a read-only view by link.
- Decisions traceable
- Each decision links to the mail or minutes it came from, and every version is kept.
- A person decides
- Nothing goes to a tenant, an investor or an authority until someone accepts it.
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 handle several developments at once?
Yes. Each development is its own project with its own sources and people.
Can investors see progress in AUVY?
Only what you share, for example a read-only view by link. Nothing else in the project is visible through it.
Does AUVY replace our cost planning software?
No. It reads the budgets and exports you give it and shows what changed and why.
Is our data used to train AI?
No. AUVY does not designate customer data for model training.
Also read
Checked 29 September 2026 against what AUVY does today.