CONTACT / CONVERSATION STARTER
Bring a real operating problem.
A clear contact pattern for discovery, support, or template evaluation—without creating a payment or purchase flow.
01 / REQUEST MAP
Route the conversation before you send it.
A useful first message names the operating constraint, the people involved, and the outcome that needs a clearer system.
01 / CONTEXT
Describe the workflow, team, and current handoff.
02 / FRICTION
Name what breaks, repeats, or requires manual recovery.
03 / OUTCOME
Define the decision, launch, or operating rhythm you need.
DEMO CONTACT PATTERN · NO LIVE SERVICE OR RESPONSE-TIME CLAIM
02 / DISCOVERY BRIEF
Start with the operating constraint.
Required fields are marked in their labels. Replace the demo destination and privacy copy before launch.
03 / BEFORE YOU SUBMIT
Bring enough detail to make the next step useful.
01 / WORKFLOW
Map the handoff.
Who creates the work, who reviews it, and where does ownership become unclear?
02 / EVIDENCE
Bring the failure signal.
Examples, screenshots, or recurring exceptions make the operating problem concrete.
03 / BOUNDARY
Keep claims reviewable.
Do not submit secrets, regulated data, or claims that have not been reviewed for your launch.