An empty glass-walled meeting room with a long table, in a Montreal office.

Buyer-side record

Three published engagements

These are the three buyer-side files the practice has published. Each table repeats that text. The paragraph under a table only explains those words. No organization is named. Nothing has been added. Nothing here is a supplier result.

Digital Transformation

Enterprise Financial System

Published facts for this engagement.
Challenge	Replacing a legacy G7 financial system with strict interoperability requirements.
Action	Led the Agile procurement strategy for a $1.2B integration.
Result	Successful vendor selection with zero trade challenges.

The published file was the replacement of a legacy G7 financial system. The constraint named with it is strict interoperability: the replacement had to work with what would remain around it, and the solicitation had to say that clearly enough to evaluate. The practice led the Agile procurement strategy for a $1.2B integration. The published result is a successful vendor selection with zero trade challenges.

The buyer is not named. No schedule and no further outcome are published. This site does not expand the term G7, because the practice has not published an expansion. Zero trade challenges means no trade challenge is part of the published result. It does not mean a challenge was heard and lost.

Agile Pilot

Cloud Recruiting Solution

Published facts for this engagement.
Challenge	Sourcing a recruiting platform for 300k+ users without waterfall delays.
Action	Implemented one of the first true Agile contracting models in federal history.
Result	Delivered 100% compliance in record time.

The requirement was a recruiting platform for 300k+ users, sourced without waterfall delays. The published action is that the practice implemented one of the first true Agile contracting models in federal history. The published result is 100% compliance, delivered in record time.

The number of days behind "record time" is not published. The buyer is not named. This file is not the departmental framework below. The two published agile descriptions are separate.

Strategic Advisory

Departmental Policy Reset

Published facts for this engagement.
Challenge	A major department needed to modernize their procurement governance.
Action	Drafted the complete Agile Procurement Framework and User Guide.
Result	Standardized acquisition across the organization.

The buyer is described only as a major department. The published challenge is: "A major department needed to modernize their procurement governance." The practice drafted two things: the complete Agile Procurement Framework, and the User Guide. The published result is standardized acquisition across the organization.

The department is not named. No adoption figure is published beyond that sentence. The framework is not reproduced here.