A playbook for turning client projects into products
Build with clients, not ahead of them.
A services firm earns its revenue one custom project at a time, and most of that work is never used again. I wanted every engagement to leave something reusable behind, without asking the business to fund speculative products.
- Defined a three-stage maturity path: a custom project, a reusable platform abstracted from it, and a branded, documented, supported product.
- Set a five-part screen for any candidate: repeatability across clients, pain intensity, domain fit, extendability, and ease of packaging.
- Built it into delivery. Product managers and analysts flag reusable patterns during requirements, teams generalize existing code into prototypes, and new clients see them as proven accelerators.
- Added governance: a recurring productization review, a shared backlog, and one or two components packaged per quarter.
Key decision
Clients fund the build; the company funds only the branding, documentation, and hardening. Nothing gets branded until it has worked in at least two client implementations.
Outcome
A family of reusable products grew out of client work, including a configurable workflow engine, a data import and validation tool, and a master data management platform, with identity and finance interoperability frameworks in the pipeline.