INTAKE / 09

Put the task in writing.

Share the product context in writing. The request is reviewed asynchronously; submitting it does not start a membership or book a meeting.

Clear context in. A written fit decision out.

TASK / CONTEXT / OUTCOME

Start with the work itself.

Useful intake explains the current state, the intended outcome and the evidence that would make the change reviewable.

Attach only material that is safe to store privately in an unscanned quarantine. Credentials and sensitive personal data do not belong here.

01 / CONTACTWho should receive the written response?

Work email

Used only to review and respond to this task.

Name

The person responsible for this request.

Company

The company or product team behind the task.

02 / PRODUCTWhat should change?

What are you trying to build?

Include the problem, users and important constraints. 20–4,000 characters.

Product track

Choose the current product state.

New appStart with a product idea or a new build.Existing productShip into a product or codebase that already exists.

Current stack (optional)

Add any preferred technologies or existing constraints if they matter.

Desired outcome

Describe what someone should be able to inspect, use or approve. 20–4,000 characters.

03 / CONTEXTWhat can be reviewed safely?

Relevant links (optional)

One public HTTP(S) URL per line, up to five. Links are stored for review and are not fetched during submission.

Attachments (optional)

Up to three files and 4 MB combined: PDF, PNG, JPEG, WebP, UTF-8 TXT, Markdown, JSON or CSV. Files remain private and quarantined; do not include secrets.

No login, sales call or meeting booking required.