Smartly designed. Pleasant to use.
For every challenge
a solution
that works.
Elk Solutions designs and builds software that makes complex work easier. From national document chains to software for daily practice.
ROOM TO GROW.
YOUR WORK CHANGESA new requirement.
Your app grows with you.
| Title | Priority |
|---|---|
| Document A | High |
| Document B | Normal |
Try a change. See what changes with it.
Simplified example of our approach
Since 2015. Growing without rebuilding.In practice at Leitz ServiceDifferent questions. The same attention.
Ideas you can use.
What changes?
An invisible differenceA traceable changeIllustration of the principle
Complex rules.
A clear next step.↗
From a Word document to a publication with a reliable structure.
Write without needing to know XML.↗
An editor for structured documents. In your browser or embedded in your own application.
Highly readable.
Also for a screen reader.↗
We restore document structure and check the reading order.
2015↗
Software that grows with
the work.↗
Customer information, service, and planning in one custom system.
How we work
First, understand. Only then, build.
Sharpening the question
Together, we look at your work, your users, and where things get stuck. This makes it clear what the solution needs to deliver.
Discuss your questionTrying the solution
An idea becomes a concrete proposal that you can review and try out. Your feedback determines the next step.
View our approachBuilding for practice
We build intuitive software centered around the people who work with it. See how that has been working in practice at Leitz for years.
View the Leitz case
Elk Solutions
Built for practice.
Our software runs in national publication chains and within organizations that work with it daily.
View the evidence and applications
Four checks. One verifiable outcome.
One real fragment travels the whole route. This demonstration follows a single rule change — not an audit of the entire document.
- was the text in force, with article number, source and reference date
- rule change what the machine recognises as removed and added
- becomes the consolidated result, without losing provenance
- evidence decision, identifiers, validator and stated scope
Artikel 22.12 —
Bij maatwerkvoorschrift als bedoeld in artikel 22.422.5 kan in ieder
geval worden bepaald:
Gemeenteblad 2026, 195433 · Alphen aan den Rijn, amending decision 2026-A, 23 April 2026 — the Dutch original, laid out by our software
- 01 Submission operated by · the municipality
- 02 Renvooi service operated by · Logius our software runs here
- 03 Besluitpreview operated by · Logius our software runs here
- 04 LVBB operated by · Logius
- 05 stop2fo · stop2html operated by · KOOP our software runs here
- 06 Publication operated by · officielebekendmakingen.nl
At three of the six links, software we wrote is running: four services — the renvooi service, the BesluitPreviewService, stop2fo and stop2html.
Operation and authorship are not the same: these services are operated nationally by Logius and KOOP. This shows where our software runs, not what we own.
Which symptom do you recognise?
You do not need to know the solution yet
- Structure gets lost “The document looks right, but systems understand something else.”
- The output excludes people “The PDF is finished. Its accessibility is not yet demonstrable.”
- The renderer is holding you back “Replacement is possible. Understanding the existing output exactly is the real work.”
- The entire chain is creaking “Isolated repairs no longer help. The connections need to be restored.”
- Current dossier · specialised ePI control layer One managed environment for ePI. Before and after EMA.
- The backlog is not shrinking · our own product “276 plans to convert, and 1,956 days until 2032.”
In Practice
“RIS has been a stable foundation since 2015 that we can constantly expand and that grows with our needs.”
— Theo Boskma, Managing Director, Leitz Service BV
- 10+
- years in production
- 40+
- employees at Leitz
- 1M+
- visit records in RIS
What are you struggling with?
A question doesn't have to be a briefing yet. Tell us what you want to achieve and where things are getting stuck.
View the Document Pipeline Quickscan
One pipeline · five working days · visibly bounded evidence