Some bids need a Drupal subcontractor the buyer can see: a public tender that asks for every subcontractor by name, a consortium where each member is listed, or a client who wants to know who writes the code. WeebPal takes that role under its own name: we carry the Drupal part, and the client relationship still runs through you.
Who this is for
- A tender that lists subcontractors The buyer asks for every subcontractor by name, Drupal is in the requirement, and hiring a specialist for one contract does not pay back before it ends.
- A consortium bid Companies bid together, each named for its part, and the Drupal part needs a member who can carry it.
- A client who wants to know who writes the code Procurement or a security review asks for the developer's name, location and practices, and hiding them would defeat the review.
- One part that needs a specialist A migration, an integration, performance or accessibility work inside a larger project you lead.
If your client must never see our name, that is white-label development instead. If your own organisation is the buyer, see outsource Drupal development.
What you get as the agency that leads
- Our part of the bid, in writing The scope and fixed price of the Drupal work, our company details, and the named engineers who will do it.
- Evidence for the evaluation Architecture, test evidence and answers to security and accessibility questionnaires for the Drupal part, as we provide for our own tenders.
- References under our own name Direct client work published with the client named, and reviews signed by the people who wrote them.
- Delivery into your repository Code, tests and documentation committed to your account from the first commit, to Drupal coding standards.
- Your process Your tracker, your branching model, your review gates and your release cadence.
An engineer reads it and replies within one business day.
How the work runs
How a named subcontract runs
- Discovery Under a mutual NDA: the tender, the scope of the Drupal part, and the repository if one exists. You keep the scope notes
- Fixed price Our part priced in writing, with the assumptions behind the number. You keep the quote
- Bid Our name, company details, references and named engineers in your documents. You keep the bid inputs
- Build In your repository and your tracker, with a working demo to you each week. You keep the repository
- Acceptance Tested against the scope in the contract, and reviewed by your side. You keep the test record
- Warranty Defects in what we built are ours to fix, under a warranty your agency holds. You keep the handover pack
When your client knows our name
Being named in the bid does not move the client relationship. Requests from the buyer come to you, our answers go back through you, and we join client meetings when you ask us to. The subcontract, the mutual NDA and non-solicitation are signed before the bid goes in.
Who sees what when we are your named subcontractor Your client reads our name in the bid and still works through you
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.
| 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 whole partner programme, including platforms taken to your own market, is on partners.
What you can verify
As a named subcontractor we can be checked directly by your client, so the evidence is public:
- Public-sector work under our own name Case studies with the client named, for Pacific regional organisations: PRISMSS and the Pacific Islands Roundtable, built and maintained by us, and SPREP, whose sprep.org we redesigned and maintain.
- Our code in public WE Mega Menu and Component Builder on drupal.org, with the issue queue that shows how we answer bug reports. More on our open source page.
- Named reviews Agencies that give us Drupal work have reviewed us by name on our reviews page.
- One contained piece of work A module, an audit or a migration assessment, before a bid depends on us.
Sazae is an IT Consulting / IT Solution / Drupal / Software Development firm that supports Startups, SMEs, and large corporates across Australia, Taiwan, and Japan.
We have been working with Weebpal for couple of years and has built a good relationship and foundation to develop from small to large size drupal web application for different client in various industry.
Weebpal is highly recommended with their capability and skills to achieve complex logic and business process from different client needs.
What it costs
Our part is a fixed price once its scope has edges, set the same way as a direct project. The project sizes on our pricing page, from Micro to Strategic, show how work is scoped and staffed, and the Rate Card gives the rate for each role where a bid asks for day or hourly rates. Your price to the buyer is yours to set.
What moves the number: how much of the system is ours to build, the integrations, whether content has to migrate, and the evidence the evaluation asks for. Work that continues after the contract, such as maintenance of the delivered site, is priced in the same way as for our direct clients.
Terms that hold
These terms hold across our services; where a service starts differently, its page says how. The full wording is on the warranty page and in why you own the source code.
- A prototype before you sign a build Before a build project is signed, we build a prototype at no charge: a design, a clickable prototype or a working demo on real code, so you decide against something real.
- You receive the system and its source code Custom work is yours from the first commit: the repository, custom modules, theme and deployment configuration. When we build your system on one of our platforms, you receive the whole system and its source code as well.
- Response targets we publish A first response in 4 hours for critical issues, 1 business day for high priority and 3 business days for normal. Support runs in business hours; cover outside them is an option, priced separately.
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.
Questions we get asked
What do you need from us to price our part of a bid?
The tender documents, or the sections that concern the Drupal work, the evaluation criteria and the submission date, all under a mutual NDA. Where there is an existing system, access to its repository lets us price what is there rather than what the brief describes.
Can WeebPal be a consortium member rather than a subcontractor?
Yes, where the tender allows a consortium: we can be named as the member responsible for the Drupal part. The lead member, the split of the work and the terms between members are agreed in writing before the bid goes in.
Who signs the contract with the buyer?
Usually your agency, as the lead bidder, with WeebPal under a subcontract to you. In a consortium the members sign as the tender requires. Either way, the terms between us are agreed before the bid is submitted.
Our client will know your name. Will you approach them later?
No. Non-solicitation runs both ways and is written into the contract for the term it sets. Knowing our name does not change who the client works through: follow-on work goes through you.
Can you take over a subcontract already in progress?
Usually, and it starts with reading what exists rather than with a start date. That assessment is a deliverable you keep, whether or not you continue with us.
Not covered here? Ask us directly.
Scope a piece of workAn engineer reads it and replies within one business day.
Start with one contained piece of work
Send the scope, the bid date and the repository you want it delivered into. The mutual NDA is signed before any of it changes hands.
An engineer reads it and replies within one business day.