Service architecture

The biomechanical intelligence layer for human performance.

AKMI is organized around one operating loop: structured assessment, AI-assisted interpretation, human review, protocol execution, and reassessment. This map shows how the public website, Coach Suite, Client App, education layer, wearables, and professional network connect without becoming one overloaded interface.

Platform definition

Biomechanical intelligence infrastructure, not a replacement for human professionals.

AKMI Human Performance combines structured biomechanical assessment, AI-assisted interpretation, and human review to help people and professionals make better decisions about movement, physical performance, and musculoskeletal health. The platform is designed to evaluate, interpret, monitor, and optimize physical function more consistently without removing the coach, therapist, clinician, or qualified professional from the decision loop.

Defensibility architecture

Core first. Enablers second. Moats last.

AKMI should not behave like a bundle of disconnected AI tools. Every layer must either strengthen the biomechanical core, reduce operational friction, or compound network and data effects after quality is proven.

Ring 01 Core

The non-replicable center: proprietary biomechanical reasoning and longitudinal evidence.

Fund this first. No enabler scales until the structured biomechanical output is machine-consumable and human-reviewable.

  • Biomechanical Intelligence Engine
  • AKMI biomechanical kernel
  • Longitudinal data flywheel
Monetization
Seat fee foundation; not sold as a detached commodity.
Value metric
Analysis time down; inter-rater consistency up; structured findings reuse up.
Ring 02 Enablers

Commodity in isolation, defensible only when connected to Core evidence.

Build only when each enabler consumes Core output and returns useful flywheel data.

  • Programming Assistant
  • Reassessment Intelligence
  • Client Assistant
  • Wearable Intelligence
  • Marketing, sales, and funnel automation
  • Visual evidence and agentic discovery
  • Clinic intelligence diagnostics
Monetization
Productivity, retention, and capacity expansion for coaches.
Value metric
Protocol creation time down; reassessment cadence up; churn risk down; coach capacity up.
Ring 03 Moats

Network, credential, data, and switching-cost effects that compound after Core and Enablers mature.

Activate after sufficient data density, quality control, and professional supply are proven.

  • Coach Business Operating System
  • Student Suite
  • Certification permissions
  • Marketplace
  • Community and professional network
Monetization
Higher LTV, marketplace take-rate, certification revenue, and ecosystem lock-in.
Value metric
LTV up; active managed clients up; certified supply quality up; qualified demand routing up.

Investment sequence

Build what protects the moat before building what looks attractive.

This matrix keeps the product roadmap honest: the Core earns priority, enablers must consume Core evidence, and network effects wait until quality and data density are real.

Priority Service Ring Defense LTV Build rule
P0 Biomechanical Intelligence Engine Core High High Build and harden first; every other service depends on its structured output.
P1 AI Programming Assistant Enabler High High Build once findings, hypotheses, constraints, and coach approval are machine-readable.
P1 Reassessment Intelligence Enabler High High Build with the programming loop because it proves change and feeds retention.
P2 24/7 AI Client Assistant Enabler Medium High Build after approved protocols, escalation rules, and answer boundaries are stable.
P2 Wearable Intelligence Layer Enabler High Medium Build provider abstraction first; interpret readiness only inside the biomechanical context.
P2 Visual Evidence Loop Enabler High when tied to findings and reassessment deltas High Build through reports and reassessment; every visual claim must cite evidence, confidence, and coach approval.
P2 Agentic Discovery and Action Layer Enabler Medium Medium Start with public metadata, schema, source-grounded answers, and safe action boundaries; never expose private app state.
P2 Clinic Intelligence Blueprint Enabler Medium when tied to AKMI operating standards High Ship as a public diagnostic with calibrated ranges and 90-day roadmap before deeper Business OS automation.
P3 Coach Business Operating System Moat High High Build after enough lifecycle, reassessment, adherence, revenue, and churn data exists.
P3 AI Marketing Copilot Enabler Low Medium Keep thin as acquisition leverage; do not let it steal focus from Core quality.
P3 Coach Local Growth Engine Enabler Medium when tied to AKMI-approved proof High Ship as templates and workflow automation now; custom build only after conversion and retention lift are measured.
P4 AI Sales Assistant Enabler Low Medium Integrate after lead sources, fit scoring, and follow-up stages are explicit.
P4 Coach Funnel Builder Enabler Very low Low Prefer integration or templates before custom build; this is not the moat.
P4 Student Suite Moat High Medium Build around case competence, labs, audits, and permissions rather than passive content.
P5 Certifications and Marketplace Moat High High Activate after supply quality, demand density, and outcome audits are credible.

Choose your entry point

