For agencies
Engineering under your name
Project work, monthly support, a team reserved for you, or a named place in your bid. White-label work is delivered as your own and your client never meets us; as a subcontractor we are named alongside you.
-
White-Label Drupal Development
White-label developmentA defined project built or extended under your brand and priced per project, with the NDA signed before anything is shared.
-
White-Label Support & Maintenance
White-label supportMonthly updates, fixes and monitoring for your clients' live sites under your brand, including sites we did not build.
-
Dedicated Drupal Team
Dedicated teamNamed engineers reserved for your agency by the month, working to your backlog, your process and your tools.
-
Drupal Subcontracting
SubcontractingA named subcontractor on your tender or in your consortium: we appear in the bid documents alongside you, with the NDA signed before anything is shared.
-
Outsource Drupal Development
Outsourced developmentFor an organisation rather than an agency: a senior Drupal team without recruiting one, at a fixed price once the architecture is agreed.
Compare
Subcontracting, white-label or a reserved team
These arrangements are often called by the same name. What separates them is what you are buying and who your client sees.
What you buy, how it is priced, who your client sees
| Arrangement | What you buy | Priced | Client sees | Suits |
|---|---|---|---|---|
| Named subcontracting | A defined piece: a module, a migration, an audit, a build | A fixed price for our part | Our name in the bid, your agency in the relationship | Tenders and consortia that list subcontractors |
| White-label delivery | The same kind of work, delivered as your agency | A fixed price per project | Your agency only | Clients who must see only your brand |
| Reserved team | Named engineers by the month against your backlog | Monthly, by role | As you decide | A roadmap with no finish line |
Live client sites kept running month to month under your brand are white-label support. The contract clauses behind these arrangements, and the order to agree them in, are set out in white-label agency contracts: NDA, non-solicitation and warranty.
Terms
Agency terms
Agreed in writing before any work starts, and the same for every agency we work with.
- NDA first A mutual NDA is signed before a client name, a requirement or a repository changes hands.
- Non-solicitation, both ways We do not approach your clients or hire your staff, and you do not hire ours. The clause is written into the contract, for the term the contract sets.
- The warranty is held by your agency On development projects the warranty belongs to your agency, as the party that signs with us: 1 year by default, up to 3 years, including the security releases of Drupal core and contributed modules. What you promise your own client is yours to set.
- Code delivered to your agency The code goes into your repository, and your client receives the whole system and its source code under your contract with them.
- Platforms, taken to market together When a client's system runs on one of our platforms, we deploy and extend it with you for that client, and we grow that market together.
- You decide who appears As a white-label team we never appear to your client. As a named subcontractor, on a tender or in a consortium, we appear under our own name where you want us to. Either way, you decide who joins a client call.
Platforms
Sell a platform that already runs
Our platforms are already in production. You bring the market and the clients; we deploy and adapt the platform together with you, under your name, and your client receives the running system and its source code. On a platform partnership we take the minority share and you take the majority; the terms are agreed per partnership, before you commit.
-
For agency partners
Talk about a partnershipYou know the clients and the sector; we deploy the platform with you and stay behind the code.
- Source access, documentation and training
- A priority support route to our engineers
- Delivered under your name, to your client
-
For operators
Browse the platformsYou offer the platform as a service in your market, under your own brand, and we deploy and maintain it with you.
- Platforms ready to deploy
- Setup and training for your team
- Hosting on your infrastructure or ours
Process
How a partnership runs
-
-
You bring the opportunity
A client, a market or a product idea. You keep the relationship and the brand throughout.
-
We show the closest thing we have
A working demo on real code, a platform or a prototype, so the conversation starts from something real rather than a deck.
-
Terms agreed before commitment
NDA, non-solicitation, platform terms, support routing and warranty are settled up front, so both sides can plan around them.
-
-
-
We build, you deliver
Engineering, integrations and deployment on our side; the client relationship on yours.
-
We stay behind the code
The team that built it fixes it. Development projects carry a warranty of one year by default, up to three.
-
Roles
Who handles what
You
- The client relationship, the brand and the commercial terms with your client
- The market knowledge, and what the product needs to become
Us
- Engineering, customisation and integrations
- Deployment, upgrades, and the warranty on development work
- Documentation and training for your team
Together
- Support routing, agreed before launch, so your client is never handed between two companies
How does a platform partnership work?
We deploy and adapt the platform together with you, for your clients, under your name. You hold the client relationship and know the market; we handle engineering, deployment and upgrades, and stay behind the code. Your client receives the running system and its source code, and we do not appear in the relationship unless you decide we should.
Deployments are done together rather than by either side alone, so every deployment stays on the maintained platform and improvements can reach all of them. Territory, exclusivity, fees and renewal are set per partnership.
Customisation we build for you on top of a platform is a development project and carries the project warranty.
What happens if the partnership ends?
The platforms are built on Drupal, which is open source, written to Drupal coding standards and documented, so another Drupal team can read them. Client data sits in a database you can export, on infrastructure you choose, and your clients keep what they received: the running system and its source code.
What we agree per partnership, before you commit, is the practical part: what happens to customisation in progress, and who supports those clients during the transition, so no client is handed between two companies.
What can you check before committing?
The platforms are running, and demos are available on request: see the platforms. The client work is named in the case studies, and the reviews carry reviewer names and projects, including development firms that give us Drupal work, such as Ingenuity Solution in the United States and Sazae in Australia. Our contributed modules are published on drupal.org, where anyone can read the issue queues.
We are a U.S-based Drupal development firm and finding a true Drupal talent is always our top priority. We are fortunate enough to work with the WeebPal team.
With a solid technical knowledge foundation, the WeebPal team delivers exceptional work consistently. Granting projects to the WeebPal team gives us some sort of comfort level, since we know the WeebPal folks will deliver no matter what.
We do not put a number on partner outcomes. We have not measured revenue from partnerships in a way we would stand behind.
Questions
Questions agencies ask
- Can we deliver it under our own brand?
Yes. White-label project work and platforms are both delivered under your name, and the client relationship stays yours. If you would rather name us, for example in a tender or a consortium, that is subcontracting.
- Who holds the warranty?
You do. On a development project the warranty belongs to the party that signs with us, which is your agency: one year by default, up to three. What you promise your own client is yours to decide.
- Do we get the source code?
Yes. Bespoke work ships with the full source code from the first commit. On a platform deployment, your client receives the running system and its source code, and your team gets documentation and training to work on it with us.
- How is a platform partnership split?
We take the minority share and you take the majority. Territory, exclusivity, fees and renewal are set per partnership and agreed before you commit.
- What if our client needs something the platform does not do?
That is normal, and it is the usual reason partnerships start. Customisation is quoted as a project; if it turns out to be broadly useful it often lands in the platform for everyone.
- Who supports the end client?
Agreed before launch. Most partners keep first-line support because they own the relationship, with technical escalation to us. What we avoid is a client being passed between two companies.