Phase 2 · Working Plan · Pivot × Integrity Design

Rebuilding the quote system — with everything Brandon's been waiting for.

Re-platforming Integrity Design's custom-coded quote and PO automation onto HubSpot's new React module architecture, unlocking Commerce Hub Pro for automated tax and tiered pricing. Cutover aligned to the June 12 renewal.

Client
Integrity Design
Engagement
Phase 2 — Module Rebuild
Investment
$8,500 fixed-fee
Cutover
Friday, June 12, 2026
Status
Awaiting approval
01

Context — why we're here.

In October 2025, Pivot delivered Integrity Design's custom-coded quote and purchase order system on HubSpot's legacy quote architecture, scoped at $4,000. That system has been running in production across all six pipelines — Dealer-Terms, School-PO/Terms, School-Prepay, Under Armour, Sample/Comp, and Warranty Reprint — generating thousands of customer quotes and vendor POs, integrated with Brandon's Softr customer portal for Under Armour (and rolling to BSN and Sports Inc. this month).

HubSpot's Commerce Hub Pro upgrade unlocks two features Integrity specifically needs: automated sales tax calculation (eliminating the manual California tax workaround in QuickBooks) and tiered pricing (consolidating the current 20-SKU-per-product structure down to a single SKU per pricing tier). However, activating Commerce Hub Pro on the legacy architecture would break the custom-coded module that renders proofs on quotes and POs — confirmed by the September 2025 trial incident.

As of May 7, 2026, HubSpot released the public beta of custom-coded React modules on CPQ quote templates, with general availability on May 25, 2026. This is the architecture we re-platform onto. Pivot has been working with HubSpot's product team since November 2025 to be ready for this transition.

Phase 1 was completed and delivered, with 10 points unused at the close of that engagement — those 10 points carry forward into Phase 2 and are applied against this work. The Phase 2 scope below represents 85 additional points, for a total project scope of 95 points of work across the Pivot team. During our May 21 review call, Brandon asked Pivot to extend scope to include the product library restructure and Commerce Hub Pro tax setup — both included in this engagement.

Original Engagement
$4,000 — Phase 1 paid October 2025
Points Remaining
10 points carry into Phase 2
This Engagement
$8,500 — Phase 2 rebuild + Brandon's May 21 additions
Total Project Scope
95 points (10 carried + 85 new)
HubSpot Renewal
Friday, June 12, 2026
New Pricing Rollout
June 19, 2026 (on new system)
02

Scope of Work — ten deliverables.

Each deliverable below has check-off, status, and a comment field for ongoing tracking during execution. This document is the live working plan — it becomes the project's source of truth from approval through cutover and into post-launch.

Not started Complete

1. React quote module on the new CPQ architecture

Build the custom-coded React module that renders Integrity's print proof grid on customer-facing quotes and vendor purchase orders. Replaces the legacy quote_imageProofs HubL module with a TypeScript/React implementation deployed via HubSpot Developer Projects. Reads the same two deal properties the existing UIE card writes to (print_proof, print_proof_info) so the data layer needs no changes.

Owner: Chandler Effort: ~21 points Builds on: Existing demo work

2. Two-column proof layout (Image + Description)

Per Brandon's May 21 confirmation, the proof grid drops the "Name" column. The line-item description is already shown above; the proof name was redundant. New layout: Image and Description, two columns. Saves CSR time. The data schema keeps three fields for backward compatibility with existing quotes.

Owner: Chandler Effort: Included in module build

3. New PO naming convention

Update generated PO titles from [Deal Name] | Vendor X - Purchase Order to Integrity Design PO# [Sequential Deal Number] | [Vendor Name]. The "Sequential" app already generates the deal number Brandon uses as the quote number — we incorporate it into PO names so it appears in vendor email subject lines and makes tracking easier across systems. Workflow enrollment criteria updated to match the new naming pattern (prevents the regenerated POs from re-triggering the workflow).

Owner: Chandler Effort: ~1.5 points

4. Compressed header layout (Quote + PO templates)

Brandon's vendors report the current blue header takes up roughly three-quarters of the printed page, sometimes pushing product onto page two. This applies to both the Quote template and the PO template, which share the same header treatment — both need the compressed layout. Reduce header height by removing unused fields and tightening spacing. Keeps all required information (logo, Quote/PO number, billing/shipping, dates) but in a more compact form that leaves room for product on page one.

