Building since 2009  /  Bloemfontein, ZA
I design operational systems that earn their keep — mapping how work really flows, then applying the simplest reliable fix: process, rules, or governed AI.
Systemsthatship.Systemsthatship.
Systemsthatship.Systemsthatship.
Systems·Agents·Governance·Systems·Agents·Governance·
Systems·Agents·Governance·Systems·Agents·Governance·
JacquesWainwrightJacquesWainwright
JacquesWainwrightJacquesWainwright
Scroll ↓
Start a project →
Workflow first
Observe the work before choosing technology
Hard gates
Receipts, scopes and explicit refusal paths
Local first
Private state, narrow access, portable systems
Ship proof
Working software with evidence, not demos
Fig. 01 — the operator
01 — Position

Workflow first. Technology second.

I work with owner-led businesses to find where work stalls, leaks context or depends on somebody remembering the next step. The first answer is often a clearer process, not more software.

Where technology earns its place, I build the smallest reliable system: rules-based automation, local-first applications, integrations, or AI agents operating behind explicit scopes, gates and human release.

My operating background spans manufacturing, managed IT, energy and finance workflows. That matters: useful systems begin with how the business actually runs.

Workflow architecture TypeScript / Python Agent systems / MCP Cloudflare / Local-first
02 — Capabilities

What I
actually do

One discipline: make operations legible, reliable and easier to run.
{{ s.no }}
{{ s.name }}
{{ t }}
03 — Use cases

Where systems
earn their keep

{{ k.no }}
{{ k.name }}
{{ k.body }}
{{ k.metric }}
04 — Contact

Got a workflow held together by memory, spreadsheets or copy-paste? Bring it.

jacques@jacqueswainwright.com
Elsewhere
LinkedIn GitHub
Based
Bloemfontein / Free State
Serving all of South Africa
Let'sbuildit·Let'sbuildit·
Let'sbuildit·Let'sbuildit·
© 2026 Jacques Wainwright
Systems · Agents · Governance