Custom OKR software development
Appfront builds custom software for organisations that work with objectives and key results. Goals link up across organisation, team and individual, progress comes automatically from your own systems wherever possible, and the quarterly rhythm of check-ins and reviews lives in the system rather than in one person's diary. Get in touch.
What is OKR software?
OKR stands for objectives and key results: an objective that gives direction, with a handful of measurable outcomes that show whether you are getting there. The method relies on a rhythm: setting goals at the start of a period, regularly catching up on progress, and looking back honestly at the end.
That is not the same as a KPI dashboard. A dashboard shows how the indicators you track anyway are doing. OKRs are about what you want to change this period, and they disappear once the goal is achieved. In practice, organisations use both, with an integration between them so that a key result takes its current value from the dashboard.
Appfront builds this as custom software when your way of working differs from the standard model, for example because you work to a different rhythm, because goals span multiple entities, or because progress has to come from systems an off-the-shelf package does not know.
Goals that link up
A team goal that contributes to an organisational goal, with visibility of what happens to the higher-level goal when an underlying goal falls behind.
Progress from the source
Where a key result can be measured in an existing system, we pull the current value from there. That saves manual updating and prevents over-optimistic self-reporting.
The rhythm built into the system
Check-ins, interim results and the end-of-period review as fixed moments, with reminders instead of a recurring calendar appointment.
OKR or KPI dashboard? Drawing the line
They look alike but serve a different purpose. The difference determines which page you are looking for.
What you want to change
Goals for a defined period with measurable outcomes, linked across levels, with check-ins and a review. They come and go with the period.
How you are doing
Ongoing indicators that you always track: revenue, lead time, utilisation. In that case, look at a custom KPI dashboard, optionally linked to your OKRs.
Our development process for your goals system
The pitfall is building a system that is heavier than the rhythm you will actually sustain. That is where we start the conversation.
We map out the rhythm you work to, the levels at which goals are set, who sets them and where the figures that determine progress come from. We also take an honest look at what is already being sustained, because that predicts what will actually be used.
We design the model of goals and outcomes, the linking between levels, the check-in flow and the views per role (board, team leader, employee), each of which wants to see something different.
We build in short iterations with automated tests, structured logging and monitoring. You see working versions along the way and steer based on what your team actually needs in practice, rather than on a specification written months ago.
A controlled go-live with validation and a safety net, followed by ongoing maintenance, monitoring and further development as your planning rhythm or organisational structure changes.
What custom OKR software delivers in practice
What you need differs per organisation. These are the components that come up most often.
Goals at multiple levels
Organisation, department, team and individual, with an explicit link so it is clear what a goal contributes to and which goals are left hanging without a contribution.
Measurable outcomes
A handful of key results per goal, with a start and target value, unit and owner, so that progress is a number rather than a feeling.
Automatic values
Integrations with the systems where the figures already live, so a key result updates itself and the check-in is about interpretation rather than data entry.
Check-ins and alerts
A fixed moment at which the owner records the status and their confidence, flagging goals that have stalled or whose confidence is falling.
Evaluation and history
At the end of the period, record what was achieved and what was not, with the history of earlier periods alongside to help you spot patterns.
Views by role
An employee sees their own goals, a team leader sees those of their team, and the board sees the whole picture. Without that separation, the system becomes a means of control and honesty stops.
Typical use cases in practice
OKRs work best where multiple teams need to stay aligned without central direction.
Growing organisations
Companies that have grown too large to keep everyone aligned through conversation, and where teams would otherwise each go their own way.
Multiple locations or entities
Organisations where the same goals play out differently in different places and where there is no overview across entities.
Semi-public institutions
Organisations with a multi-year plan that must be translated into concrete goals per period, with accountability to a council or board.
Programmes and transformations
Projects that run for several years, where goals shift from period to period but the direction stays the same.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.
View OneDayBuild →Technology we use
The exact choice depends on your processes, the systems to be integrated and your hosting preferences. We deliberately choose a stack that your own team can manage and develop further, with no dependence on per-user licences.
Why Appfront for your goal-tracking system?
Appfront builds custom software for a wide range of organisations in the Netherlands. With OKRs, we start by asking the awkward question: what rhythm can you realistically sustain? A system that assumes monthly check-ins when in practice you review twice a year will be abandoned within a quarter.
If you work with goals in the Treams platform and want to link it to your HR system and reports, read more about our Treams integration.
That is why we would rather invest in retrieving progress automatically than in extra features. Every manual input step you can eliminate increases the chance that the system is still being used a year from now.
On every project we write clear documentation and make sure your own team, or a future supplier, can understand and manage the system. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance. You own the solution and pay no per-user licence.
Also see our broader services around custom software, a KPI dashboard and project management software. Not sure about the approach? Get in touch.
Security and privacy in your goal-tracking system
Individual-level goals are personal data and touch on how employees perform. Appfront builds in line with OWASP ASVS and with the GDPR as a starting point, using role-based access that is restricted by default rather than open by default.
Who gets to see which goals is a substantive choice with consequences here. Transparency about team goals usually works well; making individual progress widely visible usually backfires. We set this up per level and record access in an audit trail.
More about our approach to security: information security policy and CVD policy.
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access following least privilege
- Audit trail of views and changes
- Secrets in a secure vault, not in code
- Documented data flows for your processing register
- Individual goals have limited visibility by default
Frequently asked questions about building OKR software
Answers to the questions we get asked most often.
A KPI is an indicator you track continuously and that never goes away: revenue, lead time, absenteeism. An OKR is a goal for a defined period with measurable outcomes, aimed at changing something. A KPI can serve as the yardstick for a key result, which is why we often link the two.
With five teams and a single rhythm, a shared document will take you a long way. Software starts to pay off once goals are linked across multiple levels, once you want to pull progress from source systems, or once nobody has an overview of which goals are running. If that is not the case, we will tell you.
If your cadence and structure match the standard model, a package is almost always faster and cheaper. Custom pays off if you work to a different cadence, if goals span entities or partnerships, or if progress has to come from systems that a package cannot connect to.
By setting up the views and permissions so that not everyone sees everything, and by retrieving progress automatically wherever possible. As soon as people fill in their own figures and are judged on them, an optimistic picture takes hold and the system becomes worthless.
For key results that can be measured in an existing system, yes: revenue from your accounting system, volumes from your own application, lead time from your ticketing system. Goals about behaviour or quality remain a matter of judgement. We make that distinction deliberately during the design.
Yes. The quarter is customary but not sacred; in education or programme-based work a different rhythm often fits better. The system works with periods you define yourself, even if different parts of the organisation move at a different pace.
Preferably not directly, and that is a substantive recommendation. As soon as the outcome of an OKR counts towards a review, goals are set more cautiously and you lose exactly what the method is meant to deliver. What does work is recording the conversations about the period itself in the system, separate from the HR cycle.
Then goals get adjusted, and that should happen visibly. The system keeps the original objective alongside the amended one, with when and why. Without that history, everything looks achieved in hindsight, and the organisation learns nothing from the period.
Ready to build your OKR software?
Tell us which rhythm you work in, at which levels you set goals and where the figures come from — we'd be glad to think along on scope, integrations and the first version. A no-obligation first conversation gives you a clear picture of the possibilities and whether custom software pays off in your situation.