Map your stack

Why you need a map

Most rental companies did not choose their software. They collected it. A free website builder in year one, a booking system the next spring, a payment processor that came with it, a phone app someone recommended at a trade show, a scheduling app for the crew, three email addresses, two Facebook pages and a spreadsheet nobody remembers starting.

Each tool made sense when you added it. Together they cost more than you think, overlap in ways you have not noticed, and depend on logins that live in one person's head. The day that person quits, gets sick or loses their phone, you find out how fragile it all is.

A one-page stack map fixes that. It takes an hour and it is the foundation for every other lesson in this course.

What goes on the map

List every tool your business touches, even the free ones. For each, write down:

• Name and what it does. One line. "Booking and online checkout," "business phone and texting," "crew schedule."
• Who owns the account. Whose email is it registered to? Is it a business email or someone's personal one?
• Who has the login. Everyone who can sign in today, including former staff and outside helpers.
• How you sign in. Password only, or two-step verification? Where do the codes go?
• What it costs and how it bills. Monthly or yearly, which card, and the renewal date. Check current pricing on your statement, not the website.
• What data lives there. Customers, bookings, payments, photos, reviews.
• Can you export it? Can you download your data as a spreadsheet, and have you ever tried?

Where to find the tools you forgot

You will not remember everything from memory. Go hunting:

• Your card and bank statements for the last twelve months. Every recurring charge is a tool. Mark any you cannot explain.
• Your email inbox. Search for "welcome to," "your receipt," "your invoice" and "verify your email."
• Your phone's home screen and your crew's phones.
• Your website. Look at what is embedded: a booking widget, a chat bubble, a review badge, a tracking code.
• Your domain registrar. Who controls your domain name and email? This one matters more than almost anything else.

Spot the overlaps

Once it is all on one page, overlaps jump out. Common ones in rental companies:

• Two tools sending booking reminders, so customers get duplicate texts.
• A separate e-signature app when the booking software already collects signatures.
• A standalone texting app and a phone system that also texts.
• A paid scheduling app for a crew of three who could use a shared calendar.
• A website builder subscription for a site that now lives somewhere else.

Do not cancel anything yet. Mark each overlap with a question mark and decide in the lessons ahead.

An example from the field

A 15-unit company delivering to four suburbs sits down on a rainy Tuesday in February with its card statements. The owner expects to find eight tools and finds fourteen. Two are subscriptions for a website the company stopped using two seasons ago. The domain is registered to a former partner's personal email. The booking software and a separate texting app both send day-before reminders, which explains why a few parents asked why they got two messages. The crew lead still has the owner's personal password for the payment dashboard, written on a sticky note in the truck.

None of this is unusual. The owner cancels the dead subscriptions, moves the domain to a business email and adds the remaining fixes to a list for the security lesson. The map now lives in a shared folder, and it gets reviewed every January before the season starts.

Keep it to one page

The point is a document you will actually look at. Use a simple document or spreadsheet with one row per tool. Group them by job:

• Getting found: website, domain, Google Business Profile, social pages, ads accounts.
• Booking and money: booking software, payment processor, accounting.
• Talking to customers: phone, texting, email, review requests.
• Running the day: crew schedule, routing, checklists, file storage.

Put the date at the top and a note on where the full list of logins lives (a password manager, which we cover in the last lesson, not the map itself).

Common mistakes

• Writing passwords on the map. The map lists who has access, not the passwords themselves.
• Skipping free tools, which often hold the most customer data.
• Leaving key accounts, especially the domain and payment processor, registered to a personal or former employee's email.
• Canceling a tool before exporting the data in it.
• Building the map once and never updating it when tools or staff change.