For clubs, venues & membership organisations
I’m Jack, a software developer in Sydney. I replace scattered tools with a single platform and one database behind it, so every booking, member and payment is recorded in one place — and nothing depends on who is on shift.
Tools I work with
The problems I solve
None of these need a bigger team. They need the repetitive part handed to software that does not forget.
Some get answered twice, some never get answered at all, and nobody can tell which is which.
One person babysits both, and everything stops when they are away — or when the file quietly forks into two versions.
Every booking costs someone five minutes of copying names, dates and details into an email.
A spreadsheet, a paper diary, an inbox and someone’s memory — and nobody can say which one is right today.
What I build
Most projects begin with one of these and grow from there. Every engagement is scoped in writing with a fixed price before any work begins.
Fast, mobile-first, and built so a first-time visitor understands what you do and how to reach you within seconds.
The repetitive half of front-of-house work, handled by software instead of by staff.
The replacement for five disconnected tools. Bookings, members, events and payments held in a single database instead of scattered across spreadsheets, paper and inboxes.
Approach
Most operational problems are not caused by missing software. They are caused by information sitting in separate places that do not talk to each other, so people become the glue — re-typing the same booking into a spreadsheet, a diary and an email. One system with one database behind it removes the glue.
No open-ended hourly work and no vague statements of work. You know the price and the deliverables before anything starts.
Step 1
A short call about how the work is handled now and where the time actually goes. No pitch.
Step 2
Scope, deliverables, timeline and a fixed price in writing before anything is built.
Step 3
You see working software as it comes together, not a finished surprise at the end.
Step 4
Deployed, documented, and yours — with support afterwards if you want it.
The result
Operational software is judged on a busy night, not in a demo. Everything it shows comes from one database, so what you are looking at is the record itself — not somebody's copy of it.
Illustrative interface, not a client system.
Try a working demonstrationAbout
I’m Jack, a software developer based in Sydney. I build web platforms and the operational systems behind them — the software a business actually runs on, where being wrong has consequences on the night.
Most of my work is consolidation. An operation runs on a spreadsheet, a paper diary, an inbox and three apps that do not talk to each other, and my job is to replace all of it with one system and one database — registrations, bookings, scheduling, member records, and the dashboard over the top of them. Systems staff use every shift, which have to behave predictably while several people act on the same information at once. That kind of work rewards understanding a process properly before writing any code, which is how I start every project.
You deal with me directly — no account manager, no handover to a junior developer, no agency layer in between. I keep the number of projects I take on small enough that each one gets my full attention, and I scope every engagement around what will actually solve the problem, not around what is easiest to build.
Questions
A free 30-minute call about what you actually need, then a written scope with a fixed price. No hourly billing. A deposit starts the work, the balance is due on completion.
A small site, one to two weeks. Booking and enquiry automation, two to four. Bigger systems are split into phases, so you see something working early.
You do — both. Everything transfers on final payment. Always register your domain in your own account, never your developer’s.
Usually a few dollars a month, plus your domain. Email and SMS add small per-message costs. You get the real figure before you commit.
No. Importing and checking what you already have is part of the build, and you keep the original files.
In one managed database, not files on someone’s laptop. Traffic is encrypted. Hosting, access and backups are set out in your proposal, and you can export everything at any time.
Often no, and I’ll say so. A scheduled reminder doesn’t need a language model. AI is worth it when something has to read unstructured text.
Contact
Email is the fastest way to reach me. I read every message myself and reply to all genuine enquiries, usually within one business day.
Or write tohello [at] jackteng.com
None of it has to be exact. A couple of lines on each is plenty to work out whether I can help.