SEO agencies
Technical fixes, performance, schema, migrations and changes that need code rather than another plugin.
You own strategy and creative. I deliver the difficult WordPress work.
Technical capacity for agencies. No recruitment required. Agency Development Desk gives your agency reserved senior engineering capacity for builds, integrations, repairs and review. Work is white-label, inside agency or client repositories, from written tickets.
A written fit assessment, sent on CET working days.
Desk Core
EUR 2,760
24 hours / month
For a regular backlog across several client accounts.
- 24 reserved engineering hours
- up to two active tickets
- queue priority and report
For agencies that need dependable technical cover
The model works best when you retain the client relationship and I remain accountable for the agreed technical result.
Brand and UX studios
Careful Figma implementation, components, animation and CMS work without diluting the design.
Software teams
Senior WordPress or WooCommerce capacity for integrations, review and a defined delivery stream.
Reserved capacity, not unlimited tickets
The package follows the real backlog. Each option has a monthly hour limit and its own place in the ticket queue.
Desk Flex
EUR 1,250
10 hours / month
For irregular fixes, consultation and code review.
- 10 reserved engineering hours
- one active ticket
- monthly time summary
standard queue
Send a written partner briefDesk Core
EUR 2,760
24 hours / month
For a regular backlog across several client accounts.
- 24 reserved engineering hours
- up to two active tickets
- queue priority and report
queue priority
Send a written partner briefDesk Embedded
EUR 5,280
48 hours / month
For a steady delivery stream and technical ownership.
- 48 reserved engineering hours
- up to three active tickets
- next-month capacity plan
top queue priority
Send a written partner briefRules that protect both sides
Terms are short, measurable and written before delivery starts.
Hours per month
The package covers one calendar month. Unused hours do not carry over, because that capacity was reserved for the agency.
Initial term
The first term is two months, then monthly with one month's written notice.
Scope and estimates
Small tasks use the package. Larger sprints receive a separate written scope, estimate and approval.
Out of hours
Work happens on CET working days. Evening, weekend and emergency work requires a separate written agreement.
Queue order
| Priority | Example | Desk Flex | Desk Core | Desk Embedded |
|---|---|---|---|---|
| P1 - critical | production or checkout unavailable | 3rd in queue | 2nd in queue | 1st in queue |
| P2 - high | release or key feature blocked | 6th in queue | 5th in queue | 4th in queue |
| P3 - standard | development, review, optimisation | 9th in queue | 8th in queue | 7th in queue |
Ticket priority comes first, then the package: every P1 goes before any P2 or P3. There is no guaranteed response or fix time; the order only decides what I pick up next.
Your brand and client relationship remain yours
NDA before access
We can sign confidentiality terms before you disclose the client, repository or environment details.
White-label delivery
Communication, documentation and commits can follow your agency process. I do not present my brand to the end client.
Non-solicitation
I do not bypass the agency or pitch the end client during the engagement or for 12 months afterwards, subject to the contract.
Ownership and access
Code sits in an agency- or client-controlled repository, while accounts and licences do not depend on me.
Start without a chain of meetings
- 1
Brief
Email your client types, stack, sample backlog and expected monthly capacity.
- 2
Fit
I reply with risks, recommended package, scope boundaries and anything I cannot cover.
- 3
NDA and rules
We agree confidentiality, white-label terms, non-solicitation and access controls.
- 4
First backlog
We set priorities, ticket readiness rules and begin the two-month initial term.
Delivery can be demonstrated without breaking an NDA
The case studies document constraints, architecture decisions and risk controls. Client details remain anonymous where the contract requires it.
Frequently asked questions
Do you communicate directly with the agency client?
Only when the agency asks and we agree the white-label role. By default, all communication stays with the agency.
Do unused hours roll over?
No. Hours are used within the month; if they keep going unused, a smaller package is the better fit.
Can we commission a one-off project?
Yes, when it has a defined scope. Development Desk suits recurring backlogs, while a larger project receives a separate estimate.
Does a package guarantee a response or fix time?
No. The package sets the order: ticket priority first, then the package when priorities match. I reply on CET working days, and resolution depends on diagnosis, access, dependencies and scope.
How do we submit work?
Use a written ticket with the intended result, links, environment and acceptance criteria. Meetings are not required.
Send a sample backlog before reserving capacity.
You will receive a fit assessment, recommended package and the conditions needed for a safe start.
Send a written partner brief