01
Intake
Share the workflow, the stakes, and the evidence you need to produce.
WORKFLOW LOGGED
CONTACT · ROUTE THE REQUEST
Bring the work. Keep the proof. Own the model.
Tell us what is shipping, who needs to review it, and what evidence security or procurement needs to see. We are independent and founder-led, and we route the request to a named team — not a generic inbox.
REPLY
One business day
Sales, support, and partnerships each have a clear route.
INDEPENDENT
Founder-led
No lab-aligned conflict. No pooled-data architecture. A second source you can defend under audit.
INTAKE
One scoping form
Workflow, stakes, reviewers, timeline — captured up front.
Workflow scoping · structured intake
Scope the request.
Tell us the workflow type, the stakes, the reviewer needs, and the timeline. We reply in one business day with the next clear step.
What happens next
Three steps. One owner. One next action.
Every request should resolve to the right team, the right materials, and the right next step.
02
Review
We route the request to sales, support, or partnerships — not a generic inbox.
OWNER ASSIGNED
03
Response
You leave with a next action: a demo, a technical follow-up, or a security review.
NEXT STEP CONFIRMED
Trust · on file before the first call
Procurement, security, compliance — already covered.
Materials, not slogans. Controls, audit trails, and the deployment posture you can hand a reviewer today — with provenance attached to the datapoint, not bolted on. The EU AI Act's training-data rules land in August 2026. Walk in ready.
Two products · one standard
Start a project.
Human Data OS — the data only people can give. App Data OS — an AI app for your field, and you keep the weights. Tell us what is shipping. We'll route the request, share the evidence on file, and end with a clear next step.
Contact intake
Accepting
OwnerRouting desk
ReplyOne business day
PathIntake → Review → Response
PacketSecurity · compliance · pricing