Services

What we take on

We work by engagement, with a written scope and a clear schedule. No surprise invoicing.


Consulting

Decide before you spend

Four short engagements, hourly or fixed-price. None of them obliges you to continue with us.

Second opinion before investing

You've received a quote and no way to judge it. We read it, ask the questions it doesn't answer, and tell you what the price actually buys.

Who it's for: A director who has to approve a technical budget without in-house expertise.

Audit of an existing system

An honest read on an application you inherited: what holds up, what's fragile, what's expensive to keep alive. You leave with a prioritised list, not a verdict.

Who it's for: An organisation depending on a system nobody understands any more.

Fractional technical leadership

A few days a month: architecture calls, reviewing a vendor's work, mentoring an in-house developer, technical planning.

Who it's for: An organisation that needs steady technical judgement but not a full-time hire.

Build or buy

The question few suppliers ask: would an existing tool do the job? We compare honestly, and sometimes conclude that you don't need us.

Who it's for: An organisation tempted to commission custom software for a solved problem.


Delivery

Build it and ship it

Once the decision is made, we take the product from beginning to end.

Custom web product

A complete web application: data model, API, interface, hosting. We start from how you actually work — not from a template you'd have to work around.

Who it's for: An organisation running on spreadsheets, email and one tool nobody likes.

Mobile app and store release

iOS and Android published under your own accounts. We handle signing, certificates, versioning, automated deployment and the back-and-forth with Apple review.

Who it's for: An organisation that needs to be in the stores and would rather not discover mid-project that releasing is a trade of its own.

Modernising an existing system

Taking over legacy code: stabilise, document, add tests and deployment, then modernise in stages. Without a full rewrite imposed on day one.

Who it's for: An organisation whose system still works, but whose workings nobody remembers.

Maintenance and evolution

A live product keeps needing attention: security updates, store requirements, small improvements. Monthly retainer or on request.

Who it's for: An organisation with a product in service and nobody to look after it.


How it works

  1. Opening call

    Thirty minutes to understand the need. Free, no commitment.

  2. Written proposal

    Scope, schedule, price. A document you can put in front of your board.

  3. Work in stages

    You see the engagement progress at short intervals. No six-month tunnel.

  4. Handover and after

    Documentation, access transfer, and ongoing maintenance if you want it.

Let's talk about your project