When services are a wedge — and when they become a trap

Many successful enterprise software companies begin with services.

The founders perform implementation work, handle operations manually and solve problems that the product cannot yet solve.

This is often described as something to eliminate.

That can be a mistake.

Services can provide access to the workflow, reveal how customers make decisions, create training data and allow a company to deliver an outcome before the product is complete.

In complex industries, this may be the only credible way to enter.

But services are useful only when they produce product learning.

A service is a wedge when each delivery makes the next delivery easier. The company identifies recurring tasks. It builds internal tools. It standardizes decisions. It reduces manual effort. It captures structured data. It narrows the range of exceptions.

A service becomes a trap when growth requires proportional growth in people.

The warning signs are familiar.

• Every customer has a different process.
• Senior employees are required to resolve routine problems.
• Important knowledge remains undocumented.
• Internal tools are postponed because manual work keeps the customer satisfied.
• Margins are justified as temporary, but do not improve.

The distinction is not whether humans are involved. Many valuable businesses combine software and operations.

The distinction is whether human effort compounds.

If an employee resolves an exception and the system learns nothing, the company has performed labor.

If the resolution creates a new rule, improves routing, enriches the data model or prevents the same exception in the future, the company has created an asset.

This suggests a simple management discipline: every recurring manual task should have an explicit destination.

• It will be automated.
• It will be standardized and delegated.
• It will remain a premium human service.
• Or the company will stop doing it.

The dangerous category is work that has no destination. It simply continues because someone is willing to do it.

Founders should also be honest about customer expectations. Once customers become accustomed to unlimited operational flexibility, converting them to a standardized product can be difficult. What the company considers temporary assistance, the customer may consider the core offering.

Services are therefore most powerful when the boundaries are clear.

Use them to learn the workflow. Use them to control the outcome. Use them to earn the right to build the product.

But do not confuse being indispensable because your software is valuable with being indispensable because your employees absorb unlimited complexity.

Those are very different businesses.