Reply 01
Questions
Two or three things the brief cannot tell us: exception paths, who decides, what cannot change.
Contact
A useful first message describes a task, the systems around it and a date. This page assembles that into a brief you can email, copy, or read out on a call — the site itself sends nothing.
01Scoping form
Five fields. The output is plain text, written to be forwarded: no formatting to lose, no attachment to open.
| Sent by this page | Nothing |
|---|---|
| Stored | Nowhere |
| Output | A brief you send from your own email app |
| Reply route | info@northwindcloud.net or 626-563-3835 |
Output
Nothing is sent by this page. Send it to info@northwindcloud.net, or copy it into your own message.
02After you write
Not a price. A set of questions specific enough that answering them changes the shape of the work.
Reply 01
Two or three things the brief cannot tell us: exception paths, who decides, what cannot change.
Reply 01
Whether this is work we should take. If it is not, the reply says so and, where possible, what kind of help fits better.
Next
A short conversation to test the assumptions, by telephone or video, at a time you choose.
Next
If it still makes sense, a bounded discovery produces the written scope and the assumption register.
Then
Build, configure, or stop. All three are documented, and all three are acceptable outcomes.
Before you send
No customer records, no identity documents, no payment details, no staff personal information. A description of the task is enough to scope it; real data belongs in a sandbox after an agreement exists. If a sample is genuinely required to judge feasibility, it can be anonymised first.
The company's office is a correspondence address, not a walk-in shop. Visits are by appointment only.
Next step
Send the task, the systems it touches and the deadline you are working to. The first reply is a set of questions, not a quote.