← Back to concept explainers

Concept Fable

Professional services

Conclusion first:Professional services are labor-intensive delivery around consulting, implementation, customization, training, and integration. For enterprise AI / Agent companies, they are often used for early pre-sales validation, complex integration, process mapping, and launch support, and can drive deals and customer success. But Professional Services gross margins are usually lower than product revenue, and scale is limited by the supply of experts. A healthy approach is to turn recurring parts of professional services into templates, connectors, SOPs, Agent workflows, and productized services, so that they serve product expansion rather than swallowing product gross margin.

Professional Services · Business model / delivery

Read the story first. There is no rush to give a definition here; let the question grow on its own first.

Fable

The bridge builder could repair every bridge well, but could not get rich by redrawing the blueprints every time

In the river valley there was a bridge builder who, wherever a bridge broke, could carry his ruler and ink line and hurry there. Mountain villages, docks, temples—every bridge had different terrain, and he could always measure the water flow, examine the soil, and redraw the plans.

In the early years, the bridge builder had a fine reputation and charged no small fee. But he soon discovered that he was on the road every day. Every bridge had to be inspected in person, blueprints could not be directly reused, apprentices could only assist, and his income was tied rigidly to his time.

For the first fix, he recruited more apprentices. With more apprentices, the bridge builder had to spend more time reviewing, and each bridge still had to be judged from scratch. Headcount grew, but profit was eaten by management and rework.

The second time, he sold the old blueprints to the villages. Several small bridges were built according to the drawings, but cracks appeared where there was soft soil and sharp bends in the waterway. The villagers complained that the blueprints were useless, and the bridge builder had to go fix things himself.

The old accountant suggested separating the business clearly: complex bridges continue to be charged by person-days and solution; recurring small bridge types are consolidated into fixed processes, material lists, and acceptance standards; for those not suitable for standardization, the price must cover the cost of personal judgment.

After the bridge craftsman did so, the apprentice could independently deliver some common bridges, while difficult bridges still required him to step in. Clients also knew whether they were buying specialized judgment or a mature approach, and no longer mixed the two services into one price.

The bridge builder finally understood: the value of professional services lies in experts solving complex problems on site; the very reason it's hard to scale is that every case depends on expert judgment. To make money, you must know which experience can be codified and which can only be sold at a premium.

Later, before taking on a project, the bridge craftsman would first judge whether the client was buying a craftsman's on-site judgment or a set of already-validated practices. The former can be expensive but cannot be separated from the person; the latter can be replicated but must have its boundaries honed in advance. Without seeing this clearly, the stronger one's professional skill, the easier it is to trap oneself in a schedule. The bridge craftsman later also dared to quote more boldly. For projects that required him to personally inspect the terrain in the rain, he no longer sold them at ordinary blueprint prices; for projects that apprentices could deliver by following the process, he no longer pretended they were mysterious craft. By distinguishing service forms, both clients and the bridge craftsman lost less. In the end, the bridge craftsman finally turned his reputation into a business, rather than turning his reputation into an even fuller schedule. This sentence was later written into the newcomers' handbook, reminding everyone to look at the on-site cost first before talking about saving effort.

Reveal

This story is about: professional services

Professional services are labor-intensive delivery around consulting, implementation, customization, training, and integration. For enterprise AI / Agent companies, they are often used for early pre-sales validation, complex integration, process mapping, and launch support, and can drive deals and customer success. But Professional Services gross margins are usually lower than product revenue, and scale is limited by the supply of experts. A healthy approach is to turn recurring parts of professional services into templates, connectors, SOPs, Agent workflows, and productized services, so that they serve product expansion rather than swallowing product gross margin.

What matters is that it is not just a term, but a structural problem that repeatedly appears in real AI / Agent systems. Understanding it lets you judge when to add a model, when to change a process, and when to add governance.

Metaphor mapping

  • Bridge Artisan for Hard Problems: a highly skilled consulting, implementation, and customization team
  • Every bridge resurveyed: differences in enterprise customer processes and integration complexity
  • Raising the day rate: the revenue ceiling of charging by person-day
  • Quality becomes unstable after scaling the team: the challenge of scaling professional services
  • Floods wash out projects: project risk and rework in custom delivery
  • Standard drawings, material kits, acceptance checklists: productizing repeatable services
  • Remote water-level gauges and maintenance crews: software, automation, and managed operations
  • Professional services as entry point and fallback: services should drive productization, not replace it

Andy Ren Xu's judgment

The practical value of this concept is that it helps you break "AI features that look smart" into deliverable, verifiable, and governable units of work.

Implementationconsultingmanaged serviceservices-as-softwarecustomizationonboarding

Related distinctions

This concept is easily confused with adjacent concepts; it is recommended to continue to the comparison page.

京ICP备2026014272号