An open platform you own
Payload is open-source and widely adopted. The system we build with you stays yours to run and evolve, on a platform actively maintained by a community we contribute to, with no vendor owning the roadmap.
Engineering with AI
We ship with AI in the loop, every day. We can set your engineers up to do the same.
WAYF builds on Payload and the modern TypeScript stack, with coding agents such as Claude Code part of how we work. We configure that tooling around your codebase, train your team to direct it, and stay on as the tools change.
Payload & the open stack
We build on open source, and give back to it. Payload and the modern TypeScript stack, actively maintained.
WAYF is a recognised Payload top contributor and partner. You build on a maintained open-source core that is widely used and that you can host yourself, with a community around it we're part of.
- AI agents
- Payload
- Node.js
- TypeScript
Your patterns, as reusable skills
We encode the Payload and TypeScript patterns we use most into reusable skills your agents apply, and bring them to your codebase.
Why it pays off
Faster delivery, on your own stack. With the quality bar held where it is.
One setup for the whole team
Every engineer works from the same configured baseline, tuned to your stack and conventions, so the tooling fits how you already ship.
Speed that keeps the bar
AI-assisted work moves faster, held to the same review and quality standard as everything we ship, so speed doesn't trade against quality.
Engineers who direct agents
Your team learns to prompt, review, and direct agents on real work, the way ours does every day.
What we set up
Claude Code, set up around your codebase. Ready for real work from day one.
WAYF ships with Claude Code day to day, and this site is built the same way: engineers stay in charge and direct the agents, across code generation, testing, and review. The repository's conventions are written so that any coding agent an engineer runs, Codex and Cursor included, works from the same instructions. We can configure that setup against your codebase, your conventions, and your review process. What a full rebuild looks like in practice is written up in replacing Webflow with Claude Code.
- 01
Reusable skills for your codebase
We encode the patterns your team repeats — your Payload work: content modelling, access control, migrations, admin customisation — into reusable skills your agents apply, so routine work gets faster and more consistent.
- 02
Agents configured for your stack
We set up AI coding agents against your codebase, standards, and delivery model, with guardrails that match how your teams ship and suggestions tuned to your own conventions.
- 03
Connected to your systems
We connect agents to your internal tools and data, with the right scopes and access.
- 04
A shared developer setup
We build a reproducible developer environment with the tooling preconfigured, so every engineer starts from the same baseline.
Working with agents
Engineers who can direct agents. The skill that turns the tools into output.
A look at how you ship
We start with your codebase and how your team works, then point to the most practical place to begin.
Hands-on training
Working sessions on directing AI tools and agents against your real codebase and real tasks.
Practices that stick
We work alongside your engineers so the habits hold after we step back.
Tuning as it grows
As adoption grows and tools change, we keep the workflows and setup current with your team.
How we'd work
We scope it before we start. Then we set up, pilot, and keep it current.
Look at your stack
We look at your codebase, tooling, and how your team ships, then come back with scope, cost, and timing before anything changes.
Set up and pilot
We configure the tools and agents, prove them on a real slice of your work, then roll out wider.
Keep it current
As adoption grows and tools and models change, we keep the setup current alongside your team.
Common questions
Questions we get asked before the first call.
Book a 25-min call-
Will this work with our existing stack?
Yes. We configure the tooling around what you already use. It's strongest on Node.js, TypeScript, and Payload, where WAYF is a recognised Payload top contributor and partner, and it extends to the rest of your stack from there.
-
How would we know it's working?
You'll see it in the delivery signals your team already watches. We don't stand up a separate measurement product; what we bring is the discipline of holding AI-assisted work to the same review and quality bar as everything we ship, so speed doesn't trade against quality.
-
How does your team actually use agents?
Engineers stay in charge and direct the agents, across code generation, testing, and review, while holding the quality bar where it is. That's how we ship, and the same setup is what we'd put in front of your team.
-
What would a rollout look like?
A look at your stack and delivery process first, with scope, cost, and timing before any work starts. Then setup and a pilot on a real slice of work, and an ongoing track as adoption grows. The first conversation is a free consultation.
-
Why does the Payload angle matter?
Most of the speed-up comes from encoding the patterns your team repeats. Because WAYF builds on Payload daily, we can turn your content modelling, access control, and migration patterns into reusable skills your team's agents apply.
-
What does an engagement with WAYF include?
A scoped piece of work with a fixed quote, agreed before anything starts. That can be WAYF engineers building the software with Claude Code and the agents we direct, or setting your own engineers up to work the same way. The conventions, the agent configuration and the review process are written down as we go, so your team can audit how the work was done.
-
Who owns the repository and the agent setup afterwards?
You do. The repository, the conventions files the agents read, the skills we encode for your codebase and the pipeline sit in your accounts under your licences. Claude Code takes its instructions from plain files in the repo, so the setup does not depend on WAYF holding it. Payload underneath is a maintained open-source core you can host yourself.
-
What can our engineers do on their own after we hand over?
Direct the same agents on the same codebase without us in the room. Training runs on your own backlog, and the conventions the agents follow are files your team can read and change. We stay available for the tuning that comes with new tool and model releases, and you decide how much of that to keep.
Want your team working with AI the way we do?
Book a 25-minute call. We'll look at your stack and how you ship, and point to where the tooling would help.