Work with KyperX

Engage KyperX on a difficult technical question.

KyperX takes on engineering, R&D, technical studies, due diligence and development collaboration where a technology or project has to be understood before it can advance. Each engagement is scoped around the question, the evidence it needs and the decision it should support.

Discuss a requirement →

Scoped to the decision
Written proposal before work
Non-confidential first enquiry

Find the right path

What do you need to do next? Define, analyse or plan a difficult system Decide whether a concept should advance Test a technology, supplier or project claim Develop something with a partner

Four engagement paths

Choose the closest need

See what each path produces and how to start, or compare all four below.

Discuss a requirement → Compare engagement paths ↓

Engagement Paths

Start from the question you need answered.

The four paths share the same engineering method. They differ in who relies on the work and the decision it serves.

Engineering & R&D

“We need a technically difficult system defined, analysed or planned for development.”

Research, requirements, system architecture, technology evaluation, preliminary techno-economic analysis and development planning.

Typical outputRequirements, architecture, option evaluations and a staged development plan.

Engineering & R&D engagements →

Technical Feasibility

“We need evidence before committing to the next development step.”

A defined study of whether a concept is technically workable within its boundary, what it depends on, and what should happen next.

Typical outputA study report ending in a recommendation to advance, revise or stop.

Technical feasibility studies →

Technology Due Diligence

“We need to test a technology, supplier or project assumption before a decision.”

A technical review of maturity, engineering assumptions, dependencies, scalability and risk, limited to the evidence provided.

Typical outputFindings that grade each material claim and name the evidence gaps.

Technology due diligence →

Collaborative Development

“We want to explore developing something together.”

Joint R&D, research and industry partnerships, supplier development, licensing discussions, joint ventures and project development.

Typical outputAgreed scope, roles, evidence, IP treatment and decision points before commitment.

Collaborative development →

Scoping

Scope follows the question, not a package.

The work is too varied for standard packages or published prices. Each proposal is built from six things:

The question or decision

What has to be known, and who will rely on the answer.

Current maturity

How far the concept, technology or project has already been defined.

Available evidence

The data, specifications and prior work the analysis can build on.

Disciplines involved

Which areas of engineering and analysis the question actually needs.

Interfaces and dependencies

The systems, infrastructure and parties the subject connects to.

Required deliverables

The form and depth of output the decision calls for.

How an Engagement Starts

Defined in writing before work begins.

An enquiry is not a commitment on either side. It starts a review of whether KyperX’s capabilities fit the question.

Enquiry

You describe the question, its stage and the timeframe. KyperX reviews the fit with its capabilities.

Discovery

Where there is a fit, a conversation sets the boundary, the evidence available and the decision the work should support.

Proposal

A written proposal states scope, method, deliverables, assumptions, exclusions, timing and fees.

Work and decision

The work is delivered against that scope and ends with findings that support a decision.

Technical Basis

The capabilities behind KyperX’s own R&D.

Engagements apply the capabilities KyperX uses in its own programs. Those programs are at concept stage, and each is described with its current maturity.