Do you replace Centric or Pink Roccade?
For the heavy core packages (citizen services, financial administration, the central case management system), no. That market is mature, and migration costs are almost always unjustifiable. Your processes are deeply embedded in your organisation, the packages are functionally extensive, and vendors keep evolving them around standard processes. What we do instead is build custom software for the domains those packages don't fit well, and connect that custom application neatly to Centric Key2, Pink Roccade Civision or another vendor's package via the VNG APIs. In practice you often work with several systems that together support the workflow. We build the custom part of that, not the entire chain.
Do you work according to Common Ground?
Yes. Common Ground is, for us, a natural architectural choice: data at the source, standardised APIs (Case, Document, Notification and Client APIs), and interchangeable components. We work with the VNG standards, ZGS, and StUF-ZKN where older integrations require it, and the Federated Data System where it already applies. Our applications talk to your existing Common Ground components through the official interfaces, so you aren't locked in to us as a supplier. Another party could later take over or replace our application without touching the architecture.
What about BIO and information security?
Included as standard. We work in line with the Baseline Informatiebeveiliging Overheid (BIO): a threat analysis at the start of the project, a penetration test by an external party before production acceptance, a DPIA where personal data is processed, encryption in transit and at rest, and an audit log that records every significant action. For healthcare data, NEN 7510 applies in addition, and for financial transactions the relevant PCI requirements. We deliver the BIO documentation with the evidence your CISO and data protection officer need for accreditation and go-live.
Can you integrate with BRP, BAG, Kadaster and KvK?
Yes. We have experience with BRP queries via Haal Centraal or your own BRP interface, BAG via PDOK and the BAG API, Kadaster data via the PDOK services, and the KvK Trade Register via the KvK API. We also handle DigiD and eHerkenning for authentication, via your own routing facility or a provider such as Signicat, ConnectIS or iWelcome. These integrations are a standard part of the architecture, not a separate phase added afterwards. For more specialised registers (BRO, BGT, NHR, BLAU) we take the same approach to building them in.
How do you handle accessibility and WCAG?
Accessibility is mandatory for public applications and is considered from the design stage onwards — not as a final check. WCAG 2.1 AA is the baseline, tested by an independent party before production and repeated periodically. We deliver the accessibility statement you need to publish on the application, with the correct status and any exceptions substantiated. During ongoing development we monitor accessibility in our sprint checks so regressions are caught early, and we work with design systems that are accessible by default.
How does tendering or contract award work?
It depends on your thresholds and framework agreements. For contracts below the European threshold, we often work through DAS systems, a direct invitation based on a single-supplier request for quote, or a framework agreement you are already party to. Above the threshold, we support your procurement team with the technical specifications, a well-founded scope, a suitable lot division and an award model in which quality weighs more heavily than price alone. We have experience with the VNG model terms, BIBOB screening and the usual municipal procurement procedures.
How long does a project like this take?
It depends on the scope, the degree of integration with existing systems, and the procurement route. A focused process application for a specific domain can be on acceptance within a programme of several sprints, with a phased rollout to production. A larger citizen portal with multiple integrations takes longer, delivered module by module so that earlier components already add value while the whole continues to be developed. We provide a reasoned plan after the discovery phase, not commitments based on a first conversation, as that would be unfair to an environment we have yet to get to know.
Do you also work for provinces, water boards and safety regions?
Yes. The technical starting points, such as Common Ground where applicable, BIO, WCAG, eHerkenning and DigiD for citizens, are comparable. For provinces, much of the municipal legislation applies at a different scale. For water boards we work with the Informatiehuis Water and the standards that apply there, including for measurement data and water permits. For safety regions we work with the specific chains (LCMS, MultiTeam) and the requirements around crisis information provision. We have also supported implementing bodies such as RDW, UWV and SVB with clearly defined modules, often in collaboration with their own in-house teams.
How do we handle open data and transparency?
Open data and transparency are a policy priority for many municipalities. We build APIs that make data available in line with the high-value datasets under the Open Data Directive, dashboards that help residents understand how decision-making works, and publication platforms for decision lists, council documents and Woo requests. We work with the standards of data.overheid.nl and the open standards prescribed by the apply-or-explain list.