runbookify
← All plans
Sales & CRM / Account & Contact Management

Book-of-Business Reassignment Tool

Plan and execute account ownership changes - rep departures, territory realignment, new-hire ramp - with a before/after book, load balancing, conflict flags, and a clean reassignment file plus handoff notices, so reorg day never drops or double-assigns an account.

IntermediateA weekendBuilds onNext.js (App Router) on VercelSupabase (Postgres, Auth, RLS, Storage)Resend (email)
What you'll build

Import your current book and rules, get a computed proposed reassignment with balance and load metrics, review flagged conflicts (like deals closing mid-cycle), approve as ops, and export a clean ownership-change CSV plus auto-sent handoff notices - with a full before/after audit trail.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.

Before you start

  • A current account book you can export (CSV or Google Sheet) with owners and key attributes
  • Your reassignment rules and targets (who gets what, load caps)
  • Free Vercel, Supabase, and Resend accounts

The problem this kills

A rep leaves, a territory gets re-carved, or a new hire needs a starter book - and someone in sales ops is in a spreadsheet at 11pm dragging account names between columns. One slip and an account ends up owned by nobody, or by two people who both think it's theirs. Deals mid-cycle get yanked away from the rep who's about to close them. Nobody can reconstruct who decided what, or why. Reorg day becomes a week of cleanup, angry reps, and customers who get three "I'm your new contact" emails or none at all.

The spreadsheet has no guardrails. It can't tell you that one rep just got 40% more revenue than everyone else, it can't stop you from assigning the same account twice, and it has no memory of what the book looked like yesterday.

What you'll build

A small, secure internal web app that turns the territory carve-up into a reviewed, auditable workflow:

  • Import your current book - accounts with their current owners and the attributes that matter (revenue, region, tier, open deals) - from a CSV or Google Sheet.
  • Load your reassignment rules - who's eligible to receive accounts, load caps by count and revenue, and any "keep with current owner" protections.
  • Compute a proposed new book - the tool drafts ownership changes, balances the load across reps by both account count and revenue, and shows a clear before/after view.
  • Flag the conflicts before they bite - accounts with deals closing soon, reps over their cap, accounts that would be left unassigned.
  • Human approval gate - ops reviews the proposal and the metrics, resolves exceptions, and only then commits the changes.
  • Clean output - an ownership-change CSV in exactly the columns your CRM expects, plus handoff notice emails sent through Resend.

What's inside the Implementation Plan

The plan is a complete, paste-and-go runbook for an AI coding agent (Claude Code). You don't write code - you paste the plan, answer a few questions, and approve as it builds.

It opens by interviewing you about your business. Before a single screen is built, the plan has the agent ask about your current carve-up process, the systems and spreadsheets you live in, the exact field names and ID conventions in your account data, your typical and peak account volumes, your real load caps and protection rules, and your messy edge cases (house accounts, co-owned strategic accounts, deals closing this week). It reflects a short tailored spec back to you and waits for your thumbs-up - so the tool fits your book, not a generic template.

Then it walks the build step by step, each step ending with a ready-to-copy prompt:

  • Project setup, login, and database with row-level security.
  • The import flow for your current book and your rules.
  • The reassignment engine with balance-by-count and balance-by-revenue.
  • The conflict and exception flagging logic, including deal-protection rules.
  • The review-and-approve screen with the before/after book.
  • The ownership-change CSV export and the Resend handoff notices.
  • A full before/after audit trail and duplicate guards.

The governance it includes (this is the point)

This isn't a toy. The plan builds the controls sales ops needs to trust the result:

  • Login so only your team can open the tool.
  • Row-level security so people only ever see their own organization's data.
  • A hard human-in-the-loop approval gate - the tool drafts the new book; a person reviews the balance metrics and exceptions and approves; only then are ownership changes committed and handoff emails sent.
  • A complete audit trail - the full before book, the after book, who approved, and when.
  • Duplicate guards keyed on account ID - one new owner per account per run, so the same account can never be processed twice or double-assigned.

Who it's for

Sales ops analysts and sales managers who run territory realignments, handle rep departures, and ramp new hires - the people who currently do the carve-up by hand in a spreadsheet and dread the cleanup. If you can use a spreadsheet and follow instructions, you can build this.

You've got this - paste the first prompt and let the agent interview you.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.