Engage

A role, or a defined piece of work.

Both are the same method pointed at a different frame. One is a commitment inside an organisation; the other is a bounded problem, scoped and delivered.

If you are hiring

The roles I am after sit where the constraint is organisational rather than technical: transformation lead, head of operations, chief of staff, or the product owner who owns the seam between the business and the build.

the full CV →

If you have a defined problem

Three shapes of work. They are not products and they are not priced on this page — each is scoped against the problem in front of it.

Two weeks

Diagnostic sprint

Find the constraint and put a number on it

A costed current state, one committed pathway, and the three gates we would measure against.

The cheapest way to find out whether the rest is worth doing.

An engagement, typically 6–12 weeks

Embedded build

Build the thing with the team that has to live with it

Process, system or both — plus the training content and the governance that makes it stick.

The output is owned by the organisation, not licensed by the consultant.

A fixed cadence

Standing advisory

Keep a working system working after the engagement ends

A named decision-maker, a standing view of what is drifting, and a route for remedial action.

For organisations that already have the machinery and need it steered.

Pro bono and non-profit

Mission-aligned and non-profit work is scoped the same way, and is not priced differently. If the problem matters and the budget does not exist, say so plainly and we will find the shape that fits.

Not offered

Next step

Tell me what you are trying to move and who is closest to the work. If it is a role, send the description. If it is a problem, describe it in a paragraph. Either way, I will answer with a view rather than a brochure.

jun@junbuilds.ca