For companies

A company is just another stack.

This page is for the owner of a twelve-person business, not a technology executive. You are about to be sold a great deal of enterprise intelligence. Most of it is a portal with your logo on it. Here is what to do instead, and it is short.

Who you are dealing with

Everyone in your business already carries their own phone. You did not buy it, you do not own it, and you do not decide what is on it. What you provide is the things the phone can reach: the email account, the shared calendar, the schedule, the payroll. The device is personal. The company is the set of records and permissions the device is allowed to touch.

Intelligence works the same way. Each of your people will have their own stack, on their own bill. So will each customer, each supplier, your bank, your accountant, your landlord, and the inspector. Your company will not have an intelligence of its own that people talk to. It will have records, rules, and connectors. Its job is to be easy for all of those other stacks to deal with.

What your stack is made of

Records: The ledger, the inventory, the schedule, the customer file, the terms, the price list. If a record matters to anyone outside your walls, another stack needs to be able to reach it under your rules, without a phone call. Most of these already exist. They are in a spreadsheet, an accounting system, a calendar. The work is making them reachable, not replacing them.
Rules: Who may read what. Who may change what. What is approved automatically and what needs a person. "Anything under two hundred dollars with a receipt is approved." "A customer's stack may read their own order history and nothing else." "Reorders under the standing terms go through; anything above needs me." Written down, as rules, not as a feeling you have. This is your real product now. It is what makes you safe to deal with.
Connectors: The doors. A way for an employee's stack to file an expense against your ledger. A way for a customer's stack to place an order and read a confirmation. A way for a supplier's stack to see that your inventory dropped below the reorder line. The open standard for this exists and every frontier company has agreed to it. You do not need to know how it works. Whoever sets up your records needs to.

What a good Monday looks like

A customer's stack places an order with yours at 6:40 in the morning, checks the confirmation against the customer's own records, and moves on. An employee's stack files last week's expenses and gets them approved by the rule. A supplier's stack notices your stock is low and proposes a shipment; yours accepts it under the standing terms. You read a two-paragraph note at eight. Nobody opened an app. Nobody logged into a portal. You did not talk to anyone. You were simply easy to deal with.

The to-do list

Stop building the app. No portal, no branded assistant, no place people are supposed to go. Every one of those is a store, and your customers' stacks will route around it the way they route around every other store. If a vendor's pitch begins with a screen, ask what record it holds and whether you could reach that record without the screen.
Get your records in order and reachable. One place for each fact. A price lives in one list. A customer lives in one file. Then make the place reachable by a stack that has permission. Where your accounting system or scheduling tool already offers a connector, use it. Where it does not, a well-kept spreadsheet in a shared folder is more reachable than a portal.
Write the rules down as rules. Start with the five decisions you make most often and write what would let someone else make them. Those are your first rules. Add the ones you are nervous about last.
Make it easy to be dealt with. The measure is how little of anyone else's time it takes to do business with you. Not how good your intelligence is. How little anyone needs to talk to it.

What you can stop paying for

The small business section of the Does list covers invoicing, reorders, customer questions, reviews, onboarding, and scheduling. Run the Stack Test on each of your monthly charges. Some will come back "keep." Your accounting ledger is a record. Your payroll provider is a record. Your booking page might be a product you need, because your customers' stacks are not placing orders yet, and some of your customers are not people with stacks. That is allowed. The test is honest in both directions.

Where this is wrong

Most of your customers do not have a stack that places orders today. For now, being easy to deal with still means a phone that gets answered and a website that says your hours. The rules you write will be wrong at first and will need a person watching them. And if the connector standards fork into walled versions, the store comes back wearing a protocol. None of that changes what to build toward. It changes how fast.