Data Panda brings your Ziggu data together with the data from the rest of your business. From one place, we turn it into dashboards, automations, AI workflows and custom apps your team uses every day.
Ziggu was founded in Ghent in 2017 and grew into the buyer portal that a large share of Belgian residential developers use to run off-plan projects. The platform covers the buyer side of a nieuwbouw project end to end: a branded portal per project, structured choices and meerwerk approvals, document storage for plans and contracts, financials and payment schedules, voorlopige oplevering and snagging lists, and after-sales requests once kopers move in. Customers include Belgian developers like Immobel and Hoprom.
The point of pulling Ziggu into a warehouse is that the buyer journey for a nieuwbouw apartment runs eighteen to thirty months and crosses three teams that rarely share a system. Sales sits in the CRM, the choices and meerwerk live in Ziggu, the invoicing happens in the accounting tool, and the snagging list shows up again at oplevering. In a warehouse, every approved keuze, every meerwerk-bedrag, every defect logged after sleuteloverdracht and every payment milestone sit next to the unit, the koper and the project. The questions a developer asks at the partner meeting (which units are slipping, which kopers cost the most after-sales hours, which projects show meerwerk-marge drift) become answerable on real data instead of werfleider memory.
Choices, meerwerk, snagging and payments per unit on one screen.
Let Ziggu events drive the sales, finance and after-sales stack.
Turn Ziggu history into project and koper insight.
Internal tools on Ziggu data for sales, project leads and finance.
A list of concrete reports, automations and AI features we have built on Ziggu data. Pick the one that matches your situation.
How much meerwerk did we approve last quarter that has not yet been invoiced?
Meerwerk approved in Ziggu, joined to invoice runs in your accounting tool, by koper and unit. Surfaces the extras that the koper signed off on but the finance team never billed, before the year-end review turns it into a write-off.
Which projects are heading toward a noisy oplevering?
Snagging volume and resolution time, against project stage and contractor mix, compared to projects that delivered cleanly. Flags the developments where the punch list is growing faster than the team can clear it, with weeks of runway left to add capacity.
Which kopers are absorbing the most after-sales hours?
After-sales tickets in Ziggu joined to unit, project and contractor responsible, scored on hours spent per case. Lets the developer see the kopers, units and partners that drive the bulk of the post-handover load.
Meerwerk approved versus meerwerk invoiced, payment milestones outstanding per koper, and per-unit margin tied to the accounting ledger. Year-end stops relying on the project lead remembering which extras were billed where.
Choice-funnel completion per project, time-to-decision per koper segment, and meerwerk-uplift per finishing package. The next campaign targets the segments and packages that paid, not the ones that felt popular.
Snagging volume, resolution time and contractor responsibility per project. Capacity calls land on the projects that need them, on data the project leads already produced in Ziggu.
Every meerwerk a koper approves in Ziggu becomes a draft invoice on the right project administration in Exact Online, with VAT and grootboek coding resolved. Developers stop chasing the project lead at month-end for the list of extras that still has to be billed.
Sales-side records in Teamleader Focus pick up the latest koper choices, meerwerk totals and document status from Ziggu. The account owner walks into the next call with the full picture instead of the version sales had at compromis.
Open snagging points, meerwerk volume and oplevering date on the HubSpot deal that sold the unit. Marketing knows when a koper is in heavy after-sales and stops sending newsletters that look tone-deaf during a defect dispute.
Hello Customer surveys after voorlopige oplevering and after sleuteloverdracht come back tied to the Ziggu unit, project and contractor. Two Ghent-grown platforms put a satisfaction number next to the snagging list and the meerwerk file.
These are the 23 tables we currently pull from Ziggu 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 Ziggu 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. Approved choices, finish packages and meerwerk amounts are first-class in the warehouse, attached to the unit, the koper and the project. That makes margin and invoicing analysis work on the same grain Ziggu already captures, not on a roll-up that loses the per-unit detail.
Yes. Snagging points logged at voorlopige oplevering and after-sales tickets raised after sleuteloverdracht are pulled with their status, owner and resolution time. Developers can see which projects, contractors and finishing partners drive the bulk of the post-handover load.
We review your Ziggu setup and the systems around it. Together we pick the first thing worth building.