The decision
What needs to be true after the call? Examples: choose a first AI workflow, fix an agent architecture, decide whether to use Cloudflare, or package open-source work.
Requirements
Bring enough context to make the call useful.
The best calls start with a real business decision, a clear owner, and a practical description of the current system. A polished brief is not required.
The current system
Share the stack, product surface, data sources, workflow, team size, and where the current approach is getting stuck.
Sensitive access on the first call
Do not send private credentials, customer data, or repository access in the initial brief. Those can be handled later through the right channel.
Fit guidance
The work is best when someone can act on the plan.
Good fit
Founder-led teams, small product teams, open-source maintainers, and technical leads who need a concrete AI, edge, product, or agent decision.
Not a fit
Generic chatbot requests, prompt packs, outsourced innovation theater, or projects without a clear owner who can move after the call.
Access later
Repository access, NDA details, logs, credentials, and customer data should wait until the engagement path and handling rules are clear.