Scoped discovery
A written scope: what is being built, what is explicitly out, and what done means.
High-ticket engagement · proposal
A private build lane with a written scope and a written handover. Terms are proposals, discussed on a call with a person.
A written scope: what is being built, what is explicitly out, and what done means.
Work happens in a private lane. Nothing about your engagement appears in a public demo.
A named point of contact for the engagement, not a ticket queue.
Documentation of what was built, how it runs, and what remains unverified.
Every claim in the handover carries an evidence status. Proposed stays proposed.
Write down the workflow, the data involved and what a good outcome looks like.
A person walks the relevant demos with you and says plainly what is built and what is not.
Deliverables, exclusions, evidence status and a handover definition, in writing.
Private lane, direct access, written handover with unverified items named.
Write these four things down before the call. It is the difference between a demo and a decision.
What happens today, step by step, and who touches it.
What data is involved, where it lives, and who is allowed to see it.
The one thing that must not break, and the deadline that matters.
What a good result looks like in numbers you would actually accept.
Email your prepared brief to 0@shadow.black. A person reads it and replies. There is no form on this page and nothing is submitted from it.
This link opens your own mail client with a draft. Nothing is sent from this page, and no booking, payment or calendar change happens here.
Retainer and guarantee terms are proposals only and are not commitments made by this page.
Look at the working demos first, then decide whether a scoped engagement is worth a conversation.