How I built a source-backed UK and Netherlands financial calculator platform

I started building Qalqlet after noticing the same problem across many financial calculators: they provide a number, but often give very little context about where it came from.
A take-home salary figure can look precise while hiding important details:
Which tax year was used?
Does the calculation include pension contributions?
Which region or tax rules apply?
When were the underlying thresholds last reviewed?
What does the result exclude?
I wanted to build something more useful than another isolated salary calculator.
The real question is rarely just “What is my net salary?”
People usually arrive with a simple question, but the decision behind it is much larger.
Someone comparing job offers may also need to ask:
How much will I actually take home?
How will pension contributions affect the result?
What size mortgage could I potentially afford?
How much might housing and household costs leave each month?
Would the same salary support a different lifestyle in another country?
That led me to build Qalqlet as a connected financial decision platform rather than a collection of unrelated calculators.
The UK platform currently covers salary, tax, mortgage, pension, benefits, business and household tools:
https://qalqlet.com/uk
Connecting financial decisions
A typical calculator website gives the result and ends the journey.
Qalqlet tries to connect the next relevant question.
For example:
Salary → tax → pension
Mortgage → affordability → household budget
Business income → tax → personal take-home
The goal is not to force users through a funnel. It is to help them understand which calculation naturally comes next.
The platform is free to use and does not require an account.
Why I added the Netherlands
I wanted to test whether the same product structure could support another country without mixing its rules with the UK system.
The Netherlands was a useful second market because it has strong demand around salaries, mortgages, benefits, pensions and expat decisions, but its financial and tax systems are materially different from those of the UK.
Instead of translating UK calculators and changing the currency symbol, I created a separate Netherlands route:
https://qalqlet.com/nl
The Dutch section is Dutch-first, with English available as a secondary route where it helps international users.
Keeping country rules isolated
One of the most important architectural decisions was to keep UK and Netherlands calculation rules separate.
This reduces the risk of:
Applying one country’s thresholds to another
Mixing tax years
Publishing translated calculators with incorrect logic
Updating a shared rule and unintentionally breaking another market
Shared design and publishing components can still be reused, but the underlying country rules, sources and review processes remain isolated.
This creates more work initially, but it should make future country expansion safer.
Official sources are only part of the solution
Saying that a calculator uses official sources is not enough.
Financial rules change. A source may be correct but outdated, incomplete or interpreted incorrectly.
I therefore added a methodology and update policy that aims to show:
Where the rules came from
Which period or tax year applies
When important data was reviewed
Which assumptions are used
What the result includes and excludes
The methodology is available here:
https://qalqlet.com/uk/sources-and-methodology
The calculations are intended for planning and decision support, not as replacements for professional tax, payroll, mortgage or financial advice.
Building the UK and Netherlands comparison
Once both country routes existed, the next question was obvious:
How can someone compare an opportunity in the UK with one in the Netherlands?
A gross salary comparison is rarely meaningful on its own. Taxes, housing, healthcare, childcare and local costs can materially change the outcome.
I built a London versus Amsterdam comparison page that combines salary and local-cost scenarios:
https://qalqlet.com/uk-vs-nl
It is still a planning model rather than a definitive answer, but it is closer to the question users actually want to answer:
“Which place could leave me with more money after the important local costs?”
What I learned
A few lessons from building Qalqlet:

1. The calculation is not the whole product
   Explaining assumptions, limitations and next steps is just as important as displaying the result.
2. More calculators do not automatically create more value
   The tools become more useful when they support a connected decision journey.
3. Country expansion is an operational challenge
   Translation is the easy part. Maintaining sources, rules, review dates and local intent is the difficult part.
4. False precision damages trust
   A financial estimate should be labelled as an estimate when it cannot represent every individual circumstance.
5. Distribution needs to be designed into the product
   Each calculator should answer a specific high-intent question, but it should also help the user continue to the next relevant decision.
   What comes next
   My current priorities are:
   Improving the most-used UK and Netherlands calculators
   Making assumptions and source information easier to understand
   Expanding the cross-border comparison experience
   Learning which calculator journeys users actually complete
   Validating sustainable monetisation without compromising trust
   Deciding which country should be supported next
   Qalqlet is currently bootstrapped.
   I would genuinely appreciate feedback from other founders:
   Does the source and methodology approach increase your trust?
   Which calculator would you use first?
   Is the UK–Netherlands comparison useful?
   Which country should Qalqlet support next?
   UK platform: https://qalqlet.com/uk
   Netherlands platform: https://qalqlet.com/nl
   UK–NL comparison: https://qalqlet.com/uk-vs-nl