KERNAXIS
Contact

A practical guide to your enquiry

Deutsche Version

Prepare for an engineering assessment

A clear outline of the system, the decision ahead and the questions that matter helps KERNAXIS review whether an assessment fits. Start with what you can share safely; details and scope can be agreed later.

01 / CONTEXT

A useful starting point

You do not need a finished specification. Share what is known, mark what is uncertain, and connect the technical question to the decision your organization needs to make.

01

Name the decision and question

What technical question is in front of you, and what decision will the answer support? Include the requirements that matter, your current approach, the advisory outcome you want, and any uncertainty you are trying to resolve.

  • Describe the requested scope and what should be left out.
  • For an Architecture Review, identify the existing architecture or project, review focus, desired outcome and scope boundaries.
02

Describe the product and its stage

Identify the product or system being built or evaluated. It may involve hardware, software, embedded components, connected systems, or a combination, with the relevant sector context.

  • For a concept, outline what it is, its current development stage, what is already known and the decision still pending.
  • For Technical Due Diligence, identify the product, project, technology approach or development organization being evaluated. Maturity can only be discussed as far as available evidence permits.
03

Make constraints and review questions concrete

Note the requirements, current technical approach, constraints and open questions that shape the decision. Explain which areas you would like considered and why they matter to this project.

  • Depending on the project, relevant areas may include risks, dependencies, scalability, maintainability or integration; they do not all apply to every assessment.
  • A concise statement of the desired advisory outcome helps set a useful boundary for the discussion.
04

List materials and the evidence available

Name any available or planned diagrams, specifications or other project documentation, and say what each item could help clarify.

  • For feasibility or due diligence, state what evidence is available, missing or inaccessible, or that none is available yet.
  • Missing material is a limitation to record, not evidence for a conclusion.

02 / COORDINATION

Include the practical details

The enquiry form asks for the details needed to respond and coordinate a possible discussion:

  • Contact person and work email
  • Organization name, country, and city or region
  • Urgency
  • Preferred consultation window and time zone

03 / MATERIALS

Start with a non-confidential outline

Do not put confidential files, source code, credentials or sensitive personal information in the general enquiry fields. If a private upload control is visibly available, you may use it for relevant selected files and state the purpose of each one. If no private upload is shown, KERNAXIS will agree an exchange method with you before files are sent.

04 / PRIVACY

Possible AI processing is considered case by case

Possible third-party AI processing is considered case by case. The form’s AI consent is specific to this request and applies only where applicable data-protection requirements and provider safeguards are in place. AI is not used in every case and does not supply authoritative engineering conclusions. Read the privacy information.

05 / SERVICES

Choose the enquiry that fits the question

Each service can be enquired about independently. There is no required sequence or bundled package.

Each fixed price applies to its agreed scope. Product Concept & Systems Architecture and broader feasibility or strategy work are scoped and quoted; no fixed price is stated for that work.

06 / SCOPE

An enquiry starts a discussion

Submitting the form supports founder review of fit. It is not an appointment, accepted scope, contract, engagement or payment, and it does not promise a particular deliverable. Before acceptance, the assessment question, relevant material and access, scope boundaries and timing are agreed with you. Additional work is scoped separately.

The founder is KERNAXIS’s Principal Engineer and final technical authority for engineering conclusions and customer commitments.

This technical role is not regulatory, certification, safety or compliance approval.