← All guides Guide

Ten things businesses do by hand that software can do

Some of the most valuable work software does isn't impressive at all. It remembers a date, sends the letter, passes the job along, or builds the report nobody wants to build. Here are ten everyday jobs that often get done by hand, and what they look like once software takes them over.

The list

Ten jobs worth a second look

Where we've built one of these for a client or for ourselves, we link to the story and the demo. The demos use made-up sample data.

01

Following up on overdue payments

Chasing payment depends on someone noticing an invoice has gone quiet. When that person is busy, the follow-up slips, and so does the cash.

By hand

Someone scans the open invoices now and then and calls whoever stands out.

With software

Every invoice starts a clock. When it runs out, the follow-up lands in front of the right person, and unpaid accounts can move on to collections.

Where we've done it: a local moving company, where a payment timer reminds accounts receivable to follow up. Read the story →

02

Keeping track of expiration dates and renewals

Certifications, exemptions, contracts, insurance, licenses: each has a date, and missing one can cost real money. Too often the reminder lives in someone's head or a calendar only they check.

By hand

Checking the paper file or the spreadsheet each time, and hoping it's up to date.

With software

The dates are stored with the record they belong to, so the system already knows what's current and what's about to lapse.

Where we've done it: Circle T Oil, where each well's tax exemptions and their expiration dates are already known when a ticket is entered. Read the story →

03

Writing the same letter over and over

Statements, notices, and owner letters often follow the same pattern with different names and numbers. Typing them one at a time is slow, and every copy is a chance for a typo.

By hand

Start from last month's letter, change the details, print, repeat.

With software

Letters are generated from information the system already has, and a month's worth go out in one batch.

Where we've done it: the same Circle T Oil system, where owner letters come straight from the ticket and the well. Try the After demo →

04

Putting together month-end reports

A report that takes a day to assemble is usually a report built from scratch every month, by gathering numbers that were already entered somewhere else.

By hand

Pull the month's paperwork, add it up, fill in the form.

With software

Each entry is recorded where it belongs as the work happens, so the month-end report is mostly a matter of reviewing it.

How we organize the work →

05

Typing the same information into two systems

If someone reads from one screen and types into another, the two systems should probably be talking to each other. Often neither one has to be replaced.

By hand

Finish the work in one program, then copy the details into the accounting program.

With software

Once a person verifies the work, the details pass to the next system automatically.

How we connect systems →

06

Catching numbers that don't match

Inventory in one system says 40, the spreadsheet says 36, and someone has to figure out which is right. When the same number lives in more than one place, it drifts.

By hand

Compare reports side by side when something looks off, usually after it has caused a problem.

With software

Keep one source for each number, or compare the systems on a schedule and flag the differences for a person to resolve.

How we connect systems →

07

Handing work from one department to the next

Work tends to get lost between people, not within a job. A change made in sales never reaches operations, or finished work never reaches billing.

By hand

A conversation, an email, a note on someone's desk, and a hope that it was read.

With software

Every job belongs somewhere and is always in front of someone. Finishing one step moves it to the next person's list.

Where we've done it: a local moving company, where operations' sign-off moves a finished job straight to accounts receivable. Try the Before demo →

08

Getting the right approvals

Some work needs a second look: a large job, a discount, a purchase over a certain amount. When approval depends on remembering to ask, it gets skipped or holds things up.

By hand

Walk it over, send an email, wait, and follow up.

With software

Work that meets the rule goes to review automatically, and once it's approved it moves on by itself.

Where we've done it: a local moving company, where larger jobs go to contract review before they reach operations. Try the After demo →

09

Working out what to bill at month end

If you bill by the hour or by the project, month end can mean digging through email and calendars to work out where the time went. Small jobs sometimes go unbilled because finding the details takes longer than the work did.

By hand

Rebuild the month from the inbox, the calendar, and memory.

With software

Time is logged in blocks against each project as the day goes, so the invoice is already built at month end, and you can see which projects ran over their bid.

Where we've done it: our own project management system, built for how we work. Read the story →

10

Answering "where does this stand?"

When status lives in people's heads, every question becomes a phone call, and work that nobody is asking about can quietly stall.

By hand

Ask around, check a whiteboard, or wait for someone to notice.

With software

Anyone who needs to know can see where each job is and who has it, and nothing sits forgotten because it's always on someone's list.

Where we've done it: the local moving company's system, and our own project management, where projects no longer stall because they were forgotten. How we organize the work →

Not everything is worth automating

There's always more that could be automated. The real question is whether it makes enough of a difference to be worth building, and worth looking after afterward, since every feature brings some ongoing upkeep.

A few questions help: How often does this happen? What does a mistake cost? Who is stuck doing it, and what would they do with the time? Sometimes the answer is a big change. Sometimes it's a better spreadsheet, a template, or nothing at all.

For the local moving company, we built the job details, the flow between departments, and tracking, and stopped there. More was possible, and it still is. The owner decides when the next step is worth it, and we'll say so when an idea is technology for its own sake.

Start with a conversation

Recognize a few of these?

Tell us which ones, in your own words. In a 20-minute call, we'll talk through which are worth taking on and which aren't. You don't need a plan or any technical requirements.

Not sure where to start? Try the self-check →