A drawing saved in Archicad shows up next to the project stage, a stage approval issues the invoice in your invoicing software, the calendar knows the permit-office deadlines. We connect what the studio already has instead of replacing it.
The floor plan PDF is in Archicad, on Drive, in an email to the client and in the contractor's folder. A change in one means copying by hand to the other three.
Stage closed on Friday, invoice issued in Fakturownia a week later, because the client's details have to be copied from the contract. Payment terms start counting from then.
Hours are in Excel, projects in email, holidays in a calendar. You take on a new inquiry without knowing whether anyone has time for it.
We do not replace Archicad, Drive or your invoicing software. We connect them to ArchiFlow, or to the tool you run projects in, so data entered once reaches everywhere it is needed.
Three years ago features like these needed a data science team. Today language models read emails, documents and photos, and we build them into the system we make for you. Below is what makes sense in this solution. A person approves, AI prepares.
A new file in the folder gets a proposed stage, drawing type and revision number from the file name and the title block. The architect confirms with one click.
Example file "A-101_ground_floor_plan_revC.pdf" → stage detailed design, floor plan, revision C, the previous one marked as superseded
AI reads an email from the permit office or a consultant, recognizes the project by address, plot number or case reference, and pins it to the thread with a short summary.
Example an email from the district office with a case reference → project "House in Zalesie", summary: request for supplements, 14-day deadline
An invoice with no approved stage, a closed stage with no invoice, a project with no folder, a revision with no date. An alert to the lead architect before the client notices.
Example stage "concept" approved 9 days ago, no invoice issued → a reminder with a ready invoice draft
The monitor describes what failed and what to do, instead of showing an API error code.
Example an invoice rejected by the API with an error code → "Fakturownia rejected the invoice: the client has no tax ID on file. Add it and click retry."
If a tool has an API, we connect directly. If not, we work with folders, exports and IFC files.
We start with the flow that costs the most manual work. Usually that is CAD files next to stages, or the invoice after approval. The next ones follow once the first is running.
You have the diagnosis, we build the solution. Web applications, B2B portals and automations for companies without a large IT department. Today a system can read emails and documents, suggest decisions and answer customers on its own, so we build that in from the first version, not as an add-on a year later.
We agree scope, price and dates upfront, show progress every week, and the code and data stay yours.
Updated:
Tell us which files and data you copy by hand between programs. We will say which flow to start with and how long it takes.
Write to us