Different roles should not be forced through the same door.

The fastest path is the one that matches the user's job: client clarity, full coaching, professional operations, field work, education, or organizational rollout.

I am a client

I need to understand what is limiting my movement, training, pain, or performance.

Public website -> Client App

A protocol should come after structured evidence, not before it.

Start with assessment
I want ongoing coaching

I want AKMI to manage training, nutrition, reassessment, and follow-through.

Public website -> Coach review -> Client App

The service must stay assessment-led, not habit-tracker-led.

Apply for full coaching
I am a coach or clinic

I need a professional operating system for assessment, programming, reporting, and client progress.

Coach Web Platform

Use desktop for deep decisions; reserve mobile for fast field work.

Enter Coach Suite
I work hands-on with clients

I need floor-side capture, cueing, drill decisions, and quick notes during 1:1 sessions.

Coach Mobile App

Capture quickly, then escalate complex planning back to the Coach Suite.

Open coach mobile
I want to study AKMI

I want certification, case practice, practical labs, and a shared professional standard.

Student Suite

Education should unlock permissions only after observed competence.

Apply for education
I run a team or institution

I need a repeatable assessment-to-outcome system for coaches, clinics, or organizations.

Marketplace and AKMI Master Layer

Scale only where quality control, onboarding, and outcome reporting are ready.

Discuss enterprise fit

Ecosystem layers

One data logic, different interfaces for different users.

Athletes, older adults, clients, coaches, clinics, students, and AKMI operators should see different interfaces while sharing the same evidence model underneath.

01

Structured assessment protocol

A repeatable evaluation process identifies movement patterns, functional limitations, asymmetries, and opportunities for improvement.

02

AI hypothesis engine

AI turns assessment data into hypotheses, recommendations, report drafts, and protocol suggestions that remain reviewable.

03

Human review layer

Certified professionals approve, adjust, reject, or escalate outputs when context, symptoms, uncertainty, or judgment require it.

04

Coach Suite operating system

Professionals manage assessments, programming, communication, reports, adherence, business operations, and client follow-up.

05

Client App execution layer

Clients see today's protocol, progress, education, recommendations, reassessment status, and messages in a simpler interface.

06

Wearable context layer

Recovery, sleep, HRV, training load, activity, and adherence signals inform context without becoming isolated decision rules.

07

Student Suite and certification

Education, labs, cases, exams, simulations, and continuing development create a shared operating standard for professionals.

08

Certified professional network

The marketplace connects users with audited professionals by language, location, specialty, experience, and need.

Operating loop

Assessment to outcome, not disconnected features.

The map is designed to reduce decision friction: users understand where to begin, coaches understand what to review, and AKMI can scale without losing clinical discipline.

1 / Assess

Assessment-first entry

Free tools, intake, posture, ROM, foot mechanics, exercise video, and goal context.

2 / Explain

Evidence report

A coach-readable and client-readable brief: what changed, what matters, and what is uncertain.

3 / Prescribe

Protocol compiler

Training, mobility, cueing, recovery, and nutrition decisions matched to the client profile.

4 / Execute

Client app and coach suite

Daily sessions, effective load, compliance, readiness context, and coach review in one loop.

5 / Reassess

Delta engine

Baseline versus current: ROM, pain, output, adherence, risk, and next intervention.

Evidence graph

Every decision leaves a trail.

AKMI becomes harder to copy when assessment, hypothesis, protocol, execution, reassessment, and quality review are connected as one evidence model.

Movement Evidence Graph

From observation to verified next action.

The value is not a single scan, chart, or AI answer. The value is the longitudinal chain that explains why a protocol exists, whether it was executed, and what changed.

Coach review

Assessment finding

Captured

ROM, asymmetry, posture, gait, movement video, symptoms, equipment, goals, and constraints.

Decision use

Defines what problem AKMI is actually trying to solve before any plan is written.

AI draft + human approval

Hypothesis

Captured

Pattern, joint or region, likely limiter, confidence, uncertainty, and red-flag status.

Decision use

Turns raw observations into a reviewable explanation instead of a black-box answer.

Coach platform

Protocol decision

Captured

Exercise, drill, cue, progression, regression, loading target, volume, focus, and risk note.

Decision use

Connects the hypothesis to a concrete intervention the client can execute.

Client app + coach mobile

Execution evidence

Captured

Completion, sets, reps, effective load, RPE, symptoms, readiness, adherence, and session notes.

Decision use

Shows whether the plan was actually delivered and tolerated in the real world.

Delta engine

Reassessment delta

Captured

Baseline versus current ROM, output, pain, asymmetry, confidence, compliance, and wearable context.

