Customer portals
Customers log in to see their orders, documents, statements and requests — instead of emailing to ask.
Custom Apps & Business Systems
Software built around your business.
When spreadsheets, disconnected tools and off-the-shelf software start getting in the way, we design and build systems around the way your business actually operates — portals, dashboards, configurators, quoting systems and internal tools, for businesses across South Africa.
You do not need a technical specification. Show us the spreadsheets, the forms, the email threads and the workarounds — that is enough to start.
Before
Quotes live in a spreadsheet
Orders arrive on WhatsApp
Job status lives in email threads
History lives in someone’s memory
After
One system
Quote → order → job → invoice in one place
Everyone sees the same status
Nothing depends on remembering
An honest starting point
Not every business needs custom software
Where an existing platform genuinely fits your process, we recommend it — that is cheaper for you and better for the work. Custom development has to earn its place.
It earns it when generic tools are being forced to run workflows they were never designed for: the same information captured twice, workarounds taped over workarounds, errors nobody can trace, and no way to see where anything stands. At that point the tools are shaping the business instead of serving it, and purpose-built software becomes the cheaper option — not the indulgent one.
What you run on today
What it becomes
- A spreadsheet only one person really understands
- Copy-paste between quotes, emails and invoices
- WhatsApp threads standing in for a job board
- Status questions answered by interrupting someone
- History that leaves when a person does
- A defined workflow with structured data
- Permissions — everyone sees exactly what they should
- Automation for the steps that repeat
- Reporting from live data, not reconstruction
- A searchable history the business owns
What we build
Eight kinds of system, one method
Different names, same discipline: understand the workflow, then build the smallest system that properly runs it.
Dealer & partner portals
Resellers and partners place orders, check stock and pricing, and pull the material they need, with the right access per partner.
Dashboards
The numbers that run the business, live in one place — instead of reconstructed in a spreadsheet every month-end.
Quotation systems
Structured capture, consistent pricing rules and a professional document out the other end, with every quote on record.
Product configurators
Guided selection for complex ranges: requirements in, valid options out, and a structured quote request at the end — scoped inside a system project, connected to the quoting and CRM workflow it feeds.
Booking & scheduling
Availability, bookings, confirmations and reminders that agree with each other — without a person retyping any of it.
Internal operations tools
Job cards, approvals, registers, stock movements — the workflows currently held together by spreadsheets and memory.
Progressive web apps
Installable, mobile-friendly applications delivered through the browser — no app-store build needed to get going.
Selected native-app work is taken on where it is genuinely justified — see the architecture section below for how that decision gets made honestly.
Connected, not isolated
CRM Accounting Payments Email WhatsApp Databases APIs Analytics Automation AI agents
Where suitable and technically available — what each platform exposes and your account types decide what is possible, so integrations are confirmed during scoping rather than assumed.
Web app, PWA or native
The least complex architecture that properly solves the problem
A browser-first web app — one codebase, no installation, working on every device your team already has — is the right default for most business systems. A progressive web app adds installability and mobile-first behaviour without separate iOS and Android builds. Native is for selected work where deeper device integration or app-store presence genuinely justifies the extra build and maintenance cost, and we say when it is not warranted.
How it runs
The smallest useful system, then evidence
Big-bang software fails quietly and expensively. This sequence exists so the first version is small enough to be right, and every extension is justified by real use.
Understand the workflow
Walk the process as it actually runs — including the workarounds and the undocumented parts. The spreadsheet usually tells the truth.
Define the smallest useful system
The version that removes the worst of the pain on day one. Everything else goes on a list, deliberately.
Prototype the experience
Screens and flows you can react to before anything expensive is built. Cheap to change here, costly to change later.
Build the core system
The data, the workflow and the permissions — built properly, with validation and predictable error handling.
Test with real workflows
Your actual cases, your actual people. The awkward ones on purpose, not just the happy path.
Launch progressively
One team or one workflow first. Widen the rollout as confidence is earned, not assumed.
Improve from evidence
What gets used, what gets avoided and what gets asked for decides what is built next.
Your system, properly yours
Built so you are never trapped
Custom software should reduce your dependency on any one person or provider — including us.
- Ownership
- Agreed in writing before development starts — never assumed afterwards.
- Documentation
- How the system works is written down, not held in a developer’s head.
- Access
- You keep appropriate access to your system and data, during the engagement and after it.
- Support
- Ongoing development can continue through Ongoing Growth & Support — or another developer, because the documentation allows it.
Scope and price
Custom Business System Project — from R35,000
Custom Apps & Business Systems is the capability — everything on this page. A Custom Business System Project is how a substantial piece of that work is scoped and bought: one written scope, one price, one accountable delivery.
Smaller tools can land below that starting point; multi-user, integration-heavy systems cost substantially more. Because a large system cannot honestly be quoted from an informal message, scoping is staged — paid discovery from R5,000 settles the scope and the price before the build is committed, and third-party costs are identified separately throughout.
The easiest way to start
Show us the messy process
Nobody arrives with a software specification, and you do not need one. The spreadsheets, the forms, the email chains and the workarounds are the specification — they show exactly what the business is already trying to do.
We map the workflow from what you show us, tell you honestly whether custom software is justified, and if it is not — we say so and point at the cheaper answer.
What to bring
- The spreadsheet that actually runs the process
- Screenshots of the forms, emails or WhatsApp threads involved
- Who does what, roughly — titles do not matter
- Where it hurts most, in your own words
Show Us the Process
A conversation first, always. No scope, no invoice, until you have a written proposal you have agreed to.
If the systems you already have just need connecting
Automation & IntegrationsIf part of the workflow needs interpretation, not just rules
AI AgentsQuestions about custom business software
Why not just use an off-the-shelf platform?
Often you should, and when a platform genuinely fits your process we recommend it — it is cheaper and faster. Custom software is for the workflows where generic tools are being bent out of shape: duplicated capture, workarounds, and a process that has quietly reorganised itself around the tool’s limitations instead of the customer.
What does a system really cost?
Projects start from R35,000, smaller tools can come in below that, and multi-user or integration-heavy systems cost substantially more. Anyone quoting a large system precisely from one conversation is guessing — which is why scoping is staged, with paid discovery from R5,000 settling the scope and price before the build is committed.
How long does it take?
The smallest useful system is the point: a focused first version is typically weeks, not months, once the scope is agreed — and it goes to work while later phases are still on the list. The honest driver of timelines is scope discipline, which is exactly what the method protects.
Who owns the system?
Ownership or licensing is agreed in writing before development starts, and client-specific work in the approved scope transfers after full payment, subject to third-party licences and reusable components. The system is documented, and you keep appropriate access to it and to your data throughout.
What happens after launch?
The system keeps improving from evidence — what gets used, what gets asked for. That can run through an Ongoing Growth & Support plan, a scoped follow-on phase, or your own team; the documentation is written so that choice stays yours.
Next step
Show us the messy process
The spreadsheet, the WhatsApp thread, the thing everyone complains about on a Friday. That is all a first conversation needs.
Not sure a custom system is justified? Start with a free Website Review — it often answers that question for free.
Or email lance@wedevelop.co.za