Laravel

Laravel development, from a UK team you can ring

We build business applications on Laravel: customer portals, job management platforms, booking engines and internal systems. UK based, fixed price agreed before the work starts, and the same engineers host and support what they build rather than handing it over and disappearing.

  • UK team, named people
  • Fixed price up front
  • We host what we build

Why we build on Laravel

Laravel is a mature PHP framework with a large ecosystem, a long release cadence and a very deep pool of developers, which matters more than any technical argument. The most important property of a business application is not how elegant it was on the day it shipped. It is whether somebody else can pick it up in four years.

A system written on an unfashionable stack, or on whichever framework was interesting the year it was built, becomes progressively harder and more expensive to change. Laravel is boring in the way infrastructure should be boring: widely used, well documented, and unlikely to leave you stranded.

It is also genuinely productive. Authentication, permissions, queues, scheduled jobs, database migrations and testing are solved problems in it, which means the budget goes on the part of the system that is specific to your business rather than on rebuilding the plumbing.

The wider process, from scoping to a fixed quote, is on our page about custom software development.

What we build with it

  • Customer portals

    Logged-in areas where clients see their own jobs, documents and invoices. Real authentication, real permissions, and access removed properly when somebody leaves.

  • Job and workflow systems

    Platforms that move work through stages, hold the documents attached to it and tell people what needs doing next. TradeyHub is one of these and we still run it.

  • Booking and scheduling engines

    Availability generated from real working patterns, with resources, travel time and rules that reflect the business rather than a generic calendar.

  • Integrations and internal tools

    Services that sit between the systems you already run, with queues and scheduled jobs doing the work quietly rather than a person doing it every afternoon.

Two developers working through a problem at a desk

What a UK team changes about the arrangement

A great deal of Laravel work is quoted by offshore agencies at rates a UK team cannot match, and for some projects that is a perfectly reasonable choice. Where it tends to go wrong is on business applications that need a lot of back-and-forth about how the business actually works, and on anything that needs supporting years later.

What we offer instead is a named team in the same time zone, a fixed price agreed before the work starts, and the same engineers hosting and supporting the application afterwards. You can ring us and get somebody who knows your system.

  • Fixed price agreed up front, not time and materials
  • The people who build it are the people who support it
  • Code and data are yours, with no lock-in

The rest of the stack, honestly

Laravel is what we reach for on the server. On the front end that is usually server-rendered HTML with just enough JavaScript to make the interface pleasant, because a business application that renders on the server is faster to build, faster to load and considerably easier to maintain than one that ships a framework to the browser to do the same job.

Where a genuinely interactive interface is warranted we build one, and we will say why. What we try to avoid is choosing an architecture because it is current rather than because the application needs it, since the person paying for that decision is the client who has to fund the rewrite.

Inherited a Laravel application?

Taking over an existing codebase is normal work. We start with an audit: what version it is on, how far behind the dependencies are, whether there are tests, and what the deployment and backup situation actually is.

You get that in writing before committing to anything, including an honest view on whether it is worth continuing with.

Ask about a code audit

Get in touch

Talk to us about laravel development

A few lines is enough. We will tell you straight whether we can help, what it would cost and how quickly we can be there. No hard sell, and no follow-up sequence if you decide against it.

  • We reply within one working day
  • A straight answer, including when it is no
  • Free process review available, before any money changes hands

Would rather just ring? 01623 354250, Mon–Fri, 9am–5:30pm.

We reply within one working day. Your details are used to answer your enquiry and nothing else, see our privacy policy.

Frequently asked questions

If the answer is not here, ask us. You will get a straight one, from someone who does the work.

Mon–Fri, 9am–5:30pm

How much does a Laravel project cost?

A focused first version of a business application typically runs from the low thousands to the low tens of thousands depending on scope and what it has to connect to. We quote a fixed price before work starts rather than working on time and materials, so the number does not move underneath you.

Do you work with our existing developers?

Yes. Working alongside an in-house developer or another agency is common, whether that means taking a defined piece of work or covering the areas they do not handle.

Who owns the code?

You do, in full, along with the data. It is handed over in a repository you control, and you are free to take it to another team whenever you want without asking us.

Will you host and support it afterwards?

Yes, and most clients take that. The same engineers who built the application run it, which means an issue does not begin with somebody reading the code for the first time. Hosting elsewhere is entirely workable too, and we will hand over what another team needs.

Do you do staff augmentation or day rates?

Our normal arrangement is a scoped project at a fixed price, because that is where we do our best work and where the risk sits with us rather than with you. For longer engagements we will discuss what suits the project.

What version of Laravel do you build on?

The current stable release, and we keep applications we host on a supported version rather than letting them drift. An application three major versions behind is a security problem and an expensive upgrade waiting to happen.

Talk to us about IT support or a project

Tell us what is going on and we will tell you straight whether we can help, what it would cost, and how quickly we can be there. No hard sell.

Monday to Friday, 9am to 5:30pm