Sales Stack

Adding one more tool always looks like the right call. A sequencing tool means the rep no longer tracks send dates by hand; a call transcription tool erases the twenty minutes spent writing up notes afterward. Considered one at a time, every one of them saves time.

Stack four of them, though, and a rep's day gets strange. After one call there are four things to do: update the stage in the deal record, remove that company from the next step in the sequencer, copy the notes out of the transcription tool into the deal record, and write the contact date into the list spreadsheet. Work that took twenty minutes before any tools existed now takes twenty-five with four of them.

Worse, the information that landed in four places starts to disagree. The sequencer still has that company marked as pending outreach, so an introductory email goes out again to someone you met yesterday. They read that as a company that doesn't remember them.

The phrase sales stack exists to make people look at tools as a combination. What connects to what comes before what to buy next, and that whole argument is compressed into the one word.

What the combination removes is a human moving information by hand. Setting out which tool removes which work makes the shape of a stack visible.

1. The deal record. A customer relationship management (CRM) system, which holds the history of contact with each customer, sits in the middle. Every other tool pushes information into it and pulls information out of it. Leave that seat empty and you don't have a stack, you have five tools that each know a quarter of the truth.
2. Lists and contact data. Tools that find companies matching your criteria and the contact details of people inside them. If what they find doesn't land in the deal record directly, the rep copies and pastes it.
3. The sequencer. This is what actually runs a sales cadence, the pre-set order of which channel to use at which interval. Removing a company from the sequence when they reply or book a meeting has to be wired to the deal record.
4. Call capture. Recording and transcribing calls. When the summary attaches to the deal record automatically, twenty minutes after every call disappears, and the notes stop depending on what the rep still remembered at the end of the day.
5. E-signature. Contracts signed online, wired so the deal stage flips to closed-won when the signature lands.
6. Reporting. Stage win rates and the forecast. If the first five don't accumulate in one place, the numbers this step produces are wrong.

The wiring needs an owner. Sales operations, the role that runs the tools and data a sales team works on, is that seat, and past about six reps it stops being something anyone can hold as a side job.

Cost belongs to the combination as well. At $100 per rep per month per tool, a twelve-person team on five tools spends $6,000 a month. Any one of those five that can't exchange information with the others leaves that share of the spend sitting next to manual retyping.

Wiring everything together is not automatically the answer. Three shapes exist depending on where the company is.

1. Surviving on one spreadsheet. Under three reps this is the better option, because the effort of wiring tools together exceeds the time the tools give back. The limits are clear: as reps grow, the same company lands on two lists, and asking for last quarter's win rate produces no answer.
2. One deal record and nothing else. Common between three and six reps. Sending and call notes stay manual while the records collect in one place. If you can buy only one thing, this is it — everything else attaches to it, so reversing the order leaves the other tools nothing to attach to.
3. One vendor's suite. Using tools built by the same company makes most of the wiring disappear. The trade is that no individual tool is the best in its category. Picking the best tool per category pays the opposite price: the wiring never goes away, and when one vendor changes a format the connection breaks that week.

What decides the choice is team size and whether anyone owns the wiring. With no owner, what was wired together comes apart six months later, and the team goes back to copying between tabs without ever deciding to.

"Before we add this, check whether it exchanges data with the CRM."

Setting the criterion for adding a tool.

"A company we already met is still getting intro emails. The sequencer isn't wired to the deal record."

The kind of incident a broken connection produces.

"The stack costs $6,000 a month and nobody uses two of those tools."

Nothing was removed after things were added.

At Pagedeck, with three reps, the team runs two tools: the deal record and e-signature. Email goes out by hand and Sofia writes her own call notes. The rule Grace set when choosing the combination was to write down, for each candidate tool, both the time it removes and the time it takes to wire in.

They've decided to add the sequencer and call capture once reps pass six — but they fixed the order first. The day the sequencer goes in, its connection to the deal record gets finished in the same pass, and if the connection can't be made, the tool doesn't go in.

A common belief is that more tools make a team faster. Each tool's saving is concrete, so adding them should add up. But savings attach per tool while overhead attaches per pair. Two tools have one seam; five have ten. That's why the first three usually come out ahead and the fifth is where retyping starts eating the savings. The fix isn't fewer tools by principle — it's refusing to add one whose connection nobody has built yet.

The other belief is that a stack, once built, stays built. Connections made feel like connections kept. But these connections span products built by different companies. When one side changes a format or a pricing tier, the link breaks quietly, and the break usually surfaces weeks later — you go looking for why last month's forecast was wrong and find that a connection died three weeks earlier. So a checking cadence gets fixed alongside each connection: what should be arriving, and whether it actually is.