do.enterprises
Problem brief

Bring a problem, not a pitch.

Intake is a problem brief structured around the job to be done. Answer what you can; short is fine. We reply with whether it is a problem we can produce against, in writing.

  1. 1The signal
  2. 2The job
  3. 3Hired today
  4. 4Who goes without
  5. 5The regulated edge
  6. 6Your own lines
  7. We reply in writing: a problem we can produce against, or not.

The first-party life-event signal. A closing, a claim, a payroll run, a shipment. Name it.

The functional job your customer is trying to get done in that moment, in their words, not your product’s.

The product, vendor, or workaround your customer uses now. Where does it over-serve, where does it under-serve?

The population that cannot get the job done at all today: too expensive, too far, too slow, no one licensed nearby.

Licenses, registrations, counterparty approvals, or credentials the work requires. We will need the NewCo to hold these itself.

If the thesis attacks your own over-served customers from below, say so. That is a different play with a different mandate.

We reply to this address and use it for nothing else.

Send the signal category, not customer records. The brief is stored in the operator’s own database, read by a person, and deleted on request. Privacy · Trust