One ICM System or One Per Customer?

A question for those using ICM to provide software or consulting services:

When you work with multiple customers, does one ICM system support all of them, with separate customer configurations, requirements, data, and outputs? Or do you create and maintain a separate ICM structure for each customer or software product?

I’ve been thinking about this through the way I create my own products. I reuse many of the same standards, checks, scripts, and production methods, but different product types may still need different schemas and workflows. A devotional is not built exactly like a prayer card set, even though they share part of the same underlying system.

I’m curious whether software providers (or consultants) approach this similarly. Do you maintain a common core and adapt it for each customer, keep every customer implementation completely separate, or use some combination of the two?

I’m still learning how others structure this, so I would genuinely appreciate hearing what has worked for you—and where separation becomes important.

3 comments

One ICM System or One Per Customer?