Read Me First

The 22 boring things that fix most revenue problems before anyone touches your tools.

Your team has more software than at any point in history. Your pipeline reports still don't match reality. Your reps still keep a private spreadsheet. Your "AI strategy" is four people pasting things into a chat window and hoping.

Here is the uncomfortable part: most of what is slowing you down is not advanced. It is the stuff underneath the stuff. Browsers that haven't been updated since the last fiscal year. Passwords on sticky notes. One laptop screen running a forty-tab life. A CRM that everyone manages and nobody uses. AI tools getting one-line instructions and producing one-line garbage.

I have spent ten years inside revenue teams of every size, and the same pattern shows up every single time. The tools change. The basics don't. The teams that skip them pay for it in slow weeks, missed leads, reports nobody trusts, and a quiet tax on every hour of work.

This page is the precursor to everything else. Think of it as a readme file for running revenue. Start at number one. Work down. None of it requires a budget meeting. Most items take less than an hour. If you do all twenty-two, you will be ahead of most companies I have ever walked into.

Part One: Your Machine

The desk you work at is the first system in your revenue system. If it is slow, everything you do is slow.

1. Update your browser. And everything else.

An outdated browser is slower, less secure, and quietly breaks modern web apps in ways you blame on the app. Turn on automatic updates for your browser, your operating system, and your core tools. Then restart your computer. Actually restart it. If your machine has an uptime measured in weeks, you are working through sludge and calling it normal.

2. Use a password manager.

If your passwords live in a notebook, a sticky note, or your head, you are one bad day away from a very expensive problem, and you are wasting minutes every single day on logins and resets. Pick a reputable password manager, put every credential in it, and turn on two-factor authentication for anything that touches money or customer data. This is an afternoon of work that pays you back forever.

3. Add a second screen.

You cannot compare two things you cannot see at the same time. People working on a single laptop screen spend their day flipping between windows, losing their place, and re-reading. A second monitor is one of the cheapest productivity purchases that exists. If you work with data, email, and a CRM all day, it is not a luxury. It is the job.

4. Fix your internet.

If your video calls stutter and your pages crawl, every tool you own feels broken, and your team learns not to trust the system. Run a speed test. If you are running a revenue job on weak Wi-Fi, you are choosing latency and calling it a tech problem. Hardwire what you can, upgrade what you must.

5. Know where your files live.

One place. Sane folders. Backed up automatically. If "where is the latest version" is a question anyone on your team asks more than once a month, you do not have a storage problem, you have a trust problem, and it costs you hours every week. Pick one home for files, agree on it out loud, and stop emailing attachments to yourself.

Part Two: Your Habits

Tools don't have habits. People do. These five cost nothing and change everything.

6. Write it down where someone else can find it.

A decision that lives only in someone's memory is a decision that will be made twice, badly, by two different people. Notes from calls, decisions from meetings, the reason you changed something: written down, in the shared place, same day. If you got hit by a bus tomorrow, how much of your job would leave with you? That number should scare you into typing.

7. Kill the private spreadsheet.

This one is a diagnosis, not a tip. When someone on your team keeps their real pipeline in a personal spreadsheet, they are telling you they do not trust the official system. The spreadsheet is a symptom. Find out why they trust their sheet more than the system everyone paid for, fix that, then retire the sheet. Until you do, your reports are fiction and everybody quietly knows it.

8. Keep your calendar honest.

Your calendar should tell the truth about your time. Block the work, not just the meetings. Decline what you will not actually attend. If your calendar says you are free and you are not, you have built a small lying machine that everyone around you has to route around.

9. Name things like a stranger will read them.

"Final_v3_NEW_use-this-one.xlsx" is not a name, it is a confession. Pick a simple convention for files, reports, campaigns, and email templates: what it is, who it is for, which version. Then hold the line. Six months from now, the stranger reading your names is you.

10. Decide how fast you respond, then keep that promise.

When a new lead or a customer question comes in, how long until a human touches it? If you have never said the number out loud, the real answer is "whenever," and "whenever" is where deals go to die. Pick a window you can actually keep, even a modest one, and treat breaking it as a real failure rather than a shrug.

Part Three: Your Tools

You already own more software than you use. These six are about making what you own actually work.

11. Use the CRM.

Not manage it. Not maintain it. Use it. Open it every day, work out of it, log what happened in it. If your team cannot run their day inside the CRM in a few clicks, that is not a discipline problem to yell about, it is a design problem to fix. But here is the rule that does not bend: the deal does not exist until it is in the system. No record, no commit.

12. Give every tool one owner, by name.

