Data Panda brings your ArchX data together with the data from the rest of your firm. From one place, we turn it into dashboards, automations, AI workflows and custom apps your studio uses every day.
ArchX is a Belgian cloud ERP built for architecture and engineering firms, covering project administration, time registration, planning, document workflows, fee and contract management, and invoicing through Peppol. Where AutoCAD or Revit handle the drawing side, ArchX runs the practice: who works on which project phase, against which fee, with which deliverables and at what realisation.
The point of pulling ArchX into a warehouse is that fee realisation in a studio leaks the same way it does in any project-based business, only it hides inside per-project files. The Monday morning run-through sees the invoice that went out. The warehouse sees the hours behind it, the phases that ran past their fee, the contract types where realisation drifts every year, and the projects that quietly stopped being profitable two phases ago. Next to Exact Online, Microsoft Dynamics 365 Business Central or HubSpot, ArchX becomes the studio's own P&L signal in real time.
Hours, fees and realisation per project, phase and partner.
Let ArchX events fire the rest of the firm's stack.
Use studio history to forecast risk and workload.
Internal tools on ArchX data for partners and project leaders.
A list of concrete reports, automations and AI features we have built on ArchX data. Pick the one that matches your situation.
Which projects have quietly stopped being profitable?
Hours at cost against contracted fee per project and phase, across the last twelve and twenty-four months. Ranks the projects whose phases keep eating hours while the fee was set at the start, which is where most studio margin disappears.
Where is fee realisation leaking, and on whose projects?
Realisation pattern per partner, contract type and project size. Exposes the pattern that nobody at the Monday review wants to name, because the data makes it visible regardless of who runs the room.
Does next quarter's project pipeline match the capacity we have?
Committed phase hours against planned capacity per discipline and quarter, with delivery dates on the same view. Hire-or-reassign conversations happen the quarter before overtime starts, not after a deadline slips.
Realisation, fee health and studio P&L tied to timesheet, invoice and contract data. Fee setting on new projects moves from gut feel to the contract-by-contract view of where margin is leaking on the existing book.
New-project pipeline, proposal-to-signed conversion and contract-type performance. Growth conversations stop leaning on which partner remembers which proposal is still out.
Utilisation, timesheet completeness and workload forecast across disciplines on one board. Resourcing and planning decisions are made against data, not against the loudest project leader at the meeting.
Approved invoices in ArchX post to Exact Online with customer, VAT and ledger coding aligned. Partners see realisation against the contracted fee and the ledger view stays consistent for the year-end audit, without re-keying figures into the bookkeeping.
Studios on Microsoft Dynamics 365 Business Central keep their ArchX projects, contracts and invoices aligned with the group ledger. Project-level realisation rolls into the same financial dimension as the rest of the group, so the consolidation no longer waits on per-studio exports.
New projects opened in ArchX create or update the matching company and deal in HubSpot, with contract value, project type and partner owner carried over. Sales and partner conversations happen on one customer record, not on a CRM that lost track of the project the moment it was signed.
Project phases in ArchX appear as items on the studio's monday.com board, with deliverables, owner and due date in sync. Project leaders work in the planning tool the team already uses, while ArchX stays the system of record for fee, hours and contract.
Phase completion, fee threshold reached, deliverable overdue and new contract signed events from ArchX post into the right Slack channel for the studio. The team reacts the same day, instead of catching the signal on the next Monday review.
Larger studios running Salesforce as the group CRM keep ArchX contracts and the originating Salesforce opportunity linked, so won-revenue, fee value and project type are reported on the same record. Sales operations and studio operations stop arguing about which number is the real one.
These are the 9 tables we currently pull from ArchX into your warehouse. Query them directly in SQL, join them to the rest of your stack, or build reports on top.
Missing a table you need? We can extend the sync. Tell us what is missing and we will build it for you.
You keep the reporting tool you already have. We connect it to the warehouse where your ArchX data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.
Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.
We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.
We set up the foundation. Your team builds on top.
Best fit Teams that already have a BI analyst or data engineer and want to own the build.
We build the whole thing, end to end.
Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.
You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.
Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.
No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.
Yes. Each studio lands with the right dimension and partner identity is preserved. Firm groups get per-studio and per-partner realisation plus a group-level view, without merging timesheet and invoice data by hand.
Yes. Fixed-fee project agreements, hourly engagements and add-on work come across as distinct constructs so realisation can be measured the way each project was sold. Mixing them in one studio average, which is where realisation conversations usually go wrong, stops happening.
We review your ArchX setup and the systems around it. Together we pick the first thing worth building.