You don't need another person. You need a process.

An agency owner tells me the back office is a mess. Payments are late, the books are behind, nobody knows what a booking actually earned. Then, almost always, the next sentence:

"I think I need to hire someone."

It is the most natural response in the world. It is also, in my experience, the most expensive way to make the problem permanent.

What hiring actually does

Hiring adds capacity to whatever process already exists. If the process is sound, capacity is exactly what you needed and the new person makes everything better.

If the process is broken, you have just bought a second person to perform the broken process. Now two people enter payments into a spreadsheet with no booking reference. Two people guess which deposit belongs to which reservation. Two people are needed to reconstruct a month at year end, and when they disagree, you have a new problem: deciding which of your own employees to believe.

You have not solved anything. You have doubled the cost of not solving it, and you have made the problem harder to see, because now it is somebody's job.

The tell is simple. If you cannot describe the process in one sentence, hiring someone to run it will not go well.

The three P's, in the order that works

Most people, asked to list what a business needs, say it in this order: People, Product, Process.

That order is backwards, and the sequence matters more than the list.

Process first

A process is just a rule about what has to be true before something can happen. No payment is recorded without the booking it paid for. That is a process. It fits in one sentence, it can be checked, and it either happened or it didn't.

Process comes first because it is the only one of the three you can fix for free, this week, with the people and tools you already have. It costs nothing but the decision.

It also determines everything downstream. A process you can state is a process you can automate. A process you cannot state is one you will hire people to perform, badly, forever.

Product second

Product, in this context, means the system: the software, the spreadsheet, whatever holds the record.

Software cannot invent a process. It can only encode one. Every good system is a set of rules made unbreakable, and every bad system is a place where the rules are optional. When someone buys software hoping it will impose order they haven't defined, they get an expensive filing cabinet.

But once the rule exists, the right product stops it from being broken. Not by reminding you, but by refusing. A payment cannot exist without a booking behind it is a sentence a person can forget on a Friday afternoon. It is not a sentence software forgets.

People last

This will sound wrong, and I want to be precise: people are not last in importance. They are last in sequence.

Put a good person into a defined process, supported by a system that enforces it, and they will be excellent within a week. Put the same person into an undefined process and they will spend their first year building private workarounds. Those workarounds are the actual reason your back office cannot survive them leaving.

Hire when the work exceeds the capacity of a process that works. That is the only time hiring is the answer.

Understand the process before you change it

For twenty years, every time I joined a company, I did the same thing.

The first three months, I changed nothing. I watched. Where does the number come from? Who touches it? What do they do when it doesn't tie? Not what the documentation claims, what actually happens on a Thursday. Then I wrote down where it broke, and built a plan. Then I spent six to eight months executing that plan.

Nine months to fix a process. That is not slow. That is an investment with a return you collect every month afterwards, for as long as the business exists.

You do not have nine months, and you don't need them. Your operation is smaller than a corporate finance function, and you already know most of the answers. But the sequence is the same, and skipping the first step is what makes the rest fail:

Watch it for two weeks. Take the next twenty bookings. For each one, write down what happened, in order: who recorded it, where the payment landed, how the supplier invoice arrived, who checked it against the booking, when the commission was calculated. Do not fix anything yet. Just describe it.

Then find where it breaks. It will be obvious. It is always the handoff, the place where information moves from one person or system to another and something gets dropped. Usually it is the moment the money arrives without the booking reference.

Then change one thing. Not five. One rule, enforced from a fixed date forward.

Owners skip straight to the change, because the problem feels urgent and watching feels passive. But a change to a process you have not described is a guess, and guesses in a back office cost more than the original problem.

The corporate trap, and why small business is different

For twenty years I worked in corporate finance, and I watched the same thing happen everywhere. Business partners across the company did not really understand finance. They understood there were guidelines, that the guidelines were not optional, and that the finance team would come asking. Compliance without comprehension. Finance was a necessary evil.

It worked, because the guardrails were institutional. Someone else wrote the policy. Someone else audited it. A business partner could remain financially illiterate and the numbers still tied, because the system around them did not permit otherwise.

Nobody writes the policy. Nobody audits it. Nobody comes asking, until a client disputes a charge or the tax filing arrives. And so the same financial illiteracy that was survivable inside a corporation becomes existential inside a small business.

Worse, it is usually invisible. A corporate business partner knows finance exists because it keeps sending them things. An agency owner running at speed may have no idea there is a problem at all. Not because they are careless, but because nothing in their day has ever told them. The bank balance is positive. The clients are travelling. Nobody is complaining.

