Data Panda brings your OpusFlow 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.
OpusFlow is an ERP for installation companies that fit solar panels, heat pumps, home batteries, EV chargers and HVAC systems. It is built in Deventer in the Netherlands, has been on the market since 2022 and is used in the Netherlands, Belgium, Germany and Spain, in Dutch, French, English, German and Spanish. One platform covers CRM and quotations, project planning and digital field forms. Time registration, purchasing and stock, invoicing and service contracts sit in the same package.
Quotes are built with the PV Designer, the heat pump calculator and the battery calculator, and the bill of materials of a signed quote becomes a purchase order and a stock reservation for that project. Technicians clock their hours and fill in forms with photos and a signature from the mobile app, and the invoice is generated from the project, in milestones if you work that way. OpusFlow has an open API that makes project, customer, invoice and planning data available outside the platform, for reporting and for links with other systems.
Margin per job from signed quote to final invoice, without exporting grids from OpusFlow.
Let the accounting package, the CRM and the customer follow what happens in OpusFlow.
Use your OpusFlow history to prepare the next quote and next week's planning.
Small tools on OpusFlow data for people who do not need an OpusFlow licence.
A list of concrete reports, automations and AI features we have built on OpusFlow data. Pick the one that matches your situation.
Which installations earned less than the quote promised?
Signed quote value per project set against the hours clocked on site, the materials from the bill of materials and the purchase invoices for that job. Ranks the projects where the margin slipped the most, per product type and per team, so you know whether the calculator or the crew needs adjusting.
How many quotes do we need to send to fill next month's planning?
Conversion rate per product type and lead source from the last twelve months, combined with the planned jobs and the available technician hours per skill. Shows how many signed quotes the pipeline still has to deliver before the planning runs dry.
Where is our stock tied up in projects that have not started?
Stock reservations per confirmed project, next to the planned start date and the open purchase orders for that project. Picks out the panels and inverters sitting in the warehouse for a job that keeps moving, and the projects that start next week without the material in house.
Margin per project after hours, materials and purchase invoices, and milestone invoices and prepayments next to what the accounting package has received. Month-end stops being an export from OpusFlow and an export from the accounting package glued together in Excel.
Conversion per salesperson, product type and lead source, and the gap between what the quote calculated and what the installation cost. The next quote is priced on what past jobs really took, not on the default time standards.
Planned versus clocked hours per technician, stock reservations against planned start dates, and the projects with a return visit after the completion form was signed. Planning next week is done on numbers instead of on what the crew leader remembers.
Invoices and prepayments sent from an OpusFlow project land in the Exact Online sales journal with the right customer, VAT rate and ledger account. Payment status flows back, so the office sees in OpusFlow which milestone invoices are paid without checking two systems.
Invoices generated in OpusFlow are pushed to Billit, which books them and sends them to business customers over Peppol. Payments matched in Billit come back to the OpusFlow project, so the open items list is the same in both tools.
Sales invoices from OpusFlow projects and supplier invoices matched to OpusFlow purchase orders are booked in Yuki with the project as cost centre. The accountant closes the month in Yuki, and margin per project in the warehouse uses the booked cost instead of the ordered cost.
When a HubSpot deal reaches the quote stage, the contact, address and requested installation type appear as a lead in OpusFlow, ready for the calculator. Quote sent, signed and installed states flow back to the HubSpot deal, so marketing sees which campaigns end in a completed installation.
When a job is planned or moved in OpusFlow, the customer gets a WhatsApp message with the date and the time slot, and a reminder the day before. Replies are logged against the project, so the office knows who confirmed and who asked to reschedule.
A signed quote, a completed field form or a stock shortage on a project planned this week posts a message in the right Teams channel with a link to the project. The office and the crew leaders see what changed without opening OpusFlow every hour.
You keep the reporting tool you already have. We connect it to the warehouse where your OpusFlow data lives.
OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys. Read our DPA
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. OpusFlow describes an open API that gives access to project, customer, invoice and planning data, without call limits. That is the route we use, so there is no export step on your side and the warehouse stays in step with what your team enters in OpusFlow.
The accounting link moves invoices from one system to the other. The warehouse joins those invoices with the quote, the clocked hours, the stock reservation and the purchase orders of the same project, and with the payments the accounting package has received. That is what gives you margin per project and payment behaviour per customer, which neither tool shows on its own.
No. We pull the objects you actually use. If you quote and plan in OpusFlow but keep purchasing elsewhere, the stock and purchase order tables simply stay empty and the margin reporting is built on hours and invoices. When you switch on a module later, its data starts flowing without changing the setup.
We review your OpusFlow setup and the systems around it. Together we pick the first thing worth building.