Contact
One form, reviewed by a human
Tell us what you are trying to automate, who does the work today, and what must never run without your approval. We scope in plain language before any build time — no platform pitch, no chatbot theatre.
What helps us reply usefully
You do not need technical detail upfront. Symptoms, boundaries, and the job you want off your plate are enough — we will ask for access only if a next step needs it.
What to include
A short picture of the workflow: who runs it, how often, and which tools are involved (inbox, CRM, spreadsheets — names are enough).
State hard limits in your own words — for example “never send money,” “never email clients without me approving,” or “read-only on the shared drive.”
If you arrived from the readiness check, your result is attached automatically; you can still add context the checklist did not capture.
What to expect
Your message is read by us, not routed through a generic support bot. We may ask clarifying questions before suggesting scope.
First engagements stay on one workflow with written limits, logging, and a way to turn automation off — not a vague “AI everywhere” rollout.
We usually reply within two business days and answer as soon as practical on our side; complex notes can take a little longer while we think them through.
Please do not send
-
01
Passwords, API keys, recovery codes, or shared login details.
-
02
Seed phrases, wallet backups, or cryptocurrency credentials.
-
03
Production database dumps or full exports of customer data.
-
04
Live access in the first message — describe symptoms; we request access only when needed.
-
05
Urgent legal, medical, or safety decisions — we automate operations, not professional judgment.
What happens next
-
You submit
The form posts to our inbox. Nothing is published, scraped for training, or passed to a third-party “lead” tool.
-
We read and match
We map your note to the kind of help that fits — chatbot, script, supervised workflow, local setup, or “not yet.” A readiness result speeds this up when you have one.
-
We reply in plain language
Expect clarifying questions or a suggested first step, not a generic brochure. If it is a good fit, we outline scope and limits in writing before build time.
The form
Required fields only. Consent covers this enquiry; see the privacy notice for retention and processors.
Unsure where to start?
The readiness check recommends chatbot, script, supervised workflow, local setup, or probably not yet — then links here with your result attached.