Skip to content
Interface language: English
Imperium / Signal

Modular services: what can change without rebuilding the company

Design modular services around real work, input conditions, handoffs and permitted variants without hiding missing stages.

Article language: English

Concept illustration: a woman rests her hands on the outer two of three round discs mounted on an axis in a navy and red interior.
In this article

A client wants to write an instruction manual themselves and asks to leave out editing. One line disappears from the offer. The work returns when illustrations begin: someone must establish the order of the steps, the names of the parts and what the photographs actually show. If the next person is expected to do all this quietly, the company has removed the name of a stage, not the need to perform it.

Imagine a company that produces short instructions for exhibition equipment. Its team wants to sell a modular service: adapt the scope to the client's materials while keeping a repeatable way of working. It wants to avoid designing the whole delivery process from scratch for every new package. That requires decisions about how the parts connect before giving them attractive names.

A module needs an output that can be handed on

Here, a module is a distinct part of a service that can be used in more than one configuration. In our example, it could be content development, illustration or assembly of the final material. Dividing the offer into these items does not by itself establish that the work can be performed this way. Look at what each part needs and what it passes on.

In their 2017 research review, Brax and co-authors draw attention to the process nature of services and the importance of client input. They suggest that modularity principles developed for products need to be reconsidered for services. The reference point is the organization of work, not merely an offer that resembles a catalogue of ready-made pieces.

The company needs to name the output of each stage. Editing might mean polishing finished text or developing a sequence of steps from source material. If the next module needs that sequence, omitting the second kind of work changes its input. The illustrator then receives a different task, even though the offer still lists illustrations under the same name.

The owner should therefore decide what remains constant across configurations. For instance, illustration might always begin with an approved description of the steps and named parts. The client can supply it or order its preparation beforehand. These are two routes to the same input condition. They do not automatically represent two levels of quality in the final instructions.

That decision differs from choosing a unit in which to sell a service (in Polish). A company can still sell a completed item while organizing its production in several parts. It can also offer particular stages separately. First, however, it must know whether it can perform and connect them as described, whatever pricing format it later chooses.

Two ways into the same work

Look at our fictional example from the worker's position. The first client has approved text describing a folding display stand and supplies material that connects the names of its parts to their appearance. The second has a demonstration video, photographs and an employee's working notes. They want a similar kind of instruction, but their material still needs content development.

The company can work with both sets. It must decide what precedes illustration in each case. With finished text, that may mean checking completeness against the agreed scope. Working material also requires development and confirmation of the information by the appropriate person at the client. People who know the product confirm facts about the equipment; an editor should not invent operating steps from an unclear photograph.

When the client prepares the text, the acceptance condition must be clear. The company should be able to say what it considers ready for the next stage and what it will do if the condition is not met. The condition establishes who will perform the work needed before that stage.

Suppose the first client sends three sentences and a dozen or so photographs, calling the file a finished manual. The person accepting the order sees that the pictures are not linked to the order of operations. They can ask the client to complete the material or propose an appropriate development stage. They should not ask the illustrator to guess the relationship within an unchanged stage.

In the second route, developing the material leads to the same kind of handoff as finished client text. This is where repetition becomes possible: the next person receives a recognizable input. The history of the content may differ, but the boundary between stages remains clear. The company does not need a separate illustration process for every earlier conversation.

A service menu and the architecture behind it

In the abstract of their 2009 article, Voss and Hsuan distinguish choosing existing services from a menu from combining service processes and elements. Their account of architecture also includes the connections between parts. This is useful for a company with a list of add-ons that is only now checking how they will be delivered together.

An extra form option may appear independent. In our example, illustration and final layout remain connected to the content. If the client selects layout alone, someone must supply material ready to assemble. If they choose illustration without content development, the illustrator still needs an agreed input. A selection form does not remove these dependencies.

The company should specify which combinations it actually offers. It need not sell every imaginable configuration. It may offer illustration on its own when specified materials are available, or restrict it to a broader assignment. The decision should reflect the ability to perform and accept the work, not a desire for a symmetrical number of price-list options.

With several variants, it is easy to miss a connection that works only because one person remembers it. An employee knows the client's material and fills the gap between stages. The next person will not have that knowledge. A repeatable service requires the company to recognize this work and decide where it belongs in the model.

