Aurenhold Studio

By direct engagement

Software built under contract.

Bespoke software built under contract for a small number of clients at a time — internal tools, operational systems, integrations and applications that a website alone cannot solve.

Available by direct contact with the team. Not a packaged service, and not publicly priced. The studio takes on a limited number of software engagements at a time so each one gets senior attention throughout.

Capability

01 / 03

The problems a website cannot solve.

Most businesses reach a point where the constraint is not how they look but how they operate — and the thing holding it together is a spreadsheet nobody is allowed to touch.

  • Internal tools

    Systems that replace the spreadsheet the business is quietly held together by.

  • Operational systems

    Scheduling, quoting, job tracking and reporting built around how the business actually runs.

  • Integrations

    Making existing systems talk to each other, reliably, without manual re-entry.

  • Applications

    Customer-facing and internal applications, built to be maintained after handover.

  • Data & reporting

    Turning what the business already records into something it can act on.

  • Technical rescue

    Taking on a stalled or inherited codebase and making it safe to work in again.

How it is built

02 / 03

Boring technology, chosen deliberately.

Software you cannot hire anyone else to maintain is a liability, not an asset. The stack is mainstream on purpose, and the code is handed over with the documentation needed to work on it without us.

  • Interfaces

    Fast, accessible front ends that feel considered on every screen size.

  • Data

    Durable storage designed around how your records are actually used.

  • Infrastructure

    Global delivery, so it is quick wherever your customers happen to be.

  • Systems

    The right tool for each job, chosen for longevity rather than fashion.

  • Practice

    Engineered to a standard — tested, reviewed and built to be maintained.

  • Handover

    Your source, your documentation, your accounts. Nothing held hostage.

Engagement

03 / 03

How a software engagement starts.

  1. A conversation about the problem before any proposal exists

  2. A written scope with staged delivery and defined acceptance

  3. Direct access to the people building it

  4. Source code and documentation handed over on completion

Why there is no price on this page

Website pathways are published with figures because they can be — the scope is knowable in advance. Software is not. A quoted rate before anyone has seen the problem is either a guess or a lie, and both cost you more than the honest answer. Scope comes first, then a written figure, then work.

Start the conversationWebsite pathways & pricing