That is the most dangerous position of all: a process problem with no symptom. If you want to know whether you have one, run the five checks. They take an afternoon and they cost nothing.

"But I don't understand accounting"

You don't need to. This is the part that gets lost.

Understanding accounting means knowing which account a transaction debits, how to close a period, how to handle deferred revenue. That is your accountant's job, and it should stay their job.

Understanding your process means knowing that every dollar that moves has a booking attached to it. That is not accounting. That is a rule you can explain to a new hire in one sentence, on their first morning.

Every number you actually want falls out of that rule. What a booking earned. What a client still owes. What you owe a supplier. Your margin. Your cash position. None of these are things you enter. They are things that are calculated, and they can only be calculated if the rule was followed.

So the question is never "do I understand accounting?" The question is "does my record hold together?" Those are different problems, and only one of them is yours.

Why good software can feel overwhelming at first

I should be honest about something, because it bears directly on this.

Wihemi Travel was built by finance people. To us it is obvious. Bookings, payments, supplier costs, commissions, an audit trail. Of course.

To an owner who has never worked in finance, the first screen can feel like a lot. And I have come to believe that reaction is almost never about the software. It is about what the software is showing them.

When you first see every booking laid out with what was paid, what is owed, what the supplier charged and what you actually earned, you are seeing your operation described accurately, most likely for the first time. That is uncomfortable. It should be. The discomfort is not complexity. It is recognition.

There is a real risk here, though: an owner who feels overwhelmed does the reasonable thing and retreats to the spreadsheet they already understand. So the way you start matters enormously.

How to start, and what to ignore

Do not migrate your history. Not in the first month. Start with new bookings only. Old data is a project; new data is a habit, and you need the habit first.

Do two things, and only two. Record the booking. Record the payment against it. That is the entire discipline. Everything else in the system is downstream of those two actions.

Ignore the reports for two weeks. They will be empty, or nearly so, and an empty report is discouraging for no good reason. Reports describe data. You do not have the data yet. Come back when you do.

Give the record one owner for thirty days. Not a committee. One person who enters bookings and payments, every day, without exception. Consistency in the first month is worth more than accuracy in the third.

Then open the dashboard. After thirty days of clean entry, it stops being a wall of numbers and becomes a mirror. Most owners find something in that first look that pays for the software.

How you know the process is strong: one minute

Most advice about process improvement is unmeasurable. Here is the standard I have used my entire career, and it takes no consultant to apply.

If your process is sound, the answer takes under a minute. You open the booking, you see every payment recorded against it, with dates, amounts, method, and who entered them. You tell the client what they paid and when. The call ends.

If your process is broken, that same question takes hours. Sometimes days. You search email. You open a spreadsheet, then a second spreadsheet because the first disagrees. You call the agent who handled it. You look at a bank statement showing a transfer, a first name, and an initial. Eventually you form a belief about what happened, and you tell the client your belief.

Same question. Same business. The only difference is whether the record was built to answer it.

This is the test, and it applies to everything:

• A supplier says an invoice went unpaid. Under a minute.
• An agent asks what a booking earned them. Under a minute.
• Your accountant asks what a deposit from March was for. Under a minute.
• You want to know what you are owed today. Under a minute.

Reconciliation should not take hours, and it certainly should not take days. If it does, the problem is never the person doing the reconciling and never the number of hours available. The problem is that the relationship between the money and the booking was never recorded, so somebody has to reconstruct it from evidence every single time.

That reconstruction is not work. It is rework, and you pay for it forever.

What to do on Monday

You do not need a consultant, a new hire, or a system, to take the first step. You need one sentence written down and enforced:

Write it. Tell whoever handles payments. Apply it to every transaction from Monday forward, and to nothing before that. You will feel the friction immediately, and the friction is the point. Every time it is hard to apply that rule, you have found a place where the record was previously breaking.

That is process. It costs nothing.

Then, and only then, ask whether a system should enforce it for you, and whether the work has outgrown the people you have.

Most owners discover, having done the first step, that they never needed the third.

Where Wihemi fits

Wihemi Travel is accounting and back-office software for travel agencies, built by a finance team out of exactly this problem. It does not replace your accounting system; it feeds it. It does not ask you to understand accounting. It asks you to record the booking and record the payment, and it makes everything else impossible to get wrong.

You don't need to be an accountant. You need the record to hold together.

Part of the bigger picture: read the full guide to travel agency back-office accounting.