Secure intake
Request written scope without sending sensitive materials first.
A structured intake path for serious buyers who need to describe workflow, tools, data classes, decision deadline, and desired deliverable at a high level.
What you receive
Concrete outputs for a specific decision.
- Workflow description
- Tools and integrations
- Data classes
- Decision deadline
- Desired deliverable
- Access and sensitivity notes
Structured intake
Describe the scope at a high level
This intake collects only routing information. Keep sensitive details out of the first message and request a secure path if materials are needed.
01
What to include
- The business decision the review must support.
- The system type: agent, MCP/tool workflow, RAG, coding assistant, AI SaaS, incident review, or briefing.
- High-level tools, integrations, data classes, and environments.
- Timeline, stakeholders, and desired deliverable.
02
What not to include
- No secrets, credentials, tokens, API keys, regulated data, customer PII, payloads, or confidential files.
- Use the first message to request a secure path for sensitive materials if needed.
Next step