Feasibility studies
Technical questions investigated and answered before significant design or tooling spend.
Discuss thisPrototyping & ProductPrototypes built to answer
Prototypes built to answer
a question, not to look impressive.
A prototype is only worth building if it reduces uncertainty. We define the question the prototype must answer, choose the cheapest fidelity that can answer it, build it, and report what the result actually means for the product.
- Question-led builds
- Feasibility before investment
- Reported findings, not demos
Why prototypes waste moneyA pretty prototype that answers
A pretty prototype that answers
no useful question.
The most common waste in product development is building something that looks finished and settles nothing. A machined enclosure is no help if the question was whether the sensor can detect the target at distance, and a working demo is no help if nobody recorded what it cost or what failed.
We agree the question and the success criteria first, build the cheapest thing that can answer it, and report the result including the failures. The prototype is an experiment with a defined outcome.
Fidelity is chosen, not assumed. A simulation may answer the question more cheaply and faster than a board, and we will say so rather than build something because it was requested.
- 01Question agreed first
The uncertainty to be resolved is defined before anything is built, with success criteria written down.
- 02Cheapest sufficient build
Fidelity chosen to answer the question at the lowest sensible cost, not the highest available.
- 03Failures recorded
Results reported including what did not work, so decisions are made on evidence.
- 04Reusable insight
Findings fed into the next stage instead of being lost when the prototype is put in a drawer.
- Question firstThe uncertainty to resolve is agreed and written down before any build begins.
- Right fidelityThe cheapest prototype that can answer the question is chosen deliberately.
- Failures reportedResults include what did not work, not only the successful parts.
- Findings carried forwardConclusions feed into the design rather than stopping at the demonstration.
What we deliver
Prototyping and concept services
Engagements range from a short feasibility study to a sequence of builds that de-risk a product before tooling.
Proof of concept
The riskiest part of the design proven at the lowest sensible fidelity.
Discuss thisFunctional prototypes
Representative builds that test the product against its real requirements.
Discuss thisConcept modelling
Appearance, ergonomics and handling explored before mechanical detail is fixed.
Discuss thisIterative build cycles
Successive builds, each testing a specific hypothesis and recording the result.
Discuss thisDesign-for-manufacture input
Prototype findings fed back into the design so production is not a surprise.
Discuss thisWhat is included in scope
Scope is agreed in writing before work starts, so deliverables and responsibilities are clear.
- Question & criteriaThe uncertainty to resolve and the evidence that would resolve it agreed up front.
- Approach & fidelitySimulation, model or hardware approach chosen to answer the question economically.
- BuildThe prototype designed, built and tested against the agreed criteria.
- Testing & measurementMeasurements taken and recorded, including negative results and limits found.
- Findings & recommendationsResults reported with conclusions and a clear recommendation.
- Next-stage inputFindings carried into the design, so the following stage starts from evidence.
Capabilities
Prototyping capability
The discipline is in choosing what to build and what to measure, not in the build itself.
Feasibility investigation
Technical questions researched and answered before money is committed.
Proof of concept
Risky elements proven early at the lowest sensible fidelity.
Functional prototypes
Representative builds tested against real requirements and real conditions.
Concept & form studies
Appearance, ergonomics and handling explored before detail is fixed.
Sensor & system testing
Measurements taken on real targets rather than assumed from datasheets.
Rapid iteration
Successive builds testing one hypothesis each, with results recorded.
Failure analysis
Failures reproduced and diagnosed rather than worked around quietly.
Manufacturing feedback
Prototype experience fed into the design so production is repeatable.
Faster iteration on physical form is covered in rapid prototyping and 3D prototyping; production planning in manufacturing support.
Our process
How a prototype is approached
Define the question, choose the cheapest sufficient build, test it, and report the result.
Question & criteria
The uncertainty and the evidence needed to resolve it agreed before building.
Success criteriaApproach
Simulation, model or hardware approach chosen for cost and time to answer.
Chosen approachBuild & test
Prototype built and measured against the agreed criteria.
Tested prototypeFindings & recommendation
Results reported, including failures, with a recommendation for the next step.
Findings report
Technologies
Prototyping methods
The method is chosen to answer the question, and the tool follows the method rather than the other way around.
- SimulationCircuit, thermal and mechanical simulation used where it is faster and cheaper than building
- Breadboard & evalEvaluation boards and modules used to prove vendor claims and interface behaviour
- Custom PCBsPurpose-built boards where a module cannot test the actual question
- 3D printingRapid form and fit iteration without committing to tooling
- Machined prototypesPrecise mechanical builds where printed parts are not representative
- Test & measurementInstruments and methods chosen so results are defensible
We prefer to answer a question with simulation or an evaluation board when that is sufficient. Hardware is built when the question genuinely requires it, not because a build was quoted.
Industries
Built around how your product is actually used.
Handling, temperature, ingress and certification expectations are captured before tooling, not after the first enclosure.
Industrial
Control panels, motor drives, gateways and automation hardware for continuous operation.
IndustrialAutomotive
In-cabin electronics, LED drivers and control units designed around automotive electrical and thermal expectations.
AutomotiveHealthcare
Diagnostic and monitoring devices designed with patient safety and compliance in mind.
HealthcareEnergy & power
Monitoring, metering, conversion and control electronics for energy and power systems.
Energy & powerRailways
Onboard and signalling electronics built for vibration, temperature cycling and long maintenance cycles.
RailwaysBeauty & wellness
Skin, hair and wellness devices with careful low-voltage design and safe user interfaces.
Beauty & wellnessCapability examplesSee the engineering problem.
See the engineering problem.
Imagine the possibilities.
The scenarios below illustrate the kind of work we do — they are not published client case studies or measured results. Ask us about relevant experience for your product.
Illustrative · New concept
A concept that had to be proven cheaply
Challenge: The team needed to know whether the idea worked before committing to tooling.
Approach: A proof-of-concept build answering one specific question before further investment.
Explore prototypingIllustrative · Mechanical fit
A housing that had to fit a crowded board
Challenge: Boards, connectors and controls competed for a limited internal volume.
Approach: Internal layout developed in 3D, with fit verified before any tooling was cut.
Explore mechanical designIllustrative · Production readiness
A design moving towards manufacturing
Challenge: The prototype worked, but documentation and assembly were not repeatable.
Approach: Design-for-manufacture review and a complete release package prepared for the assembler.
Explore manufacturing supportFrequently asked questionsGood questions.
Good questions.
Clear starting points.
What buyers usually want to know before scoping this kind of work.
Ask about your requirements →What prototyping and concept services do you offer?
Feasibility studies, proof-of-concept builds, functional prototypes, concept modelling, iterative build cycles, and design-for-manufacture input.
How do you decide what to prototype?
We start from the uncertainty that would most change the project, and build the cheapest thing that can resolve it. Sometimes that is a simulation or an evaluation board rather than a custom board.
Do you report failures as well as successes?
Yes. A prototype that shows something will not work has still done its job, and reporting it is what prevents the team committing to the same approach later.
Can you work with our existing prototype?
Yes. We can evaluate an existing prototype against the question it was meant to answer, identify what it does and does not prove, and recommend what to build next.
How many iterations are usually needed?
It depends on the uncertainty. We aim for the fewest builds that resolve the question, and say so at the proposal stage rather than after several rounds of testing.
Do you help move from prototype to production?
Yes. Findings from the prototype are fed into the design, and the documentation and design-for-manufacture work needed for production is part of the later stages.
Related services
Prototyping & Product
Explore the rest of the programme, or get in touch about this service directly.
Start your projectLet’s find the question
Let’s find the question
worth building for.
Tell us what you are unsure about and what decision depends on the answer. We will tell you whether a prototype is needed, and what the cheapest useful one would be.
No complete specification needed. A short brief of your product and goals is enough to start.
What happens next?
- Share your product goal, application and current stage.
- Discuss the components, interfaces and constraints that matter.
- Agree a practical next step and the scope for a proposal.