FAQ

Questions people ask before they start.

Straight answers on cost, timing, ownership, hosting, AI and support. If yours is not here, email and ask.

How much does custom software cost?

Less than most people expect, and more than a template. Fixed-scope assessments and prototypes start in the low thousands. Platform builds usually run as a monthly engagement over several months, stepping down to a lower support fee once the system is stable. Hosting is separate, runs in your own accounts and typically costs tens of dollars a month. We give a written estimate after a short discovery, and we tell you early if we think a product off the shelf would serve you better.

How long does it take?

A working prototype on your real data usually exists within days. A first production release with logins, roles and the core workflow typically lands within a few weeks. From there features ship weekly. The racing operations platform described in our work section went from an approved demo to a secured production cutover in two days, then grew for months by extension.

Who owns the code?

You do. Source code lives in a repository you control, hosting runs in your own accounts, and documentation and a handover checklist are part of the delivery. There is no licence fee and no lock-in; another developer could take the system on from the handover documents.

What technology do you use?

Python with FastAPI or Django, PostgreSQL, server-rendered HTML with light JavaScript, SwiftUI for native iOS, Flutter for Android, progressive web apps where an app store is unnecessary, and Render, Cloudflare and Google Cloud for hosting. For AI, the Anthropic Claude API and open-source machine learning such as LightGBM; for vision, YOLO, ByteTrack, SAM and custom pose-estimation models. The stack is chosen to be reliable, cheap to run and easy for others to maintain.

Can you integrate with Xero, payroll and our other systems?

Yes. We use official APIs where they exist (Xero, Google Sheets, Firebase, weather services), scheduled exports and email ingestion where they do not, and careful, monitored headless-browser automation as a last resort for vendor portals with no API, always within the vendor's terms. Every integration reconciles back to its source and tells you when it stops.

Is it safe to put AI in front of our staff and data?

It is when it is built with guardrails. Our natural-language assistants only see allow-listed tables, run read-only queries with a hard time limit, block sensitive columns at the database layer, are only offered to roles already permitted to see the data, and are rate-limited with a daily spend cap. Models are tested against question banks or held-out data before release. Where a feature does not need a language model, it does not get one.

Do you build mobile apps?

Yes: native iOS in SwiftUI, Android (and cross-platform) in Flutter, and installable progressive web apps with push notifications when an app store is unnecessary. Apps are built alongside the backend, often with server-driven screens so new features ship without an app release. We handle TestFlight, signed APK distribution and store listings.

Can you work with cameras and video?

Yes. We build the whole pipeline: capture hardware on a Raspberry Pi, upload to cloud storage, serverless classification, GPU pose estimation, measurement with repeatability checks, storage and dashboards. We have processed tens of thousands of videos and trained custom keypoint models on our own labelled data.

What industries do you work in?

Deepest experience is in thoroughbred racing and breeding, construction compliance, sport and education, and data-heavy businesses generally, with an agribusiness platform now in scoping. The methods transfer: any business with an unusual workflow, several systems that need reconciling or data that needs collecting and cleaning.

Where are you based and do you work remotely?

Victoria, Australia. Most work is remote with site visits where they help, such as installing cameras or sitting with staff during discovery. We work with clients across Australia.

What happens after launch?

Support on a simple monthly basis, scaled to how much the platform changes. Monitoring, backups and alerts are set up before launch, so problems are seen early. If you want to take the system in-house, the handover documents and the deliberately conventional stack make that straightforward.

Do you do fixed-price work?

Yes, for assessments, prototypes and well-defined builds with a written output. Platform builds with evolving scope run monthly, which is usually cheaper and more honest for both sides.

Will you sign an NDA and keep our name off your site?

Yes. None of the case studies on this site name the client, and we will not name yours without permission.

Have something you need built?

Tell us the problem, the systems you already use and what a good outcome looks like. You will get a plain-language reply within one business day, usually with a first sketch of how we would build it.