For work we can't prove yet.
Co-design is how we build Solutions that don't exist yet. You bring a real scenario Teleport can't fully handle today, and we build the missing pieces together over about three to four months. The finished project becomes a public Solution, with you as the launch customer. We run two or three at a time, and we never sell what isn't built.
If your work already runs today, like rehab draws, snow and ice visits or franchise checks, you don't need co-design: start with a Solution pilot.
Five stages, a go/no-go at each.
Either side can stop at any gate, and you keep what each stage produced.
- Week 0
Request
You fill in the form below. We reply within 5 business days with yes, not now, or no.
Gate: Meets the six must-haves, and the gap would serve more than one business.
- Weeks 1–2
Scoping
A half-day workshop maps your workflow: who requests, who performs, what counts as done, what evidence exists, and where we fall short. You get a draft spec extension, a safety review and written success criteria.
Gate: Both sides sign off on the success criteria and the safety review.
- Weeks 3–10
Spec and sandbox
We add the new fields to the next draft and simulate your scenario in the sandbox. You test it against your own systems (robot logs, badge scans, lockers, sensors) with no real-world risk.
Gate: The sandbox run meets the success criteria on your data.
- Weeks 11–16
Limited live pilot
Real tasks, one site, narrow scope, after a second safety review. Safety-critical scenarios may need longer.
Gate: Success criteria met with zero safety incidents.
- Then
Becomes a Solution
The scenario gets a public Solution page and template. You're named as launch customer if you agree, and move to a normal contract with the fee credited.
What each side gives and gets.
Protocol changes (new fields, condition types, conformance tests) go into the public spec. Your data, evidence, sites, configuration and prices stay private. Paid program, credited to your first contract.
- You give
- The co-design fee, a named owner, access to your environment and test data, and honest feedback at each gate.
- You get
- A Solution built around your workflow, first live use, launch-partner pricing, a voice in the spec, and the fee credited to year one.
- Teleport gives
- Product and protocol engineering, the sandbox, safety review, the verification policy for the new scenario, and pilot operations.
- Teleport gets
- Real requirements instead of guesses, a reference customer, a more complete protocol, and a Solution to offer others.
Who qualifies.
- A real, recurring scenario: about 50 or more tasks a month once live, not a one-off.
- Money or risk depends on the proof: a payment, release, compliance record or liability decision.
- A named owner with budget authority, in a weekly 30-minute check-in.
- Access to a real environment: your systems, robots, sites or logs.
- A paid commitment: the co-design fee.
- You accept the open spec: protocol changes are published openly.
- We decline or defer
- Requests to monitor, rank or report on identifiable workers
- Work with physical risk to performers that can't be designed out
- Exclusive rights to a protocol feature
- Interest in a token rather than in verified work
- Scenarios that only fit one company and wouldn't become a general Solution
- Starting with
- Custody chains and team member shares. Each one unlocks two or three Labs scenarios.
§ 05 · Request co-design
Tell us about the work.
It takes about five minutes. If open publication of protocol changes is a problem, say so: we'll talk it through rather than decline.
Scenarios waiting on a partner
- A stuck humanoid that hands the controls to a person
- A hotel room that books its own turnover
- One trailer, unloaded by humanoids, people and robots
- A phone left in a robotaxi, returned with proof
- A home robot benchmarked in fifty real kitchens
- Blood samples with no gap in the chain
- A pest outbreak treated only where it was needed