A concrete goal and the people, notes or sources you explicitly allow the product to consider.
Start with a goal.
Start with a goal. Explore who may be relevant, why they could help, and what you still need to find out.
As you refine the overview for Alex, you decide the project could benefit from an adviser. A confirmed example note says Alex knows Sam through a product team. Whether either person fits the goal, is available or wants to help is still unknown.
Ask
Turn a goal into a thoughtful next step.
WHAT WOULD YOU LIKE HELP WITH?Example records only. No real people are searched.
Describe the help you are looking for.
Read the UI demonstration walkthrough
- Add the example goal. Find a product adviser for a short project.
- Explore the goal. The interface checks the selected example notes.
- Inspect why Sam appears. Read the note behind the result.
- Return to the result. Keep those limits in view.
- Review the introduction path. Open the possible route through Alex.
- You → Alex → Sam. Review the path before deciding whether to ask.
This illustrates the proposed interaction. It is not a recording of a released app. Planned.
A clear input.
A considered outcome.
- 01
Describe the goal: an adviser, referral, client or supplier.
- 02
Compare possible connections using the supporting evidence.
- 03
Review the unknowns before deciding who to approach.
Possible people to approach, with evidence for relevance, source context and open questions. You can continue to a person’s profile or an introduction path.
The choice stays with you.
Choose the sources and the goal. Inspect each reason and keep availability, interest and missing information visible.
Why might someone appear in the results?
Because information you allowed may connect their experience or relationships to your goal. That relevance is separate from whether they are available, interested or comfortable helping.
Follow the build.
Hear when it’s ready.
Join for Keykind product progress and launch news. Choose the parts of the vision you care about most.
Photography sources
Are these real conversations or a finished product?
Can I use Keykind today?
What happens to my waitlist information?
This waitlist stores your email, optional interest (a product area or feature you choose) and phone preference, signup time, consent version, and a one-way hash of a private management code.
The records are held in this site’s Cloudflare D1 database through OpenAI Sites. They are used to manage the waitlist and understand which product areas people request.
The page does not read your messages, contacts or keyboard, and it does not send signup data to an advertising or email-marketing service. No email delivery service is configured.
Waitlist records are retained without automatic expiration, including if you never become a customer. You can withdraw from the waitlist and delete your record from the live database with the private link shown on your first successful registration. Anyone holding that link can remove the registration; do not share it.
Save a copy of your private link. No public contact details or manual recovery route are currently provided. If you lose the code or joined before private links were available, self-service access cannot currently be recovered here.
Email addresses and management codes are never displayed in the owner’s statistics.
Hosting providers may process connection metadata and retain service backups under their own policies; deleting a live record is not a claim that every provider backup is immediately erased.
Do you track visits or clicks?
Only if you choose “Allow anonymous counts”. The site then stores daily totals for approximate page visits, waitlist-button clicks and new signups from people who opted in.
A browser tab counts each visit or button-click type at most once per UTC day. These are not unique people or a complete visitor count.
Short-lived random event receipts prevent retries being counted twice; they expire after 24 hours and are removed on a later measurement request. The receipts are not linked to signup records.
Your allow/deny choice stays in this browser’s local storage; temporary per-tab deduplication uses session storage.
No tracking cookie, stored IP address, browser fingerprint, full URL query, referrer or third-party analytics is added by this application.
Recognized owner sessions, admin pages and marked QA signups are excluded.
Turning counts off stops future events; existing anonymous totals cannot be traced back to remove an individual contribution. Registration works whether you allow counts or not.