vs. Your Home-Grown Planning System

The System Isn't the Problem. The Queue Is.

A home-grown planning system usually does exactly what the business asked for, because someone who understood the business built it. The constraint shows up later: when a planner needs a new hierarchy level, a new channel, or a KPI that isn't there, they can't make that change. They raise a request. In Buyer's Toolbox, the planner adds the level, writes the KPI, and changes the formula themselves — in the UI, without a developer. Ask your team how long the current change list is.

One Person Knows How It Works

Most internal planning systems depend on one or two people who understand the formulas, the stored procedures, and the reason for that one workaround in the 2019 sheet. That's not a criticism of them — it's the natural result of building something valuable in-house. But it means your buy depends on someone's calendar. Buyer's Toolbox is documented, supported and maintained by a team that has done nothing else since 1992, and it comes with the coaching to make sure the knowledge lives in your planning process rather than in one person's head.

Prove It Side by Side, Free

We'll build a proof of concept on your own data — your hierarchy, your categories, your sales history — and you can run it beside your current system and compare the numbers. No cost, no contract. If your system holds up, you'll have confirmed it with evidence rather than assumption, and you'll have lost nothing.

Comparison Highlights

Aspect	Buyer's Toolbox	Your Home-Grown Planning System
Fit to your business	Configured to your hierarchy, categories, calendar and KPIs — by you, not by us.	Excellent. It was built for you. This is its real strength.
Who changes the plan structure	The planner. Formulas, KPIs, hierarchy levels and views change in the UI — no code, no developer, no ticket.	The person who built it. Every structural change is a development task in a queue.
Who maintains it	A team that has built merchandise planning software since 1992. Support, upgrades and process coaching included.	One or two internal staff, usually alongside their actual job.
Documentation	Product documentation, training, and a support team.	Ask: if the person who built this were unavailable for three weeks during pre-season, who would change a formula?
Error control	Tested product logic, validated calculations, audit trail, sandbox environments for testing changes before they go live.	Independent research on operational spreadsheets has found errors in a large majority of those audited; studies disagree on the rate, but not on the presence. Errors are also very hard to find once made.
Scale ceiling	Item, week and location granularity across multi-banner, multi-currency, multi-country structures. 5 years of history included.	Excel has a hard limit of 1,048,576 rows per sheet. SQL Server back-ends move that ceiling but add a second system, and a second thing to maintain.
Planning depth	Top-down, bottom-up, middle-out. Attribute-aware. Cost, Retail and Units. Pre-season, in-season, cross-season. Vendor planning, collections, key items.	Whatever was built. Usually strong on the original requirement, thinner on scenarios, attribute planning, and anything added after the original design.
Exception alerting	Xi surfaces stockouts, overstocks and plan variances ranked by dollar impact, proactively.	Typically conditional formatting and a report someone remembers to run.
Adding a channel, banner or country	Configuration. Hierarchy changes and additions are standard.	A project. Usually the point at which retailers start looking.
Cost	Published: from $995/month. Annual, billed quarterly, no multi-year lock-in.	Invisible, not zero. A share of one or two salaries, indefinitely, plus the risk that isn't on any budget line.
What happens to the internal expert	They stop maintaining a planning system and go back to the work only they can do.	They keep maintaining a planning system.

Common Questions

Answering your questions.

Our system works. Why would we replace something that fits us perfectly?

If it fits and it's stable, you may not need to. We'd rather tell you that than sell you something. The question we'd ask is what happens next: are you adding a channel, a banner, a country, wholesale? Has your store count grown significantly since the system was designed? Is the person who maintains it doing more of it than they used to? A home-grown system usually doesn't fail — it just stops keeping up with a business that changed shape. If none of that is happening, you're fine.

Our IT team built it and knows it inside out. Isn't that better than depending on a vendor?

They probably do know it better than any vendor knows their own product — that's genuinely an advantage. What we'd ask you to look at is the concentration. If that knowledge sits with one or two people, your pre-season buy depends on their availability, and the change list depends on their capacity. Most internal builders we meet are relieved rather than threatened: maintaining a planning system is rarely what they were hired to do, and it's rarely what gets them promoted.

Isn't this just a spreadsheet argument? We're not running on Excel alone — we have a proper SQL Server back end.

A SQL back end solves the row limit and the version chaos, and it's a real step up. It also means you now maintain two systems and the connection between them, usually without a test environment, version control, or a second person who understands the stored procedures. The question isn't whether it's well built. It's whether the business can change it as fast as the business changes.

We've invested years in this. Isn't switching wasteful?

The years aren't wasted — they're the reason this will go quickly. Everything your team learned about how your business plans is exactly what we configure into Buyer's Toolbox, and it's why our proof of concept runs on your data rather than a demo dataset. The logic you built doesn't get thrown away; it gets somewhere it can be changed by the people who use it.

How do we compare fairly without disrupting the planning cycle?

Run them side by side. We build a proof of concept on your data in one to two weeks at no cost, and you compare the output against your current system for a full planning period. Nothing gets turned off, nothing gets migrated, and no contract exists. Then apply the same test we'd give any vendor: pick three changes — add a hierarchy level, add a custom KPI, restate a formula — and time how long each system takes to make them.

What happens to our IT staff if we do this?

They stop being the planning system. In practice that means they hand over formula and hierarchy changes to the planners who need them, keep ownership of the data integration, and get their time back for work that isn't maintaining a merchandise plan. We implement and support the product ourselves, so they're not inheriting a new maintenance burden either.

Is Your Planning Process Burning Out Your Best People?

Buyer's Toolbox AP vs. Your Home-Grown Planning System