Proof Artifacts

Working outputs for real technical decisions.

These are the types of artifacts I create with teams: clear enough for executives, detailed enough for technical teams, and practical enough to support a real decision.

Downloadable redacted example

Available

Example Architecture Brief

A concise technical decision document for teams that need architecture direction, scope boundaries, integration assumptions, and implementation risks in one place.

Sample structure

Executive recommendation

Current-state workflow

Architecture risks

Next-step plan

What this helps decide

Architecture direction, integration assumptions, scope boundaries, and implementation risks.

Best used when

A buyer or internal team needs a concise technical decision document.

Download PDF

Downloadable redacted example

PDF available

POC Validation Plan

Turn a vague technical evaluation into a structured validation path a buyer can review and act on.

Sample structure

POC objective

Success criteria

Validation steps

Go / no-go decision

What this helps decide

Whether the solution works, what must be proven, who needs to approve, and what risks remain.

Best used when

A team needs to structure a POC around success criteria instead of random demos.

Download PDF

Next step

If one of these artifacts would help, start with the live problem.

The first conversation is there to understand the pressure and decide whether the next useful output is a plan, memo, workflow map, or clean no.

Get a Clarity Plan View Services