Body:
Hey folks,
I’m currently helping a U.S.-based client (real estate firm) decide whether to go with a fully custom Laravel-based web solution or opt for an existing SaaS platform to handle their property listings, customer interactions, and internal reporting.
They have specific requirements like:
Integrating with local MLS APIs
Role-based access for agents, clients, and admins
Custom dashboards and analytics
Potential fintech integrations for payments and escrow
I’m leaning toward custom development using Laravel + Vue or Livewire due to flexibility and long-term scalability, but they’re also considering ready-made SaaS tools (e.g. Propertybase, AppFolio) for faster time-to-market.
Questions:
Has anyone here worked on similar real estate projects using Laravel?
How do you approach explaining the value of custom software to non-technical clients when SaaS looks “cheaper” upfront?
Any Laravel packages or starter kits you'd recommend for real estate-style apps?
Would Livewire suit such a dynamic platform, or would Vue give more control?
Looking forward to your thoughts — especially if you’ve built fintech or real estate tools from scratch.
Thanks!
@faisalkazmi When looking at the off-the-shelf SaaS solutions, looks at things like extensibility.
Sure, a pre-made SaaS might get them say, 75% of the features they want off the bat, but then if it’s difficult or impossible to customise anything or argument it with your own solutions and add-ons, then you’re stuck with a product you can’t take past that 75%, and the customer is wasting their money on something that does most—but not all—of what they want.
It depends on your client’s needs, budget, and goals.
Custom Web Development Great for clients who need a unique, scalable solution. It offers full control, flexibility, and can be tailored exactly to their business—but it takes more time and money to build.
Best for: Complex platforms, long-term growth, full customization.
SaaS Solutions Ideal for quick launches and smaller budgets. SaaS tools come with built-in features, hosting, and support, but offer limited flexibility and customization.
Best for: Simple websites, small businesses, MVPs, or fast deployment.
The problem with SaaS solutions is that users often use only a small part of the functionalities.
But sur the choice also depends on the budget that the client wants to allocate to the project.
A SaaS solution is less expensive, but you will probably use only a small part of the functionalities and you can't add the functionalities you really need, so it's not really scalable.
A custom web application is more expensive, but it is also scalable, you can easily add new functionalities according to your needs.
I face this situation all the time, and in most cases it depends on the client’s budget and goals. It’s important to clearly explain that a SaaS solution is not as fully customizable as building a solution in-house, and that relying on SaaS can lead to ongoing costs through paid features and add-ons.
At the same time, clients have the right to go to market as quickly as possible and at the lowest possible cost, in order to validate their idea, achieve stability, and start seeing real benefits from the website.
For this reason, I usually recommend a hybrid approach. Build the core functionality internally, while integrating third-party services wherever possible. With AI solutions such as Claude, this process becomes much easier and quicker, especially when it comes to integrating third-party services and accelerating time to market.
After a few months, you can analyze which features are actually being used and which ones come from paid services or SaaS tools, and then gradually rebuild or customize those features specifically for the client.
Please or to participate in this conversation.