Engagements
Choose a working shape that fits the need.
Some problems need a focused project. Others need an ongoing rhythm of creation, maintenance, and improvement. Define the outcome and responsibilities before deciding the engagement format.
Three practical starting points.
These are ways to structure a conversation, not fixed packages or a published price list.
Focused project
A defined piece of work with agreed deliverables, dependencies, and acceptance criteria. Useful when the need and completion point can be described clearly.
Ongoing program
A continuing set of priorities with a review rhythm and a defined capacity or scope. Useful when the work needs regular learning and adjustment.
Team extension
Specific skills or delivery support alongside your internal team. Useful when ownership, approvals, and communication can be agreed clearly.
What we need to scope the work.
Business context
The audience, offer, goal, and reason the work matters now.
Current situation
Existing assets, systems, evidence, constraints, and known dependencies.
People and decisions
The owners, reviewers, and access needed to make progress.
Practical boundaries
Timing, budget context, deliverables, and how changes will be handled.
The proposal should make the tradeoffs clear.
Fees, schedules, third-party costs, support expectations, and ownership terms belong in the actual agreement. We do not substitute an undefined promise of unlimited work for a clear scope.
A few useful answers
Can we begin with an audit or planning project?
Yes. A focused discovery or audit can help define priorities and implementation scope before a larger commitment.
Do you publish standard pricing?
This page describes engagement formats, not prices. The scope, complexity, dependencies, and level of ongoing support need to be understood before a proposal is prepared.