Not a department. A person. Every tool in your stack should have one name attached to it: the human who answers for whether it works, whether it is configured right, and whether it should still exist. Tools without owners drift, break silently, and bill you monthly while doing it. If you cannot name the owner in five seconds, you found the problem.

13. Check your email plumbing twice a year.

There are a few technical settings that prove to the world your email really comes from you. When they are wrong, your messages land in spam and nothing in any dashboard tells you. You just watch reply rates die and blame the copy. Have whoever runs your domain verify those settings every six months, and any time you change how you send email. If the phrase "we changed email tools last quarter" was just spoken in your office, check today.

14. Know what happens when someone fills out your form at midnight.

A real buyer hits your website at 11:58 PM and fills out the form. What happens by 8:30 the next morning, automatically, without anyone remembering to do anything? If you cannot answer that in one breath, walk the path yourself: submit your own form and watch where it goes, who gets it, and how long it sits. Most companies are shocked. Speed to that first touch is one of the few things in revenue that is both completely controllable and completely ignored.

15. Retire one thing before you add one thing.

Every new tool, field, and process step has a cost that never shows up on the invoice: one more thing to learn, maintain, and work around. So make it a trade. New tool in, old tool out. New field added, two stale fields removed. New step in the process, one step deleted. If nothing ever leaves, you are not building a system, you are hoarding.

16. Test that your backups actually restore.

A backup you have never restored from is a hope, not a backup. Once or twice a year, actually pull something back: a file, a record export, whatever matters most. The day you discover your backup does not work should be a quiet Tuesday test, not the worst morning of your year.

Part Four: Your AI

This is the new layer, and it is where the basics are being skipped fastest. The tools are genuinely powerful. They are also not omniscient, they do not share memory with each other, and they will confidently state things that are wrong. Until that changes, the discipline lives with you.

17. Brief it like a new hire, not a search bar.

One-line prompts get one-line answers. Treat the AI like a smart contractor on their first day: tell it who the work is for, what good looks like, what to avoid, and what format you want back. The quality of what you get out is mostly the quality of what you put in. People who say "AI doesn't work for us" are usually describing their own instructions.

18. One conversation per job.

When you cram your pricing question, your blog draft, and your spreadsheet formula into one endless chat, the AI's grasp of all three degrades, quietly. Start a fresh conversation for each distinct piece of work. It costs you three seconds and saves you from the slow slide into confused, mushy answers.

19. When a conversation gets long, close it out properly.

Long AI threads decay. The model starts forgetting the beginning, contradicting itself, and drifting. Before that happens, ask it to summarize everything important: decisions made, context gathered, where things stand. Then start a new conversation and paste that summary in as the opening brief. You just gave the next session a clean handoff instead of a haunted house. This one habit separates people who get compounding value from AI from people who get noise.

20. Assume it is confidently wrong until you check.

AI states false things in the same calm, fluent voice it states true things. Numbers, names, dates, legal claims, customer details: verify before anything ships, gets sent, or gets quoted in a meeting. The rule is simple. AI drafts, a human owns. Whatever goes out under your name is yours, no matter what wrote the first version.

21. Keep secrets out of the chat box.

Passwords, API keys, customer lists, contract terms, anything you would not paste into a public forum: it does not go into a chat window, period. Set this as a team rule before someone learns it the hard way. The convenience is never worth the cleanup.

22. Keep the manual version.

If your AI tools disappeared tomorrow, could your team still run the process and get the same outcome? If the answer is no, you have not automated a process, you have replaced one you no longer understand. Write down the manual version of anything important that AI now does for you. It is your fallback, your training document, and your proof that you actually know how your own business works.

What This List Is Really For

None of this is impressive. That is the point. There is no tool to buy here, no certification, no platform migration. Just twenty-two things that have been true for years and will still be true after the next wave of software ships.

Here is what I have seen over and over: companies skip this layer, then spend real money on advanced systems, then wonder why the advanced systems disappoint. The fancy stack inherits every bad habit underneath it. AI inherits them faster, because AI amplifies whatever you feed it, including the mess.

Work the list top to bottom. Most items take under an hour. When your team has these handled, every tool you own gets better without a single new purchase, and you are finally standing on a floor instead of a pile.

And if you work through this page and the deeper problems are still there, the reports that don't match reality, the leads that vanish between systems, the tools nobody owns, that is the layer underneath the basics. That is the part I look at.

Tyson Parody runs Sixty North, a revenue systems practice. This page is free on purpose. Start here.

Ready to go deeper? Try the Revenue Audit or book a call.