Six logins before any work gets done

You wake up, pour coffee, and open the laptop. Before you've looked at a single job, you've already typed four different passwords. The scheduling app. The invoicing software. The supplier's parts portal. The city permit portal. Then the phone rings, you answer it on the mobile, and now you're trying to remember where you left the estimate you were building.

Nobody designed this situation on purpose. It accumulated. Each tool solved one real problem when you added it, and now they all live side by side, sharing nothing, demanding your attention in rotation. For a plumber or electrician running a small crew, the login count is rarely discussed — but the time it eats shows up every day.

What the average stack actually looks like

Walk through a typical morning for a two-truck HVAC shop. There's a scheduling tool — maybe Jobber, maybe ServiceTitan, maybe a shared Google Calendar that got out of hand. There's QuickBooks or something similar for invoicing. There's the supplier's web portal for checking parts availability and order status. There's whatever the city or county uses for permits — Accela, eTRAKiT, a one-off municipal system. There's the business phone, which may be a separate app if you're using a VoIP line. And there's probably an email account that serves as the catch-all for everything the other systems don't handle.

That's six before you've done anything billable. Some shops add a seventh: a customer-facing booking page, a separate CRM, or a fleet-tracking tool. Each one requires its own credentials, its own session, its own mental context.

The switching cost nobody measures

The time to type a password is maybe fifteen seconds. That's not the cost. The cost is the reset that happens every time you move between systems. You were building an estimate in your invoicing tool, you tab over to check a part price in the supplier portal, and when you come back you've lost the thread of what you were calculating. You fill in the wrong line. You forget to add the trip charge. You send the estimate and it's short.

Multiply that by the number of context switches in a morning and the error rate starts to matter. A misquoted job isn't just an awkward conversation — it's either margin you absorb or a customer who feels misled.

There's also the time spent on authentication itself. Expired sessions, two-factor codes that go to a phone you left in the truck, passwords that don't sync between your phone and your laptop. A locksmith running calls solo can spend ten minutes of a slow afternoon just getting back into systems that timed out.

What falls through the gaps between systems

The real damage isn't the login friction, it's what gets lost in the space between tools. A customer calls while you're in the permit portal. You don't pick up. The scheduling app doesn't know that call happened. The CRM doesn't know. Nobody sends a text back. The caller tries the next name on the list.

Or a parts order ships, the supplier portal updates, but nothing in your scheduling tool reflects that the part is now available. The job sits on the board as 'waiting on parts' for two extra days because nobody checked the portal. The customer calls to ask what's going on and you don't have an answer ready.

These aren't software failures. They're the natural result of running disconnected systems. Information lives in one place, action needs to happen in another, and the person in the middle, usually the owner, is the only integration layer.

The phone is the worst-integrated tool of all

Most of the systems in a trades stack are at least theoretically connectable. Scheduling tools have APIs. Invoicing software can import job data. The phone is different. A call comes in, a human answers or doesn't, and whatever was said lives in someone's memory or a voicemail that may or may not get transcribed.

For a garage door company or an appliance repair shop, the phone is where revenue enters the business. It's also the tool least connected to everything else. When you're in the scheduling app confirming tomorrow's route and the phone rings, you have to stop, answer, gather information verbally, then re-enter it manually into the tool you were just using.

That manual re-entry step is where bookings get lost. The tech takes down the address wrong. The time slot they quoted isn't actually open. The callback number gets transposed. Small errors, but they compound across a week of calls.

Where a portal audit fits into this

One piece of this problem, not all of it, is the portals: the permit portal, the supplier portal, the licensing board, the warranty system. Each holds a status you only learn by logging in, and each is easy to skip on a busy morning.

Cheaply's Portal Audit reads every portal your business logs into and hands you a list of what's pending, what's about to lapse, and what's stuck. Access is a named sub-user on each portal, the way you would add a new hire, never your own password. It costs $500, and the list arrives inside 3 business days.

It doesn't replace your scheduling, invoicing or supplier tools. It tells you what is waiting inside the logins you already have, so the next morning starts from a list instead of a row of tabs.

The integration problem isn't going away

Software vendors will keep promising that their tool connects to everything. Some of them even do, partially, for the most common combinations. But a two-person landscaping company running a regional supplier's portal, a city permit system from 2014, and a scheduling tool the owner's nephew set up isn't going to get a seamless integration suite. They're going to keep tabbing between windows.

The practical response isn't to find one tool that does everything, that tool doesn't exist for the range of work a trades shop actually does. The practical response is to identify the two or three gaps that cost the most in time or lost revenue, and close those specifically. For most shops, the phone gap is near the top of that list. Everything else can wait while you're on a job. A ringing phone can't.