Laravel for Small Business: What to Build, What to Buy and Hosting Costs

Laravel is an open source PHP web framework for building custom applications with a developer. It can give your business a customer portal, a job tracker or an unusual booking process. It is usually the wrong purchase for a brochure website or a store that Shopify or WooCommerce already handles.

The software has an MIT license. The work of turning it into your business system still costs money. Someone must decide what happens when a customer cancels, a payment fails or an employee needs access to only one location. Laravel supplies useful building blocks; your developer supplies those rules.

Start with a stubborn problem. If your crew copies the same job details between paper, email and a spreadsheet, there may be something worth building. If your complaint is simply that your website looks dated, custom application development is an expensive way to get a fresh coat of paint.

We read the primary sources on October 29, 2026. We have not installed these products for this article. The businesses below are illustrations, and the effort ranges are our planning assumptions, not customer results or quotes.

What version are you buying into?

Laravel 13 was released on March 17, 2026. It requires PHP 8.3 or later; its release table lists PHP 8.3 through 8.5. Laravel publishes a major release annually, with bug fixes for 18 months and security fixes for two years. The official support table matters more than a developer saying a version is fairly recent.

Starting a new project on 13 gives it a longer support runway. An existing application on 12 still has a security window, but the upgrade belongs in the budget now. A supported PHP version does not extend the framework's support deadline. Additional Laravel libraries receive bug fixes only on their latest major release, so their update plans need separate attention.

Laravel has company backing from Laravel Holdings Inc. alongside its open source maintainers and contributors. Laravel's company announcement describes engineers dedicated to open source work, while its contribution guide explains community participation. The framework's MIT license permits commercial use and modification with its notice retained; it carries no warranty. Paid hosting is a separate purchase.

What the pieces do during a working day

You do not need to learn PHP to hire well. You do need to know which parts of a proposal represent existing framework features and which parts somebody must design for you.

The table links to Laravel’s documentation. Cashier for Paddle has separate documentation from Cashier for Stripe. Livewire keeps much of the interactive work in PHP; Inertia connects Laravel to React, Vue or Svelte pages.

These are choices, not a shopping list. A bakery stock form probably does not need live broadcasts. A daily report may need one scheduled task and no separate queue service. An app that does use asynchronous queues needs someone to keep its workers running and investigate failures.

A starter kit is also only a beginning. Signing in does not prove that a tenant cannot open somebody else's document. Ask for tests of those boundaries. Similarly, Cashier does not decide your cancellation policy or remove payment processing fees.

There are also third party products. Filament is a Laravel toolkit for admin panels and applications, not a finished field service system. Statamic is a Laravel based content management system. Either can shorten a suitable project, but neither turns every business requirement into a setting. Ask which work is already in the product and which work your developer must maintain.

Seven businesses that could use it

The estimates below cover a limited first release, including development and testing. They exclude major data cleanup, training, external hardware and specialist compliance work. Development uses the $93.40 hourly compensation estimate explained below. Every example also needs hosting and upkeep; the two worked comparisons show how quickly those add up.

A property manager with four staff and 120 homes

The problem might be: repair photos arrive by text, while permission to enter arrives by email. Build a tenant portal with work orders, document access and a clear approval history. On a normal morning, the coordinator opens one queue, assigns the next visit and sees which tenant still needs to reply.

Our path would be a custom Laravel app starting with authentication and a Filament staff panel. Our assumption is 140 to 260 development hours, or $13,076 to $24,284 before operations. Keep lease documents private and test access for every property. Skip the custom build if the existing property management system already offers a usable portal. Moving a few forms is rarely worth maintaining a second rent ledger.

A salon with four stylists at one location

The problem is an awkward booking rule: a color service uses a stylist, then a waiting period, then a shared finishing station. A custom booking flow could reserve the right resources and request a deposit through a payment provider. Staff would see one usable schedule instead of correcting overlapping bookings by phone.

Use an authentication starter kit and a custom scheduling app. Our assumption is 80 to 160 hours, or $7,472 to $14,944 in development. That is a narrow booking process, not a replacement for a complete salon system. Test an existing booking product first. The Square comparison below shows why ordinary appointments should usually stay with a subscription service. Check PCI DSS responsibilities with the processor before choosing any payment integration; keep card data out of your own forms and database where possible.

