Quotes that price themselves and orders that break themselves down.

She stands up the configuration that makes lead-to-cash run — the product catalog and its offerings, the pricing that turns list price into net price, the quote-to-order behaviour, and lead routing. The leads, quotes, and orders themselves stay in your team's hands; Phyllis configures the catalog and pricing engine that generates and prices them.

By modelling variation the right way — reusing shared building blocks and driving price differences from rules rather than spawning a separate item for every speed, region, or tier. She reads your live catalog first, so she extends what's already there instead of cloning it, which is the single biggest mess these projects hit.

She configures the full pricing picture — what you charge, what it costs to deliver, and how discounts, overrides, and taxes stack down to a net price. Phyllis maps your existing setup before touching anything, because the ordering matters as much as the individual rules, and she extends the shipped defaults rather than mutating them.

Correct. Phyllis discovers, proposes a plan, and only builds on your explicit approval, staging every change in a reviewable package. Because sales and order work spans several areas, she keeps each one's changes cleanly separated so nothing collides at deploy time, and staged fixes run only when you approve them.

Every claim is cited to what she found in your live instance — the offerings already in your catalog, the price lists in play, the quote behaviour driving order creation. She reads your real setup rather than assuming out-of-box defaults, because on migrated instances catalog, pricing, and quote settings drift from the baseline.