Insights

/

18 Nov 2026 · 3 min read

Note

Start with the job your team already avoids

Start with the job your team already puts off. Not the one that looks best in a demo. When the system takes that job, the team sees why it's there.

Start with the job your team already avoids

Somebody always draws the short straw. Hand that job over first.

“Where do we start?” Owners often ask us this on a first call. Search it, and the answer is the job that repeats the most. Or the one that eats the most hours. That’s fair on paper. We have a tool for it too: our Maverick Matrix, which scores each job by ease and impact.

But your team has to live with the choice. Pick a job they don’t mind, and it’s one more screen to learn. A month on, the work is still done the old way. Now you pay for a system nobody opens. So start somewhere else: with the job your team already avoids.

How do you find the job your team avoids?

Ask them. Then check what’s always late. You’re looking for the job that gets done last. Or the one the owner does at 9 pm.

  • Ask what they’d drop. “If one job vanished tomorrow, which one?” They’ll answer fast.
  • Look for what’s always late. The follow-up that waits a week. The invoice that waits for Friday.
  • Listen for “I’ll do it later.” Whatever comes after those words is the job.
  • Watch for copying. Typing the same job into two different places is on the list.
  • Notice what lands on you. If the owner does it at night, nobody else wanted it.

We said it at a workshop last December: “You take some of that grunt work off their plate, then they start seeing the value.”

At that workshop, the job was chasing quotes. Nobody likes asking twice. So the quote goes out once, and nothing follows it. That’s the quote that only gets sent once.

Why not start with the impressive part? Because it asks the team for something. A new screen needs facts typed in. A chatbot needs someone to check it. Each one adds work before it saves any. There’s nothing wrong with the impressive part. It just comes second.

The Maverick Matrix puts them in the same order. Catalysts come first: quick to set up, and they change a lot. The job your team avoids is often one of them. The big builds are Transformers. They pay off too, just later.

Build the thing your team would thank you for. Not the thing that looks good in a demo.

Take the hated job first. The first thing the team notices is less work. They feel it on the first quote that chases itself. After that, the next step is an easier yes. They’ve seen what Income Mavericks is for.

No system yet? The hated job can still go first. Most accounting software can send invoice reminders on its own. If chasing payment is the job nobody wants, switch that on first.

In Income Mavericks, the jobs a team puts off can be handed over:

  • Chasing quotes. A quiet quote can be asked about again on a schedule. The asking stops when they reply.
  • Sending invoices. The invoice can go out when the job is done.
  • Asking for reviews. The request can go out once the invoice is paid.
  • Calling back missed calls. A missed caller can get a text asking what they need.
  • Typing it in twice. Form answers can land on the customer’s record, so nobody retypes them.

It comes down to order. Take away one job they hate. Then the rest of the system has someone on its side.

More on this topic

Automation

1 Oct 2026 · 5 min read · 5 min

Explainer

Missed call text back buys time, not the job

A missed call text back stops the caller ringing the next name. One saved job a month pays for it many times. It stops working when nobody answers the reply.

→

Automation

18 Sep 2026 · 5 min read · 5 min

Explainer

Most quotes get sent once and never followed up

The revenue is already sitting in quotes you sent. One client reported close to 30% more revenue after the chasing ran on a schedule instead of on memory.

→

Rather talk than read

Bring us the process that keeps going wrong

Tell us what is breaking and we will tell you what it would take to stop it.

Get in touch