Your move-in trigger, run to completion.
One move, many providers, one execution layer. A lease, an address or an offer from your platform becomes a permissioned 60-day task graph. Your users approve; the agent executes across providers; you get completion signals instead of unqualified clicks.
Six kinds of partner already own the trigger.
They get conversion, retention and revenue per user. Schools and employers plug in the same way, with a cohort instead of a listing.
Partners pay for completed relocation outcomes.
Every flow is tested on real walk-in moves first.
Same engine, two doors.
- 01Send the trigger
A lease, address, offer or move date, with the user's consent scope.
- 02User approves the Move Profile
Budget · household · documents · rules · inventory. Permissioned, editable, theirs.
- 03The agent executes
Verify → prepare → approve → act → follow through, across providers. Status webhooks on every step.
- 04You get the outcome
Booking · activation · hand-off · exception report. Completion data improves the next case.
POST /v1/cases
{
"trigger": "lease_signed",
"move_date": "2026-10-03",
"address": "1450 Fell St, SF",
"consent": ["housing", "movers",
"activation"],
"webhook": "https://partner.example/hooks"
}
→ 201 case mv_8f2… · 42 tasks
→ hook task.completed movers.booked
→ hook task.exception isp.no_service
→ fallback
Taking 3 design partners for the proof window.
0–3 months, San Francisco, D-30 → D+30 live. 20–30 real cases, one partner KPI improved or a paid activation tested.