Why Piloti? Because it does not just look things up. It works alongside you.
The clause in the code, the drawing from 2019, the condition from the authority: Piloti finds them, with sources you check against the original. And then it keeps going, until the decision is on file.
Hand over work. Not just questions.
A reference book waits until you ask. Piloti takes on tasks: it researches drawings and regulations, files the report in the project, turns findings into open points and checks again when you want it to.
Fictional project · every step a shipped feature
Mon · You, in the chat
“Do the submission check for the Vienna 1030 housing scheme by Friday.”
One sentence is enough. It becomes a task, under your name and with your permissions.
Mon · Task running
Submission check · Housing 1030
Researching · 3 rounds · 9 documents
Reads the project’s drawings, permit and zoning plan and the regulations that apply. You keep asking in the same chat.
Mon · Report in the project
Submission review report
2 met · 1 open
- Escape routesmet
- Parking spacesmet
- Façade fire stopopen
Verdict first, then one row per requirement, with its citation. Filed under “Reports”.
Tue · Open point
Fire stop missing in the façade section
Clarify →
The finding becomes a task of its own. The project memory keeps it open until it is resolved.
Thu · Inbox
Review report for approval
ApproveRequest changes
The project lead approves or sends it back, and Piloti revises it from the reason given.
From now on · Schedule
“Check this every Monday.”
The check runs again every week, and the result comes to your inbox.
Deadlines, findings and approvals stay in the project, visible to the whole team. That is the difference between a tool that answers and one that works alongside you.
Every feature in the changelog →Who Piloti is built for
Office principals
Less risk in the permit submission, and knowledge that does not retire with one person.
→ An office archive every planner can ask, and answers whose source goes on file.
Project leads
A sound answer before the design meeting starts, not after three days of research.
→ The rule that applies, where the project stands against it, and the options, with reasons.
Planners on the team
Not interrupting the senior colleague for every question on building class or escape routes.
→ An answer with section, clause or page that you read in the original, and learn from.
Whoever decides on data
Clarity on where drawings and documents go before a tool comes into the office.
→ No training on your data, drawings stay the office’s property, and every provider involved is named in the privacy policy.
Why not just use ChatGPT?
ChatGPT answers questions. Piloti answers them in the context of your project: with your documents, Austrian building law and sources you can check. A general language model is a good tool for text. For a question whose answer goes into a permit submission it lacks three things: the right edition, your project and the evidence.
| General chatbot | Piloti | |
|---|---|---|
| Legal basis | Whatever was in its training, undated and often without the state | State building codes from RIS and the OIB guidelines, cited the way an official decision cites them |
| Evidence | A source if you ask for one, and not always one that exists | Every citation is checked against the source text before it appears, and opens at the marked passage |
| Your project | Whatever you upload to this one conversation | Drawings, permits and room schedules in the project, for the whole team, with versions and approval |
| Drawings | Reads the text of a PDF | Looks at plan and section as an image and marks which drawing on the sheet it read |
| Office knowledge | Does not have your archive | Searches your office’s archive, kept apart from every other office |
| What is missing | Answers even without the document that matters | Says when, for example, the zoning plan is missing, instead of answering as if it had read it |
What grows with every project
Anyone can buy the language model underneath. What makes Piloti sits above it, and it gets better with every project your office runs:
- Austrian building law
- State building codes, OIB guidelines and a register of standards.
- Your project
- Drawings, permits and conditions, filed where the team works.
- Your office
- How your office solves things: standards, details and experience from past projects.
- Ways of working
- Building class, fire safety, submission check, existing buildings: built-in procedures your office extends with its own.
- Project memory
- What a project has settled goes into the next answer as a fact or an open point.
- Learning from criticism
- An answer marked unhelpful becomes an anonymised lesson that every later answer reads.
What you can rely on
- Every answer brings its sources, down to section, clause or page. You check against the original before anything goes into the submission; responsibility for the design stays where it belongs, with you.
- Your data stays yours: we do not train models on it, drawings and projects remain your office’s property, and no other office sees your archive.
- You build it with us: pilot offices get early access, a direct line to us founders and a say in what we build next.
Piloti gets better every week.
606 changes in 7 weeks, each one in the changelog. The pilot offices help decide what comes next.
Everything that’s new →Piloti compared
Weighing several AI tools for your office? Piloti next to ChatGPT, Copilot, NotebookLM, Reiner AI and BaurechtGPT, compared, and why Piloti is the better choice for planning questions in Austria.
All comparisons →