Statamic 6 on Laravel
New Statamic sites, moves from WordPress, and Statamic added to an existing Laravel application. We have UK clients on Laravel, the framework Statamic is built on, and we invoice in pounds.
We are not based in the UK, and it is better you hear that now. This is what we do to make it work.
We are an engineering team in India with 3–5 hours of overlap with the UK and Europe; US calls by appointment. Overlaps with UK and European mornings; US calls by appointment.
Work is invoiced in USD, GBP, EUR or INR, so a UK finance team does not have to handle a foreign-currency invoice. Prices on this site are in USD.
Statamic is self-hosted, so the site and its data sit wherever you decide, including on a UK server. There is no CMS vendor's cloud in the middle.
Our UK engagements include a telecom billing platform for resellers and MSPs, and a garage-booking SaaS built around MOT, registration and VAT invoicing. Both run on Laravel.
Statamic stores content as files by default and runs on Laravel, which makes it a good fit for sites that have outgrown a stack of WordPress plugins.
A site your marketing team can edit with blueprints built around their content, using Statamic's Antlers templates, or Blade if your developers prefer it.
Content and media moved, every old URL mapped to a redirect, and SEO checked before the switch. Worth doing when plugin upkeep has become the main cost of the site.
Statamic is a Laravel package and installs into an existing application, so your product and its marketing pages can share one codebase and one set of views.
Statamic Pro includes REST and GraphQL APIs, which can feed a Next.js site or an app while editors keep using the Control Panel.
Flat files suit most sites and work well with Git. When content or user volume calls for it, the official Eloquent driver moves it to a database, and can export it back.
Custom addons for what the marketplace does not cover, and version upgrades. Statamic 6 needs PHP 8.3 and Laravel 12 or later, so an old site may need Laravel moved as well.
The licence is a small part of the budget, but people ask, and older articles quote out-of-date figures.
One administrator, one content form, and unlimited collections and taxonomies. Fine for a site with a single editor.
Includes one year of updates, then $99 a year. Adds unlimited users and roles, revisions, REST and GraphQL, multi-site and Git integration. Free during development.
Statamic's own prices in USD, from statamic.com/pricing, October 2026. Paid to Statamic, separately from our work.
Most Statamic projects are fixed-scope. The content model comes first, because it decides how pleasant the site is to edit for years afterwards.
We map your page types, fields and who edits what into collections and blueprints, before any design work. Mistakes here are the costly ones to fix later.
Templates are built against your actual copy on a staging site, with weekly demos on most projects, so your editors can try the Control Panel early.
On a migration, we import content, list every old URL, write the redirects and compare the two sites before going live.
Deployment, licence transfer to your account, and documentation for your team. Ongoing updates can continue with us if you want them.
These are not Statamic sites. They are UK engagements on the framework Statamic runs on, one of them two and a half years long and still going.
UK telecom billing and revenue-assurance platform for resellers and MSPs: CDR rating, locked bill runs, Stripe card and Direct Debit collection, full receivables and ledger, Xero/QuickBooks/Sage sync, supplier-invoice reconciliation. Laravel + Next.js, two and a half years and ongoing.
UK garage-booking SaaS: car owners book, pay, receive invoices and reminders from their phone; garages manage services and slots. Laravel API, Next.js web app, React Native iOS/Android apps. About one year.
Licences, budgets, and working with a team outside the UK.
According to Statamic's pricing page, Core is free, with one admin account and one content form. Pro is $349 per site including a year of updates, then $99 a year for updates, and it is free to use during development. Pro adds unlimited users and roles, revisions, multi-site, REST and GraphQL APIs and Git integration.
Probably, if more than one person edits the site. Core suits a site with a single administrator, and Pro is needed once you want several users with their own permissions, content revisions or more than one site.
We quote a fixed price after seeing your content model and designs, and we do not publish a price band. A migration depends mostly on how many content types and custom plugins the old site has, so an export and a list of plugins is a good place to start.
No. Our team is in Kerala, India, working with UK clients remotely. Mon–Fri 09:00–18:00 IST; meetings outside hours by prior booking.
We have no public Statamic case study on this site. Most of our work is delivered under NDA, so many projects cannot be named. The projects shown here are our UK Laravel work, because Statamic is a Laravel package and the same engineers and practices apply.
Yes. Statamic documents installing into an existing Laravel application with Composer, and content is stored as flat files by default. Statamic's docs note that a fresh project is simpler, because some setup that is otherwise automatic has to be done by hand. Statamic 6 needs Laravel 12 or later.
Tell us what the site does now, who edits it and which plugins it depends on. We will come back with an approach and a way to price it.
We reply within one business day (IST).