Skip to content
Rony
Download CV

MBS Builders Ltd

Construction Portfolio & Quote Request Website

Role
Primary Full-Stack Developer (via SETS Tech)
Dates
Apr 2026
Status
Live
  • Laravel
  • PHP
  • MySQL
  • Tailwind CSS
View live project
MBS Builders Ltd

Summary

Construction company website for MBS Builders, built with Laravel: a project portfolio, services, team and blog, and an online quote request form with photo upload. A lettings platform on the same system is in progress.

Two phases

  • Phase 1 (live): construction website with project portfolio, services, team, gallery, blog and an online quote request form.
  • Phase 2 (in progress): the company is expanding from building into selling and letting property. I'm leading the build of a lettings platform on the same system: property listings for sale and rent, applications and tenancy management, rent tracking and maintenance.

The problem

MBS Builders had no website at all. New work came by referral and phone, and every quote started with a long back-and-forth to gather the basics. The company needed a place to show completed projects, prove its certifications, and collect enough detail from an enquiry to price the job.

Before

  • No website
  • Referrals and phone calls
  • Every quote starts from scratch

After (live)

  • Completed projects and services online
  • Quote requests with the address, project details and photos
  • Every request emailed to the office, with a confirmation to the customer

Planned (in progress)

  • Property listings for sale and to rent
  • Applications, tenancies and rent on the same platform
From referrals and phone calls to a website that does the first half of every quote.

My role

Led the architecture and build via SETS Tech. I designed the architecture and data model, planned the work, built the core of the system myself and guided the in-house and freelance developers working with me. On the lettings platform I wrote the product spec with the client and designed the data model; the build is under way.

What I built

  • Owned requirements discovery, application structure and full-stack implementation.
  • Designed the project portfolio and the data structure for services and completed work.
  • Built the quote request form: contact details, site address, project details and an optional photo, collected before anyone calls back.
  • Set up the email flow: each request goes to the office, and the customer gets a confirmation.
  • Built the admin for projects, services, team, gallery, blog, testimonials and quote requests.

Architecture

One Laravel 13 application on PHP 8.3, with Blade templates and Tailwind CSS, a MySQL database and SMTP email. - Public pages for projects, services, team, gallery and blog, managed from an admin area. - The quote form validates each request, guards against spam with a honeypot and a timing check, stores it with any uploaded photo, emails the office and sends the customer a confirmation. - Phase 2 (in progress): lettings modules (properties, listings for sale and rent, applications, tenancies, a rent ledger and maintenance) are being built into the same app, on the same data model and login.

Phase 2 target architecture for MBS Builders. The top half is live; the lettings group is still being built.

  • Live: one Laravel 13 app with Blade and Tailwind CSS on PHP 8.3, serving the portfolio, services, team, gallery, blog, quote form and admin.
  • Alongside it: MySQL for content and quote requests, SMTP email for the office alert and the customer reply, and file storage for project and quote images.
  • In progress, on the same app: lettings modules for properties, listings for sale and to rent, applications, tenancies, a rent ledger and maintenance.
Phase 2 target architecture (in progress): the lettings modules join the live Laravel app, on the same data and login.

Key decisions and trade-offs

1. Structured quote intake Chose: a quote form that asks for the site address, project details and an optional photo before anyone picks up the phone. Not: a one-box contact form. Why: the team quotes faster and with fewer calls. Downside: a longer form loses some casual enquiries. 2. One platform for building and lettings (in progress) This is a design decision for the lettings platform, which is still being built. Chose: extend the existing system with properties, tenancies and rent on the same data model and login. Not: a separate lettings website or an off-the-shelf lettings SaaS. Why: one brand, one customer record, and a quote for a build can later become a property to let. Downside: one codebase carries two businesses, so clear module boundaries matter.

Results

  • 0 → 1 the company's first website
  • Structured quote requests
  • In progress lettings platform

Live at mbsbuildersltd.com. Enquiries now arrive with the detail needed to quote, and completed projects are on show. The client has come back for a much larger second phase: a lettings platform for selling and renting property, currently in development.

Key features

  • Dynamic project gallery.
  • Quote request form with site address, project details and photo upload.
  • Dedicated service pages.
  • Team, blog and testimonial content.
  • An email to the office and a confirmation to the customer for every quote request.
  • Admin for projects, services, team, gallery, blog, testimonials and quote requests.

Development timeline

  • Discovery
    Mapped the existing phone and email quotation process and the information gaps.
  • Phase 1 build
    Built the project portfolio, the quote request form and the trust content: services, team and testimonials.
  • Live
    Launched mbsbuildersltd.com, the company's first website.
  • Phase 2 — Lettings platform (in progress)
    Properties, listings for sale and rent, applications, tenancies, rent ledger and maintenance on the same system.