Choosing an R&D Partner
How to Choose a Bathroom Product Development Partner
A field-tested evaluation framework for bathroom product development partners: engineering evidence, IP terms, compliance design, manufacturing reality, and the questions that separate engineers from renderings.
What a product development partner is
A bathroom product development partner is an engineering organization that carries a sanitary product from a defined problem to a design that can be manufactured and certified. Brands, importers, and project buyers work with one when they own the channel but not a hardware R&D team: the partner supplies the engineering — concept, patents, design for manufacturing, validation, certification planning — while production runs at contract factories.
Most buyers reach this decision through the same sequence: a supplier recommendation, a directory, then a shortlist evaluated over weeks. The evaluation itself is where programs succeed or fail, and it is harder than it looks because the market is full of organizations that look alike in a pitch deck: factories with an "R&D department," design studios selling renderings, and trading companies claiming engineering. This article is the checklist we would use — and the one we expect to be measured against.
First, decide what you are actually buying
Before comparing partners, settle the engagement shape, because it changes what you should evaluate:
| Model | What you get | How it is priced |
|---|---|---|
| Design only | Engineering design and documentation; you handle production | Fixed fee |
| Design + DFM turnkey | Design plus production coordination at contract factories, delivered as a working program | Milestone-based |
| Design + royalty | Design at reduced upfront cost, IP licensed per unit sold | Lower fee plus per-unit royalty |
If what you actually need is an existing product with your logo on it, you do not need a development partner — you need an ODM factory, and that is a different evaluation. We compare the models in OEM vs ODM vs private label. This article is about choosing the organization that engineers something that does not exist yet.
Seven criteria that separate engineers from renderings
1. Engineering evidence you can verify
Patents are the fastest diligence instrument in this industry, because they are public, numbered, and name inventors. Ask which patents came out of the work, then check the assignee record yourself.
- A partner with real engineering will answer with patent identifiers and named inventors. Our own record: 38 patents and published applications under Xiamen Wugong Technology's name, with principal inventor Li Renzhong named on 34 — spanning the axial-pump flushing cluster (CN220318693U, CN117721886A, CN118482474A), the thermostatic shower architecture (CN121154031A), the easy-clean floor drain (CN110629859B), and the flip-waste drainage redesign (CN121853662A).
- Rounded marketing numbers with no list behind them ("100+ patents") are a flag. Precision is free when the work is real.
2. Coverage of the full chain, not the fun half
Development runs problem → patented solution → manufacturable → certifiable. Studios that stop at styling and factories that start at tooling both cover half the chain. Ask what artifact exits each stage: a problem statement with acceptance criteria, filed applications, DFM documentation, test plans and reports, a certification roadmap.
3. Compliance treated as a design input
In this industry, product certifications (cUPC, WRAS, EN 1111, CE, WaterMark) attach per finished model and are typically held by the brand or the manufacturing partner — an engineering firm holding none is normal, not a defect. What you should evaluate is whether certification requirements shaped the design: materials in contact with drinking water, seal geometry against the standard's test conditions, the electrical envelope for wet environments. We cover the certification landscape for smart toilets in a separate guide.
4. Manufacturing reality, stated plainly
Ask directly: do you make this? A development firm without its own plant is a normal, workable structure — much of the electronics industry runs this way. What you want is a named manufacturing setup by discipline: brass casting and CNC, electronics and PCBA, injection molding, final assembly — with each factory's role, where tooling is made, and who owns it. Vagueness here becomes your logistics problem later.
5. IP terms written before the first sketch
Who owns foreground IP, whether it is exclusive, and what happens if the program stops — these are negotiation items, and reasonable answers differ by engagement model. Design-only work usually transfers IP on payment; royalty models usually keep IP with the developer. Any arrangement is workable; discovering the arrangement after the first milestone is not.
6. Numbers they volunteer — and how they frame them
A development partner should speak in measurable specifications: our fifth-generation flushing system is engineered for a 70 L/min opening flow, a roughly 4-second full flush, and 100,000-cycle durability; our smart shower program carries a ±0.5 °C temperature-control reference target. Notice the framing: a design target is a statement of intent, a validated result is a statement of evidence, and a partner who volunteers that distinction unprompted is more credible than one who blurs it.
7. Red flags
- A portfolio of renderings with no patent identifiers or test data behind them
- "ODM" claims from an organization that cannot show its own IP
- Manufacturing partners that cannot be named "for confidentiality" until very late
- Pricing with no stage gates
- An engineering firm claiming to hold product certifications
A due-diligence question set
| Question | What a good answer looks like |
|---|---|
| Which patents resulted from this work? | Identifiers and inventors, checkable in public records |
| Who holds the certifications, for which model? | Per-model attribution: the brand or the manufacturing partner |
| Who manufactures, and who owns the tooling? | Named partners by discipline, tooling ownership in writing |
| What does the test plan measure, and against what acceptance criteria? | Conditions, criteria, and who signs the report |
| What happens to the IP if the program stops? | A pre-agreed written answer |
| What do you not validate in-house? | An honest scope boundary |
The last row matters most. Every engineering organization has boundaries; the trustworthy ones state them.
Frequently asked questions
How is a development partner different from an ODM factory?
An ODM factory sells products from its own existing catalog, optionally customized; the factory owns the IP. A development partner engineers a product that does not exist yet, and the IP arrangement is negotiated. If your strategy depends on differentiation and patent protection, you need the second; if you need speed to market with commodity products, the first is cheaper.
Isn't a small engineering team a risk?
Evaluate evidence per engineer, not headcount. Our five-engineer team produced the 38 patent records cited above; IP-led development is typically done by small teams of senior engineers, and large headcounts at design firms usually indicate junior staffing, not depth.
What does an engagement cost?
Pricing follows the three shapes above and is driven mainly by prototype iterations, tooling, and per-market certification — not by the design hours alone. Ask for milestone-based pricing so that every payment is attached to a verifiable artifact.
Work with us
Wugong is a patent-driven bathroom product development company in Xiamen: engineering, patents, and production coordination across partner factories. If you are evaluating partners, the fastest diligence step is to ask any supplier — including us — for the artifact behind a claim: a patent record, a specification, a test plan. Start a project with us.
Engineering review: Li Renzhong, General Manager and principal inventor at Xiamen Wugong Technology — named inventor on 34 of Wugong's 38 patents. This article reflects our evaluation practice; it is not legal or procurement advice.