Skip to content
Fona

Service

Custom software

We build the software your operation needs when nothing on the market fits. With architecture designed for five years, not for the demo.

Let's talkSee case studies
Abstract illustration of stacked architecture blocks in layers

The problem

The off-the-shelf product forces you to work backwards

You have a process that is a competitive advantage and a tool that insists you do it differently. In between sit three spreadsheets and one person holding it all together.

Signs this is you

  • A core company process lives in Excel
  • You pay licences for a product you use fifteen per cent of
  • The current tool cannot cope with current volume
  • Every change depends on a vendor who takes months
  • Nobody holds the code or the documentation for what already exists
  • What was built years ago is now something nobody dares touch

What we do

What we do

Business applications

Customer portals, internal operations tools, planning systems and booking engines. Built around your business logic, not a generic product’s.

Multi-tenant platforms

A shared core serving several brands, sites or clients, with per-instance configuration and centralised deployment. Architecture proven on real project portfolios.

Legacy rescue

For when what exists works but nobody dares touch it: tests, documentation, dependency upgrades and modernisation in parts, without stopping the business.

No surprises

A release every two weeks in an environment you can try. Your code, in your repository, with automated deployment from day one.

2 wks
between testable releases
14+ years
building production systems
100%
of the code in your repository from day one

How we do it

How we do it

  1. Definition

    We walk the process with the people who run it, not only with the people who describe it. We come out with scope, priorities and an explicit list of what is out of the first release.

    DeliverableScope and phased estimate

  2. Architecture and skeleton

    Data model, written technical decisions and the skeleton deployed with CI/CD before any feature work. Everything after that is born deployable.

    DeliverableWorking integration environment

  3. Fortnightly delivery

    Every two weeks there is something you can use and react to. Priorities adjust with what we learn, not with what we assumed at the start.

    DeliverableTestable release every two weeks

  4. Launch and warranty

    Training, data migration, hands-on support through the first weeks and a warranty period on what we delivered.

    DeliverableProduction, manuals and warranty

Technologies

  • Laravel
  • PHP
  • Vue.js
  • Nuxt
  • TypeScript
  • Node.js
  • PostgreSQL
  • Docker
  • GitHub Actions
  • AWS

FAQ

What people ask us

Is the code ours?

Yes, without qualification. It lives in your repository from the first commit and the intellectual property is stated in the contract. If you want to change vendor tomorrow, you take everything: code, documentation and deployment.

Fixed price or time and materials?

Fixed price per phase, with that phase’s scope agreed in writing. A fixed price for an entire twelve-month project is a fiction that ends badly for somebody; per phase, it works.

What happens when the project ends?

You can take a monthly maintenance retainer, hand it to your team with training and documentation, or move it to another vendor. We design so that all three remain possible.

Can you pick up a project someone else started?

Yes, it is a regular part of our work. We begin with a code and infrastructure review to establish the real state of things, and from there we decide together whether to continue, refactor or rewrite in parts.

Next step

Half an hour well spent

Walk us through the problem on a short call. You leave with a first read on how we'd approach it and what it would involve — no commitment, no sales deck.

Let's talkHow we work