Consulting

Who this is for

• Students and student teams planning a capstone project.

Proposed scope

• Clarifying the problem and planning the technical work.
• Discussing implementation choices and reviewing your own progress.
• Identifying questions to take back to your academic supervisor.

Proposed deliverables

Indicative outputs for scoping. The final deliverables depend on an agreed brief.

• Agreed mentoring discussion scope.
• Planning notes and suggested technical review questions.
• Feedback on work prepared by the student team.

Client responsibilities

• Remain responsible for your assessed work and submissions.
• Share institutional requirements and supervisor guidance.
• Complete your own implementation and disclose external assistance where required.

Academic responsibility

Students remain responsible for their assessed academic work. Mentorship supports understanding, planning and implementation discussions. Students must follow their institution’s academic integrity rules and disclose external assistance where required.

Scope and availability

These pages describe proposed scopes for discussion. Deliverables, timelines, availability and commercial terms must be agreed before any engagement.

Submit an inquiry for review. Email notifications are not enabled; availability requires separate confirmation.

Who this is for

• Researchers defining an implementation question.
• University and research teams scoping technical collaboration.

Proposed scope

• Reviewing the domain, methods and expected technical output.
• Discussing available data, hardware and implementation constraints.
• Planning evaluation and documenting implementation decisions.

Proposed deliverables

Indicative outputs for scoping. The final deliverables depend on an agreed brief.

• Research implementation brief.
• Agreed prototype, technical notes or evaluation scope.
• Documentation of implementation decisions and observations.

Client responsibilities

• Define the research question and current stage.
• Confirm permissions for data, hardware and disclosure.
• Retain responsibility for research claims, attribution and publication decisions.

Scope and availability

These pages describe proposed scopes for discussion. Deliverables, timelines, availability and commercial terms must be agreed before any engagement.

Submit an inquiry for review. Email notifications are not enabled; availability requires separate confirmation.

Who this is for

• Founders and startup teams evaluating a physical-system concept.

Proposed scope

• Clarifying the intended application and technical constraints.
• Reviewing system architecture and prototype options.
• Separating business assumptions from technical evaluation questions.

Proposed deliverables

Indicative outputs for scoping. The final deliverables depend on an agreed brief.

• Technical scoping notes.
• Agreed prototype or architecture review scope.
• Evaluation questions and proposed development priorities.

Client responsibilities

• Share the application context and existing work.
• Identify constraints, resources and business assumptions.
• Agree priorities and retain ownership of commercial decisions.

Scope and availability

These pages describe proposed scopes for discussion. Deliverables, timelines, availability and commercial terms must be agreed before any engagement.

Submit an inquiry for review. Email notifications are not enabled; availability requires separate confirmation.