The real cost of feeling “not a computer person” in a 1 to 5 person shop

Feeling “not a computer person” does not just mean you dislike software. It costs you in retyping the same details, slow follow-ups, and invoices that need chasing. It pushes work into your evenings and lets a few good jobs slip. Use the quick tally below to see it in your shop.

What the Doorman Fallacy is, and why it matters to your shop

The Doorman Fallacy, a term from Rory Sutherland, is the mistake of reducing a human role to its most visible task and trying to automate only that. A doorman does more than open doors. They offer judgment, security, recognition, and reassurance. In your business, quoting and billing are not just “clicks.” There is context, price judgment, and customer trust.

So the goal is not to replace the human parts. It is to put repeatable admin on rails so your attention is free for the judgment and relationships that win and keep work.

How “not a computer person” shows up in a 1 to 5 person shop

If you run without office staff, the hidden cost shows up in small leaks that add up:

• Retyping the same customer details into a notes app, a bid, a job card, and an invoice.
• Scattered records across texts, voicemail, email, and a spiral notebook, which means searching when a customer calls back.
• Bids that sit in Drafts or on the truck console, then go cold without a check-in.
• Invoices you chase at 14 and 30 days because the first one never triggered a nudge.
• “Where did we leave that?” time, hunting for job history or photos to answer a simple question.
• Missed calls that never get a quick text back, so the lead moves on.

You do not need fancy software to fix most of this. You need a connected record and a few steady prompts that happen on time, every time.

Quick tally: the cost of “not a computer person” in your shop

Grab your last 10 jobs. Pencil this on a pad. This is an illustration to help you see the shape of the problem in your numbers.

1. Retyping minutes: For each job, write how many minutes you retyped basic info you already had [__]. Add them up.
2. Searching minutes: Minutes spent digging through texts, email, or photos to answer customer or crew questions [__]. Add them up.
3. Bid follow-up minutes: Minutes spent remembering and sending “Just checking in” on open estimates [__]. Add them up.
4. Invoice chasing minutes: Minutes spent resending invoices or reminders at 14 and 30 days [__]. Add them up.
5. Missed-call recovery minutes: Minutes to catch up on voicemails and lost leads [__]. Add them up.
6. Total minutes from steps 1–5 = [__]. Divide by 60 for hours lost.
7. Multiply hours lost by your target billable hourly rate for dollars lost.

Recommendation: If you want placeholders to start, try 5 minutes for retyping per job, 5 minutes for searching, 5 minutes to send one bid check-in, 10 minutes per invoice that needed a nudge, and 5 minutes per missed call you had to recover. Replace with your real numbers next week.

Decision rules: when to fix a step

• Type-once rule: If you enter the same name, address, or job description twice, set up the system so it carries over automatically into your estimate and invoice. That is the first leak to plug.
• 5-day bid check-in rule: Send one friendly follow-up five days after every estimate. Short, polite, no pressure. This catches stalled good fits without you remembering.
• 14/30 invoice nudge rule: If an invoice is unpaid at 14 days, send a clear reminder. If still unpaid at 30 days, send the second. Keep it consistent and documented.

These rules respect the human parts of the job. You still decide the price, scope, and exceptions. The rails handle the routine nudges and copying.

Why big software or a “computer person” alone is not the answer

The Doorman Fallacy bites here too. Hiring a “computer person” to click for you ignores the value of your judgment and relationships. Buying a giant platform to “do it all” can bury a small crew in screens you will not use. What you likely need is smaller: one connected place for customers, bids, jobs, invoices, and steady follow-ups.

A practical way to cut admin without losing the human parts

Recommendation: Build or adopt a simple connected record that:

• Keeps customer history, bids, active jobs, and invoices in one place you own.
• Fills your estimate and invoice templates from the same fields so you stop retyping.
• Sets a five-day bid reminder and 14/30-day unpaid-invoice reminders so follow-through happens on time.
• Lets you add notes by voice or text during the day, then asks for your approval before anything is written to the record.

If you want a ready-made version of that approach, The Bureaucracy Lab offers the Bid, Invoice & CRM Automation System. It connects a CRM, Bid Tracker, and Job Log in Google Sheets and Drive, generates estimates and invoices from reusable templates, and schedules five-day bid follow-ups plus 14 and 30-day unpaid-invoice reminders. Daily voice or text capture runs through Claude, and it reads back planned changes and waits for your approval before writing to the spreadsheet. That keeps control where it belongs: with you.

You can do the tally above without buying anything. If the leaks are real and you want rails that match the rules here, this system is a practical place to start.

Bid, Invoice & CRM Automation System