Custom software, built around how your business works.
Operations platforms, internal tools and portals for Australian businesses that have outgrown spreadsheets and off-the-shelf apps. Designed, built and handed over by one senior team, with AI built in where it earns its place.
What you get
Custom systems we build.
01
Operations platforms
An operations platform is a single system for running the day-to-day work: every job, order or client moves through clear stages, with the tasks, documents and owner for each step in one place. It replaces the spreadsheets, inboxes and chat groups where work usually gets tracked. Your team sees what is due, what is stuck and who has it, and the system, not a manager, chases anything overdue. Connected to the CRM, accounting and e-signature tools you already use, it picks up a signed deal and turns it into work for the team, with no retyping in between.
02
Internal tools and admin panels
Internal tools are the screens your staff use to run the business behind the scenes, built around your process instead of five spreadsheets and a shared inbox. Common examples are an admin panel over your records, a job or booking board, a register of assets or contracts, and the forms people fill in every day. We start from the spreadsheets you already rely on: the columns that matter become a proper database with validation, search and permissions, so two people can update the same record without overwriting each other. Anyone who still wants a spreadsheet can export one.
03
Customer and supplier portals
A customer or supplier portal gives the people you work with their own login, where they check progress, upload documents and sign without emailing you. Each person sees only their own jobs, documents and messages, and every upload or signature lands in your system against the right record. It suits applications and onboarding, order or job status, and document collection with e-signature. The portal reads the same data your team works in, so nobody has to keep customers up to date by hand.
04
Approval workflows
An approval workflow sends each request to the right person, records the decision and tells everyone involved, with an audit trail of who approved what and when. Purchases, expenses, leave, refunds and contract changes all fit the pattern. Rules set the route: who approves which amounts, what needs a second signature and who stands in when someone is away. Approvers can act from their phone or a Lark message, and the documents travel with the request, so nothing gets lost in a chat thread.
05
System integrations
System integration connects the software you already pay for, so information entered in one place shows up wherever it is needed and nobody types the same thing twice. We write each integration directly against the other system's own API, two-way where it needs to be: Lark, Microsoft 365, Google Workspace, Xero, HubSpot, Stripe, e-signature services and shared drives. There is no extra service in the middle handling your data, and every sync is logged, so a failed update raises an alert instead of going missing quietly.
06
Dashboards and reporting
A dashboard puts live numbers from the systems you already use on one screen, so nobody waits for the month-end export. It reads straight from the source: the platform itself, your CRM and accounting software, and any spreadsheets still in use, so the figures match what your team sees. The usual views are work in progress, overdue tasks, the sales pipeline, payments coming in and team workload, each with the detail one click away. Scheduled reports can arrive by email or Lark every Monday, and who sees what follows the same permissions as the rest of the system.
works with: Next.js · TypeScript · Postgres · AWS · Vercel · Lark Open Platform
When it is worth doing
Four signs you have outgrown what you have.
- 01
Your process lives in spreadsheets that only one person understands.
- 02
You pay for a big platform and use a tenth of it, or bend your process to fit it.
- 03
Staff type the same data into two or three systems.
- 04
Customers keep asking for a login, a status page or self-service.
Still deciding?
How it runs
Prototype first. Demo as we go.
- Written scope
Discover
A 30-minute call about the problem, then a written scope you approve before any work starts.
- Prototype first
Design
A clickable prototype before any code is written, so you see what you are getting first.
- Regular demos
Build
Working demos at the interval set in the written scope, so there are no surprises at the end.
- Documented handover
Launch and support
Deployed, documented and handed over. Ongoing support is there if you want it, never required.
Buy when a product fits the way you work and the process is not what makes you different. Build when you are bending the business around the tool, paying for features nobody uses, or stitching several tools together by hand. If buying is the better answer we will say so on the first call.
A CRM such as HubSpot tracks contacts, leads and deals, mostly up to the sale. An operations platform runs the work that follows: the stages, tasks, documents, approvals and people that deliver what was sold. Many businesses keep their CRM and connect it to the platform, so a won deal becomes a job without anyone retyping it.
Yes. Most projects start with the part that hurts most and connect to everything else. Nothing has to be replaced all at once.
Yes. We go through the spreadsheets with the people who use them, keep the columns and rules that matter, and move the data into a database with screens built for each task. Before anyone switches over, you check the moved data in a test environment, and the data can still be exported to Excel afterwards.
Moving data across is scoped with the project. We agree what moves, what gets cleaned up and what stays archived, and you check the result in a test environment before launch.
Every project includes 30 days of fixes after launch, and ongoing support from us is there if you want it.
Tell us what you are trying to fix.
A 30-minute call is enough for us to say what we would do, and what we would not.