Agriflow Cloud is a UK software development company. We build native iOS and Android apps, web platforms and bespoke business systems — in PHP, Java and C#, with Laravel and the frameworks that suit the job.
Twelve systems written from scratch by us across mobile, desktop and web — live platforms and working prototypes. They are the clearest illustration of what we can build for you.
A complete operational platform for smallholdings and commercial farms — fields, livestock, resources and financials in one place, on any device.
Rotations, growth stages and every intervention recorded with full history.
Individual animal records, health, movements, breeding and veterinary history.
Water, fertiliser and spraying planned against live weather data.
Costs, income and yield per hectare, ready for compliance or the bank.
A consumer location platform built on Google Find Hub, tracking people and devices with no SIM card, no subscription and no per-device fee.
Real-time position on an interactive map, with full movement history.
Arrival and departure alerts for home, school or anywhere that matters.
Notifications the moment something changes, on phone or desktop.
iOS and Android alongside the web app, sharing one account.
Employee activity monitoring and remote Windows management, running on your own server. A silent agent, a live portal, and full control of every company machine.
Every device online, idle or offline, with the current app and window title, refreshed every 30 seconds.
Clock-in, clock-out, breaks and attendance recorded without anyone filling in a form.
A daily score per person, a six-month calendar and a team leaderboard against your own target.
USB lock, remote desktop, screen lock, restart and remote wipe — even on a machine offline for weeks.
A complete sales and customer-management platform for a South African truck and heavy-equipment dealer running three yards — a web CRM and a companion Android app for company phones, sharing one live database.
Enquiries arrive from the website, phone, walk-ins, AutoTrader, Gumtree or referral, get assigned or claimed from a branch pool, and carry their whole history through to a closed deal.
Each yard sees its own customers, stock and unclaimed leads — while still being able to sell a machine standing at another branch, because that is how the business actually works.
The phone calls the same services the website does, under the same permission rules. A lead assigned at a desk reaches the rep's handset instantly; a note typed in a yard shows on the desktop as it is saved.
A call placed from the app is recorded against that customer by the number dialled, so what was agreed survives a salesperson leaving. Company handsets can be locked, wiped or retired remotely.
Email sends from the salesperson's own mailbox and copies a tagged address, so replies land back on the customer record. Stock syncs from the company's WooCommerce site without duplicates.
A device-management layer for Android handsets, built during a company-phone rollout. Every phone enrols itself the first time someone signs in, then appears on an admin screen where it can be locked, signed out, wiped or retired — without anyone touching the device.
The app is installed directly rather than through the Play Store, and the handset registers itself on first sign-in. No profiles to build, no per-device setup, no IT visit.
Four remote actions from one admin screen. A wipe clears the company data from the handset and leaves the staff member's own phone life alone; retiring a device stops it signing back in at all.
The app's own screens are blocked from screenshots and copying, so a customer list can't be photographed and taken to a competitor on someone's last day.
Periodic capture for oversight of company-owned devices, on the same principle as our Windows product: employer hardware, working hours, and a clear policy staff have been told about.
Handsets authenticate with revocable tokens over a separate channel from the web session, so a phone can only ever act as itself and its access can be cut centrally the moment it needs to be.
Job and delivery management for businesses whose work happens out in the field — cleaning, facilities, courier and delivery operations. One loop from scheduling through proof of work to an invoice that raises itself, with a live read on where people and vehicles actually are.
A weekly office clean or monthly delivery run regenerates automatically, so nobody has to remember. Staff see only the jobs assigned to them, never the whole company's workload.
Digital checklists with time-stamped before-and-after photos attached to each item, and a real client signature captured on the spot rather than a tick-box.
Each site carries its own printed QR code. Staff scan it, enter their employee number and take a photo — a verified clock-in for that site at that moment, not a generic "I'm at work" toggle.
Multiple drops are ordered by Google's route optimisation against real roads and traffic the moment a driver's day is planned — an ordered stop list, a live map, and one tap into turn-by-turn navigation.
WhatsApp or SMS at each moment that matters — job confirmed, crew on the way, delivery en route, invoice overdue. Each business connects its own account and picks the channel.
A built-in assistant answers plain-language questions about that business's jobs, invoices and attendance — and nothing else's, because every tenant is fully isolated.
A complete operations system for a portable toilet hire business running around 180 units with a small team of drivers — replacing a paper diary, a spreadsheet and a great deal of remembering.
The office allocates work to drivers and sees how the day is actually going — who is where, what has been signed off and what has not.
Drivers carry their run on a phone, take photos and signatures on site, and scan a QR label on each unit to confirm they are at the right one. It syncs when it gets back.
Every visit becomes a charge and every charge an invoice, with statements of account, credit control stages and a deliberate stop process for what is late.
Their own login shows when you are next coming, what stands on each site, their invoices and signed delivery notes — and lets them request an extra empty.
Waste transfer notes against a carrier licence, and certificates that warn before they expire rather than after.
It ships in stages so week one is learnable, with sample data staff can practise on and remove cleanly. Updates are signed packages that back up files and database first, and roll both back if anything fails.
Most church software comes from America or Britain: dollars, a January tax year, and no idea what a Section 18A receipt is. This one starts from how a South African congregation actually runs — and the church owns the system outright, on its own server, with no per-member fee.
Members, adherents, children and visitors, kept together as families on statements and in the directory. Consent flags for email and photographs, pastoral notes with a private option, and records archived rather than deleted so history survives.
A leader opens their group on a phone, taps who is present and saves. Large targets, a live count, visitors captured inline, and a head count for the people nobody knows by name yet.
Counting batches checked against what the stewards counted, so a discrepancy surfaces on Sunday rather than at year end. Multiple funds, every payment method, pledges tracked against what actually arrived, and household statements.
R 19 040,00 formatted properly throughout and on every printed document, with giving reported from 1 March to the end of February — matching SARS and the church's own accountant, not the calendar.
Four levels, so a home group leader can take a register without seeing a cent of anyone's giving. A full audit log of who changed what, in a system holding minors' details and financial records.
Including from discontinued products. Household counts, member counts and giving totals are reconciled against the old system before anyone switches, and the old one stays readable for a month afterwards.
Built originally for a non-profit congregation, given to them free, and still running. Mobile apps are scoped per project. Section 18A output should be confirmed with your accountant before you rely on it for a submission.
Customers log tickets from your website, your team works them from a private dashboard, and everything ties back to a customer record holding contacts, encrypted notes and contracted services with their margins. Built bespoke, so there is no monthly cost per technician and no vendor sitting on your client data.
The embedded form returns a reference instantly, generated randomly rather than sequentially — so no one can walk another customer's ticket or work out how much you are handling. Rate limiting, a honeypot and a timing check keep the junk out.
Customers sign in through an emailed link — nothing to reset, nothing to leak — and see every ticket their company has logged. Anyone who would rather not sign in can check status by reference and email.
Incoming tickets attach to the right company automatically by contact address or email domain. Triage, assignment, threaded conversation, and internal notes the customer never sees.
First response and resolution timestamps captured as work happens, so service reporting comes out of the system rather than out of somebody's memory at month end.
Row-level security denying access by default, with the browser never holding credentials that can read the database. Sensitive notes encrypted with AES-256-GCM using a key held outside it, so a leaked backup yields ciphertext.
Customer records carry contracted services with cost price, sell price and margin — visible to admins only, enforced in the data rather than hidden in the interface, with every sensitive read written to an audit trail.
A private finance system for a two-person household whose money does not fit a budgeting app: income in two currencies, ten-plus cards across two providers, and separate funds paying for separate things. It answers one question each morning — are we on track this month, and what needs attention?
Banks export CSVs with different columns, sign conventions and encodings. The importer detects the header, guesses each column and infers direction from the account type — then shows every row before anything is saved.
A PDF has no columns once its text is out. The parser handles a dozen date formats, wrapped descriptions and missing years — and where money in and out look identical, the running balance decides the direction.
Each card number routes its spending to a budget. Unknown cards are listed once with a suggested match, and choosing it applies to every past and future payment on that card.
Budgets answer "are we within limits?", funds answer "has enough come in?" and cards answer "what do we owe?" — three questions most apps collapse into one, and get wrong.
Every alert type — card budget levels, large payments, money in, daily and weekly summaries, failed sign-ins — chosen per person across email, in-app and phone.
Secrets encrypted at rest and kept out of the config cache. A failed email, push or bank call is logged and skipped, so a sign-in, an import or a sync always completes.
A client-facing Android app and a complete business back office for a South African practitioner taking live one-to-one readings. The constraint that shaped everything: she has no computer. So the admin side is not a cut-down mobile view — it is eighteen screens covering everything she does, with a web portal for when a laptop is borrowed.
Clients see only the times she is genuinely free, pay by card or with plan credits, and move or cancel within the rules. Availability comes from her own calendar.
Plans grant credits monthly and every grant, spend and refund is an entry. Balances are derived rather than stored, so they cannot quietly drift out of step.
The gateway reports a payment twice — once on return, once by server notification — which once credited subscribers twice. Payments are now keyed per period, so the same money can be reported any number of times and counts once.
Yearly plans remind the client 90, 60 and 30 days out, each showing next year's price. Every client's price is locked at signup, so raising the catalogue price never changes what an existing subscriber pays mid-year.
The app reports a trail of steps to the server. When the store rejected the first submission as unresponsive, that trail showed the reviewer being bounced to sign-in on every tap — they had been given a login that no longer existed. Diagnosed in minutes.
Enter hectares and a GPS point and the farm is drawn over satellite imagery, the herd converted to large stock units, and the break-even question answered honestly.
Tap surveyed corner beacons and the area is measured off your boundary, not the figure on paper.
Grazing capacity by veld type, with the herd counted class by class — cow, calf, replacement and bull.
Rotation-driven camp counts and trough placement, with coordinates you can hand to a contractor.
Herd needed to break even, margin per hectare, cost per weaner and a ten-year projection.
Working systems, shown here as portfolio pieces. Most are internal, so access is passphrase-protected — ask us for a guided walkthrough.
The portfolio above is mostly internal systems behind a login. This one is public — a live product with its own customers, which you can open right now.
A small tag in a child's bag or coat, and an app that says in plain words where it was last seen and where they have been today. Built on Google's Find Hub network, so there is no SIM and no subscription to a tracker.
Most agencies do apps or they do systems. We do both, which means your phone app and the platform behind it are built by the same people and actually fit together.
Native applications for Apple and Android, plus cross-platform builds where a shared codebase makes better sense than two.
Web applications, customer portals and APIs — responsive from the first line, because most of your users arrive on a phone.
Windows software, background services and the integration work that connects new systems to the ones you already run.
Agriflow Cloud is operated by Redplumm, a custom software company working from South Africa and the United Kingdom. This site is our portfolio — Redplumm is where the consultancy side lives.
We run our own products in production, which changes how you build — you stop shipping things you wouldn't want to support at eight o'clock on a Friday.
Before any code, we want to understand the job you're actually doing — the spreadsheet everyone works around, the process nobody enjoys. The best feature is often the one that removes work rather than adding a screen.
You see working software early and often, not a demo six months in. Every platform in our portfolio grew from a first version someone was using within weeks, then shaped by what they told us.
Host with us or on your own server, with audit trails and one-click exports. The people who built your system are the people who answer when you email support.
Some businesses need something that doesn't exist yet. We take the same engineering that runs Farm, Waypoint and Vanta and build it around your operation instead.
We sit with the people who'll use it and map how the work happens today, including the awkward bits nobody documents.
A working version of the core idea, fast — so you're reacting to something real rather than approving a document.
Iterative delivery with regular releases you can see and test. Scope stays visible, and so does progress.
Hosted by us or installed on your infrastructure, with the migration, training and documentation that goes with it.
We stay on it — fixes, improvements and new features as your business changes. Systems that stop evolving start dying.
Every project starts with a conversation and a fixed-scope proposal — no obligation.
Whether you use one of our systems, want a demo, or have a project you'd like built — we'd love to hear from you. Local contracting and local support hours in both countries.