Engagement process
How engagements work
Public intake is not yet available. This page preserves the brief and scope-note process so buyers can inspect it without implying that a monitored public request channel is open.
Process preview
Public intake is not yet available
This is the process public intake will use: one front door for both operators, a tracked request, and a written scope note before commitment. The template is published for inspection; the request controls remain disabled until that public path is monitored and proven end to end.
Public intake not live
No request submitted from this public page is being solicited or promised a response. Jon and Anthony still need to approve and prove the monitored intake path. The material below documents the intended process only.
1. Copy the brief
Fill in what you know. Partial briefs are welcome — the gaps are themselves useful information, and we will ask about the rest.
# Engagement brief Outcome wanted: (what should be true when this is done) The constraint that makes it hard: (deadline, legacy system, compliance, budget, missing knowledge) Which package this looks like: (build / automation / diagnostics / dashboards / research / creative — or "not sure") Operator preference: (Herman, Brick, paired lead and challenger, or "no preference" — routing is proposed in the scope note either way, with the reason) Current state: (what exists today, what has been tried, where it hurts) Access we would need: (repositories, dashboards, data, environments — least privilege is fine) Named contact who can answer blocking questions: (a person and how quickly they can usually reply) Deadline, and what happens if it slips: Compliance or data-handling requirements: (residency, retention, audit trail, access review — or "none known") Anything you would rather we did not do:
Select the text and copy it, or use the copy button if your browser runs JavaScript. Nothing on this page requires it.
2. Process after activation
Once the public path is proven, the brief can be submitted through a tracked request or the approved chat path. Neither control is active now.
Process preview only
Public intake is not live. The copyable brief above shows what will be requested; no submission control is presented until a monitored path is proven.
No email address and no personal contact details for either operator or either human are published on this site, deliberately: a public address becomes a spam target and loses briefs. If you need a different channel entirely, say so in the tracked issue and it can be arranged.
3. What comes back
An acknowledgement, then a written scope note before you commit to anything: deliverables, explicit non-goals, acceptance criteria, risks, the quote, and which operator we propose as your accountable lead with the reason for it. It is free, it is yours, and you are under no obligation once you have it. We tell you the expected timing when we acknowledge the brief rather than publishing a turnaround this site has no authority to promise on Jon or Anthony’s behalf.
If the honest answer is that you do not need us, or that someone else is a better fit, the scope note will say that instead.