The service category and the client's real alternatives (in Polish) concern an earlier choice: which task the company wants to help with. Here it decides how to deliver that scope in several repeatable configurations. A new menu should not accidentally expand the business into work it has neither planned nor learned to hand on.

Aeneia conceptual photography

Now trace a dependency back from the end. The company is considering either one instruction file or separate cards for individual tasks. These are two hypothetical forms of the result. Choosing cards may require each selected task to be described so it can be understood on its own. The team should recognize this before earlier work begins.

If the company treats the final form as a completely independent add-on, it may discover the need for further content work only during layout. The client selects another option and the editor must revisit content already developed. One solution may be to prepare common content for both permitted forms. Another may be a separate variant of the earlier stage. The owner should choose what the company actually wants to maintain, instead of leaving the decision to the last person touching the file.

The review produces permitted combinations and their conditions. In this model, a client can choose to supply finished content if it meets the requirements of the chosen final form. A different request needs prior agreement. Modularity then means deliberately prepared possibilities, not arbitrary combinations whose effects emerge after an order begins.

A boundary need not run between people

Content development and sketches may require frequent joint revisions. The editor clarifies a description after seeing a sketch, while the illustrator needs an explanation before the next version. It may be worth treating them as one larger part of the service. Calling them independent modules will not separate work that the company actually performs jointly.

Our team could keep content and illustration development together and handle preparation of approved material for a particular final form separately. Another company might separate the earlier stages more clearly. The owner should examine its own workflow and choose boundaries the team can maintain.

Observe an ordinary assignment. Where can the next person actually begin using the material handed over? When must they return to the previous worker just to establish the task? That return may be a necessary consultation or a sign that the declared module ends too early. Understand its purpose before counting every conversation as inefficiency.

Be especially careful with promises that modularity removes coordination. Division can clarify responsibilities and materials, but someone must still see the connections. In our example, the finished file should correspond to the approved content and illustrations. Completing each item separately does not itself prove that the ordered instructions are complete.

Who makes sure the parts form one service?

In a working paper dated 15 October 2007, Gittell and co-authors examine coordination of modules in professional care services. They discuss the importance of a role connecting stages and the limits of conclusions about its effectiveness. Their analysis does not settle how people actually cooperate merely because such a role exists.

Our company therefore needs a person who sees the selected configuration and can resolve questions between stages. They should know what the client ordered, what material was accepted and what constitutes the complete result. If they only forward messages and nobody can resolve a discrepancy in scope, the company has an internal postal service rather than coordination.

Suppose an illustrator receives material for an earlier version of the stand. The person leading the service should establish whether the wrong material was accepted or the client has just changed the product. The next step depends on that answer. The team should not create another version of the instructions merely to work around uncertainty at a module boundary.

For a change to a specific order, identifying a change in service-project scope (in Polish) helps. Regular development of a shared part of the offer raises a different decision: when a new version applies to subsequent work. Batching orders and setting a change window (in Polish) helps consider that rhythm without accidentally switching all work already in progress.

Aeneia Design

Have you established the service parts, permitted variants and required inputs? Let us turn that division into a clear website offer so the client's choice corresponds to work the company will actually perform.

Show the conditions for choosing service modules

Client adaptation need not rebuild the shared core

Return to the two input routes. The company can retain a common way of handing over approved material while varying how it is prepared. It need not change every stage for every client. But a new request that violates a condition on which the next task depends is no longer a minor change of label in the offer.

A discussion of packages and conditions rather than a discount alone (in Polish) can show the real possibilities. Removing a module makes sense when someone else supplies its necessary output or the goal of the order changes entirely. A promise of the identical whole with nobody performing the missing work remains incomplete, however tidy the price arithmetic looks.

Before publishing the offer, walk through selected configurations with the people who will deliver them. Do they know what they accept, what they hand on and when a question returns to the lead? If each route is rescued by a different undocumented task, the division needs another decision. If a common condition and explicit differences can be named, the company has a basis for a repeatable offer.

At Aeneia Design, an approved division can be presented through the service structure, variants and inquiry path. The site should show which materials clients can prepare themselves and what happens when they do not have them. In our example, editing can disappear from the order only when it is clear where the next worker will obtain the content they need.

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear