A client project needs expertise your agency doesn't have in-house.
White label technical consulting for agencies and software houses
I support web agencies and software houses on their clients’ projects as an external technical consultant. The agency keeps the client relationship; I bring the technical side, from analysis to release.
It works well when a project falls outside your team’s usual scope: business software, a complex integration, an accessibility audit, a custom plugin. Instead of turning the work down or taking it on blind, you have a consultant who handles that part with clear timing and boundaries.
I’ve worked this way for years: much of my work has started behind the scenes for agencies and software houses.
How I approach it
The problems I see most often start before the project, at the quoting stage. The agency commits to time and cost without having understood the technical side, or quotes changes on an inherited project as if the code were in good shape. Once work starts, integrations, data to migrate or code to fix turn up that nobody had accounted for, and the margin disappears.
So when you bring me in, I start with the analysis. If the project already exists I check what state it's in, then I split the work into parts and estimate time and risk for each. You get a document to build your quote on, and if a part is uncertain I tell you before it reaches the client.
When it helps
- You have a client whose technical project is bigger or more complex than your usual work.
- You need specific expertise for one phase of a project, such as the initial analysis or an audit.
- The client asks for accessibility, integrations, business software or a custom plugin, and your team lacks that skill.
- You've inherited a project written by someone else and want to know its state before you quote.
What's included
- Technical analysis and estimates before you quote the client.
- Any service on this site, on an agreed scope.
- Reports and documents under your brand, ready to hand to the client.
- Work on agreed goals and deliverables, organised independently, in your repositories and with your tools when needed.
How it works
- Brief
You tell me about the client, the project and what you need from me. Tell me who talks to the client, too.
- Estimate
A technical analysis with scope, timing and risks that you build your quote on.
- Delivery
Consulting and, where agreed, delivery within the agreed scope, with regular updates to whoever runs the project.
- Handover
Code, documentation and handover to your team, so the project doesn't depend on me.
What you get
- Technical analysis and estimate for your quote.
- The agreed deliverables, in your repositories if needed.
- Documentation for your team.
FAQ
Does the end client know I'm involved?
That's your call. I can stay behind the scenes or join technical calls as the agency's technical consultant.
Do you only work on WordPress?
No. WordPress is part of the work; the rest is business software, web applications, apps and integrations.
Further reading
Quoting changes on an inherited project without losing your margin
For web agencies: what to ask the client, what to check in inherited code, and how to write phases, exclusions and assumptions into the offer.
Let’s talk
info@giusepperusso-dev.itWant to know if it fits your case? Send me a couple of lines about the problem: I reply within 24 business hours.