Protected commercial relationship
The agency keeps the client, proposal and communication. There is no parallel contact or solicitation.
How I work with agencies
How we agree scope, ownership, client communication and handover for white-label development.
Working terms you can share with your team
We use these terms to discuss responsibilities before agreeing the scope, price and schedule for your project.
Before work starts
We agree the goal, who approves the work, which access I need and how I am introduced to the client.
Progress you can review
You can review working versions, decisions and outstanding risks against the agreed acceptance criteria.
A documented handover
Your team receives the code, documentation, access details and remaining tasks needed to continue the work.
Operating conditions
We confirm these responsibilities in the project agreement, along with scope, fees and timing.
01
Confidentiality and the end client
Visibility is agreed before sensitive context is shared.
- NDA available from the start.
- Contact with the end client only as agreed with your agency; no approach for separate work.
- 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.
- Ownership and licensing of code and deliverables agreed before work starts.
- 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
You review working changes at the agreed milestones and approve them against the acceptance criteria.
- 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
The handover sets out what has been delivered, what remains and how support will work.
- Post-delivery support window agreed per engagement.
- README, deployment, decisions and pending work supplied where relevant.
- Handover to your team or a separate agreement for ongoing work.
- Closure or rotation of credentials and temporary access.
A project you can review
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- 203
- backend/API calls documented in the +DERA diagnostic
- 115
- issues and improvements reviewed
- 23
- actionable items identified
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.
Tell me about the work you need to deliver.
I will reply within one business day to say whether I can help, what else I need to know and how we could start.