Two formats: a referral or joint delivery
For a direct referral, the client discusses development with the studio. Under the pommeDeTerre programme terms, the partner receives 10% of payments in the first year and 5% in subsequent years. The studio qualifies, estimates and delivers the work. If your design input is needed, define its scope separately.
For joint delivery, you keep a role in the project and the partner delivers the agreed technical scope. The published programme calls this Production Partner: the studio can contribute design, frontend, backend, integrations and operations. Communication and responsibilities are agreed separately. Referral rates should not automatically be treated as the terms of this contract.
| Question | Direct referral | Joint delivery |
|---|---|---|
| Who manages development with the client? | The studio directly | Agreed separately |
| What are you paid for? | An accepted referral after work is paid for | The payment basis and arrangements are agreed separately |
| Who accepts the result? | The client under its studio contract | The owner and procedure are defined before work starts |
What to hand over with the designs
Provide a link to the current designs, a list of screens and an explanation of user actions. A form needs submitting, error and success states; a catalogue needs empty results, filters and different product card layouts. Specify which screens have mobile layouts, which copy is ready and which images the client still needs to supply.
Name data sources and external services: where products come from, where enquiries go, whether login is required and which payment or delivery options are planned. Without these decisions, a developer cannot reliably estimate a project from one attractive homepage. Share production access through an agreed secure channel, separately from a public design link.
How to keep your role and approve changes
Before estimating, agree who collects client questions and approves answers. If you lead design, the technical partner needs to know which interface changes require your approval and which belong to implementation. The client benefits from knowing who handles design, scheduling and data questions.
Changes after design approval can affect development scope. Another payment method, a new user role or a different catalogue source is a separate requirement. Record what changed, its effect on the estimate and who approved it. The client and both teams then share one current scope.
How to accept development against the designs
Review the agreed screens on desktop and mobile, then follow user actions. Submit a form, check validation errors, open a product and place a test order if a store is in scope. A screenshot matching the design establishes appearance only; enquiry delivery and order persistence need separate checks.
Record issues with the page URL, screen size, action and expected result. Before launch, define who accepts fixes, who owns the domain, source code and service accounts, and who maintains the site after delivery. These are points to agree, rather than promises of specific terms from every studio.
How to discuss price and fees
Separate design, development and project management prices. For a direct referral, use the referral fee calculation: the basis is studio work actually paid for. If you manage the project, the contract should separately describe your work and settlement with the technical partner.
Do not quote a final development price before agreeing the scope with the provider. Send completed designs for estimation, the desired launch and known constraints. If the project has already been sold, explain your commitments to the client so the partner can establish what it can actually take on.
How to start a conversation with the studio
In the partnership enquiry, describe the task and whether you want to introduce the client directly or keep managing the project. Include a product link or designs you can share for discussion. A clear scope and your contact details are enough for the first conversation; access credentials are not needed for the first conversation.
For a direct handover, agree the introduction and confirm referral eligibility. If you stay involved, start by allocating responsibility. That decision shapes client communication, the technical estimate and acceptance, as well as your compensation.
Frequently asked questions
Can I hand over only backend work?
The programme allows the studio to join specific technical tasks. The actual scope, access and responsibility boundaries are defined after discussing the project.
Must I hand over client communication?
No. For joint delivery, you can continue managing the client; communication with the studio and responsibilities are agreed separately.
Can I receive a fee if the client already knows the studio?
Direct referrals require the client not to have previously negotiated with the studio or submitted an independent enquiry. A possible joint format for an existing client is discussed separately.