What your agency can hand us
Each request starts from decisions your team has already made: the design, the copy and what the client approved. The parts below can be taken alone or combined in one project.
Builds from your Figma files and copy
Approved Figma files and copy become a custom WordPress theme with reusable blocks and editing fields. Missing states, such as error messages, empty fields and phone layouts, go to your designer as a list before the build, so nobody has to guess them in code.
Page designs from your wireframes
When your team supplies wireframes, messaging and copy without final designs, our designers create the pages in Figma within the brand you provide. Your creative lead approves them before development, and each approved section is then built as a block.
Content types and custom code
Custom post types, taxonomies and fields for what gets published, such as case studies, resources or job listings, plus PHP and JavaScript for behavior the design needs beyond standard blocks. Forms are connected to the CRM or inbox each project uses.
Tickets on sites you already run
Single tickets or overflow work on WordPress sites another developer built. We read the theme and plugins before changing anything, follow the conventions already in the code, keep each change in its own commit and note what changed and why.
Your review rounds and client relationship
We report to your project lead and work through the review and approval rounds your agency already runs. Questions for the client go through you, and we stay out of client conversations unless you bring us in.
Working alongside your developer
If your agency has its own WordPress developer, we agree who owns which parts of each site and work in the same Git repository under your branching and code review rules, so changes from both teams are reviewed before they reach staging.
Handback your team can maintain
At handover the code sits in your repository with a short guide to its templates, blocks and fields, an editing guide for whoever publishes on the site, and a list of plugins and licenses. Accounts created for us are removed or passed to you.
Repeatable launches and support after them
The launch checks agreed on the first project, covering forms, tracking, redirects and production settings, become the checklist for every later launch. After launch, fixes and new pages continue under a monthly plan or as separate projects.