Talk about your next project
Illumio one-pager

The lesson

Make a service add-on easy to buy by tying scope, prerequisites, deliverables and dependencies to the core package.

The move

The datasheet opens with “Additional PCE Migration Window” and an “Overview” that explains the add-on, when customers need it, what Illumio Professional Services does during the window, and how it relates to the core migration package. “Prerequisites” is split into “Package Dependencies,” “Strongly Recommended Packages,” “Technical Readiness” and “Customer Readiness.” “Covered Services” breaks the work into “Window Planning,” “Window Migration” and “Window Validation and Handoff,” each followed by a “Customer Outcome.” It closes with “Expected Timeline,” “Get Started,” and a visible SKU in the side rail.

Why it works

  • Our readThe overview answers the buying question first: what the add-on covers and why a customer might need another migration window.
  • Our readSeparating technical readiness from customer readiness shows which blockers belong to systems and which belong to scheduling, access and staffing.
  • Our readAdding a customer outcome under each service block turns delivery tasks into plain evidence of what the customer receives.

What not to copy

Don't copy the migration-window framing unless your service is sold as an add-on to a larger engagement. Keep the sequence of overview, dependencies, readiness, covered services, outcomes, timeline, SKU and contact CTA.

More from Illumio

More one-pagers

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.