Decision use

Separates real progress from noise and guides the next protocol cycle.

AKMI master layer

Quality standard

Captured

Coach overrides, audit trail, certification status, case quality, escalation, and outcome history.

Decision use

Protects trust as AKMI scales across coaches, clinics, languages, and countries.

Operating intelligence

AI is useful only when it removes work and strengthens human review.

AKMI uses intelligence engines to turn repeated professional work into evidence, decisions, escalation, and proof artifacts. The coach or qualified professional remains responsible for clinical judgment.

01 Core moat

Biomechanical Intelligence Engine

Turn structured assessments into reviewable hypotheses, limits, confidence, and next actions.

Surface
Coach web platform
Output
Hypothesis, evidence summary, uncertainty note, priority regions, and next-test recommendation.
Human gate
Coach approves, edits, rejects, or escalates before the client sees the interpretation.
02 Core-fed enabler

AI Programming Assistant

Convert evidence, objectives, constraints, equipment, and readiness into coach-approved protocols.

Surface
Coach web platform
Output
Protocol draft, exercise blocks, progressions, regressions, cueing, risk notes, and reassessment trigger.
Human gate
Coach owns final prescription, loading, substitutions, and escalation decisions.
03 Core-fed enabler

24/7 AI Client Assistant

Answer repetitive client questions instantly and escalate symptoms, uncertainty, or red flags.

Surface
Client app
Output
Client answer, setup cue, adherence nudge, clarification request, or coach escalation ticket.
Human gate
Anything clinical, painful, contradictory, or low confidence is routed back to the coach.
04 Core-fed enabler

Wearable Intelligence Layer

Translate sleep, HRV, load, activity, and adherence into today's dose and expectation changes.

Surface
Client app + Coach web platform
Output
Readiness context, dose adjustment, recovery note, coach alert, and confidence level.
Human gate
Wearables adjust the decision context; they do not override assessment or coach review.
05 Ecosystem moat

Coach Business Operating System

Surface churn risk, LTV, pipeline, utilization, retention opportunities, and operating leaks.

Surface
Coach web platform
Output
Risk list, follow-up queue, upsell/downsell opportunity, exit reason, and business health view.
Human gate
Coach or AKMI admin decides outreach tone, commercial action, and account intervention.
06 Core-fed enabler

AI Marketing Copilot

Turn cases, outcomes, and coach expertise into reusable campaigns, posts, emails, and landing drafts.

Surface
Website + Coach web platform
Output
Post, carousel, reel script, email, newsletter, CTA, lead magnet, and landing draft.
Human gate
Coach approves claims, privacy, positioning, and brand fit before publication.
07 Core-fed enabler

Reassessment Intelligence

Compare baseline versus current and explain change, uncertainty, and next protocol implications.

Surface
Coach web platform + Client app
Output
Delta summary, likely driver, remaining limit, next test, next intervention, and client explanation.
Human gate
Coach validates whether the observed change is clinically meaningful or just noise.
08 Ecosystem moat

Education Copilot

Tutor professionals with cases, quizzes, simulations, and practical reasoning checks.

Surface
Student Suite
Output
Explanation, quiz, case simulation, gap analysis, remediation path, and permission recommendation.
Human gate
Certification and marketplace permissions require observed competence and audit review.
09 Core-fed enabler

AI Sales Assistant

Qualify leads, suggest follow-ups, protect speed-to-lead, and route opportunities.

Surface
Marketplace + Coach web platform
Output
Fit score, routing decision, follow-up draft, booking prompt, and lost-reason capture.
Human gate
Coach or AKMI admin approves pricing, promises, and final sales communication.
10 Core-fed enabler

Coach Funnel Builder

Generate lead magnets, pages, forms, and nurture flows from the coach's service strategy.

Surface
Website + Marketplace
Output
Landing page outline, lead form, nurture sequence, qualification path, and conversion checklist.
Human gate
Coach approves public claims, audience fit, data capture, and follow-up process.
11 Core-fed enabler

Coach Local Growth Engine

Create local/niche acquisition kits that help coaches win clients in their market without leaving AKMI.

Surface
Website + Marketplace + Coach web platform
Output
Local landing brief, neighborhood/niche positioning, lead magnet angle, outreach sequence, booking CTA, and routing rule.
Human gate
Coach or AKMI admin approves claims, privacy, pricing, territory, and follow-up before any public launch.
12 Core-fed enabler

Visual Evidence Loop

Convert findings, deltas, and rationale into client-readable visual evidence that improves trust and adherence.

