A Magento white-label partner takes over development in the background while your agency keeps client contact and brand. This guide describes what such a partner should deliver, how you recognize one and which questions to ask before the first collaboration.
A client switches to your agency and brings a finished shop. Anyone who wants to take over a Magento project should know the condition of the shop before making an offer. This guide shows what a technical check examines and how the result feeds into your quote.
The Magento handover decides whether a project stays viable after go-live. This guide shows which documentation, access, licenses and protocols belong to a clean close so that client and agency stay in control.
Finding a Magento subcontractor is easy, finding a reliable one is not. This guide shows where agencies search, which criteria they check, which warning signs exist and how a trial job limits the risk.
As soon as an external developer works on your Magento project, Magento project management decides speed and quality. This guide shows roles, a ticket template, the right rhythm, branching rules and acceptance.
A long-standing client asks about Magento and your agency has nobody for it. As an agency without a Magento team you do not have to turn the request down. This guide shows four options, the fears about external partners and a checklist before you say yes.
Additional Magento developer capacity is for many agencies the difference between declining and accepting. This guide compares models for rented capacity, works through an example and shows when hiring is the better solution.
An agency that has to calculate a Magento quote without knowing every part itself faces a risk: too low and the margin is missing, too high and the order is lost. This guide shows line items, buffer, external services and a worked example.