When Does a Workflow Deserve Its Own Product?

Most internal workflows don’t deserve dedicated software. They’re handled fine in email, in spreadsheets, in the existing CRM, in whatever’s already there. But some workflows do deserve their own product — and recognizing which ones is the difference between operational excellence and operational sprawl.

Three criteria

A workflow deserves its own product when it meets all three:

It’s central to how the business operates. Not peripheral. Not “would be nice.” Central. If you removed this workflow, the business would feel it within a week.

It happens repeatedly with predictable structure. Daily, weekly, hourly. Each instance follows roughly the same pattern. You can describe the shape of “doing it” without referring to a specific case.

It has specific rules that don’t fit generic tools. Industry-specific. Company-specific. Regulatory requirements. Specialized math. Things that can’t be captured in standard fields and dropdowns.

All three. If only two are true, it probably doesn’t deserve dedicated software. It deserves better discipline using existing tools.

Examples of yes

A few that pass all three:

• Insurance renewals with cross-sell tracking
• Multi-state moving quotes with specialized equipment
• Healthcare scheduling with pre-authorization
• Manufacturing job costing with material variations
• Commercial real estate deal tracking

Each of these is central, repeatable, and has specific rules generic tools can’t capture cleanly. Each justifies its own product.

Examples of no

A few that fail one or more criteria:

• Generic CRM (central but generic — buy off-the-shelf)
• Quarterly board prep (central but not repeatable — handle in docs)
• One-off compliance reports (not repeatable enough)
• Internal team experiments (not central yet — maybe later)

For these, dedicated software is overkill. The cost outweighs the benefit.

What “deserves its own product” actually means

It doesn’t mean a separate platform with its own login. It can mean:

• A custom application embedded in your existing portal
• A focused tool that integrates with your CRM
• A workflow layer on top of existing systems
• A purpose-built dashboard with workflow actions

The “product” part is about treating the workflow with software discipline, not necessarily about building a standalone SaaS.

Signs you’re under-investing

• The workflow lives in spreadsheets that multiple people have to coordinate
• It has personal shortcuts that vary by person
• It’s slow despite being central
• New hires take weeks to learn it because it’s unwritten

Each of these is a signal that the workflow has outgrown ad-hoc tools. (See When Off-the-Shelf Software Stops Fitting Your Business.)

What to do

Those 2-4 candidates are the workflows worth productizing. Pick the one with the highest business impact and start there. (See How to Build a Software Strategy That Supports Growth.)