Know exactly what you own, what's installed, and what you're overpaying for.

She builds the licensing foundation: your software product setup, entitlements with the right license metrics, and rules that reclaim dormant seats. She reads your installed software, entitlements and current license position first, so every proposal is grounded in real numbers, then stages the changes in one reviewable package. You get a licensing setup ready to manage compliance and cost.

No. Reconciliation compares what's actually installed against your entitlements, so an inventory source has to be populating installs first and they have to be recognised against a vendor catalogue. Phyllis flags both as prerequisites rather than promising a compliance position on empty data. You get an honest readiness check, not a false green light.

Individual seat allocations are day-to-day records your fulfilment process creates at request time, not licensing config. Phyllis builds the entitlement and the process that allocates against it, and checks remaining seats before promising access. She sets up the engine; your team keeps handing out the seats.

No. Phyllis reviews, proposes a plan, and waits. Nothing is written to your instance until you approve, and every build is staged in a reviewable package you can inspect or roll back. You stay in control.

Every finding is read from and cited to your live instance — your real entitlements, installed titles and license metrics — not a template. Where there's no safe way to build something, she flags the gap in the plan instead of forcing a risky change. You get grounded evidence, not guesswork.