Your business needs custom software when the way you work is the thing that makes you money, and off-the-shelf tools keep forcing workarounds: double data entry, spreadsheets holding the real records, permissions the tool cannot express, or integrations held together by hand. If a well-chosen product fits your process, buy it. Building makes you responsible for maintaining it.
I have worked in IT and development since 1998. The facts about Laravel, hosting and POPIA come from the published sources, read on 12 October 2026.
When is off-the-shelf software enough?
Most of the time. Start with a product when:
- Your process is the same as most businesses’ process: invoicing, payroll, email, a standard CRM pipeline.
- The product’s limits are ones you can live with, and you know what they are before you sign.
- Someone else carrying the upgrades, security fixes and hosting is worth more to you than control.
An existing product spares you commissioning the core software yourself. Whether it is cheaper overall depends on its fees, its integrations and the manual work it leaves behind. With custom software, you must budget for applying and testing updates to your application, even when the framework and dependency updates themselves are free.
What are the signs you need custom software?
Check where your current tools create repeat work or cannot enforce your business rules:
- Your staff re-enter the same data in two or three systems, and mistakes come from the copying.
- The real records live in a spreadsheet because the tool cannot hold the shape of your data.
- Your permissions outgrew “admin and editor”: you need approvals, roles per branch or client, and an audit trail.
- Several systems need one source of truth: a website, a mobile app and a back office that all read and write the same data through one API.
- Each workaround needs another workaround, and every update of the tool risks breaking the chain.
- The process is the product: what your customers pay for is the way you do the work, and no vendor sells that.
When several of these are true at once, the workarounds are already costing you in time, errors and delays that never appear on an invoice.
Before you replace a system, check whether configuration, an existing connector or a small custom integration removes the problem. Keep the products that already work, and commission a larger application only when the remaining requirements justify owning it.
What did we decide on our own website?
Two recent decisions on rizonetech.com went in opposite directions, and the reasons are the test this guide recommends. Neither was a Laravel build: one is WordPress code, the other a hosted product.
We replaced a plugin with our own code. Until 26 September 2026 the site’s three forms ran on WPForms and its Signatures add-on. We replaced them with the site’s own forms code: entries stored privately in WordPress, spam checks plus Cloudflare Turnstile, and a Microsoft 365 agreement signed with a drawn signature, a typed name and a tick, sent as a PDF with the agreement’s version. We chose to own that code and accepted responsibility for maintaining it. A form builder can do much of this, so these features alone do not mean another business needs its own form system. On 12 October 2026 the intake form also began recording which version of our terms each client accepted.
We dropped a plan to build and bought instead. We had a 28-section plan for our own booking plugin. On 11 October 2026 we retired it unbuilt and chose Calendly, because a separate booking plugin would have been more to build, secure and maintain than the job was worth. We accepted real limits for that. Calendly’s webhooks and Scheduling API need a paid plan, and its payments run through Stripe or PayPal, not PayFast or Yoco, so our meetings are free for now.
What the two decisions share is the question we asked: is this part of how we work, or a solved problem a product handles well?
Where does Laravel fit?
Laravel is a PHP framework for applications with structured data and business rules. It gives a project routing, queues, scheduled tasks, database migrations, testing tools and API support, so the code follows conventions the next developer recognises. It suits:
- Customer portals with secure login and roles.
- Internal dashboards for operations, stock, service tickets or reporting.
- Tools that replace fragile spreadsheets with a proper database.
- Payment, CRM, accounting or email-platform integrations.
- API layers that connect a website, a mobile app and a back office.
It also works beside WordPress: WordPress runs the public marketing site, and Laravel runs the private portal or workflow behind it.
What do you take on when you build?
You take on the upgrades. Laravel’s support policy is a major release every year, around the first quarter, with “bug fixes … for 18 months and security fixes … for 2 years”. Laravel 13 came out on 17 March 2026 and needs PHP 8.3 or later. Laravel 12 stopped getting bug fixes on 13 August 2026, and its security fixes end on 24 February 2027. There is no long-term support edition to sit on.
So plan upgrades before your version leaves security support. Review the framework, the PHP version and the dependencies together, and allow time to test the update. A quote for custom software should include that maintenance, not leave it for later.
Where does it run, and where does your data live?
Check which deployment platforms accept new projects and support the region you need, then decide. As read on 12 October 2026:
- Laravel Vapor, which runs on AWS, “is no longer accepting new signups”.
- Laravel Cloud, Laravel’s managed platform, runs on AWS in regions across the US, Canada, Europe and Asia Pacific. None is in Africa.
- Laravel Forge manages servers you rent. It connects directly to providers such as AWS, DigitalOcean and Hetzner, and can manage a compatible Ubuntu server from another provider, Azure included, through its custom VPS option.
In-country hosting is possible when you build on a South African region directly: Azure’s South Africa North in Johannesburg (its Cape Town region is restricted to specific scenarios such as disaster recovery), or AWS’s Africa (Cape Town) region, which you must switch on first. Do not assume that a platform running on those clouds offers a South African region.
If personal information leaves South Africa, the transfer needs a valid basis under POPIA section 72, for example a recipient bound by law, binding corporate rules or an agreement giving an adequate level of protection, or the data subject’s consent. Check the destination, the safeguards and the specific transfer with your privacy or legal adviser before you build.
Does your application need multi-tenancy?
If one application serves many clients, branches or franchises, you must decide how each tenant’s data is kept apart: a shared database with a tenant identifier on every row, or a database per tenant. Microsoft’s guidance on tenancy models treats isolation as “a spectrum”. With a shared database, “you typically rely on your application code and a tenant identifier” to keep data apart.
A database per tenant isolates each tenant’s data and can make some per-tenant tasks simpler, but it can increase hosting and operational costs, and provisioning and updating the databases should be automated. Either way, isolation still depends on how the application controls access, the credentials it uses, the infrastructure, and backups you have actually tested, and Microsoft says to test that “one tenant’s data isn’t accidentally leaked to another”.
Decide it from your requirements, early, because changing it later is expensive. Our Custom Laravel and multi-tenant SaaS whitepaper covers the choice in depth.
What does custom software cost?
It depends on the scope, so a useful budget separates discovery, build, integrations, testing and ongoing maintenance, and says which assumptions could change each part. Our guide to budgeting for custom software walks through it.
How do you start without betting the business?
Start with the smallest useful version: the one workflow that removes the most friction, built properly.
- Map who uses the system, what each role can do and which steps need an audit trail.
- List the systems it must connect to, and check their APIs and limits early.
- Clean your existing data before you import it.
- Write acceptance checks in plain language, so your staff can test the process and not only the code.
- Plan hosting, backups, monitoring and upgrades before launch.
- Decide what stays in WordPress, Microsoft 365 or an existing product.
Ask for the scope and its assumptions in writing. Ours say what is included, what is not and the access we need, and you approve them in writing before any work starts.
What should you ask a developer before you start?
- What process are we improving or replacing, and what does it cost us today?
- Could a product do this instead, and why not?
- Who are the user roles, and what can each one do?
- Which systems must it connect to, and what happens when one is down?
- How will it be hosted, backed up, monitored and kept on a supported version?
- What is the smallest useful first release?
FAQ
Is Laravel better than WordPress?
For different jobs. WordPress is usually better for content your team edits. Laravel is usually better for custom workflows, permissions, data and integrations. Many businesses use both.
How long is a Laravel version supported?
Each major version gets 18 months of bug fixes and two years of security fixes, and a new major version comes out every year. Laravel 13, released on 17 March 2026, gets security fixes until 17 March 2028.
Can a Laravel application keep its data in South Africa?
Yes, but the application server is only part of it. Check where the database, files, backups and logs are kept, and which other services receive personal information. The infrastructure can sit in a South African region, such as Azure’s South Africa North or AWS’s Africa (Cape Town). Laravel Cloud has no African region as of 12 October 2026, so check the region of any managed platform before you choose it.
What maintenance should you agree before launch?
Agree which updates, fixes and monitoring are included, and whether improvements are quoted separately. Agree who applies security updates, and how quickly.
What should you do next?
See where your systems stand with the free IT health check. If your business has outgrown its spreadsheets and plugins, see how Rizonetech builds custom software. For the public website side, read the WordPress cost guide or see WordPress development, and for the cloud side, our Azure migration guide.
Published 16 June 2026. Last updated 12 October 2026.