An HVAC company with five people

The owner wants to know which quotes need a decision and which jobs are waiting for parts. Build a quote and job tracker with photos, a parts status and a customer approval link. Each morning the office can distinguish a booked visit from a job that cannot start, without calling every technician.

Use a custom Laravel app with a Filament admin interface. Our assumption is 120 to 240 hours, or $11,208 to $22,416 for a deliberately small scope. Keep the existing accounting package. Replacing dispatch, invoicing, routing and every mobile feature of a field service product would be a much larger job. Jobber wins the subscription comparison below. A custom app needs an unusual workflow benefit to justify that gap.

A bakery with eight staff and two shops

The problem is that the second shop runs out of packaging while the first has boxes stacked upstairs. Build an internal stock and transfer tool, with reorder levels and a record of who counted what. The opening supervisor enters a count; the purchasing person sees what to order and what to move between shops.

Use a small Laravel app with Filament forms and tables. Our assumption is 40 to 100 hours, or $3,736 to $9,340 for the first version. Begin with packaging and supplies, where a count is easy to check. Recipe yields, spoilage and ingredient traceability need a separate scope. If staff will not record stock movements, new software will produce a tidier version of the same unreliable numbers.

A gym with six instructors and one studio

The problem is a membership rule that the current booking system cannot express: members have different class allowances, and missed classes sometimes become credits. Build member accounts, a class capacity list and an explicit credit ledger. At reception, staff see why a booking was accepted rather than arguing over a spreadsheet.

Use a custom app from a Laravel starter kit, with Cashier if its supported billing model fits. Our assumption is 100 to 180 hours, or $9,340 to $16,812. Put freeze, refund and cancellation rules in the contract before building. Do not quietly expand the project into a health record system. A packaged gym service is a better starting point when its membership rules fit.

A self storage facility with two staff and 180 units

The problem is repeated calls asking for balances, receipts and access information. A portal could show an authenticated tenant their units, payment history and approved access status. Staff would spend less time resending documents and more time resolving actual exceptions.

Build a narrow Laravel portal around the existing management system's supported integration. Our assumption is 160 to 320 hours, or $14,944 to $29,888, including room for integration testing. Gate hardware, vendor charges and a replacement management ledger are excluded. Never promise that a payment webhook alone can safely control a physical gate. Keep an operator override, record access changes and check the gate supplier's documented interface before quoting. Buy an integrated storage product when it already does the job.

An accounting firm with five staff

The problem is clients sending tax documents as scattered email attachments. A portal could collect an intake checklist and show which documents are still missing. On a normal day, staff would work through complete client packets instead of searching individual inboxes.

Our path is a custom Laravel app with authentication and private document storage. Our assumption is 120 to 240 hours, or $11,208 to $22,416 before a security assessment and any compliance work. Check the GLBA Safeguards Rule and FTC guidance before storing tax records or Social Security numbers. A framework choice is not a compliance claim. A specialist client portal may be the better buy even when a custom form looks simple.

Build versus buy: put the labor back in the price

The latest BLS OEWS profile for Software Developers, occupation 15-1252, reports a May 2025 median hourly wage of $65.38. The June 2026 ECEC series puts private industry wages at 70.0% of total compensation. Our developer estimate is therefore $65.38 / 0.700 = $93.40 per hour.

For server setup and administration, the shared series estimate is $68.09 per hour, from the systems administrator median of $47.66 divided by 0.700. These estimate employee compensation. An agency or freelancer bills more to cover overhead, risk and profit. Get quotes; do not hand a contractor these figures as a promised rate.

Both examples use one DigitalOcean Basic Regular Droplet with 4 GiB RAM, at $24 a month. This is our starting capacity assumption, not a Laravel minimum or a tested load result. Server setup takes 4 to 12 hours; administration takes 1 to 3 hours each month. Those are our assumptions for one server, and a serious incident can exceed them.

We assume 50 to 200 GB of retained backup copies. Backblaze B2 lists $6.95 per TB per month and the first 10 GB free. Storage is therefore (50 minus 10) × $0.00695 = $0.278 monthly at the low end, or (200 minus 10) × $0.00695 = $1.3205 at the high end. We assume restores stay within the included egress allowance and no chargeable API usage; add actual transfer charges otherwise.

