An email — but which project?
Messages arrive mixed together. Working out which commission a consultant is writing about, and what was said last time, takes longer than the reply itself.
An architecture practice runs several commissions at once, each with its own email threads, consultants and approvals to chase. Sania files every exchange under its project and prepares what comes next.
An architect uses Sania for the administrative side of a commission, not for design. In practice it works through the practice inbox and files each message under the right project, retrieves the history of the exchange before proposing a reply, drafts coordination emails to engineers, contractors and consultants, organises meeting requests and chases client approvals that fail to arrive. Sania produces no drawings, takes no technical decisions and gives no opinion on building standards: those remain entirely the architect's.
It is not design that overflows, it is everything around it: coordinating, confirming, chasing, recording. Multiplied by the number of live commissions.
Messages arrive mixed together. Working out which commission a consultant is writing about, and what was said last time, takes longer than the reply itself.
Structural engineers, contractors, specialist consultants, the client: every decision gets confirmed in writing to several people.
A pending material choice or an unapproved quote blocks the next step. Nobody chases, because chasing a client takes tact.
A meeting produces points to confirm and messages to send. They go out in the evening, or not at all.
This is where a connected assistant earns its place: it knows which project is being discussed before proposing anything.
Sania identifies the commission from the sender, the subject line and the thread.
It brings back what has already been exchanged on the point: decisions taken, documents sent, questions left open.
The reply is drafted with that context. Anything requiring a technical judgement is left blank and marked for you to settle.
You read it, add the judgement call if there is one, and send.
A meeting leaves a list of administrative consequences: confirm a decision to the contractor, ask the engineer again for a document, fix the next date. Sania prepares those messages from what you tell it and submits them in one batch. The minutes themselves and their circulation stay your responsibility, because they commit the practice.
Sania plugs into the communication and tracking layer. It replaces neither your CAD software nor your project management tool.
Gmail, Outlook or IMAP. This is where coordination, client requests and documents pass through.
The assistant on email →Google Calendar, Outlook or Calendly: meeting requests are handled against your real availability.
The assisted calendar →Notion, Airtable or a CRM: the status of a commission and its exchanges stay attached to the right file.
All integrations →A daily topic watch can be configured on the sources you nominate, tenders included.
Sania's services →An illustrative, unmeasured usage profile for an architectural office. Credits are distributed freely — this is an example, not a limit.
| What Sania manages | Volume / month | Credits |
|---|---|---|
| Project emails sorted & answered | ~500 | 500 |
| Quote from briefs | 25 (×3) | 75 |
| Reminders & progress points | 120 | 120 |
| Meeting minutes | 60 (×2) | 120 |
| Public procurement monitoring | included | excluding quota |
| Estimated total | ~815 |
An assistant that strays outside its scope is a professional risk. Better to state where its scope ends.
Sania does not draw, does not modify any CAD file and produces no graphic document. Its scope is communication and administrative tracking.
Construction choices, sizing, comparing options: these are the architect's decisions. They are flagged as such, never settled.
Sania does not give an opinion on whether a project complies with a standard or a regulation. It can pass a question on; it will not answer it for you.
Deadlines, fees, accepting a variant: nothing is confirmed to a contractor or a client without your approval.
The data of one commission serves that commission. It is not reused to train models, and we select providers that offer guarantees against reusing your data for training.
Data protection →No. Sania has no drawing capability, modifies no CAD file and produces no graphic document. Its domain is practice admin: emails, coordination, meetings, commission tracking. Design remains entirely the architect's work.
We make no such claim. Sania does not give an opinion on whether a project complies with a standard, a municipal regulation or a cantonal requirement. If a question of that kind arrives by email, it is passed to you rather than answered.
It uses the sender, the subject, the thread and the history already attached to that commission. When the match is uncertain, it says so rather than filing at random. Accuracy improves with the setup done at onboarding.
It can prepare the administrative consequences of a meeting — confirmation messages, document chasers, the next date — from what you give it. The minutes themselves commit the practice: writing and circulating them stays under your control.
It notices that an expected approval has not arrived and drafts a measured reminder that takes into account how long it has been. You read it before it goes. This is useful precisely because chasing a client takes tact and the message is easy to postpone.
Yes, and that is often where the difference shows most, since there is no administrative support. The Starter plan at CHF 99 per month suits a small practice; the Business plan at CHF 249 is for practices wanting several services running together.
Architects & architecture practices
7 days free. No credit card. Guided onboarding.