Custom OKR software development
Appfront builds custom software for organisations that work with objectives and key results. Goals link together across the organisation, teams and individuals, progress is pulled automatically from your own systems where 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 objectives at the start of a period, regularly checking progress, and looking back honestly at the end.
That is something different from a KPI dashboard. A dashboard shows how things are going against indicators you track anyway. OKRs are about what you want to change in this period, and they disappear once the goal is reached. In practice, organisations use both, with an integration between them so that a key result pulls its current status from the dashboard.
Appfront builds this as custom software when your way of working departs from the standard model, for example because you work to a different rhythm, because goals span several entities, or because the progress has to come from systems that an off-the-shelf package does not know.
Goals that connect
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 is measurable in an existing system, we retrieve its current value from there. That saves manual updating and prevents over-optimistic self-reporting.
The rhythm built into the system
Check-ins, interim reviews and the evaluation at the end of the period as fixed moments, with reminders rather than a recurring diary appointment.
OKRs or a KPI dashboard? The distinction
They look alike but serve different purposes. 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 things are going
Ongoing indicators you always track: revenue, lead time, utilisation. For these, look at a custom KPI dashboard, optionally linked to your OKRs.
Our development process for your goal-setting system
The pitfall is building a system that is heavier than the rhythm you can realistically sustain. That is where we begin the conversation.
We map the rhythm you work to, the levels at which goals are set, who sets them, and where the figures come from that determine progress. We also look honestly at what is already being sustained, as that predicts what will actually get used.
We design the model of objectives and outcomes, the links between levels, the check-in flow and the views for each role (board, team lead, 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 the work based on what your team actually needs in practice, rather than on a specification written months earlier.
A controlled go-live with validation and a safety net, followed by ongoing management, monitoring and further development as your planning rhythm or organisational structure changes.
What bespoke OKR software concretely delivers
What is needed differs from one organisation to another. These are the components that come up most often.
Goals across several levels
Organisation, department, team and individual, with an explicit link so it is visible which goal each one contributes to and which goals are left without a contribution.
Measurable outcomes
For each goal, a handful of key results with starting and target values, unit and owner, so progress is a number rather than a feeling.
Automatic status updates
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 states the status and confidence level, with alerts for goals that have stalled or whose confidence is falling.
Evaluation and history
At the end of the period, a record of what was achieved and what was not, alongside the history of previous periods so patterns become visible.
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 instrument of control, and then honesty stops.
Typical use cases in practice
OKRs work best where several teams need to keep pointing in the same direction without central direction.
Growing organisations
Companies that have grown too large to keep direction through conversation, and where teams are otherwise each moving in their own direction.
Multiple sites or entities
Organisations where the same goals play out differently in different locations, and where there is no overview across entities.
Semi-public institutions
Organisations with a multi-year plan that needs to be broken down into concrete goals per period, with accountability to a council or board.
Programmes and transformations
Multi-year initiatives where the 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 turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology we use
The precise 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 continue to develop, without dependence on per-user licences.
Why choose Appfront for your goal-setting system?
Appfront builds custom software for a wide range of organisations across the Netherlands. With OKRs, we start with the awkward question: which rhythm can you actually sustain? A system that assumes monthly check-ins when in practice you review twice a year will be abandoned within a quarter.
For that reason, we would rather invest in automatically pulling in progress than in extra features. Every manual input step you can eliminate increases the chance that the system is still in use 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: transparent code and clear agreements on monitoring, alerting and maintenance. You own the solution and pay no per-user licence fee.
Also take a look at our broader services around bespoke software, a KPI dashboard and project management software. Unsure about the approach? Get in touch.
Security and privacy in your goal-setting system
Goals at an individual level are personal data and affect how employees are assessed. Appfront builds to the OWASP ASVS with GDPR as a baseline, with role-based access that is restricted by default rather than open by default.
Deciding who can see which goals is a substantive choice with real consequences. Transparency about team goals usually works well; making individual progress widely visible usually backfires. We configure this per level and record access in an audit trail.
More on our security approach: information security policy and CVD policy.
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access following least privilege
- Audit trail for viewing and changes
- Secrets in a secure vault, not in code
- Documented data flows for your record of processing activities
- Individual goals restricted by default
Frequently asked questions about custom OKR software
Answers to the questions we are asked most often.
A KPI is an indicator you track on an ongoing basis that does not go away: revenue, lead time, sickness absence. An OKR is an objective for a defined period with measurable outcomes, aimed at changing something. A KPI can still be the yardstick for a key result, which is why we often link the two.
With five teams and one rhythm, a shared document will get you a long way. Software becomes worthwhile once goals are linked across multiple levels, once you want to pull progress from source systems, or once nobody can see any longer which goals are running. If none of that applies, we will tell you so.
If your rhythm and structure match the standard model, a package is almost always faster and cheaper. Bespoke development pays off when you work to a different rhythm, when goals span entities or partnerships, or when progress has to come from systems a package cannot connect to.
By configuring views and permissions so that not everyone sees everything, and by pulling in progress automatically wherever possible. As soon as people enter their own scores and are judged on them, optimistic figures take over and the system becomes worthless.
Yes, for key results that are measurable in an existing system: revenue from your accounts, counts from your own application, lead time from your ticketing system. Goals concerning behaviour or quality remain a judgement. We make that distinction deliberately during design.
Yes. The quarter is common but not sacred; in education or for programmes, a different rhythm often suits better. The system works with periods you define yourself, even when different parts of the organisation run at different paces.
Probably not directly, and that is substantive advice. Once the outcome of an OKR counts towards an appraisal, goals get set more cautiously and you lose precisely what the method is meant to deliver. What does work is recording conversations about the period itself in the system, separately from the performance review cycle.
Then goals should be adjusted, and that should be visible. The system keeps the original objective alongside the revised one, with when and why it changed. Without that history, everything looks achieved in hindsight, and the organisation learns nothing from the period.
Ready to build your OKR software?
Tell us what rhythm you work to, at which levels you set objectives and where the figures come from. We are happy to help you think through scope, integrations and the first version. A no-obligation first conversation will give you a clear picture of what is possible and whether custom work makes sense for your situation.