Campsite Studios

Built small.
Shipped properly.

A one-person software studio in Australia. I take the job a spreadsheet keeps getting wrong and turn it into software that a business can rely on on a Monday morning — then leave it documented, tested and yours.

Live deployments
7
Automated tests
133
Typical build
2–6 weeks
Studio size
One

02 Closer look

Vestline

Long service leave, off the spreadsheet.

vestline.pages.dev →

The problem

Every Australian employer with long-serving staff has to book a long service leave provision under AASB 119. In most small practices that is a spreadsheet passed between people, re-derived each year, with the discount rate looked up by hand.

What I built

A calculator that produces a working paper an auditor can accept: probability of attainment, discounting to the reporting date, the RBA yield fetched and cached, and every input shown on the page. Staff data never leaves the browser.

Where it stands

Live, with 31 automated tests, licence keys signed server-side, per-IP rate limits on every paid call, and iOS and Android shells. Priced at A$149 a valuation or A$99 a month. Waiting on an accountant's review of the method before it is promoted.

03 Engage

Three ways in.

MVP build

Fixed price · 2–6 weeks

Discovery, design, build, tests, CI, deployment, and two weeks of fixes after launch. You get the repository, the accounts and a runbook, not a dependency on me.

Retainer

Monthly · Starter, Growth, Scale

Features, fixes, dependency and security updates on a product already running. Suited to a business whose software is load-bearing but does not need a full-time engineer.

Consulting

Hourly

Architecture review, code audit, or a second opinion before you commit budget. Often the cheapest hour a project spends.

Every engagement opens with a short call to agree scope, timeline and price. Nothing starts before that is written down.

04 Standards

What you get, every time.

01

Scope cut to one job

A narrow tool that gets used beats a broad one that gets abandoned during setup.

02

Tests and CI from day one

133 automated tests across the live products. Changes are safe to make because something catches them.

03

Limits stated plainly

Each product says which states it covers, what it does not decide, and when to ask a professional.

04

Handover, not lock-in

Your repository, your Cloudflare and Stripe accounts, a deploy runbook, and secrets you control.

05 Start a brief

Tell me what keeps going wrong.

The useful first message is the problem, not the solution: what the job is, who does it now, and how it fails. I reply personally, usually within two business days.

Or write directly:
[email protected]