Development for agencies, under your brand.

Your team handles design and the client relationship. I join to build the website, app or integration you need, using your channels and repositories.

White-label · NDA · Code and documentation in your repository

Consumer campaign · Agency collaboration

A landing page for every stage of the promotion.

Frontend implementation for a confectionery brand in Spain: launch, participation and closure on one codebase. The case explains the technical work; BRIZZI lets you try a recreation with a different identity.

Fictional BRIZZI gummy packaging created for the campaign recreation.
BRIZZI recreation · Fictional brand identity and products.

What your agency can commission

We can start with one part of the project. We agree what is included, who reviews it and when it needs to be ready.

Landing pages and campaign microsites

Campaign pages built from your design, with the agreed forms, tracking and integrations.

What is included
  • Faithful implementation from design.
  • Forms, measurement and events.
  • Static delivery or integration into the existing base.

Product frontend or private area

Product interfaces, operational panels or B2B frontends an agency can sell without expanding the team.

What is included
  • Components with loading, empty and error states.
  • Connection with API or existing backend.
  • Code your team can extend.

Backend, CRM and integrations

Connections between website, business and operations: APIs, automation, forms, data and third-party systems.

What is included
  • Flow design and validation.
  • Commercial tool integration.
  • Error logging and handling.

Apps and mobile feature development

Android features, SDK integration, bug fixes and release support for your client’s app.

What is included
  • Android, multiplatform or mobile integration.
  • QA before release.
  • Prioritised fixes and new features.

QA, release and stabilization

Checks on critical user flows and known issues before your agency approves a release.

What is included
  • Tests on critical flows.
  • Publication checklist.
  • Review of unresolved issues before delivery.

Technical presales and scope

Support to clarify feasibility, risks, estimate and limits before the agency commits to a complex delivery.

What is included
  • Technical scope review.
  • Risks and dependencies.
  • A proposed implementation plan.

Your client, your channels, your code

We agree client access, code ownership and support before development starts.

  • I can be visible, discreet or completely white-label, depending on what fits.
  • I only contact the end client as agreed with your agency and do not approach them for separate work.
  • Repositories, access, code ownership and publication are agreed before work starts.
  • I do not publish brands, screenshots or outcomes without explicit permission.
Read the full framework

How I join your team

Joining the team

I use your team’s existing communication channels, task tracker and repositories.

Code and documentation

I document the code, decisions and remaining work so your team can maintain the result or hand it to another developer.

Your client relationship

We agree how I take part in the project: as a named collaborator or working behind your agency’s brand.

Acceptance and support

We agree who approves each milestone, the acceptance checks and any support included after handover.

When external support makes sense

Campaigns with a fixed date

Design and strategy are clear; execution has to happen without last-minute surprises.

Commercial and operational integrations

CRM, automation, forms, measurement or data have to be connected correctly.

Projects with more technical depth

The client asks for an app, product frontend, backend or real technical support.

Help during busy periods

I take on agreed work when your team needs capacity and document it before handing it back.

Real white-label work

Your agency manages the client relationship. I work within the scope and terms you have agreed.

Support with technical decisions

I review feasibility and dependencies before your agency commits to the work.

Senior judgment

One senior developer responsible for the part of the project that needs technical support.

MaderaPlusAndroid app, API and back office

MaderaPlus: deciding what to fix first

I reproduced the +DERA environment, reviewed the technical inventory and proposed a phased roadmap for MaderaPlus to plan further work.

Read the MaderaPlus case study
203
backend/API calls documented
115
issues and improvements reviewed
23
actionable items identified

Questions before adding external support

Can you work completely white-label?+

Yes. I can stay behind the agency, work under NDA and adapt to the agency's channels and rules.

What do you need to assess a delivery?+

Tell me the goal, deadline, current state and who will approve the work. Describe the main blocker so I can suggest the next step.

Can you join a project that is already started?+

Yes. I review the existing code, take responsibility for an agreed part of the project and document the work for your team.

What happens with code and documentation?+

We agree ownership and access before work starts. Your team receives the code and documentation needed to publish, maintain or take over the work.

What does your agency need to deliver?

Tell me about the project and the deadline. We can start from an existing design, brief or codebase.

Tell me about your project