Public sector

Digital services that work for everyone.

Citizen portals, application platforms, intranets and accessible websites for organisations with formal procedures, fixed budgets and many stakeholders.

Discuss your projectSee our approach

Does this sound familiar?

Public projects work under different conditions than commercial ones. Accessibility, procurement rules and continuity are not side issues.

Citizens still have to call or come in

Applications, certificates and reports go through a counter, a phone line or paper, while most people would rather arrange it digitally themselves.

The website does not meet accessibility standards

Legal requirements around digital accessibility keep tightening, while existing sites and portals were never built for them.

Changes halfway cannot be undone

Fixed budgets and formal procedures make mid-project adjustments expensive and sometimes impossible within the contract.

Many parties, little shared clarity

Departments, communications, IT and external suppliers each hold their own picture of what should be built.

What we build

Digital services that are accessible, connect to existing systems and hold up against changing staffing and long timelines.

Citizen portals

Citizens track their case, upload documents and arrange things themselves, at any time.

Application and reporting platforms

Digital forms that land directly in the right handling process.

Accessible websites

Public websites that meet the applicable accessibility standards, including after delivery.

Intranets

One place where staff find documents, procedures and internal services.

Integrations with line-of-business systems

Connections to existing case, record and registration systems.

Accessibility remediation

Auditing and fixing existing sites and portals without rebuilding everything.

Our approach

In public projects, changing course halfway is the most expensive option. That is why we fix requirements, flows and technical choices before building starts.

01

Mapping requirements and stakeholders

Departments, communications, IT and external parties each have their requirements. We bring these together into one shared, validated picture.

02

Making it visible and getting approval

Everyone involved sees the solution screen by screen before any development starts. At that point, changes still cost nothing.

03

Fixing accessibility and technology

Accessibility standards, data protection, security and integrations with line-of-business systems are decided up front, not retrofitted.

04

Building within scope and budget

We develop in clear phases with interim deliveries, so progress is demonstrable and the scope stays under control.

05

Testing and delivery

Functional testing, accessibility checks and support for staff at go-live.

06

Maintenance and continuity

Maintenance, support and further development are agreed in advance, including documentation and transferability.

Frequently asked questions

Do you work within public procurement procedures?

Yes. We supply the requested documentation, plans and technical explanations, and work within the scope, timeline and budget structure set out in the contract.

How is digital accessibility guaranteed?

Accessibility is a design requirement, not a check afterwards. We build to the applicable standards, test during development and deliver the findings with the project.

Can you integrate with our existing line-of-business systems?

Yes. Case, record and registration systems remain the source of truth. We establish up front which data is exchanged and through which integrations.

How are data protection and security handled?

Access management, data minimisation, retention periods, logging and back-ups are considered from the design stage and matched to your obligations.

What if something has to change halfway?

By making the solution fully visible up front, most changes are caught before building starts. Anything that changes after that is recorded explicitly, with its consequences for scope, timeline and budget.

How do you align with multiple departments and stakeholders?

We work from one shared, validated picture of the solution. Everyone involved sees the same thing before development starts, which limits disagreement later.

What happens after delivery?

Maintenance, support, further development and documentation are agreed in advance, including response times.

Thought through. Then built.

Strategy & design

Problem definition
Product strategy
UX/UI design
Concept development
Creativiteit + Engineering

Engineering & delivery

Software development
Electronics and PCB design
Mechanical design
Prototyping and production

Strategy & design

Problem definition
Product strategy
UX/UI design
Concept development

Engineering & delivery

Software development
Electronics and PCB design
Mechanical design
Prototyping and production

Want to discuss a project or challenge?

Tell us about your situation. Together we map out the question, the technical options and the logical next step.

Discuss your project