Surface
Coach web platform + Client app + Reports
Output
Evidence card, baseline/current comparison, progress story, next milestone, client explanation, and coach review prompt.
Human gate
Coach validates whether visuals, claims of change, and education notes are accurate before client exposure.
13 Core-fed enabler

Agentic Discovery and Action Layer

Make public AKMI services, tools, education, pricing, and safe next actions understandable to search engines and AI agents.

Surface
Public website + Marketplace
Output
Agent-readable knowledge map, safe action list, source-grounded answers, booking routes, and noindex/private-surface guardrails.
Human gate
AKMI admin approves public knowledge, action permissions, and any change that could expose private or clinical data.
14 Core-fed enabler

Clinic Intelligence Blueprint

Turn coach or clinic intake into a score, opportunity range, and 90-day operating plan before a sales call.

Surface
Public website + Coach web platform
Output
Readiness score, biggest operating gap, opportunity range, recommended AKMI path, CRM routing tag, and 90-day roadmap.
Human gate
AKMI admin reviews claims, scoring assumptions, commercial recommendations, and outreach before scaling the funnel.

Service options

What a client can buy or enter through.

The service ladder should feel simple from the outside while preserving the full biomechanical decision engine underneath.

Decision pathways

How different users should navigate AKMI.

Each pathway converts a vague problem into a clear next step. This is where AKMI protects the user from choosing the wrong product.

Client services

For people who want a clear answer, a protocol, or ongoing coaching.

I do not know what is limiting me.
Free tool -> Complete Biomechanical Assessment -> report review
Best next: Full Assessment
One lift or movement keeps breaking down.
Exercise video -> Exercise Mastery Report -> correction protocol
Best next: Exercise Mastery
I need a plan, not a generic template.
Assessment -> equipment and constraints -> training cycle
Best next: Training
I want the whole system managed for me.
Full assessment -> training -> nutrition -> weekly review -> reassessment
Best next: Full Coaching

Coach and clinic surfaces

For professionals who need operating leverage, client clarity, and better follow-through.

I need to manage client progress clinically.
Coach Suite -> client dashboard -> assessment history -> protocol state
Best next: Coach Suite
I need a client-facing explanation tool.
Clinical avatar -> findings -> hypotheses -> cueing -> next protocol
Best next: Clinical Workstation
I need on-the-go client decisions.
Coach mobile -> triage -> upload or live scan -> cueing and drills
Best next: Coach Mobile

Navigation mindmap

The complete service and product structure at a glance.

This separates what each surface is responsible for, so clients, coaches, clinics, and AKMI operators do not get pushed through the same interface.

Product surfaces

Separate surfaces, one shared evidence loop.

Public website, coach web platform, client app, and coach mobile app should never be treated as the same interface. Each has a different job.

AKMI product surface responsibilities
Surface User Primary job Navigation
Public website Visitor, client, coach, clinic, enterprise buyer Understand the category, choose the right path, and convert. Open path
Coach web platform Coach, clinic operator, AKMI master admin Assess, plan, review, manage clients, and run the business layer. Open path
Client app End client Execute the protocol, understand progress, log feedback, and prepare reassessments. Open path
Coach mobile app Coach on the floor or between sessions Triage, capture video, make field decisions, and prescribe cueing or drills quickly. Open path

Handoff matrix

What moves between surfaces, and what must never leak.

This is the operating discipline behind the ecosystem: each product passes the right evidence forward while protecting users from unnecessary complexity.

Public website
->
Application or service path
Trigger

A visitor identifies a pain, goal, role, or need.

Evidence passed

Intent, language, user type, urgency, target outcome, and service fit.

Guardrail

Route toward assessment or qualification before promising a protocol.

Coach web platform
->
Client app
Trigger

A coach approves a protocol, session, report, or reassessment action.

Evidence passed

Objective, constraints, variables, focus, risks, expected response, and review status.

Guardrail

Expose only the executable next action, not coach-only operating complexity.

Client app
->
Coach QA
Trigger

A session is completed, skipped, modified, or paired with symptoms.

Evidence passed

Sets, reps, effective load, RPE, pain, readiness, adherence, notes, and media when relevant.

Guardrail

Do not progress the block until exposure and response are interpretable.

Coach mobile field mode
->
Coach web platform
Trigger

A floor-side observation requires deeper programming, reporting, billing, or QA.

Evidence passed

Client selected, issue tag, video capture, cue, drill, escalation note, and confidence.

Guardrail

Mobile handles fast capture and triage; desktop handles long-form planning.

Wearable context layer
->
Protocol compiler
Trigger

Recovery, sleep, load, or fatigue changes the decision context.

Evidence passed

Source quality, date freshness, trend direction, conflicts, and relevance to the session.

