Essay

When software can fit the business

For decades, businesses adapted themselves to software built for many customers. AI is changing the economics of the alternative: software built around the way a particular business works.

NoteA conceptual model, not a forecast. The diagrams below show relationships rather than measured market data.

01

One product, many businesses

Traditional software earned its scale by writing a product once and distributing it widely. Some configuration could stretch that product across different customers, but the shared core still set the boundaries.

That was often an excellent trade. The customer gained a capable tool without funding its creation. When the fit was poor, though, the business had to change its process or assemble workarounds around the product.

Figure 1

One shared product fit Business AClose fit Business BConfiguration and workarounds Business CProcess changes to fit the tool
Sharing one product creates scale. The cost of mismatch varies by customer.

02

The invoice is only part of the price

Think of the RevOps process that looks clean on a whiteboard. Back at the desk, one tool cannot support a step, another integration breaks if it changes, and a contract delays a better choice. The working system drifts from the intended one.

Licenses are visible. Lost opportunities, coordination, manual repair, and the attention consumed by the stack are much harder to see.

Visible in the purchase decisionOften borne during operation
Subscription and implementation feesWorkarounds, coordination, lost fit, and delayed improvement

The comparison is the full burden of achieving the desired process, not just the subscription price.

03

AI moves the build-or-buy boundary

AI reduces the effort involved in writing, adapting, and maintaining software. It can help a team turn established patterns into customer-specific systems, inspect changes, and respond to feedback. Human understanding of the business and responsibility for the result remain essential.

As that work becomes cheaper, tailored software can cross a threshold: for a workflow with a costly mismatch, it may become less burdensome overall than continuing to adapt the business to an existing product. A product that already fits well can remain the better choice.

Figure 2

Greater AI capability and accumulated recipes Lower burden to build and maintain tailored software Compare the full burden for this workflow Poor fit creates a persistent cost Existing product fits well Tailoring may cross the tipping point Off the shelf remains the better choice
There is no universal crossing point. It depends on fit, value at stake, implementation effort, and the ability to keep the system healthy. Existing products and AI-assisted tailoring may both improve over time.

04

Buy what fits. Tailor what matters.

This is a decision made workflow by workflow. Use a proven product when it does the job well. Configure or integrate it when the gap is modest. Consider a tailored system when the value of removing a persistent constraint outweighs the full cost of building and operating it.

Often the right answer is a combination: standard tools for common capabilities, with tailored pieces where the business is meaningfully different.

Figure 3

Evaluate one workflow Reliable productfits well? Yes Use it No Can a modest gapbe closed? Yes Configure or integrate No Is the gap persistentand valuable? Yes Compare the whole lifeof a tailored system Unclear Test the value first Evaluate one workflow Reliable product fits well? Yes Use it No Can a modest gap be closed? Yes Configure or integrate No Is the gap persistent and valuable? Yes Compare the whole lifeof a tailored system Unclear Test the value first
Custom is a threshold decision, not an ideology.

05

Better fit can expand the useful share

When a tailored system removes workarounds and supports a better process, it can recover value previously lost to mismatch. If tailoring still takes more resources, some of the gain pays for that work. If AI-supported delivery brings the resource cost closer to a standard solution, more of the recovered value remains available to the customer and those delivering the system.

Dots: filled green is favourable for the customer, grey is unfavourable, pale green is in between.
ScenarioDelivery effortWorkarounds and poor fitUseful value from the process
Standard stack with a poor fitLowHighConstrained
Tailored system with more delivery effortHigherLowerLarger
Tailored system with comparable delivery effortComparableLowerLarger still

These are qualitative relationships, not measured proportions. How the gain is divided depends on pricing and competition. Greater provider margin is not required for the case to work.

06

Reuse the learning, not necessarily the codebase

A shared product must reconcile the promises it has made to all its customers. Each feature and compatibility requirement can make the next change more complicated.

Another form of scale may be possible: shared recipes, architecture, quality checks, and AI agents that help build and operate separate systems. Lessons can travel across the portfolio while each customer’s implementation can change on its own terms.

Figure 4

Scale a product One shared codebase Customer A Customer B Customer C Scale a method Recipes, quality checks, AI agents Distinctsystem A Distinctsystem B Distinctsystem C

The second arrangement still needs governance, maintenance, and human judgment. Whether it remains efficient at large scale is a hypothesis to test, especially as integration and maintenance demands accumulate.

The open question

Existing products will continue to win where they fit well. But some businesses have been accepting compromises because the alternative was too expensive to build and maintain. AI may move that boundary, one workflow at a time.

How much standardized software is the best solution—and how much was simply the only economical one?
Wes Stinson

What we do with it

Buy what fits. Tailor what matters. It’s how we work with revenue teams. Our tool suite shows the tailored pieces we build most often, from business hubs to territory planning.