Setup = development hours × $93.40 + server setup hours × $68.09. Monthly = $24 + backup storage + administration hours × $68.09 + application maintenance hours × $93.40. The 36 month total is setup + 36 × monthly. We calculate with cents and round displayed totals to whole dollars.

One salon: Square Plus against a custom booking app

Square's US Appointments page lists Square Free at $0, Plus at $49 per location per month, and Premium at $149. We compare one location on Plus, month by month, with no introductory discount. Our custom app assumptions are 80 to 160 build hours and 1 to 3 application maintenance hours monthly, in addition to server administration.

Buying wins decisively for ordinary booking. Square Premium, at $149 per location per month, lists resource management, which is the closer match for a shared finishing station; 36 x $149 = $5,364 is still far below either custom build. Square's free plan may make the comparison even stronger if it meets the business's needs. Payment fees, hardware, SMS, migration and training are excluded on both sides and must be priced separately; this compares subscription and software ownership costs, not every operating expense. The custom app is narrower than Square's full product.

Five HVAC users: Jobber Connect against a job tracker

Jobber Connect, with the team size set to two to five people and monthly billing without a commitment, costs $199 a month and includes five users. We use the regular price and exclude temporary promotions. Our custom app assumptions are 120 to 240 build hours and 2 to 4 maintenance hours monthly, plus server administration.

The Laravel estimate is for the narrow tracker described above, not a duplicate of Jobber. Payment charges, optional services, migration and training remain outside the totals. We assume no paid SaaS onboarding; confirm that in the quote. Annual or committed pricing may lower the subscription cost further, but it is a different buying decision.

When custom monthly costs are lower, break even is the setup difference divided by the monthly saving, rounded up to a whole month. Here they are higher, so waiting longer never recovers the build cost from subscription savings alone. If an unusual workflow justifies the app, measure the avoided rework or additional gross profit separately. Saved time becomes a cash saving only when it changes spending or produces useful additional capacity.

Where to host it

Laravel's deployment guide requires PHP 8.3 or newer and the Ctype, cURL, DOM, Fileinfo, Filter, Hash, Mbstring, OpenSSL, PCRE, PDO, Session, Tokenizer and XML extensions. The examples here also need a database and its PHP driver. Composer manages dependencies; the installation guide is the starting point.

Ask who provides HTTPS, SSH or a deployment tool, a supervised queue worker when the app uses queues, and the scheduler's once per minute cron entry. The web process needs write access to storage and bootstrap/cache. Point the web server at public/, keeping application configuration outside the public document root.

Apache HTTP Server and Nginx can serve Laravel. The current deployment guide shows Nginx configuration; Laravel's application template ships an Apache public/.htaccess file. Your provider must configure rewrites and PHP handling correctly. Choosing Apache does not remove the need for a worker supervisor or backups.

These prices were read October 29, 2026. They are USD before tax, except the euro billing qualification shown. Entry prices describe different services and are not comparable total application bills.

Forge's provider documentation names Laravel VPS, DigitalOcean, Akamai / Linode, Vultr, Amazon AWS outside GovCloud, Hetzner Cloud and your own server. Forge manages the server you provision; Cloud supplies a managed platform. Vapor is another choice, built around AWS Lambda with AWS charges added.

For Vultr, either let Forge provision a server or follow the documented LEMP Marketplace setup. LEMP combines Linux, Nginx, MySQL and PHP. Its existence does not make your application's access rules or backups somebody else's responsibility.

Vultr also lists a Laravel Marketplace app, but its component list showed Laravel 11.11.1 with Apache when read. Laravel 11 is outside its security window. Require an upgrade to supported components before use; do not treat that image as a current production baseline. The listing's license label also conflicts with Laravel's own MIT license, which is the source to follow.

DigitalOcean documents PHP and Laravel detection on App Platform. That can remove server chores, but workers and a suitable database still need pricing. Ploi documents Laravel support, including queues and scheduler management; its panel subscription is separate from the server.

