1. Tx Hash
Confirm the deposit first so the sprint is tied to a paid start and the correct wallet transaction.
Minimum kickoff intake
Collect only what is needed to start the sprint.
This page is the lightest version of post-payment intake. Use it when the client does not need a long brief and you want the minimum details required to confirm scope and begin work.
- 5 minimum inputs
- 1 main bottleneck
- 1 approver
Minimum Inputs
These five items are enough to start.
2. Main Bottleneck
Ask for the single issue that matters most right now. Do not let the intake sprawl into ten competing problems.
3. Desired Outcome
Ask what should improve first once the sprint is done: approvals, response speed, cleaner handoff, or another concrete shift.
4. Relevant Links
Collect the page URLs, docs, or screenshots that show the current funnel, handoff, or payment path.
5. Final Approver
Name the person who can answer questions and approve the work so the sprint does not stall midstream.
Copyable Intake
Send this when the client asks what you need next.
|
Minimum Intake
1. tx hash 2. the main bottleneck to fix first 3. the result you want from this sprint 4. relevant page links, docs, or screenshots 5. the final approver if questions come up |
When To Use Full Brief
Escalate only if the sprint actually needs more context.
Use Intake Board
Use this when the sprint is already clear and the client only needs a fast handoff into production.
Use Brief Board
Use the fuller brief when constraints, stakeholders, or funnel complexity mean you genuinely need more context upfront.
Open Brief BoardUse FAQ Board
If the client is still asking process questions, answer those first so intake does not turn into scattered chat.
Open FAQ Board