Request access

Start the right TRACE path.

Route hardware interest, contributor onboarding, and WELL research access through one intake before checkout or data access opens.

Intake

Route the request before the product path opens.

TRACE needs the first access surface to collect intent, not payment. That keeps hardware, research, and contributor conversations aligned with the operating layer being built.

01

Path

Hardware, contributor, and research requests route through one intake.

02

Fit

TRACE can match access to task category, sensor needs, and readiness.

03

Handoff

The form becomes the integration point for onboarding and CRM flow.

Request access

Tell TRACE where you fit.

Start with the path you need, the work you want to capture or study, and the team behind it.

Sends to the TRACE intake endpoint. CRM delivery is the next integration.

Routing

The same form can serve three early access motions.

The public site should make it easy to say what someone needs, while TRACE keeps final terms, checkout, and data access tied to the right operational process.

Hardware

Join the kit waitlist.

MMT hardware and body-sensor access should match the work setting, sensor fidelity, and onboarding path.

Research

Start with data fit.

WELL access should begin with the task category, model work, research status, and downstream usage expectations.

Contributor

Prepare for capture.

Contributor onboarding needs capture modes, consent guidance, validation rules, and a clear path for session credit.

Still exploring?

See the hardware and data paths before choosing.

The request form is the front door, but the product and WELL pages explain what TRACE is building and why access needs structure.