Shared hosting deserves specific questions. Long running workers may be prohibited, SSH may be limited, and an advertised PHP version or Composer install may be too old. Hostinger documents Laravel on Web and Cloud hosting, but its installer discussion names Laravel 12. Confirm Laravel 13 and your process requirements in writing. A scheduled command is not automatically a reliable substitute for a persistent worker.

Security and upkeep belong in the purchase

Keep the framework and PHP on supported releases. The PHP support calendar gives PHP 8.3 security support through December 31, 2027, PHP 8.4 through December 31, 2028, and PHP 8.5 through December 31, 2029. A developer should choose a compatible branch with enough runway, then track both PHP and Laravel deadlines.

Set APP_DEBUG=false in production. Laravel's configuration guidance says plaintext .env files must not go into source control. Keep that file outside the public web root and protect credentials in deployment tools too. Protect APP_KEY, retain it securely for recovery, and have the developer follow the key rotation guidance. Generating a new key casually can make existing encrypted data unreadable.

This is a real maintenance issue. The CISA and FBI advisory of January 16, 2024 describes Androxgh0st malware targeting exposed Laravel .env files and credentials. An old debugging package also caused trouble: Ignition's maintainer patch addresses the remote code execution issue known as CVE-2021-3129. That historical issue does not mean every current Laravel app has the flaw. It does show why debug tools and dependency updates deserve attention.

Back up the database, uploaded files and the protected information needed to restore them. Keep a copy separate from the application server and rehearse a restore. A backup notification proves that a job ran; opening the restored customer record proves something more useful.

Budget for Composer dependency review, security updates and major version upgrades. Test changes before production and restart long running workers after deployment as required. Give failed jobs and application errors an owner. Add an independent availability check: a dashboard inside a broken app may be unreachable when you need it.

Hiring someone without losing control of the business

Ask for a short discovery phase and a written first release scope. Bring real blank forms and describe a difficult day: two people editing the same job, a canceled booking after a deposit, a failed upload. A developer who can explain how those cases work is more useful than a proposal full of package names.

The business should own its repository and hosting accounts. Give the developer their own access, with an agreed removal process. Put ownership of custom code, rights to third party components and the handover obligation in the contract. Paying an invoice should not leave your only copy of the source code on somebody else's laptop.

Require tests for permission boundaries and business rules, a separate test environment and a demonstrated restore. Agree who handles security notices, how quickly they respond, and what ongoing maintenance buys. Ask who takes over when the developer is on vacation or leaves.

Warning signs include a promise of no maintenance, production debugging left on, a quote that omits data migration, and an account held only in the freelancer's name. Another is a demonstration that shows only the happy path. Ask them to cancel a booking, deny access to another customer's file and recover a failed background task.

Your acceptance checklist should describe outcomes staff can verify. A tenant sees only their documents. A deposit is recorded once even if the provider sends its notification twice. A stock adjustment records who made it. Those sentences are more useful than accepting a project because it uses Laravel.

Download the planning kit

The Laravel Small Business Kit includes the hosting table, both cost examples, a blank worksheet, production checks and a developer handover checklist. Give it to whoever is quoting the work and ask them to fill the blanks.

The habit behind The $97 Launch applies here too: define the useful first job before spending on the machinery around it. A Laravel project should earn its extra cost by doing something your business actually needs.

Related reading

1. Apache web servers and API gateways for small business, including the server underneath a PHP application.
2. The Apache open source project guide, for other tools your developer or provider may propose.
3. A small development server behind Cloudflare email login, for a private staging copy of your Laravel app on a Kimsufi box or a small VPS.
4. n8n for small business automation, when connecting existing applications may solve the problem.
5. WordPress and WooCommerce audit guide, for a store that can stay on an established platform.
6. Serverless hosting cost comparison, for another look at usage billing.

Fact-check notes and sources

Prices and technical facts were checked October 29, 2026. Observation times are UTC. The cost assumptions are estimates, not installation results.

