Yeah, B makes sense here. Product Attributes lets you keep a single product and add skills or roles as attributes during quoting, which controls SKU sprawl. Not 100% sure but pretty confident given how CPQ handles config.
Is anyone really using Product Classification (C) for this kind of dynamic config? From what I've seen, Attributes in B solve for SKU explosion way better, but maybe there's a nuance I'm missing around Classification here?
Totally agree with B here. Product Attributes are meant for exactly this scenario, so you don't need a new SKU for every skill or role, just define them as selectable options. Pretty sure that's the best CPQ approach but open to other views.