08 / Pricing Wizard
Foundations
Period
Showing every quote since the wizard launched · Newest quote 30 Jul 2026
08Foundations · What the numbers rest on

Every figure in this report traces to 30 tables holding 1,370,589 rows.

The pricing arithmetic reconciles: the margin formula matches on every line, and package value matches on 97% of packages. What is missing is not accuracy but coverage. Five fields sit empty and each one blocks a specific report. Those are listed at the end for the data owner.

Tables
30
7 v2, 7 legacy, 16 lookup
Rows across all tables
1,370,589
7,187 of them are new-wizard quote lines
Empty tables
3
One of them is the cost source
Revision snapshots
2,246
Full JSON of the quote at each save
Exhibit 8.1

The pricing arithmetic reconciles against the wizard's own logic.

Line price = qty x unit x (1 - discount) x 1.25 if AKA
94.7%6,804 of 7,187
Markup = (price - unit) / unit x 100
100.0%7,187 of 7,187
Package quoted value = volume x sum(line price)
96.8%1,287 of 1,329
Source: every formula re-computed in SQL over all quote lines and packages, and compared to the stored value.
Exhibit 8.2

Five fields on the new wizard are present but never populated.

approvedby
75%438 of 585
approvedmaxnondtohdiscount
75%438 of 585
additionalnotes
13%74 of 585
integrationpartnername
11%62 of 585
contract_termduration
7%41 of 585
salesforceopportunityid
0%0 of 585
account_accountname
0%0 of 585
account_clientaccountnumber
0%0 of 585
Source: population counts across all 584 exhibits in ubs_pe_pricingexhibitsv2.
Exhibit 8.3

The population this report measures, and what it leaves out.

426
Priced quotes
The denominator for every figure here
99
Templates excluded
Reusable shells, not pipeline
60
Empty drafts excluded
No packages, all at a default 30% discount
Source: ubs_pe_pricingexhibitsv2 against its package children.
Exhibit 8.4

All thirty tables, with size and family.

30 rows
ubs_pe_pricingexhibitpackageproductsLegacy251,120,870
ubs_pe_pricingexhibitpackagesLegacy16171,451
ubs_pe_pricingexhibitsLegacy10866,741
ubs_pe_pricingexhibitproductsv2V2137,187
ubs_pe_pricingexhibitversionsv2V262,246
ubs_pe_pricingexhibitpackagesv2V2111,329
ubs_pe_pricingexhibitsv2V243585
ubs_pe_pricingexhibitusersv2V2464
ubs_pe_pricingexhibitpackageproductextensionsLegacy630
ubs_pe_pricingexhibitusersLegacy411
ubs_pe_statespecificskusLookup411
ubs_pe_ohservicecategoryLookup210
ubs_pe_globaldiscountLookup29
ubs_pe_customertypeLookup25
ubs_pe_eformsetupfeetypeLookup35
Source: information_schema for column counts, svv_table_info for row counts, schema edwdata1.raw.

Five questions for the data owner

Each of these blocks a report someone will ask for. They are listed in the order they would unlock the most value.

01

Will the product catalogue be populated?

Blocks: True margin. Every profitability question.

ubs_pe_priceexibitproductcatelogv2 has the right columns, including cost, and zero rows. Without it, the wizard's margin field is only a markup over list price and no one can say whether a discounted deal is profitable.

02

Will account number and Salesforce opportunity id be filled?

Blocks: Quote-to-cash. Realisation rates. Account-level reporting.

All three account fields are empty strings on every quote and the Salesforce id is null throughout. Two views already in the warehouse, ubs_vw_packages_v2 and ubs_vw_billingids_v2, join on account number and would connect quotes to billing the moment it appears.

03

Where does win and loss live now?

Blocks: Win rate. Forecast accuracy. Discount effectiveness.

The new wizard has no outcome field at all. The old one had quotestatus, but it recorded almost no losses. If outcome sits in Salesforce, a key back to it is the missing link.

04

What dimension does accioproductid point at?

Blocks: Product hierarchy. Category-level rollups.

557 distinct numeric ids on the quote lines match nothing loaded. The obvious candidate, ubs_vw_wizardsetupproductlist_v2, uses string codes and matches zero of them.

05

Is the old wizard frozen or still live?

Blocks: Whether legacy needs an ongoing refresh.

A handful of exhibits were still written to it after the cutover. Small enough to be edits of old records, but it means the table is not definitively closed.

The analyst’s read