Readiness check
A quick self-assessment to see if you have what's needed to get value quickly.
Workflow clarity
- I can name one specific recurring workflow to improve
- I can describe what "done" looks like (time saved, quality, consistency)
- I can list the main edge cases and exceptions
Access and materials
- I can share sample inputs/outputs (sanitized if needed)
- I can provide tool access (or a test environment) for anything the workflow touches
- I can identify where the data lives and who owns it
People and bandwidth
- I can assign one point of contact for fast feedback
- Someone can test early prototypes using real work
- I can commit 30–60 minutes per week during the build
Risk and boundaries
- I know what data is sensitive and what must never leave my systems
- I’m okay starting with a low-risk slice before scaling
- I’m not expecting guaranteed revenue outcomes
How to use this
If you're missing a couple items, that's normal. The point is to surface the blockers early so the first week doesn't get wasted hunting for access or examples.
Contract template
A plain-language starting point that makes ownership and handoff explicit. No legalese, no surprises.
What it covers
- Client ownership of all code and artifacts
- Clear scope and out-of-scope boundaries
- Straight hourly pricing with stated minimums
- Clean termination terms — you keep what's been delivered
- Dispute resolution — conversation first, not lawyers first
- What happens after the project ends (data, access, credentials)
Why it's included here
Most consultants hide the contract until after you've committed. I'd rather you read it upfront so there are no surprises about how ownership, scope changes, and billing work. It's a starting point — customize it, have a lawyer review it, make it yours.