Teardown: tools businesses run on
Business tools are chosen by one person, used all day by others, paid for from someone's budget and controlled by an admin. This lesson tears down three kinds with the method from pm-40: a point-of-sale system (Square), B2B ordering apps for small shops (Udaan and TradeDepot) and a team tool (Slack). You will see how each wins the buyer, keeps the user, and turns the admin side into the reason companies pay.
By the end you can
- Map the buyer, user, payer and admin of any business tool, and what each needs before saying yes
- Explain how a POS bundles payments, hardware and software, and how sales data becomes a loan product
- Explain how a B2B ordering app replaces the sales rep, and why credit drives order size and risk
- Explain bottom-up adoption, and how admin, security and billing features turn free use into paid plans
- Write copy, adapt and avoid for a store POS, a wholesale ordering app and an internal request tool
The everyday picture
Think about the coffee machine in an office. The office manager chose it and signs the monthly bill. Twenty people use it ten times a day. Facilities fixes it when it jams. Finance looks at the cost once a quarter and asks whether it is worth it.
A machine the staff hate gets replaced by kettles under desks, whatever the manager paid. A machine whose cost the manager can't control gets cancelled at the next budget review, however much staff like it. A machine that facilities can't repair stays broken. A good business tool has to satisfy all four people, and each one sees a different product.
Four people, one product
Decision question first. Imran owns the Partner app, which about 1,800 corner shops use to order wholesale stock, and works closely with the team that runs Mangrove's 400 store tills. His question: "What should the Partner app and the POS copy from the business tools that small businesses already choose and pay for?"
Business tools have four roles, and in a teardown you study each one separately.
- Buyer: the person who chooses. In a corner shop, the owner. In a company, a department head or IT. The buyer judges price, setup effort, risk and what peers use.
- User: the person who uses it every day: the shop assistant at the counter, the employee in the chat channel. The user judges speed, simplicity and whether it works when things go wrong.
- Payer: whose budget it comes from. Often the buyer; sometimes finance, which judges the bill and whether it grows predictably.
- Admin: the person who sets it up and controls it: adds and removes staff, sets permissions, exports data, answers to auditors. Admins rarely appear in demos and often decide renewals.
The first lesson of the track called this out for B2B products: the person who pays is often not the person who uses (pm-01). The teardown question is which role the product wins first, and how it wins the others later. Square wins the owner with a simple fee. Slack wins users first and the buyer later. B2B ordering apps win the owner with price and credit.
Quick check
A shop owner loves a new ordering app because of its prices, but her assistant, who places most orders, finds it confusing and keeps phoning the supplier instead. Which role is the product failing?
The buyer is happy; the user is not, and the workaround (phoning) shows it. If the user keeps phoning, the owner's choice doesn't turn into app orders. Permissions may matter later, but they are not the cause here.