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

Arafilum · Online shopView case
Arafilum website: handmade products and shopping journey. Built for a direct client.
A shop that also handles the order.

Catalogue and cart: the customer finds a product and prepares their order.

Built for a direct client. An example of the development I can handle for your agency.

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

Commercial pieces ready to publish, measure and connect with forms, CRM or automation.

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 and real states.
  • Connection with API or existing backend.
  • A base prepared to iterate.

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 evolutives

Support for apps, SDKs, publication, stabilization or mobile evolution when the client asks for more technical depth.

What is included
  • Android, multiplatform or mobile integration.
  • QA before release.
  • Fixes and evolution by priority.

QA, release and stabilization

Pre-production work to reduce regressions, close risks and avoid preventable emergencies for the agency.

What is included
  • Tests on critical flows.
  • Publication checklist.
  • Issue close 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.
  • Executable plan proposal.

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 do not contact or solicit the end client outside the frame agreed with the agency.
  • 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 enter the channel, tool and repository you already use. Slack, Notion, Jira, Linear, GitHub or whatever system makes sense.

Code and documentation

I leave code, decisions and pending items clear so the agency can maintain, sell or continue without artificial dependency.

Protected commercial frame

I work inside the agency agreement: visible, discreet or completely white-label depending on client and project.

Acceptance and support

We agree who validates, what closes each milestone and what support remains included after delivery.

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.

Work peaks without overbuilding the team

I join when capacity is needed and leave without creating dependency.

Real white-label work

I respect the agency's client relationship and the commercial frame already sold.

Less technical blocking

The agency can sell and execute technical work with less uncertainty.

Senior judgment

One senior person to resolve the technical stretch that is blocking the project.

MaderaPlusAndroid app, API and back office

MaderaPlus: deciding what to fix first

The +DERA work for MaderaPlus left a reproducible environment, technical inventory and roadmap for deciding evolutives with less uncertainty.

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

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?+

Objective, timing, current state, validation owner and the technical piece blocking delivery. With that I can orient the next step.

Can you join a project that is already started?+

Yes. That is a common case: review the base, take ownership of a concrete part and leave the exit documented.

What happens with code and documentation?+

It stays inside the agreed agency frame. The delivery is left ready to publish, maintain or transfer to the right team.

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