Pidgy is an AI email assistant for architecture practices. It sorts the project inbox before you open it, counts the days on every request for information a contractor is waiting on, drafts the reply in your words, and turns what you agreed on site into work the whole team can see.
Ask for a place in private beta →Today 2 of 14 done
Good morning.
Tuesday, 7 April
7 waiting on you·12 waiting on others·Site meeting Thursday
Illustrative data from no real practice
A working week, on average
business emails a day, per person. Perhaps six change what you do.
Radicati Group, Email Statistics Reportto get back to what you were doing after one interruption.
Mark, Gudith and Klocke, UC Irvine, 2008of the working week goes to email, before any real work is opened.
McKinsey Global Institute, The social economy, 2012
A request for information arrives from site on Thursday afternoon. It sits behind sixty other emails until Tuesday, and by then the contractor has either guessed or stopped. Both cost money, and one of them becomes a claim.
It is that nothing in the practice counts the days on an RFI, or on the engineer's question, or on the client approval that unblocks the next drawing issue. The only record is a scroll through sent items.
Pidgy does not draw.
Two hundred a day across the projects, and the ones that matter are the ones with a site behind them.
Dear Ms Van Damme, a short reminder about the window schedule we sent on 22 March. The contractor needs to place the order this month to hold the programme. A reply to this email is enough.
Which client, consultant or officer owes you which answer, how many days, and the chase already written in your words. You press send.
RFI 042 and the balustrade
We are ready to set out the stair but the balustrade detail on A-521 does not match the section. Can you confirm which one is correct and issue a revised detail before Wednesday? We have the steel fabricator on site then.
Who is asking, what for, and by when, lifted out of the RFI and put on the list with the deadline and the project attached.
RFIs, consultant markups, client approvals, planning, specifications, product updates. Labelled on arrival, so RFI 042 is one click, not a search.
Illustrative data from no real practice
Five more things Pidgy does between an email landing and the site being handed over.
Every project becomes a project in Pidgy too: open RFIs, outstanding approvals, what the consultants owe, the next issue date.
Ask for a place in private beta →Projects, created for you
Construction stage 68%. Open RFI 042 on the stair, 4 days. Window schedule sign-off outstanding with the client 16 days, which holds the order. Site meeting Thursday.
Every thread that needs a reply gets three, and they are the three things you would most plausibly say back given what the contractor or the client asked.
Ask for a place in private beta →Reply to Bram Claeys
Three likely answers click one
Dear Bram, understood. Revised A-521 will be with you Tuesday close of business. The section is correct; the detail was an earlier revision that should have been withdrawn. I will confirm in writing with the issue.
You drag one into the other, and a week with two drawing issues and a planning deadline in it looks that way on Monday.
Ask for a place in private beta →Plan mode click a task
Everyone on a project becomes a contact, with how long they usually take and how often they opened the conversation. When the claim arrives, the timeline of who waited on whom is already there.
Ask for a place in private beta →“Which RFIs are older than three days?” is a question the project architect answers today from the register and memory.
Ask for a place in private beta →Ask Pidgy
Pidgy
One. It is holding the stair on Kaai 12:
Illustrative data from no real practice
Pidgy drafts. It has no permission to send on your behalf, and there is no setting that grants one.
Data residency in the EU, scoped per mailbox, DPA on request. Export or purge whenever you want.
Nothing is archived, moved, marked read or thrown away. Your mailbox is exactly where you left it.
Correspondence builds your lists and your drafts. It is never used to train a model, ours or anyone else's.
Per mailbox, monthly, published when we open to everyone. The first group is free. Asking for a place costs nothing and connects nothing.
No. It drafts replies, you send them. Drawing issues, revisions and the register stay in your CDE exactly as they do now. Pidgy makes sure the question and the deadline reach the right person in time.
The project mailboxes you connect, and only those. The model, the CDE and anything on a workstation are invisible to it by design.
No. It knows a markup or an approval arrived and closes the request it belongs to. Reading it is your work.
Yes. It reads mixed language mailboxes and drafts in the language of the thread, which on a Brussels site can change from one email to the next.
It works on the mailboxes you connect. Everyone with access sees what they could already see. Pidgy never widens access.
Pidgy opens to a small number of practices before anyone else, and we pick them ourselves. If architecture is your trade, tell us and we will be in touch.