1. official support table. Read October 29, 2026, 21:47 UTC.
2. Laravel Holdings Inc.. Read October 29, 2026, 21:47 UTC.
3. company announcement. Read October 29, 2026, 21:48 UTC.
4. contribution guide. Read October 29, 2026, 21:47 UTC.
5. MIT license. Read October 29, 2026, 21:47 UTC.
6. Routing. Read October 29, 2026, 21:47 UTC.
7. Eloquent. Read October 29, 2026, 21:46 UTC.
8. Blade. Read October 29, 2026, 21:47 UTC.
9. Queues. Read October 29, 2026, 21:47 UTC.
10. Scheduler. Read October 29, 2026, 21:47 UTC.
11. Authentication starter kits. Read October 29, 2026, 21:46 UTC.
12. Livewire and Inertia. Read October 29, 2026, 21:46 UTC.
13. Cashier. Read October 29, 2026, 21:46 UTC.
14. Scout. Read October 29, 2026, 21:46 UTC.
15. Reverb. Read October 29, 2026, 21:46 UTC.
16. Horizon. Read October 29, 2026, 21:46 UTC.
17. Pulse. Read October 29, 2026, 21:46 UTC.
18. Cashier for Paddle. Read October 29, 2026, 21:46 UTC.
19. Filament. Read October 29, 2026, 21:47 UTC.
20. Statamic. Read October 29, 2026, 21:47 UTC.
21. PCI DSS responsibilities. Read October 29, 2026, 21:57 UTC.
22. FTC guidance. Read October 29, 2026, 22:05 UTC in a regular browser; it lists tax preparation firms among the financial institutions the rule covers.
23. BLS OEWS profile for Software Developers, occupation 15-1252. Read October 29, 2026, 21:46 UTC.
24. ECEC series. Read October 29, 2026, 21:47 UTC.
25. systems administrator median. Read October 29, 2026, 21:12 UTC.
26. DigitalOcean Basic Regular Droplet with 4 GiB RAM. Read October 29, 2026, 21:46 UTC.
27. Backblaze B2. Read October 29, 2026, 21:10 UTC.
28. Square's US Appointments page. Read October 29, 2026, 21:47 UTC.
29. Jobber Connect. Browser review received October 29, 2026, 21:53 UTC.
30. deployment guide. Read October 29, 2026, 21:46 UTC.
31. installation guide. Read October 29, 2026, 21:48 UTC.
32. public/.htaccess file. Read October 29, 2026, 21:47 UTC.
33. Laravel Cloud Starter. Read October 29, 2026, 21:46 UTC.
34. Laravel Forge Hobby. Read October 29, 2026, 21:46 UTC.
35. Laravel Vapor Unlimited Monthly. Read October 29, 2026, 21:46 UTC.
36. Vultr Cloud Compute Regular, 4 GB. Browser review received October 29, 2026, 21:53 UTC.
37. DigitalOcean App Platform Shared Fixed, 512 MiB. Read October 29, 2026, 21:46 UTC.
38. Akamai Cloud Linode 4GB. Read October 29, 2026, 21:46 UTC.
39. Hetzner CX23, Germany/Finland. Read October 29, 2026, 21:47 UTC.
40. Product page. Read October 29, 2026, 21:50 UTC.
41. Ploi Basic. Read October 29, 2026, 21:46 UTC.
42. Hostinger Premium web hosting. Read October 29, 2026, 21:46 UTC.
43. Forge's provider documentation. Read October 29, 2026, 21:46 UTC.
44. LEMP Marketplace setup. Read October 29, 2026, 21:47 UTC.
45. Laravel Marketplace app. Browser review received October 29, 2026, 21:53 UTC.
46. PHP and Laravel detection on App Platform. Read October 29, 2026, 21:46 UTC.
47. Ploi documents Laravel support. Read October 29, 2026, 21:47 UTC.
48. Hostinger documents Laravel on Web and Cloud hosting. Read October 29, 2026, 21:46 UTC.
49. PHP support calendar. Read October 29, 2026, 21:47 UTC.
50. configuration guidance. Read October 29, 2026, 21:47 UTC.
51. key rotation guidance. Read October 29, 2026, 21:47 UTC.
52. CISA and FBI advisory of January 16, 2024. Read October 29, 2026, 21:47 UTC.
53. Ignition's maintainer patch. Read October 29, 2026, 21:47 UTC.

This post is informational, not legal or financial advice. Product names identify the products discussed. No affiliation or endorsement is implied.