Mapping several services together

When a business has more than one service, submit them all in one intake when you can. The plan reads them side by side and decides, phase by phase, where they share one workflow and where a service needs its own.

Why one intake beats several

This is why a three-service business does not get three of everything. Genuinely shared phases combine into one workflow. Service-specific phases, proposals especially, split into their own.

The result is a system shaped like the business actually runs: shared where the services genuinely overlap, separate where they genuinely differ.

What you lose by splitting the intake

Mapping services one at a time as separate businesses loses that shared design. Each map is planned in isolation, so nothing can combine, and you end up maintaining parallel copies of phases that should have been one workflow.

Reading the result

The Map subtab's Workflow Index shows the decision for each workflow, so you can see exactly where the plan combined and where it split.