# Technical working framework for agencies | abuenoben

> Operating conditions for adding senior white-label development, protecting the client relationship and closing delivery without artificial dependency.

Canonical URL: https://abuenoben.com/en/agencies/working-framework
Language: en

Operating conditions for adding senior white-label development, protecting the client relationship and closing delivery without artificial dependency.

[Download PDF briefing](/downloads/agency-collaboration-briefing-abuenoben-en.pdf)[Send a short brief](/en/contact?organizationType=agency#contact-form-shell)

## A frame the agency can explain and forward

The collaboration adapts to each project, but these rules provide a base before discussing scope, price or timing.

### Protected commercial relationship

The agency keeps the client, proposal and communication. There is no parallel contact or solicitation.

### Controlled entry

Objective, owner, access and visibility are clear before execution begins.

### Visible delivery

Staging, decisions, risks and acceptance criteria make progress defensible.

### Clean exit

Code, documentation, pending work and access are ready for continuation without dependency.

## Operating conditions

They do not replace a contract, but they prevent the ambiguities that create most white-label delivery rework.

01

### Confidentiality and final client

Visibility is agreed before sensitive context is shared.

-   NDA available from the start.
-   No final-client contact or solicitation outside the agreed frame.
-   Meeting participation only when the agency requests it.
-   No publishing brands, screenshots or outcomes without explicit permission.

02

### Code, ownership and tools

The agency retains practical control over delivery assets.

-   Code and deliverables inside the agreed ownership frame.
-   Work in existing repositories, CI and tools where practical.
-   Domains, deployment accounts and services inventoried.
-   Minimum, revocable access without sending secrets through unsafe channels.

03

### Execution and acceptance

Delivery is organized around verifiable outcomes, not activity that is difficult to defend.

-   Milestones, staging or demos according to size and risk.
-   Risks and dependencies communicated before they block the date.
-   Acceptance criteria and a validation owner.
-   Changes recorded with their scope, timing or capacity impact.

04

### Support and handoff

Closure defines what continues, what ends and what the next person needs.

-   Post-delivery support window agreed per engagement.
-   README, deployment, decisions and pending work supplied where relevant.
-   Transfer to the agency team or continuity under a new frame.
-   Closure or rotation of credentials and temporary access.

## Public proof available

When permission exists, evidence is published with brand and context. Under NDA, it is limited to authorized responsibility, outcome and visibility.

[View the MaderaPlus case](/en/cases/maderaplus-technical-diagnostic)

203

backend/API calls documented in the +DERA diagnostic

115

issues and improvements reviewed

23

actionable entries prioritized

## Minimum information to start

A perfect scope is not required and access details should not be sent in the first message.

-   What should be resolved.
-   Current state and main blocker.
-   Relevant date.
-   Who accepts delivery.
-   Expected white-label or visibility level.

## A concrete delivery is enough to assess fit.

Within one business day, you will receive a reply on fit, missing information and the model worth exploring.

[Send a short brief](/en/contact?organizationType=agency#contact-form-shell)

Prepare the engagement

-   [How to outsource development without losing client control](/en/guides/outsource-development-without-losing-client-control)
-   [What a white-label development agreement should cover](/en/guides/white-label-development-agreement)
-   [Technical brief checklist for agencies](/en/guides/agency-technical-brief-checklist)
-   [Retainer or fixed project: how to decide](/en/guides/retainer-or-fixed-project)