CDCharsley Digital

Charsley Digital / software studio

Systems built
to be owned.

Custom software for organisations that need to own their systems.

Dedicated infrastructure, direct support, and no platform lock-in. The software is built around how the organisation actually operates.

Selected work, 2024–2026Dedicated infrastructure

Selected work

Live systems

02

SAPRF

Membership, PRS and PR22 matches, payments, and national standings in one system.

Design, build, and host / Laravel, Livewire, MariaDB, Redis, Mailgun Visit platform
SAPRF
05

CentreVision

Vehicle reads, watchlists, dwell, and traffic reports. It does not open gates.

Design, build, and host / Laravel, Postgres, Redis Visit platform
CentreVision
04

DeadCenter

Seasons, squadding, and scoring on the web, plus an Android app for the range.

Design, build, and host / Laravel, Kotlin, Jetpack Compose, Room Visit platform
DeadCenter

Practice

Software shaped around the operation.

01

Membership platforms

Member records, renewals, documents, roles, and the admin work around a real association.

02

Match and event systems

Entries, scoring, results, and the public record of a competition.

03

Site traffic systems

Vehicle reads, watchlists, dwell, and reports. The system records and reports. It does not control gates.

04

Point of sale

Sales, stock, and the counter workflow for a business that needs the software on its own infrastructure.

05

Operational reporting

The numbers the organisation actually uses, in a form the people running it can read.

06

Dedicated hosting

The system runs on infrastructure set aside for that client, with the data kept separate.

Ownership

The client owns the system.

Data, access, and the right to leave stay with the organisation. The software is not rented from a shared product that can change underneath the operation.

Your data

Records stay with the organisation that created them.

Your infrastructure

Each system runs on dedicated infrastructure, not a shared tenancy.

No lock-in

You can take the system and the data if the working relationship ends.

Process

Four stages

01

Discovery

How the organisation works now, and where the current tools fail.

02

Scope

What gets built, what stays out, and what it costs to run.

03

Build

The system, on infrastructure that belongs to the engagement.

04

Operate

Hosting, fixes, and changes after the system is in use.

Commercial

Clear costs. No lock-in.

01

Build

Scoped and quoted before work starts.

02

Hosting

A monthly cost for the dedicated infrastructure.

03

Support

A retainer for fixes and small changes, or quoted work when the change is larger.

04

Exit

The data and the system can leave with the client.

Start a project

Tell me what the system needs to do.

A short note is enough. I reply with whether it is a fit, and what the first step would be.

Sent to the studio. No newsletter.