Guardrail

Wearables adjust dose and expectations; they do not override human review.

Student Suite
->
Marketplace and AKMI Master Layer
Trigger

A professional completes certification, case review, and ongoing quality gates.

Evidence passed

Exam result, practical lab, case audit, permissions, specialty, language, and quality score.

Guardrail

No marketplace visibility without auditable competence and active quality controls.

Surface contracts

Route by job, not by device.

AKMI should feel simple because each product owns a precise job. The handoffs matter: the public site sells trust, the Coach Suite makes decisions, the Client App captures execution, and mobile surfaces support fast field work.

Public Website

Owns

Trust, education, qualification, SEO demand, pricing clarity, and the first routing decision.

Must not

Behave like the product, hide prices behind vague claims, or overload visitors with internal operating detail.

Handoff

Sends qualified users to application, service checkout, Coach Suite login, or the client portal.

Coach Web Platform

Owns

Assessment review, programming, protocol QA, reporting, reassessment deltas, client operations, and business control.

Must not

Become a consumer fitness feed, bury clinical decisions inside generic dashboards, or force mobile field work into desktop workflows.

Handoff

Publishes executable sessions to the Client App and quick actions to Coach Mobile.

Client App

Owns

Today's plan, workout execution, adherence, education, progress understanding, post-session insight, and reassessment buy-in.

Must not

Expose coach-only complexity, let users self-diagnose beyond boundaries, or show wearable data without a decision meaning.

Handoff

Returns execution evidence, symptoms, readiness, questions, and completion state to the coach.

Coach Mobile App

Owns

On-the-go triage, fast client lookup, 1:1 capture, issue tagging, cueing, drill prescription, and session notes.

Must not

Attempt full desktop programming, long reporting, or admin-heavy setup on a small screen.

Handoff

Escalates deeper programming, reporting, billing, and QA work back to the Coach Web Platform.

Student Suite

Owns

Curriculum, practical labs, case interpretation, exams, certification gates, mentorship, and continuing education.

Must not

Act as a marketing course without operational permissions or certify people without observed case competence.

Handoff

Unlocks coach permissions, quality scores, marketplace eligibility, and continued audit requirements.

Marketplace and AKMI Master Layer

Owns

Certified professional discovery, quality control, partner pipeline, institutional accounts, coach QA, and network trust.

Must not

Launch before supply quality is auditable or let demand bypass the AKMI evidence standard.

Handoff

Routes users to the right certified professional and routes professional risk back to QA or education.

Quality gates

What must be true before each surface scales.

AKMI should grow by raising the evidence standard, not by adding disconnected interfaces. These gates define what each surface must prove before expansion.

Public website

Standard

Trust, clarity, SEO, pricing, and role routing are understandable in one visit.

Ready when

A visitor can choose the right assessment, coaching, education, or enterprise path without a sales call.

Risk if missing

Traffic converts into confusion, not demand.

Owner

Marketing + product

Coach web platform

Standard

Assessment, protocol, reassessment, reporting, client operations, and business state share one evidence model.

Ready when

A coach can review the client, decide progress/hold/regress/retest/refer, and document why.

Risk if missing

The suite becomes a generic CRM with clinical-looking dashboards.

Owner

Coach ops + QA

Client app

Standard

The client sees today's plan, what matters, what changed, what to do next, and when to ask for help.

Ready when

A client can execute the session and understand the reason without seeing coach-only complexity.

Risk if missing

Adherence drops because the product feels like tasks instead of guidance.

Owner

Client experience

Coach mobile app

Standard

Fast client lookup, floor-side capture, cueing, issue tags, drill prescription, and escalation.

Ready when

A coach can make a field decision in under two minutes and finish deeper work later on desktop.

Risk if missing

Mobile becomes a cramped duplicate of the Coach Suite.

Owner

Field operations

Student Suite

Standard

Curriculum, cases, practical labs, exams, mentorship, and permissions are connected.

Ready when

A professional earns capabilities through observed competence, not passive content consumption.

Risk if missing

Certification becomes a course business instead of an operating standard.

Owner

Education + certification

Marketplace and AKMI Master Layer

Standard

Supply quality, ranking, matching, audit trails, outcomes, and escalation rules are active.

Ready when

A user can be routed to the right certified professional without bypassing AKMI quality controls.

Risk if missing

Marketplace growth scales trust failures faster than revenue.

Owner

AKMI master admin

Not sure where to start? Start with assessment.

The safest commercial promise for AKMI is not a generic transformation claim. It is a better decision system: identify the limiting pattern, explain it clearly, select the right protocol, and reassess whether the intervention worked.