Custom software · Built for your business

Finished software.
A price tied
to its value.

We turn a business problem into a working product. Together, we define the outcome, agree on the scope and price, and establish what counts as delivered.

01 / A defined product02 / An agreed price03 / Verifiable delivery

01 / What we build

Start with the problem
you need solved.

Custom software products

A product people can actually use.

Web applications, customer portals and internal tools built around a specific workflow. We agree on the essential features and the conditions the finished product must meet.

Integrations & business tools

Less manual work between systems.

Connect services, move data reliably and automate repetitive tasks. Define the business value in practical terms: less re-entry, fewer errors, or a workflow that completes on time.

Software rescue & performance

An existing system you can move forward with.

Fix a fragile service, resolve a performance bottleneck or complete a stalled product. We establish the current behavior and agree on measurable improvements before making changes.

For technically demanding projects, our experience includes Rust, compilers and software infrastructure.

02 / The commercial model

The product is
the unit of work.

We charge for the finished product and the value it delivers.

The proposal sets out the scope, agreed price, delivery milestones and acceptance criteria. You can assess the investment against the outcome your business needs.

  1. Define the outcome

    Who will use the software? What should improve? We turn those answers into a concrete scope and checks for success.

  2. Agree on the price

    Review the deliverables, price, payment schedule and responsibilities before implementation begins.

  3. Build, verify, deliver

    Review working software against the agreed criteria, then receive the handover needed to use and maintain it.

If the scope changes, we agree on the effect on price and delivery before taking on the additional work.

03 / A complete handover

Ready for the people
who will use it.

The product

Working software

The agreed functionality, checked against the workflows and acceptance criteria in your proposal.

The foundation

Source & documentation

The project source, setup instructions and an explanation of the decisions needed to maintain it.

The transition

A clear path into use

An agreed deployment and handover plan, with ownership, access and support responsibilities made explicit.

04 / Before we start

Good questions.

How much will my project cost?

Each proposal is priced around the finished product, its scope and the value of solving the problem. Tell us who the software is for, what it needs to do and any budget or timing constraints. We can then discuss a concrete scope and price.

Do you bill by the hour?

Our commercial model is based on the agreed product and delivered value. The proposal defines the price and payment schedule for that scope.

What counts as finished?

We agree on acceptance criteria before implementation. These describe what the software must do and how you will verify it, along with the documentation and handover included in the delivery.

Can you work on our existing software?

Yes. We first review the existing system and the problem you want to solve, then define a bounded piece of work with clear acceptance criteria.

What happens after delivery?

We agree on the handover and any included support in the contract. Ongoing maintenance and future improvements can be scoped separately.

05 / Your next product

What would make
a real difference
to your business?

Send a short description of the problem, who needs it solved, and any timing or budget constraints. We’ll start with the outcome you want.

Discuss your project