We’re looking at the ready-to-use templates for common processes like invoicing and approvals, and they look promising for accelerating our open-source BPM migration. The idea is that we start with a template for our invoicing workflow, customize it for our specific requirements, and deploy.
But what I want to understand is how much customization work actually happens in practice. Do we take the template as-is and just plug in our data structures? Or do most teams end up rebuilding significant portions of the template workflow to match their actual process logic?
I’m asking because the business case for our migration depends partly on using templates to hit certain timeline targets. If templates save two weeks of development but still require three weeks of customization work, then the timeline math changes significantly.
How much of the template typically survives to production, and how much gets replaced or heavily modified? I’m trying to figure out if starting with a template is genuinely faster than starting from scratch, or if we’re just kicking the real work downstream.