Product & Hardware / Ideas you can test

Develop your product. Test the next design decision.

Technical consulting, product design, CAD, prototyping and tests that answer a real question.

Work through constraints before committing to a design. Connect mechanics, electronics and software where the product needs them.

Discuss your product ↗

01 The instructionrotor.js

01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18

// A form, defined by its constraints.
const rotor = {
  ribs:   36,
  radius: 1.85,
  hub:    0.62,
  twist:  0.72,
  depth:  0.62
};

const profile = (t) => ({
  r: lerp(rotor.hub, rotor.radius, t),
  a: rotor.twist * t,
  z: rotor.depth * sin(PI * t)
});

repeat(rotor.ribs, (angle) => {
  loft(profile, { angle, width: 0.032 });
});

PARAMETRIC STUDY / 001JavaScript

02 The geometryPerspective / 3D

RIBBED ROTOR
36 ribs / 0.72 rad twist

POINTS → WIREFRAME → SOLIDPerspective study

Code and geometry. Taking shape together.

Illustrative parametric geometry—not a delivered machine, validated rotor design or manufacturing-ready specification.

Ways to work together

Choose a project you can put to work.

Start with the result you need. These are starting points for a scoped engagement, not fixed packages. The quote defines the deliverables, boundaries and success test for your project.

Concept & CAD development

For someone with a product idea, sketch or requirements that need a tangible design.

Deliverables, scope & handover

Deliverables: Concept options and CAD for the agreed features, with key constraints and unresolved design questions recorded.
Scope & cost drivers: Part count, geometry, interfaces, available measurements and the level of drawing detail.
Success test: The model addresses the agreed dimensions and interfaces; remaining assumptions are explicit rather than hidden in a render.
Handover: The agreed native or exchange files, revision notes and the next questions for prototype or fabrication review.

Improve an existing prototype

For a team with a model or physical prototype and a specific fit or function problem.

Deliverables, scope & handover

Deliverables: A focused design revision and a prototype plan or build where explicitly included.
Scope & cost drivers: Condition of existing files, measurement needs, affected parts, materials and fabrication arrangements.
Success test: The revised feature is checked against the agreed fit or function criteria, with observations tied to the tested revision.
Handover: Revised files, change notes, prototype specifications and any included test findings.

Focused design test

For a team that needs evidence before committing to the next design or fabrication step.

Deliverables, scope & handover

Deliverables: A test plan for one defined question, agreed measurement or analysis work, and a findings report.
Scope & cost drivers: Test setup, equipment, sample preparation, measurement method and specialist involvement.
Success test: The report answers the agreed question—or clearly records an inconclusive result and what remains unverified.
Handover: Method, available data, revision identity, findings and recommended next steps; not a certification or production approval.

How scope becomes a quote ↗

Illustrative example / CAD modification + prototype

Test the interface before rebuilding the assembly.

An enclosure fits the electronics but leaves too little room around a cable connector. Rather than commission another complete assembly, isolate the interface: confirm the connector envelope, cable bend, fastener access and the surrounding parts.

Start from what exists

Bring a sketch, CAD model or physical prototype, plus the intended use and constraints. Identify the current revision and which dimensions are measured rather than assumed. Check whether a stock enclosure or different connector solves the problem first.

Make a focused revision

Revise the affected geometry and choose a prototype method suited to the fit question. Agree who supplies components and arranges fabrication; do not assume every material or process is available in-house.

Record what the test shows

Check assembly access and fit against agreed criteria. Record the revision, parts used, observations and unresolved risks. A fit check does not establish long-term durability, certification or readiness for mass production.

Illustrative engagement, not a delivered product or performance claim. Files, prototype arrangements and specialist review depend on the agreed scope.

Explore the enclosure-interface example ↗

What should you prepare for a manufacturer?

From prototype to manufacturer / Practical guide

Prepare a package a manufacturer can assess.

A render is not a manufacturing brief. Before requesting fabrication or production, help the manufacturer understand what is defined, what is flexible and what still needs a decision.

Purpose and quantity
Explain intended use, environment, expected quantities and whether the request is for a fit prototype, functional test or production quote. Name the critical feature the next build needs to prove.
Revision and geometry
Give every supplied model and drawing a matching revision identity. Identify critical dimensions, interfaces, tolerances and which requirements remain provisional. Agree useful native and exchange formats with the recipient instead of assuming one format fits every process.
Materials and components
Provide the proposed materials, finishes and a bill of materials where relevant. Distinguish purchased components from fabricated parts, identify approved substitutions and flag unavailable or unconfirmed items.
Evidence and open questions
Include the test purpose, method and findings tied to the tested revision. State what has not been verified. Ask the manufacturer about process limits, assembly access, inspection needs and changes required for their production method.

Agree deliverables, ownership and fabrication responsibilities before work begins. Tooling, production qualification and regulatory or safety-critical review are separate decisions requiring the appropriate specialists; a prototype handoff does not imply those services are included.

Need help with a physical-process experiment?

Supporting work / Physical-process development

Make the next experiment informative.

Where a product depends on a physical process, a bounded project may include documenting the current method, planning a focused experiment and analysing the resulting data. Define the question, variables, measurement method and decision the result should support.

This is supporting development work, not a claim of plant engineering, accredited testing or guaranteed scale-up. Facility access, equipment, safety responsibilities and any specialist involvement must be agreed for the particular engagement.

Where software meets the physical world

A product is more
than its enclosure.

A useful interface, a test tool or a connection to operating data can be part of the same development effort.

Explore the software side ↗

Hardware–software integration

Scope device interfaces, data capture, controls and operator tools around the actual hardware. Agree how the system behaves when a connection fails and what must stay under human control.

What you can take away

Depending on the scope: concept options, CAD files, prototype specifications, a test plan, findings and supporting software. Deliverables and ownership are agreed before work begins.

Specialist review and validation

Safety-critical, regulated or certification-dependent products need appropriate qualified review. A prototype or simulation is not certification, production validation or a guarantee of performance.

Start with one project.

Bring us a process you want to improve or a product you want to develop—we’ll examine the work, recommend an approach, and agree on the scope, price and what success looks like before building.

Pricing & working together ↗

Discuss your product

Develop your product. Test the next design decision.

Choose a project you can put to work.

Concept & CAD development

Improve an existing prototype

Focused design test

Test the interface before rebuilding the assembly.

Start from what exists

Make a focused revision

Record what the test shows

Prepare a package a manufacturer can assess.

Purpose and quantity

Revision and geometry

Materials and components

Evidence and open questions

Make the next experiment informative.

A product is morethan its enclosure.

Start with one project.

A product is more
than its enclosure.