We build websites and platforms your team can run for years.
Fixed price, a deadline we agree up front, and a platform that stays yours.
Your marketing and content team gets a platform they can publish on without waiting on engineers. We agree the price and the deadline before any work starts. The same senior people who scope the project build it, and stay close after launch.
What we build, and what we move you off,designed around how your team actually works.
Most projects are some mix of three things. You can hire us for any of them on the same terms.
A platform your team can run
A website or publishing platform your marketing, comms, or events team can run themselves. They create pages, reuse ready-made building blocks, and publish without filing a ticket with engineering. This is what we mean by a content platform: built on a modern headless CMS, most often Payload, where we are a recognised top partner and contributor. We design it around the way your team already works, and we agree how it should behave before we build it. Run several brands, regions, or languages from one place and it handles that, multi-tenant and multi-locale from day one.
Moving off an old system
We move you off an ageing content system and onto a modern one, usually Payload or a similar modern stack, without losing what already works. We map what is worth keeping, what is worth replacing, and what is best left alone, and we write that down before any work starts. We have moved teams off a range of legacy and proprietary systems, and the build itself usually runs four to eight weeks once the scope is signed off. Ask us and we will tell you what a move off yours would involve.
Built to adapt, and to last
Every business has something non-standard about it, so we build on a code and data architecture that scales and we keep your options open. For Ingersoll Rand, that meant building the site so the system underneath can be swapped later without rebuilding everything on top of it. We build on open, widely-used technology that a large community keeps maintained and secure, with no single vendor to lock you into, so the platform stays yours to host wherever your security and compliance needs require.
We get called when an in-house team needs a platform
that does not become someone else's problem in two years.
You do not need to fit a particular profile to work with us. Most clients reach out in one of three situations, and we start the conversation from wherever you actually are.
You already have a platform that works
You mostly want it looked after well. We start by telling you honestly whether your setup is already well optimised or whether there is real headroom, especially if it sits on an ageing system where a move pays for itself inside a year or two.
You want to improve or rebuild it
Adding features, redesigning the front end, or replacing the technology underneath. This is where we add the most value the fastest, and where the savings often show up before the rebuild itself ships.
You have a new idea and funding in place
You want a partner who can scope it properly before you commit the budget. We shape the offer around what you actually need, and we are straight with you about the most sensible next step.
We work especially well with three kinds of organisation.
For enterprises
Large companies running a global or multi-brand surface, often with a legacy system underneath that has become risky to touch. We migrate onto a modern stack, model the content for the way the in-house team actually works, and stay on retainer afterwards.
Public and quasi-public bodies that need a platform serious enough to last a decade and procure cleanly. Long horizons, written commitments, open and well-supported technology, and full handover documentation all matter here.
Growth-stage companies and funded ventures who want a build scoped cleanly before they commit capital. The same fixed-scope, fixed-price contract, sized to the runway the round is meant to fund.
These are the organisations we work with most often. If you do not see yourself in any of them, get in touch anyway, and we will start from where you actually are.
04·Why WAYF
The work speaks first.
Enterprise-proven
WAYF built Ingersoll Rand's global content platform and the Council of Europe Development Bank's events platform. Kaffy's marketplace launched at 5.0 on the App Store.
Trusted by the platforms we build on
WAYF is a Payload Partner Agency and a top contributor to its open source, and a Framer Enterprise Pro Partner.
A senior team that owns it end to end
The senior people who scope your build are the ones who ship it, and they stay with the platform through launch and the years that follow.
05·Method
What you are really paying for is certainty:we specify the architecture, fix the price, and model the return before we build.
Three things carry the value of a build with us: the architecture we put in writing before delivery starts, the price and deadline we hold to once the scope is agreed, and the return the platform earns once it is live.
Architecture
We specify the content model, the integration boundaries, and the shape of the platform before the first commit, in the same document that locks scope. Security boundaries are specified there too. We build on open, widely-used technology, so the platform stays patched and community-maintained on an open cadence. Structured content lives in the platform from day one, which keeps it legible to search engines, AI agents, and whatever channels come next.
Predictability
We sell delivery you can predict before it starts. The price, the deadline, and the standard for "done" are written down before we write any code. A pre-launch milestone earlier in the project gives you time to test the build against the acceptance criteria and flag anything that misses, with room left to fix it. What counts as done is agreed at signing.
Return
The return on the build compounds across the business. Your marketing and content team stops waiting weeks on engineering to publish. Your in-house developers inherit a codebase they can actually extend. The platform stays legible to search engines and AI agents without a separate AEO or programmatic-SEO project six months later. Translation workflows ship into new markets without rewriting from scratch.
06·How we work
How working with us actually runs,stage by stage, from the first email to handover.
01
Get in touch
You tell us what you are trying to do, and we talk for long enough to understand it. You do not need a finished brief.
02
Discovery
A small team works out what is actually being asked for, and finds the gaps while they are still cheap to fix, before anyone puts a number on it.
03
Scope and a price, in writing
We put the scope in writing, name what is out of scope, attach acceptance criteria, and quote a specific price and a specific date. You sign off on it.
04
Build, with testing inside it
The scope becomes a real plan with owners, dependencies, and dates. We test as we build, so defects surface while they are still cheap.
05
A milestone before launch
You get an early date to put the product through its paces against the acceptance criteria, with time left to flag anything that misses.
06
Release and handover
We treat the release as a planned event, verified after it ships. You get the platform fully documented and yours, on open technology you can host wherever you like.
07
After launch
We maintain it if that is what you want. Support, defects, and new ideas are routed separately, so the work does not decay into a stream of urgent messages.
You do not need it all figured out first.
Most of the specs we receive are not ready to build from. In our experience, and that of agencies we know well, perhaps one in ten arrives complete. The rest have gaps, wrong priorities, or assumptions that do not hold, and finding those is exactly what discovery is for. If all you have is a problem and a rough idea of where you want to get to, that is a fine place to start.
What you get before we start.
Before you share anything confidential, just ask and we will send you an NDA to sign. Out of discovery you get a single product specification document that the rest of the project is built against; how deep it goes depends on what you already have. If you would rather write up your own requirements first, ask us for templates and examples of what a good brief looks like.
07·How we engage
We engage in one of two shapes,and both put the scope and terms in writing before any work starts.
Most work is a fixed-scope build, with the price and deadline agreed up front. If you already have a platform that mostly works, an audit and an ongoing retainer is the better fit.
Default
Fixed scope and price
We work to a fixed price on a strict scope, with the deadline agreed up front. We name the out-of-scope items on the contract. Any change after sign-off triggers a written change to budget or timeline, so there is no quiet creep where you pay for things nobody asked for.
For most migrations the build phase is four to eight weeks, with discovery in front of it.
For platforms already running
Audit and ongoing retainer
If you already have a platform that mostly works and you want continuous senior attention on it, we start with a written audit and a recommendation, then settle into a monthly retainer covering a defined scope.
We set the retainer period up front, and you can renew it or wind it down. Planned scope, support, and ad-hoc requests stay on separate tracks, so the retainer does not quietly absorb work you are already paying for.
08·What you can hold us to
Concrete things you can hold us to,in writing, on every engagement.
We sign the scope in writing and name the out-of-scope items on the same document.
We agree acceptance criteria for every deliverable before the first line of code.
We run QA inside delivery, so defects surface while they are still cheap to fix.
We build in a pre-launch milestone, so you can test the product against the criteria with time left to fix what misses.
We write decisions down as we make them, so nobody is left a month later remembering the same conversation differently.
We hand over the platform fully documented and yours; you can take it to any vendor at any time.
09·Get in touch
Bring whatever shape the brief is in.We'll talk through the open questions and a sensible first step.
Whether or not you end up working with us, you will leave the first conversation with a clearer read on the open questions, the trade-offs, and what a reasonable first step looks like.
