Let’s define the first useful step.

What actually happens when you use this form

Being precise about this matters more than being welcoming. The form checks that the required fields are filled and assembles your message into plain text inside your browser. It then offers you two ways out: open the message in your own email program, already addressed and written, or download it as a text file. The page itself calls no endpoint, writes to no database and keeps no copy. Closing the tab without using either discards the text.

Messages go to support@embodiedsoftwarelabs.com, which forwards to a mailbox that is read. That is the whole of the delivery system: no queue, no ticket number, no automatic acknowledgement, and no software between you and the message. If your email program does not open when you use the button, the download is the fallback and the address above works typed by hand.

What makes a first message useful

The most valuable messages are short, specific and slightly sceptical. What helps:

• What exists on your side today. The hardware, the software, the site, the task — whatever is real now.
• What you think would have to be built. Your read on the gap is more useful than a request for ours.
• The outcome you would measure. Throughput, intervention rate, cycle time, cost per unit — whatever would decide it for you.
• Where you think this is wrong. Disagreement from someone who has deployed hardware is worth more than agreement from anyone else.

What each route means

• Developer or technical cofounder. Capability you have built, its maturity, what hardware it depends on, and what broke. See the developers page for the specific problems in play.
• Robot manufacturer. Which interfaces you expose and support, what test hardware access would involve, where your safety authority begins and ends, and what scope you would consider.
• Potential pilot customer. The task, the environment, the existing baseline, the exception rate, and your timing. The pilot customers page sets out what a realistic programme requires.
• Strategic or investment conversation. Note that nothing on this website is an offer of securities, no financing process is open, and no offering material exists.

Please do not send

This is not a confidential channel and is not covered by a non-disclosure agreement. Keep the first exchange non-confidential and leave out proprietary source code, credentials or access keys, unpublished research under embargo, customer records or personal data about other people, unreleased roadmap detail, and anything your employer would object to you sending.

Anything requiring confidentiality needs an agreement in place first. If that is where the conversation needs to start, say so in general terms and nothing more.

What to expect in return

No response time is promised. A pre-launch venture quoting one would be guessing, and a guess presented as a commitment is the thing this site is trying not to do. Nothing you send creates an obligation on anyone to reply, and sending a message does not register you, enrol you, or add you to any list — there is no list. The development status page records exactly what is and is not working at any given time.