Payload agencies

Directory research

How this directory is researched

Sources, evidence and publishing decisions behind the Payload agency directory.

Initial research: 30 September 2026. WAYF's project coverage updated 1 October; four agencies added 2 October 2026. Research history: 30 September–2 October 2026.

Who publishes this

WAYF, a Payload partner and Top Contributor, owns and maintains this directory. WAYF is featured first; the other agencies appear alphabetically. WAYF offers the consultation calls linked on this site. All filters apply to WAYF too.

Where the list comes from

WAYF read all 36 profiles in Payload's partner directory and all 20 case studies on payloadcms.com, then each agency's own site and public code. The directory now lists fifteen agencies: the seven in WAYF's earlier shortlist of Payload agencies, plus OMNIUX, .NFQ and Riotters, which Payload names as partners in its own case studies, and Hugsmiðjan, whose profile projects, own case studies and merged Payload code all check out. Fusionary, Hatchd, Show + Tell and UPDOT joined the list on 2 October, following checks of their partner profiles and published project work. We researched other partners and left them out where the public evidence was thinner, so the list does not cover every capable agency.

What counts as evidence

Six kinds of source, from most to least independent:

Project categories reflect delivered work across technologies. The project notes identify the stack where it is documented; the Payload work list requires a source linking the project to Payload.

Named by Payload in its own case study
Payload names the agency as the partner on a published case study. The vendor confirms the relationship, so this is the strongest check.
Listed on the agency's Payload partner profile
Projects listed under “Built with Payload” on the agency's profile. Payload hosts the profile and the agency supplies what it says.
Agency case study that names Payload
The agency's own write-up of a project, naming Payload.
Agency case study that does not name Payload
A named project that demonstrates the agency's wider delivery experience. It does not establish Payload usage without another source.
Public Payload code
Repositories the agency publishes, and fixes it has had merged into Payload core.
Statement on the agency's own site or profile
How the agency describes itself. Kept for context; no project type rests on it alone.

What the directory leaves out

There are no scores, ratings or rankings. Budgets appear only where an agency states a range on its Payload profile. Outcome figures published by agencies or by Payload are not repeated, because we could not verify them. The badges are Payload's: it chooses Featured partners on the recency and quality of their Payload work, and publishes no criteria for Top Contributor.

“Not publicly verified” means we found no public source for something. It does not mean the agency cannot do it, so ask them.

Using the list

“Best” depends on the project: look for relevant work, then discuss the details with the teams on your shortlist. You can also browse Payload's official partner directory.

Corrections

If something here is wrong or out of date, email hello@wayf.ai with a link to the source and we will recheck it.

Browse the directory