How to choose a Statamic agency: 10 questions to ask

Statamic’s partner directory lists freelancers and agencies, and you can filter by region and speciality. It tells you the partner has paid and met a bar, and the bar differs by tier. These were the agency terms on Statamic’s join page on 30 October 2026:

The certified tier is the stronger signal, because of the code review and references. A directory listing is a good reason to shortlist someone, not a reason to skip the questions below. We aren’t listed there today, and you should take that into account when you read the rest of this page.

1. Who will own the licence? Pro is $349 per site and is free during development. Statamic lets a licence be transferred to the client’s account, so there is no reason for it to stay with the agency.
2. How do you model content, and when? The answer should come before design: page types, fields and who edits what, mapped to collections and blueprints. Ask to see an example in a blueprint file, not a slide.
3. Which Statamic and Laravel versions will you use? Statamic 6 is the current line, and the Statamic package requires Laravel 12.40 or 13. Statamic 5’s security fixes end in December 2026, so a new build on 5 needs a very good reason.
4. What’s your plan for Statamic 7? Statamic plans it for Q1 2027, and the release policy lists it on Laravel 13–14 and PHP 8.4–8.6. A good answer says what the upgrade would involve and who pays for it.
5. How do edits on the live site reach Git? With flat-file content, this is a real design decision. Ask which approach they use, and what happens when a developer and an editor change the same entry.
6. Files or database, and why? Flat files suit most sites. Very large volumes or many users may justify the official Eloquent driver. Listen for a reason rooted in your site, rather than a habit.
7. Which addons will you use, and what do they cost? Each addon has its own price and its own upgrade path. Ask for the list, the licence costs, and what happens if one is abandoned.
8. How will you handle caching and deployment? Statamic documents two static caching strategies, and the fuller one needs web-server rewrite rules and cache warming. You should get a clear answer on when a change appears live.
9. What do we get at handover? The repository, the licence, deployment notes and enough documentation for another developer to take over. Ask who else could take the site on. Statamic is a Laravel package, which helps.
10. May we speak to someone you built for? Much agency work is under NDA, ours included, so a named reference is not always possible. They should still be able to show the code quality of something, or describe a project in useful detail.

• A price before anyone has asked about your content.
• A promise that Statamic needs no maintenance. It has a yearly major release and a security window.
• The licence, repository or hosting staying in the agency’s name with no route to you.
• Guaranteed rankings or guaranteed speed scores.

We are a full-service agency with UK clients on Laravel, the framework Statamic runs on. 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 work below is UK Laravel work, not Statamic sites. If you need a named Statamic portfolio or a directory badge, a listed partner will suit you better.

Otherwise, read about our Statamic development work, check the Statamic cost guide, and send us your brief.