How custom manufacturing works at RDF
From a first idea, even a vague one, to a working prototype: here's how a project moves forward at RDF, step by step, and why some projects get accepted faster than others.
Identifying the real need before looking for a solution
A project rarely starts with a technical plan. It starts with a need — often vague — that has to be put into words first. Many people arrive with a ready-made solution in mind — a specific part to copy, a material already chosen — when the real starting point is the problem to solve.
Reformulating the need first avoids building a complicated answer to a poorly framed question. In practice, a simple conversation is enough to start: what doesn't work today, what you'd want instead, and the context the object will be used in. That's enough for RDF to launch a serious feasibility study, even without a drawing or 3D model on your side.
The concrete steps of a project
Every project follows a similar path, then adapts to the real complexity of the request:
- Listening to the need — a conversation to understand the real problem, not just the imagined solution.
- Feasibility study — technical check: materials, mechanical constraints, the right manufacturing method.
- Technical proposal and quote — a clear price before any commitment.
- Prototyping — a first physical version, tested and adjusted if needed.
- Manufacturing or small production run — once the prototype is validated, depending on what the project actually needs.
Each step is validated with you before moving to the next. RDF doesn't sell an off-the-shelf product: it's a working method applied to a unique need, which is why price and timeline vary from one project to another.
An R&D approach at a human scale
Research and development isn't reserved for large companies: it's an approach, not a matter of size. Studying technical feasibility before manufacturing avoids bad surprises and unnecessary costs, whether the project is personal, non-profit, or professional.
Once the solution is validated on paper, RDF moves to manufacturing: 3D printing, simple machining or assembly, depending on what the project actually needs — not on a fixed catalogue of services.
Why a single point of contact instead of several providers
Finding a designer, then an engineering office, then a manufacturer separately requires a network few individuals or small structures have. RDF combines these steps to avoid that chase for intermediaries.
It's also a matter of format: many industrial workshops turn down one-off or small-quantity projects, judged not profitable enough. RDF is built specifically for this format — a single part, a prototype, a small production run — where other structures simply don't respond.
How RDF selects and prioritizes projects
RDF can't handle every project the same way. Three criteria guide the selection: technical feasibility, budget matching the project's ambition, and clarity of the stated need. These are the three factors that determine whether a project can move forward quickly or needs to be clarified first.
Some projects require medical expertise, regulatory certification, or an industrial scale that RDF doesn't cover. In that case, the workshop points toward a better-suited partner rather than accepting a poorly matched project.
Frequently asked questions
How do I explain my idea without a technical plan?
A simple conversation is enough: what doesn't work, what you'd want instead, and the context of use. RDF turns that into a feasibility study.
How long does a project take at RDF?
It depends on the part's complexity and the prototyping needed — there's no fixed duration since every project follows its own feasibility study.
Does RDF accept single-part projects?
Yes — that's actually the format RDF is built for, unlike many industrial workshops that only accept large quantities.
What kinds of projects does RDF decline or redirect?
Projects requiring regulatory certification, medical expertise, or industrial-scale production are redirected to a better-suited partner.
Go further: