Bespoke software & internal systems
Operations portals, branch and dealer systems, claims and case management, reporting and the integrations between them: built around your process instead of bending your process around a licence.
We build bespoke software, AI agents and data tools for companies in Johannesburg, Cape Town, Durban and Pretoria. Work is designed around POPIA obligations, deployed to the region you choose, including AWS af-south-1 in Cape Town, and architected so it keeps working through load-shedding. You get a written quote after a free scoping call, and South African Standard Time is only one to two hours ahead of UK time.
Thanks, that’s with us.
A senior engineer reads every enquiry and will reply as soon as they can.
Book a time that suits you, or send a message on WhatsApp.
1,000+
Clients served since 2020
SAST
1–2 hours ahead of UK time
af-south-1
Cape Town cloud region available
POPIA
Builds designed around its obligations
Technologies we build with
Quick answer
It works the way it does anywhere, with four South African details decided up front: where the data lives, how the build behaves when the power goes out, who the responsible party is under POPIA, and which currency the contract is written in. SpiderHunts Technologies is a UK-registered company with engineers in Lahore, working remotely with South African clients on bespoke software, AI agents, machine learning and automation. We have no office in South Africa and do not pretend otherwise.
Most of the work we are asked for is ai-ready bespoke software rather than an AI product: an operations system, portal or internal tool that a company actually runs on, with AI used inside it where it earns its place: reading documents, drafting a case summary, scoring a risk, answering staff questions from your own records. Where the job is a straight data problem instead, we build data extraction pipelines and reporting on top of them.
POPIA shapes the design and stays your organisation’s responsibility. In practice that means agreeing the lawful basis and purpose for each field you collect, minimising what is stored, building the access, correction and deletion paths a data subject can use, keeping audit logs, and recording where personal information sits and who it is shared with, so your information officer has something to show the Information Regulator. We design to support those obligations and work with your information officer; we do not sign off compliance, issue certifications or act as your legal adviser.
Infrastructure is the other local constraint. Load-shedding and an intermittent line are not edge cases in South Africa, so we treat them as a requirement: capture on the device, queue the work, sync when the connection returns, and never lose a transaction because a branch went dark mid-form. Hosting can sit in AWS af-south-1 (Cape Town), Azure South Africa North (Johannesburg) or Google Cloud africa-south1 (Johannesburg) when data should stay in the country, or anywhere else you prefer.
What we build
The work South African teams ask us for most, from bespoke systems and AI to being found when a buyer asks an AI assistant instead of Google.
Operations portals, branch and dealer systems, claims and case management, reporting and the integrations between them: built around your process instead of bending your process around a licence.
Document AI for statements, invoices, ID documents and policy files, assistants that answer from your own records, and agents that prepare a case for a person to approve rather than deciding alone.
Structuring a site so ChatGPT, Perplexity, Grok, Claude and Google’s AI results can quote it: clean HTML, schema, answer-first pages and the facts a model needs to name you as a South African supplier.
Progressive web and mobile apps that capture offline, queue every change, resolve conflicts on reconnect and tell the user honestly what has and has not synced yet.
Forecasting, credit and fraud scoring, churn, anomaly detection and demand planning trained on your own data, with the features and limits documented so a person can defend the decision.
Joining the tools you already run, payment gateways, accounting, payroll, CRM and spreadsheets, so data stops being retyped between them and exceptions surface instead of hiding.
Collecting pricing, listing, tender and market data from public sources, cleaning it and delivering it as an API, database or scheduled feed your analysts can use.
Deployment to af-south-1 or another region, infrastructure as code, CI/CD, backups that are actually restored in a test, and monitoring that pages someone before a customer notices.
Why it matters
The failures we are called in to fix here are rarely about frameworks. They are about power, connectivity, currency and where the data sits.
Building for South Africa from a spreadsheet and hope?
Tell us what the system has to survive: outages, branches, audits, growth into the rest of Africa. We will suggest a first build and a realistic range.
Examples
Typical problems South African teams bring to us, and the software that addresses them. Illustrative examples of what we build, not client results.
A service that reads bank statements, payslips and ID documents submitted by applicants, extracts the fields a credit or FICA check needs, and routes anything unclear to a consultant with the source page attached.
Aim: less manual capture, and a logged trail behind each decision
A progressive web app for store and warehouse staff that records sales, stock counts and returns while the power is out, queues them locally and reconciles with head office once connectivity returns.
Aim: trading continues through an outage instead of stopping
A tablet app for inspections, permits to work and incident reports on sites with poor coverage, with photographs compressed on the device, a queued upload and a dashboard for the safety team at head office.
Aim: records captured at the face, not rewritten at the office
A driver app and operations dashboard that track loads between Durban, Gauteng and the border posts, capture signatures and photographs offline, and push status into the customer portal when a signal is available.
Aim: fewer status phone calls and cleaner proof of delivery
Restructuring a company’s site so its services, locations and pricing logic are stated as extractable facts with schema markup, then tracking which questions in AI assistants surface it and which return a competitor.
Aim: appear in the answer when a buyer asks an AI instead of searching
An internal system that takes claims from a web form, WhatsApp or email into one queue, assigns them by rules, drafts the summary with AI for an assessor to correct, and reports on ageing and outcomes.
Aim: one queue, visible ageing and a consistent assessment record
How we work
Short stages with something you can look at each time, and the local decisions, data location, outage behaviour, currency, settled at the start rather than at handover.
A video call in your working day. We go through the workflow, the systems involved, what has to survive an outage and who the information officer is, then send a written quote.
We agree the hosting region, what personal information is collected and kept, how long it is retained, the offline and sync behaviour, and which parts a person must still approve.
We develop in fortnightly slices with a demo each time, run against your test data, and test the offline path deliberately by pulling the connection rather than assuming it works.
We release to one branch, store or depot first, watch how it behaves on real connections and devices, and fix what the pilot exposes before the rest of the business sees it.
Code in your repository, documentation, runbooks and admin access on your side. Further development or a monthly retainer is scoped and quoted separately.
Clear scope · Regular demos · Full handover
Is it right for you?
We would rather tell you to buy a local product or hire locally than take on a project that does not suit remote delivery.
Make an informed choice
An honest comparison for a South African buyer. There are things a Johannesburg or Cape Town agency can offer that we cannot, and we would rather you knew before the quote than after it.
| Factor | SpiderHunts (remote, UK company) | Local South African agency | Hiring in-house |
|---|---|---|---|
| Contract & invoice currency | UK contract in GBP or USD, ZAR equivalent shown on request | South African contract, invoiced in ZAR | ZAR payroll |
| Working-hours overlap | Calls scheduled in your working hours | Full overlap | Full overlap |
| Meeting in person | Video and WhatsApp only | On site when needed | In the office |
| Where data is hosted | Your choice, including af-south-1 in Cape Town | Usually local or af-south-1 | Your choice |
| POPIA accountability | Yours as responsible party; we build to support it | Yours as responsible party | Yours as responsible party |
| B-BBEE procurement recognition | None: we hold no B-BBEE scorecard | Available from suppliers that hold one | Counts through your own scorecard |
| Time to start | Days, once scope is agreed | Weeks, subject to their pipeline | Months of hiring |
Pricing
Prices are the same as on our service pages; nothing is marked up or down by country. We quote in GBP or USD, and can show the ZAR equivalent at the rate on the day so your finance team can approve a number they recognise.
Free
30 minutes
A call in your working day on the problem, the constraints and the data, followed by a written scope and range.
Get a quote →£8,000–£20,000
4–8 weeks
One focused system, a portal, capture app or operations tool, built, deployed and handed over.
Get a quote →£5,000–£12,000
2–4 weeks
One agent or assistant doing a defined job inside a workflow you already run, with a person approving the outcome.
Get a quote →£20,000–£45,000
2–4 months
A multi-role platform with integrations, reporting and offline behaviour designed in from the start.
Get a quote →Cloud hosting, payment gateway fees, third-party licences, bank charges and any exchange rate movement sit with you and are not included. Every build gets a written quote with scope and exclusions agreed up front.
Technology
Standard, well-supported tooling, plus the South African payment, tax and identity services a local system usually has to speak to.
Sectors
The sectors that drive most of the software demand here, and what each one usually needs first.
FAQ
What South African founders, IT managers and operations leads ask us before starting.
Still have a question?
Ask us directly. A senior engineer reads every question.
Ask about your projectNo. SpiderHunts Technologies Ltd is registered in London, our engineers work from Lahore, and every South African project is delivered remotely. We have no Johannesburg or Cape Town office, no local staff and no local partner arrangement, and we would rather say so plainly than imply a presence we do not have. What we do have is a working day that overlaps almost entirely with yours, and clients who have worked with us this way since 2020.
South African Standard Time is one hour ahead of London in British summer and two hours ahead in winter, and three hours behind our engineers in Lahore. In practice your morning is already the middle of their day, so calls, demos and questions land inside normal South African business hours. We fix a regular slot that suits your calendar rather than asking you to work late, and keep day-to-day discussion in writing on Slack, Teams or WhatsApp so nothing waits for a meeting.
Yes, and for most South African projects we assume we have to. That usually means a progressive web or mobile app that keeps its own local database, lets staff carry on capturing while the power or the line is down, queues each change with a timestamp, and syncs when connectivity returns with clear rules for conflicts. The interface tells the user what has synced and what has not, so nobody has to guess. On the server side we make operations idempotent so a retried upload cannot double-post a transaction.
We design builds to support POPIA obligations and your organisation stays the responsible party. Practically, we agree the purpose and lawful basis for each piece of personal information, keep collection to what the process needs, build the access, correction, objection and deletion paths, log who saw and changed what, set retention rules, and document where data sits and which processors touch it, so your information officer has records to work from if the Information Regulator asks. We do not issue certifications, sign off compliance or act as your legal adviser.
Wherever you decide. If personal information should stay in the country we deploy to AWS af-south-1 in Cape Town, Azure South Africa North in Johannesburg or Google Cloud africa-south1, all of which run inside South Africa. Some clients prefer London or Frankfurt for cost or for services not yet in the local region, which is a decision we make with you at architecture stage and record in writing. Backups follow the same rule as the primary database; we do not quietly restore them somewhere else.
Our contracts are UK contracts and we quote and invoice in GBP or USD. Where finance needs a rand figure to approve, we state the ZAR equivalent at the rate on the day of the quote so the budget line matches something recognisable, while the invoice total stays in the contract currency. Payment is by bank transfer. Exchange rate movement between quote and payment, and any bank or conversion charges your bank applies, sit on your side, and we say which is which in the quote rather than burying it.
Yes, and this is a real question for South African firms now that buyers ask an assistant for a shortlist before they search. Answer engines quote pages they can parse and trust, so the work is structural: state what you do, where you operate and who you serve as plain extractable facts, add schema markup, answer real questions in the page itself rather than in a brochure PDF, and keep the pages an AI crawler can actually read. We then check which questions surface you and which return a competitor. Nobody can promise a placement in an AI answer, and anyone who does is guessing.
We work in English, and English is what almost every South African business system we have built runs in. If you need isiZulu, isiXhosa, Afrikaans, Sesotho or another official language in the interface, we build the application so language is a first-class setting rather than an afterthought, with the text held separately from the code, right formatting for dates and currency, and room for longer strings in the layout. You or a translator you choose supply the wording; we do not translate it ourselves and would not want to.
We hold no B-BBEE scorecard, so spending with us earns your business no procurement recognition. For enterprise and public-sector tenders where that matters, a locally rated supplier is usually the better answer and we will say so. Companies still work with us where the requirement does not apply, where we are one part of a larger programme, or where the specialist skill is the deciding factor. The decision about how to structure that procurement is yours, and we do not claim a local partner we do not have.
Yes. The integrations we are asked for most are the local payment gateways, PayFast, Peach Payments, Ozow, Yoco and SnapScan, along with DebiCheck-authenticated debit orders, EFT reconciliation from bank statement files, and SARS eFiling and CIPC lookups where a system needs tax or company registry data. Where a bank or provider offers a documented API we build against it; where it does not, we are honest that file-based reconciliation is the realistic option rather than promising a live feed.
The same as anywhere else on our site: a single-purpose AI agent is £5,000–£12,000 over 2–4 weeks, an internal tool or MVP £8,000–£20,000 over 4–8 weeks, a business web application £20,000–£45,000 over 2–4 months, and a focused machine learning model £8,000–£25,000 from six weeks. Offline behaviour and integrations with local gateways add scope, so we price them explicitly. Cloud hosting and third-party fees are yours. You get a written quote after the free scoping call.
It changes what we decide early rather than what we build. Multiple currencies, tax rules and languages are much cheaper to design in than to retrofit, so if Namibia, Botswana, Kenya or Nigeria are on the roadmap we keep currency, tax and locale as data instead of hard-coded assumptions and keep the payment layer swappable. We will not claim experience with a regulator we have not worked under; for each new market you will need local advice on data protection and licensing.
Start here
Tell us what you need built, where the data has to live and what has to keep working when the power does not. You will get an honest view on whether remote delivery suits the project, a likely approach and a realistic range, free and with no obligation.
Thanks, that’s with us.
A senior engineer reads every enquiry and will reply as soon as they can.
Book a time that suits you, or send a message on WhatsApp.