Internal tools are a growth channel

Growth budgets go to things customers see: ads, landing pages, lifecycle emails. Meanwhile the team that talks to customers all day is losing hours to spreadsheets, and nobody counts that as a growth problem. It is one. Capacity you return to a revenue team converts into revenue at a rate most channels would envy.

Three tools

A CS bandwidth view. Before it existed, deciding who could absorb a new escalation was a conversation. After, it was a screen. The tool doesn't do anything clever - it aggregates open load per person and makes it visible. The win wasn't automation, it was removing a recurring decision from a human's day.

A bonus management tool. Commission and bonus calculation was living in a spreadsheet with formulas that only one person fully understood, recalculated monthly, disputed occasionally. Moving it into a small internal app removed both the recurring work and the arguments. The second effect mattered more than the first.

A quote creator. Reps were assembling quotes by copying a previous one and editing it, which is exactly the process that produces the wrong price on the wrong document. A generator with the pricing logic encoded turned a 20-minute error-prone task into a form.

Why these get built and product features don't

Not because they're more important - because they're small enough to ship without a roadmap conversation and specific enough that the requirements fit in one meeting with the person who has the problem. That's the structural advantage of sitting between GTM and engineering: the feedback loop is one desk long.

How to pick which one

• Follow the spreadsheet. Every recurring spreadsheet with more than two contributors is a tool waiting to be built.
• Follow the Slack question that gets asked weekly. If people keep asking 'who has capacity' or 'what's the price for X', the answer should be a screen, not a person.
• Follow the disputes. Any process that produces disagreement about numbers is a process with no single source of truth.

Hours returned to a revenue team are a growth channel with no CAC. They just don't show up in the attribution model.

The catch is ownership. Internal tools accumulate, and an unowned internal tool becomes a liability the moment its builder leaves. Build few, build them boring, and write down who maintains them.