Scope Validation v2 / Latham × Nishtech / Confidential

Seven objectives, seven owners, one platform.

This version restates the scope the way Latham's business functions own it — Customer Service, Marketing, Commerce and the IT PMO each hold specific objectives. Three sections: the objectives to confirm, how the systems hand off, and the requirements grouped under the same seven headings. It is materially broader than the June 8 reading, and the places it grew are marked.

1  Objectives by business function 2  Systems & handoffs 3  Requirements by function 3  Scope expansions flagged
Section 1 Objectives by Business Function

Seven objectives. Are these yours?

Each objective now carries the Latham function that owns it, and the capabilities that sit under it. Open any card to see what it covers, what was said on June 8, and what we think it means to build. Where an objective is broader than our June 8 reading it is marked — six of the seven grew. Three of those change cost and sequencing materially, and they are the ones worth arguing about.

Use this live. Mark each objective confirmed or needs adjustment as we work through them. Nothing is saved or sent anywhere — a working tally for this conversation only.
0 / 7
Confirmed
Customer Service Marketing Marketing & Commerce Commerce IT PMO New  Expanded  since June 8
Section 2 Systems & Handoffs

Optimizely becomes the experience. Your business systems stay put.

The IT PMO objective states it precisely: IFS, Sugar, Configure One and Boomi all stay, and Optimizely is the system of reference over them — built for customer experience. That distinction is what keeps this programme sane. But it cuts both ways: some things Optimizely does replace, and being clear about which is the difference between a scoped programme and an argument in month four.

Optimizely owns

The experience layer

Every audience, authenticated and not, on one foundation.

  • One login across all accounts
  • The tile hub and dashboards
  • Corporate content and product pages
  • End-user specs and documentation
  • Invoices, AR, orders, warranty, RMA
  • Leads and rewards visibility
  • Multi-site and co-branded sites
  • Integrated DAM and editorial workflow
Configure One owns

Configuration & quoting

Untouched. No part of the CPQ investment is replaced, wrapped or rebuilt.

  • Complex product configuration
  • BOM and saleable line items
  • Distributor-to-indirect pricing
  • Quote creation and quote-to-order
  • The auto cover distributor flow
IFS, Sugar & CLIP own

The truth

Sugar stays the source of truth for the customer and continues to feed IFS.

  • Customer master and the four tiers
  • Segments, personas, entitlements
  • Pricing, inventory, orders, invoices
  • Loyalty and lead data
  • CLIP keeps lead assignment rules
  • Boomi stays the integration layer
Be explicit about this — it changed since June 8

What Optimizely does replace

The original brief kept the public WordPress site out of the B2B conversation. The Marketing objectives change that: one CMS foundation carrying corporate content, product content, end-user specs, the authenticated portal and co-branded dealer sites means the public site comes onto the platform too. That is a materially larger programme than the one we scoped in August, and it should be funded and sequenced as such rather than absorbed quietly.

Hybris commerce
Replaced by Configured Commerce. The multi-account and entitlement limits are the driver.
WordPress public site
Migrates onto the same Optimizely foundation. Corporate content, product pages and end-user specs.
Fragmented portal entries
Dealer portal, builder portal and Latham Link consolidate behind one login.
Two commitments hold the whole thing together. Administer once — segments, tiers, personas and entitlements are governed in Sugar and IFS today, and the portal consumes them; nobody maintains the same mapping twice. And one integration surface — Optimizely connects to Boomi, Boomi connects to everything else, so adding a system in a later phase is a Boomi process rather than a platform rebuild.

Pick a real question and watch the handoff

Six of these are calls your team takes today. The seventh is an audience the front door now has to serve that the June 8 scope did not.

Step 1DealerOpens the portal
▶
Step 2OptimizelyExperience layer
▶
Step 3BoomiIntegration layer
▶
Step 4IFSSystem of record
What happens today

What happens on the new foundation

Section 3 Requirements by Function

The same seven headings, now with what's under them.

Requirements grouped exactly as the objectives are, so each Latham function can read its own section. First Release is what we would build to replace the phone call and stand up the foundation. Later is real scope deliberately sequenced behind it. Items marked New did not appear in the June 8 scope at all.

Show

Explicitly not in scope — so there is no ambiguity later