Customer portals and dashboards

A report is a snapshot that someone puts together by hand. A dashboard pulls the figures itself and flags when something falls outside the limits you have set. So the difference lies in how current it is, and in who does the work.

Often, yes. We connect with accounting packages such as Exact Online and AFAS, with CRMs such as HubSpot and Dynamics, with planning tools and with custom databases. That requires an API or access to the database. We find out in advance whether your package offers that, so you are not caught out halfway through.

You decide that for each part. Real time for stock or planning. Every fifteen minutes or once a night where that is enough, because every integration costs capacity at the source. We choose that together based on which decision you make with it.

We arrange permissions per user and per role. An engineer sees his own schedule, a customer only their own file and management sees the whole picture. We log who viewed what, so you can demonstrate that later.

We map out the purpose, legal basis, data and retention periods in advance. During the build we use encrypted connections, roles, logging and data minimisation, among other things. We test the application against the OWASP Top 10.

That mainly depends on the data sources, integrations, permissions and calculations. After researching the systems and desired screens you get a cost indication. Once the scope is defined, we can agree a fixed price.