Price List Migration: Each Account Moves Once, at the Right New Amount

Why price changes go wrong between the decision and the notice

Retiring a price list sounds like a spreadsheet job. Each wholesale account on a monthly plan either migrates to the same plan at its new price, is remapped because its old plan no longer exists, stays on contract pricing until renewal, or is excluded because it is cancelling. The new monthly amount comes from the plan mapping table and the account's current quantities, and a notice goes to every account whose price actually changes.

The facts sit in four places. Owners and contract terms are in HubSpot, the live subscription and its amount are in Stripe, the billing contact's email status is in Mailchimp, and the mapping table is a Google Drive sheet that finance edits. Customers reply early, the pricing committee grants exceptions, and someone finds a mapping error halfway through. Each change is applied by hand, and the notice list drifts away from the decisions.

Who works in the room

The team runs the migration in one room. Ryan is the default agent, so a question about an account's disposition or amount reaches it without anyone naming it. Anything about the notice schedule goes to Ada, which owns that review, and anything a customer will read goes to Fin. When Ryan finishes a re-run, it opens a new thread for Fin whose first message lists the changed accounts and the reason for each, so the correspondence starts from approved numbers.

The migration in seven steps

The rules sit in the migration folder and in the room guidelines, so every agent works from the same version. Each step ends with a person.

Updates that arrive halfway through

Most changes arrive as replies. A cafe owner answers the courtesy email to say they accept the new price from this month. Fin works through the account manager's Gmail connection, which is checked on every call, finds the thread that customer actually wrote on and drafts a short confirmation there. The account manager sends it. Ryan marks the account as accepted early and leaves the approved amount alone, because accepting early does not change the price.

The mapping correction is the real test. Finance finds that one retired plan was mapped to the wrong new tier. Ryan re-runs only the accounts that were on that plan, writes a new result where it differs, and leaves the rest untouched. Ada then checks the notice schedule again, because a remapped account with a new amount needs a corrected row before marketing sends anything. Accounts whose increase passes the threshold are set to urgent in HubSpot so their account manager calls first.

What the checks catch

• A notice schedule that includes contract accounts or lists an account twice, when only migrate and remap accounts belong on it, each once
• A confirmation drafted on a similar thread from another customer instead of the one where the acceptance arrived
• Accounts rewritten after the mapping correction even though their plan and amount came out the same
• Urgent priority set on accounts below the increase threshold, which buries the calls that matter
• A billing contact whose address bounced in Mailchimp, so the notice would never reach the account

What stays with people

• Approving each disposition and amount before HubSpot or Stripe changes
• Sending every customer reply, which Fin prepares as a Gmail draft
• Scheduling the notice campaign in Mailchimp once the segment is confirmed
• Granting pricing exceptions and signing off the migration

Integrations in this workflow

Kylon is not a billing system or a CRM, and it does not replace either one. It sits across the tools the revenue team already uses and holds the coordination between them.

• Gmail
• Google Drive
• HubSpot
• Mailchimp
• Slack
• Stripe

• HubSpot holds the accounts, owners, contract terms, priority flags and close-out notes
• Stripe shows each live subscription with its plan and amount, and Ryan schedules the new price there only after finance approves
• Mailchimp holds the billing contacts and the notice segment, which Fin tags after approval and marketing sends
• Gmail carries customer replies, answered through drafts an account manager sends
• Google Drive keeps the price list, the plan mapping table, the committee's exception list and the notice schedule
• Slack is where account managers post call outcomes and quick questions for the room

Where to start

Pick one price list and the accounts on it. Connect HubSpot and Stripe, put the mapping table in a shared Drive folder, and write the one rule that matters in the room guidelines: agents propose dispositions and amounts, and nothing is written to HubSpot or Stripe, and no segment is tagged in Mailchimp, until the revenue operations lead approves.

“The mapping changed once, and only the accounts it touched moved.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.