How the matchmaker works
The Dunster Physical AI Matchmaker is a two-sided marketplace. On one side are end users: organizations with repetitive, risky or hard-to-staff work. On the other are builders: companies that make robots and physical AI, and the integrators and solution providers who deploy them. All three are members from day one. Dunster itself is a neutral broker: it matches, introduces, tracks progress and publishes the rules. It never acts as the integrator on a deal.
For end users
- Post a use case. Describe the work with text, photos, a short video or a voice note: the process step by step, the objects, the rate, the environment, who is nearby and how big the need is. Names, faces, logos and addresses stay out; the state is the only location shown.
- Dunster reviews it. Every post is checked for identifying detail before it goes live, usually within two business days.
- Builders read it anonymized. Visitors see a one-paragraph card. Registered members see the dossier. Nobody sees who you are.
- Dunster matches by hand and introduces builders whose capability cards fit, logging a reason for every builder included or excluded.
- Say yes, or pass. When you and a builder both say yes, identities and contact details are exchanged, and that builder sees your original footage. Until then, nothing.
- Report back. At 30, 90 and 180 days both sides say where the deal stands. That is the price of the platform in this release.
Any registered end user can post a use case once their profile is 40% complete. Posting a priced RFQ with sealed bids needs a verified organization and a complete profile; that flow arrives in the next release.
For builders
- List capability cards. One card per task your robots do today, each with an honest stage from D1 (concept or lab demo) to D5 (production at several sites). Stage is per capability, never per company.
- List products and services and rate each robot, component or software product with the Dunster Physical AI Benchmarking Engine, straight from its product page once the engine's return channel is live; the score and tier then land on your profile by themselves. While that channel is being switched on, the product page links to the engine and Dunster attaches the result from the engine's records instead. See Safety.
- Read the needs. Comment publicly, ask questions, and post a proposal: how you would split the work into parts and who would lead.
- Get introduced. Dunster introduces you when a card fits a need. You see the need anonymized; the end user sees your public profile. Both say yes before identities move.
- Report back and earn your record. Pilots delivered, pilots passed, reports delivered on failed pilots and status-report punctuality show on your profile as plain facts. Nothing is ranked except the safety badge.
Three identity levels
| Level | Who sees it | What it contains |
|---|---|---|
| L0, the card | Everyone, search engines included | Title, one paragraph, sector, tasks, state, size band, timeframe |
| L1, the dossier | Registered members | Goal, pain in the poster's words, process steps, objects, variability, rates, environment, people nearby, size in numbers, redacted media |
| L2, identity | One introduced pair after mutual yes, and Dunster | Organization name, contacts, existing integrator, original media |
Visitors can open three use-case pages per day; the index, builder profiles and the example posts are always open.
What Dunster never does
- Act as the integrator, or take a side in a deal.
- Rank builders for money. The only ordering is the assessed, evidence-backed safety badge, which is never for sale.
- Reveal an end user's identity before a mutual yes.
- Charge anything in this release. See How money works.