Owner: Chandler Effort: ~2.5 points

5. Rebuild PO-generation workflow + CCA

Port the existing PO-generation Custom Code Action to the new architecture, preserving all current behavior: multi-vendor PO splitting (one PO per vendor's line items), vendor-cost pricing pulled from product hs_cost_of_goods_sold, and the dual-trigger pattern (stage-driven for Softr portal flows, e-sign-driven for legacy email approvals). While in the code, we also bring it up to the same quality standards as the existing invoice automation — proper idempotency to prevent the Feb 2026 PO duplication scenario, defensive error handling, and fail-loud alerts.

Owner: Chandler Effort: ~12 points Risk reduction: Eliminates Feb 6 incident pattern

6. Two new CPQ quote templates

Build two CPQ templates in the sandbox that embed the new React module: one customer-facing (replacing legacy Quote | Integrity Design) and one vendor-facing (replacing legacy Purchase Order | Integrity Design, template ID 455856752028). Each preserves Integrity branding, includes the required hidden default Line Items module per HubSpot's new architecture, and connects to the rebuilt workflow.

Owner: Chandler Effort: ~7 points

7. Sandbox-first testing + production cutover

Full build and test in Integrity's sandbox (which already has a Commerce Hub Pro trial active). Eleven-scenario test plan covers all six pipelines, multi-vendor edge cases, the Softr-portal approval path, and the workflow re-fire scenario from Feb 2026. Brandon receives a client-side test plan to verify on his end. Cutover Friday June 12 with workflow lockdown, sandbox-to-production push, and live validation. Pivot monitors production for one week through June 19 ahead of the new pricing rollout.

Owner: Pivot team (Chandler + Christa + Jane) Effort: ~15 points Window: 1 day operational pause estimated

8. Product library restructure — schema design

Brandon's May 21 request — added to scope. Pivot designs the new tiered-pricing data structure that consolidates the current 20-SKU-per-product approach (5 quantity tiers × 4 pricing tiers — retail, dealer, barter, vendor cost) into a single SKU per pricing tier with quantity-based tiers handled by Commerce Hub Pro's native pricing engine. Includes: schema mapping document, custom properties on Products object to represent tier and quantity-break relationships, a CSV template Integrity fills with the new product data, documented upload procedure with screenshots, and validation of a sample batch in sandbox before Integrity does the bulk import.

Integrity-side handoff: Brandon's team executes the bulk product upload using the template and procedure Pivot provides. Pivot validates the first batch and provides support during the broader import.

Owner: Jane (design) + Chandler (validation) Effort: 6 points Hand off to Integrity: Bulk upload execution

9. Commerce Hub Pro automated tax setup

Brandon's May 21 request — added to scope. Configure HubSpot's automated tax calculation in production once Commerce Hub Pro activates post-renewal. This eliminates the manual California tax workaround Integrity's accountant has been running in QuickBooks (adding tax as a line item, then correcting it in QuickBooks after sync). Configures: California nexus and tax registration details, product tax categories on the new tier-based SKUs, customer tax-exempt handling where applicable. Validates that QuickBooks sync handles automated tax correctly. Tested against representative scenarios — California direct order, multi-state shipping, exempt customers.

Includes a brief configuration document for Integrity's reference and Stephanie Ledbetter's handoff. Tax setup happens post-cutover (Week 4) since Commerce Hub Pro must be active in production for these settings to take effect.

Owner: Chandler Effort: 4 points Eliminates: Manual QuickBooks tax workaround

10. Future-proof the UIE Print Proof Manager card

The UIE Print Proof Manager card is integral to the system — it's where the team manages print proofs on deals, writing to the print_proof and print_proof_info deal properties that the new React quote module (Deliverable 1) reads from. It currently runs on an older HubSpot UI Extensions version that HubSpot will eventually deprecate; left as-is, the card will stop working at some point. While we're already in the Developer Projects codebase for the re-platform, we update the card to the newest UI Extensions SDK and platform version — behavior stays identical, but the card moves onto a supported, future-proof foundation that keeps running well past this engagement. No data-layer or workflow changes; purely a version and runtime upgrade.

Owner: Chandler Effort: Included in current scope (no added points) Future-proofs: Integral proof-management card
03

Out of Scope — explicitly noted.

These items are related to the Commerce Hub Pro transition but fall outside this engagement. Most are Integrity-side work that the new architecture enables but Pivot doesn't execute as part of this rebuild.

Items not included

  • Bulk product data upload Pivot designs the new tiered-pricing schema (Deliverable 8) and provides a CSV template plus documented upload procedure. Integrity's team executes the bulk upload of all products using that template. Pivot validates the first batch and provides support during the broader import — but the data entry itself is Integrity-side work.
  • Softr portal changes The existing Softr ↔ HubSpot integration stays exactly as it is. The deal-stage-change trigger the portal already uses continues working with the new system. No changes required to the Softr side.
  • Invoice generation automation Existing invoice workflow runs independently and isn't affected by this rebuild. Continues operating throughout the cutover. (Tax automation in Deliverable 9 will eliminate the QuickBooks workaround that affects invoicing downstream.)
  • Historical data audit Optional cleanup of any historical deals that may have accumulated duplicate vendor-cost line items from prior workflow re-fires. Available as a separate small engagement if Brandon wants to verify the data going into the new system.
  • QuickBooks integration changes The HubSpot-to-QuickBooks sync stays as-is. Once automated tax is active in HubSpot (Deliverable 9), the workaround on the QuickBooks side becomes unnecessary — but no changes to the QuickBooks sync itself are part of this engagement.
04

Approach — sandbox-first, then cutover.

The Commerce Hub Pro upgrade is gated on the legacy custom module being replaced. Pivot's approach is to build the complete replacement in Integrity's sandbox (which already has a Commerce Hub Pro trial active), test it end-to-end against real production scenarios, validate with Brandon, and then push it to production in a coordinated single-day cutover aligned to the June 12 renewal.

Why sandbox-first: the September 2025 incident demonstrated that activating Commerce Hub Pro on the legacy system breaks daily operations immediately. By building and testing in sandbox, we eliminate the risk of any "find out at the worst moment" surprises. Brandon and his team can see the full system working in sandbox before any production changes.

Why aligned to renewal: June 12 is both the renewal date and a Friday. Renewal activates the Commerce Hub Pro license; pushing the rebuilt system live the same day means the upgrade is non-disruptive — flip from legacy to new, with everything tested in advance. June 19 is the planned new pricing rollout, which happens on the new system one week after cutover.

What's required from Integrity during cutover: roughly one day of "no new proofs entered" while Pivot does the sandbox-to-production push and live validation. Brandon estimated this on the May 21 call as "a couple days at most" — Pivot's estimate is one business day if everything proceeds as planned in sandbox.

05

Timeline — three weeks to cutover.

Week 0
May 27 – May 30, 2026
Approval + kickoff

Brandon reviews and approves this working plan. Pivot finalizes sandbox access, confirms Commerce Hub Pro trial is active, and Chandler clears his schedule. Christa coordinates initial milestone check-ins.

Week 1
June 1 – June 5, 2026
Sandbox build + product schema design

Chandler finishes the React module, builds two CPQ templates, ports the PO-generation CCA to the sandbox with quality improvements (idempotency, error handling, naming convention update). In parallel, Jane designs the new tiered-pricing product schema and produces the CSV template for Integrity's bulk upload. Daily progress updates to Pivot internal team.

  • React module complete with two-column layout + compressed header
  • Both CPQ templates built and validated
  • PO-generation workflow rebuilt and triggering correctly
  • Product schema designed and CSV template delivered to Brandon
Week 2
June 8 – June 11, 2026
Sandbox testing + Brandon walkthrough + product upload

Eleven-scenario test pass run in sandbox by Christa. Issues found get fixed and retested. Brandon walkthrough mid-week to verify rendering, naming, behavior. Client-side test plan delivered to Brandon for sign-off. Integrity's team executes the bulk product upload using the CSV template from Week 1; Pivot validates the first batch and supports the broader import. Final cutover plan confirmed.

  • All eleven scenarios pass in sandbox
  • Brandon's walkthrough complete, written sign-off received
  • Product data uploaded by Integrity's team; Pivot validates
  • Cutover playbook finalized
Week 3 — Cutover
Friday, June 12, 2026
Production cutover

Coordinated cutover day. Workflows paused, sandbox pushed to production, live validation runs through three smoke-test deals across pipelines, workflows re-enabled. Brandon's team back online by end of day.

  • HubSpot renewal processes; Commerce Hub Pro activates
  • Production push complete by mid-day
  • Three live smoke tests confirm end-to-end function
  • Daily ops resume by end of business
Week 4 — Monitoring + tax setup
June 15 – June 19, 2026
Post-cutover monitoring, tax configuration, pricing rollout prep

Pivot monitors production daily for issues — workflow run history, error rates, any reported anomalies. Chandler configures Commerce Hub Pro automated tax (Deliverable 9) — California nexus, product tax categories, QuickBooks sync validation. Brandon prepares new pricing rollout for June 19, now running on the new system with automated tax in place. Any minor fixes or refinements are handled during this window without disruption.

  • Automated tax configured and validated against test scenarios
  • QuickBooks workaround retired
  • New pricing rolls out June 19 on the new system
  • Tax configuration documented for Integrity's reference
06

Test Plan — eleven scenarios.

Each scenario runs first in sandbox, then again in production after cutover. Christa runs the tests (not Chandler — separation between build and test is intentional). Brandon's walkthrough during Week 2 sees scenarios 1, 3, and 7 live.

01

Single-vendor Dealer quote

One line item, one proof. Quote renders proof, signature generates exactly one PO, PO renders the same proof.

02

Single-vendor, multiple items

Multiple line items, multiple proofs from the same vendor. Module handles arrays correctly. PO carries them through with correct vendor-cost pricing.

03

Multi-vendor Dealer quote

Three or more vendors, five or more line items split across them. One PO per vendor, each containing only its vendor's items and proofs at vendor cost.

04

School-PO/Terms pipeline

Pipeline-specific trigger and stage configuration verified. Workflow fires on "Approved Via Email-ST" stage entry.

05

Under Armour via Softr

Softr portal approval path — customer approves through portal, HubSpot deal stage updates, workflow fires. The non-e-sign trigger path works.

06

Sample/Comp negative test

Marketing samples deal moves to closed-won. Verifies no PO is generated. Confirms scope boundary.

07

Idempotency — re-fire guard

Move deal to trigger stage, back, then forward again. Verifies the runaway-PO guard holds. Exactly N POs after the second forward-move, not 2N. Directly addresses the Feb 2026 incident pattern.

08

UIE card edit after send

UIE Print Proof Manager edits after a quote is sent. Behavior is defined: either quote updates dynamically or a new version is required. Documented and consistent.

09

Mid-run failure recovery

Workflow fires but PO creation fails for one of N vendors mid-run. State is recoverable, no orphaned POs left in inconsistent state.

10

Automated tax calculation

Multi-state quote with California shipping. HubSpot Commerce Hub Pro automated tax calculates correctly. The reason for the upgrade — verified working.

11

PO header on print

Vendor PO downloaded and printed. New compressed header occupies less than half the page. Product line items begin within the first half of page one.

07

Investment — $8,500 fixed-fee.

Phase 2 fixed-fee
$8,500
In addition to the $4,000 Phase 1 engagement paid October 2025, with 10 unused points carried forward. Original Phase 2 estimate was $7,500 covering the seven core rebuild deliverables; $1,000 added to include Brandon's May 21 requests — product library schema restructure (Deliverable 8) and Commerce Hub Pro automated tax setup (Deliverable 9). Fixed-fee covers all nine deliverables outlined in Section 02, sandbox build, eleven-scenario test plan, production cutover, post-cutover tax configuration, and one week of post-launch monitoring.
Project scope
95 points (10 carried + 85 new) across Pivot team
Team allocation
Chandler (lead developer) + Christa (testing & client) + Jane (architecture & schema)
Payment
Net 15 from invoice, due at project kickoff
Out of scope
Items in Section 03 — primarily Integrity-side execution work (bulk product upload, etc.)
08

Acceptance — let's get started.

Ready to proceed

Approval of this working plan kicks off Phase 2 immediately. Chandler clears his schedule, sandbox build begins June 1, and we land cutover on Friday June 12 — aligned to your renewal, ahead of your new pricing rollout on June 19.

This document becomes the live project artifact from approval through launch. Throughout execution, checkboxes get marked, comments get added, and timeline items get updated. It's the single source of truth for Phase 2 status — accessible to Brandon, the Pivot team, and anyone Brandon wants to share it with at Integrity.

Approved by — Integrity Design
Brandon Earls
Director of Operations & National Sales-Operations
Authorized by — Pivot
Christa Bender
Director of Client Growth · Pivot Communications