Different industries. The same discipline.
A debt advisory CRM, a compliance training platform, a junior sports app, two hospitality venues and a builder's website. Most of what gets built holds client data and stays private. These are the ones that can be shown, picked for range.
Each one, written up in full
Written the same way every time: what the business needed, what got built, and the decisions behind it. Where a platform holds live client data, every screenshot here uses mock records. Different industries, different budgets, different scale, on purpose.
The system a firm runs on
A debt advisory CRM in full production that replaced a Monday board. Covenant compliance across eleven states, live market rates, deal pipeline, e-signing, HR and analytics. Built from the team's wishlist, on infrastructure they own, with a deploy that cannot take the business offline. The one I would point at first.
Read the build
Twelve ways to ask the same question
A learning platform in production for NDIS providers. A registered nurse's clinical knowledge turned into twenty-six training modules, where every knowledge check can be answered as a plain list or played as one of eight games, and the record afterwards cannot tell which. Certificates that verify, and refresher training that books its own next round.
Read the build
It started with a goal song
A parent wanted the boys to hear their own song over a speaker when they scored. That got built, then it kept going: lineups dragged onto a field, live scoring several people can touch at once, and a match worm that families watch from interstate when their kid is away. Runs at no cost to the club, with row-level security on every table in the schema.
Read the build
Two brands, one back office
A banh mi cafe and a Vietnamese street food bar for the same operator. Microsoft Entra foundation, two websites that share nothing but a build, domains and mail, digital menuboards and Square point of sale. Sequenced so the software is the thing waiting on the fitout, rather than the other way round.
Read the build
A contractor's front door, built to be handed over
Eight photographic projects from 127 MB of masters, reaching a visitor as a 762 KB first load, on hosting the client owns. The quieter half of the job was moving a domain out of a previous developer's personal account without dropping a single email.
Read the buildLight is a feature you can verify
Weight is where discipline shows first. A heavy page is usually a page nobody was accountable for. Here are three pages drawn to scale. Press load, and the bars fill at the speed the bytes actually arrive on a slow connection.
And six more, where the audit trail is the product
Separate from the five above and grouped because they do have something in common: every one of them holds sensitive client data, which is also why they are described rather than named. Any of them can be spoken to in more detail in a conversation.
A practice management platform
A large operating platform for a financial advisory practice: complex data relationships, sensitive client information and regulatory obligations, in daily production use.
A multi-module care platform
Extensive involvement in the development of a substantial operating platform for the care sector, spanning participants, staff, scheduling and funding.
An electronic signing system
Document management and signing, built where an auditable trail across contracts, variations and approvals is the requirement.
A learning management system
Training software for a regulated sector, built where compliance evidence and record retention are the entire purpose of the system.
A club management application
A sporting club platform delivered end to end, including mobile use in the field by non-technical volunteers.
Websites & front doors
Numerous production sites across software products and the hospitality sector, built to be found, fast and maintainable.
And the one Leapfrog runs itself on.
Leapfrog's own CRM is built the way client platforms are built. It is where proposals are written, sent and signed through LeapSign, where the pipeline board and the morning briefing live, and where every client's portal is served from. It runs on infrastructure that costs nothing a month, behind Cloudflare, with nightly backups to a second provider and a restore drill that has been run rather than assumed. Every change ships through the same gate of 1,750 automated tests before it is allowed near a client.
Who actually did all this
Andrew Justice
Leapfrog Automation, Perth
Perth born and raised. Every platform on this page was built by me, and on the ones where I was part of a larger team, that is said plainly rather than blurred.
The person who scopes your build is the person who writes it. No subcontracting, no account manager relaying to a team you never meet, and on site when it matters. That is the whole model. It is why the timelines are short, and why you can ask a question and get an answer from whoever made the decision rather than from someone repeating it back.
The range above is not an accident. Over the past twenty years I have owned and run businesses in several industries, hospitality venues in Perth and a commercial software company among them: staff to roster, margins to hold, a development team to direct, customers to win, and everything that broke in between. I know what it takes to stay competitive when the admin never stops, because I have sat on your side of this table. It is usually why I can name the bottleneck before the first meeting is over.
The thing I would actually point at, though, is the football app. Nobody paid for it, it is my son's team, and it is the most honest picture of how I work that exists.
Talk about what yours would look like.
Bring the workflow, the compliance regime, or the spreadsheet that runs the place. You will get a straight answer on whether it is worth building, and work you can open in another tab is easier to check than a promise.