Custom backend systems
Go, Node, Postgres, Supabase, workers, queues, scheduled jobs, audit trails, admin APIs, and the boring infrastructure that makes a business process reliable.
Crispin Digital / Adelaide, South Australia
Crispin Digital builds the systems behind serious operational work.
Backend platforms, API integrations, AI-assisted workflows, and human learning systems — for businesses where the real process is more complicated than the software around it.
SYS/00 — Signal map34.93°S 138.60°E
Built for the places where spreadsheets, portals, and manual workarounds stop scaling.
SYS/01 — Input layer
The work usually starts in the mess
Most useful systems do not begin with a clean product brief. They begin with broken exports, half-mapped workflows, supplier portals, old databases, manual approvals, edge cases, and people who know the real process but have never seen it represented properly in software.
I work in that gap — and I've run businesses from inside it.
SYS/01 — Input layer
SYS/02 — Build surface
What I build
Procurement and marketplace infrastructure
Supplier data, catalogue flows, pricing rules, order handling, invoice workflows, seller operations, approval systems, and procurement logic for real-world purchasing.
Manufacturing and logistics workflows
Systems for products, movement, inventory, fulfilment, operational visibility, and the handoff points where errors usually hide.
API and integration work
Connecting platforms that were never designed to work together. Mapping data, normalising flows, handling edge cases, and building the middleware that keeps operations moving.
AI-assisted operations
Practical AI for structured work: data cleanup, review workflows, decision support, prompt systems, internal copilots, and human-in-the-loop process automation. AI where it helps, review where it matters.
Human learning systems
Software for coaching, training, observation, journals, and progression — training memory for coaches and the students they develop.
SYS/03 — Operating layer
I build the layer between business reality and software reality.
The valuable work is often not the app screen. It is the translation layer underneath: what the business actually does, what the data actually means, what the system needs to remember, what should be automated, what should stay human, and where the process needs proof, permission, or review.
L1Real-world operations[OK]
what the business actually does
L2Data and process mapping[OK]
what the data actually means
L3APIs and backend services[OK]
what the system needs to remember
L4AI-assisted workflow[OK]
what should be automated, what should stay human
L5Human decision and review[OK]
where the process needs proof, permission, or review
The skill is not writing code. It is deciding where things belong.
SYS/04 — Method
Not a generic agency.
Not a template shop.
Not another dashboard.
Crispin Digital is for specific, difficult, operationally messy work where the software needs to match the business — not the other way around.
From the floor to a fully operational system.
> embed with the team
Start on the ground
The work starts inside the team, not in a requirements document. I sit where the work happens — the orders, the exceptions, the workarounds — until the real process is visible, including the parts nobody thought to mention.
> map the real process
Make the process visible
The undocumented rules, handoffs, and edge cases get written down and agreed. Most teams see their own process properly represented for the first time here.
> model the data and ownership
Decide where truth lives
Data model, boundaries, and ownership: which system owns which truth, what must be remembered, and what needs proof, permission, or review.
> build the system spine
Build the spine
Backend services, API contracts, integrations, workers, audit trails — the infrastructure that makes the process reliable rather than heroic.
> automate with review
Automate the repeatable, keep the judgement
AI and automation where they carry real load, with human review, provenance, and accountability preserved where they matter.
> ship the operational layer
Hand over a running system
Not a prototype and not a report — a fully operational system the team runs day to day, with the knowledge transferred to keep it theirs.
SYS/05 — Fit
A good fit looks like this.
The workflow lives in spreadsheets
The real process is known by the team but has never been properly represented in software.
The platforms don't talk cleanly
API, marketplace, supplier portal, ecommerce, procurement, and inventory integrations that were never designed to meet.
The data has no clear owner
Catalogue, pricing, order, invoice, and supplier data that needs rules, validation, and a single source of truth.
AI needs review, not magic
AI-assisted workflows where judgement, auditability, and approval still matter.
The system has to survive real use
Internal tools, admin systems, workers, and backend services that need to be reliable rather than flashy.
NOT A FIT — generic brochure sites, low-context app ideas, or projects where nobody owns the operational truth.
SYS/06 — Provenance
I've been the user of every system I build.
Before building systems for other businesses, I ran my own. The first operation on this timeline was mine end to end — manufacturing, wholesale, retail floors, ecommerce, logistics — with raw materials and production equipment procured overseas. I've built ISO-rated clean rooms and commissioned fully automated production lines. I know what it costs when the system doesn't match the floor.
And I still coach. I run a jiu-jitsu gym — coaches, students, progressions, every week. There's no better study in how people actually operate: how they learn, how they perform under pressure, how individuals and teams move through real work.
That's not a side note. Systems fail when they're built around how the software works instead of how the people work. Match the system to the team, the task, and the way skills actually develop, and it gets used. Miss that, and it's shelfware.
The systems are the strategy. How a business moves data, stock, and decisions tells you what it is — and what it should do next. Good systems absorb that complexity so the people using them never carry it.
SYS/06 — Provenance
own operations → the systems to run them → client platforms · committed through 2027
SYS/07 — Contact
Work is by appointment and referral.
Crispin Digital works with a small number of medium- to long-term clients on a contract basis — where the problem is real, the work is operationally serious, and the system needs to be built properly. Current commitments run to the end of 2027.
STATUS ▸ committed through 2027 · referral required
By appointment only. Referral required.