Work
Three systems,
built end to end.
Each of these started the same way: a business running on spreadsheets, paper and WhatsApp, with nobody able to answer a simple question about what actually happened last week.
FieldMind — agriculture
Proving what happened
in the block.
The situation
An export table-grape farm has to prove what was sprayed, where, by whom, and how long before harvest. That evidence lived in notebooks, WhatsApp messages and a spreadsheet that got rebuilt from memory before every audit. The information existed. It just could not be produced on demand.
What we built
- The farm modelled properly — down to individual blocks
- A chemical register that knows withholding periods
- Spray records tied to block, operator and date at capture
- Tasks that are assigned, accepted and completed on the record
- Owner, manager and worker each seeing only their own view
- Captured on a phone, in the block, by people wearing gloves
Stack
Next.js and Supabase (Postgres with row-level security), deployed on Vercel. Mobile-first, built for patchy signal.
Status
Built and deployed. In trials with an export farm in the Hex River Valley. See the FieldMind showcase.
WildMind — game farming
Running a farm
you are never on.
The situation
The owner lives in Cape Town. The farm is in the Klein Karoo. Everything he knew about his own property arrived as a phone call, and there was no way to check any of it — no record of who was on site, what was fixed, what was found, or what the wages should be at the end of the month.
What we built
- An append-only activity ledger — entries cannot be quietly edited
- Clock-on and clock-off, with hours approved by the owner
- Payroll export that reconciles to the cent
- Incident reports with photographs, from the point of work
- Notifications routed to the person who has to act
- Self-serve signup, then invitation-only for everyone after
Stack
Next.js and Supabase on Vercel, installable to a phone home screen, with web push for notifications.
Status
Live. Running a game farm in the Klein Karoo, with staff logging from the field and the owner overseeing it from Cape Town.
Upshift — automotive
Billing that knows
what a vehicle is.
The situation
Workshops bill through generic invoicing software that has no idea what a car is. The same job gets typed three times — once as a quote, once as a job card, once as an invoice — and the vehicle history, the part that was fitted and the customer record never quite line up.
What we built
- Vehicle-first: find the car by plate or VIN, the customer fills itself
- Quote, job card and invoice as one document at three stages
- Parts stock that decrements when a linked part is invoiced
- A payments ledger with real balance-due, not just paid or unpaid
- Branded invoice documents with the workshop's own logo
- Built multi-tenant from day one
Stack
Next.js and Tailwind, with Supabase and recurring card billing through Peach Payments.
Status
Live. Workshops are running on it now, on a monthly subscription with a 14-day free trial. See the Upshift site · Tuned 2 Race case study. Pricing and sign-up.
Your turn
What would yours
have to do?
Every one of these started as a half-hour conversation about what was taking too long. Yours can too.