Ten Weeks of Client Experience,Built Before the Season Starts

The Pattern

Tax season is its own kind of business.

You don't have twelve months to figure out what works, clean something up, rewrite an email or decide halfway through that the process needs to change. You've got this very concentrated window where everybody needs something at the same time.

Documents are coming in. Clients want to know if you received them. Somebody is missing a W-2. Somebody wants an update. Somebody's return has been filed and now they have another question. And all of those little communication moments are happening while you're also trying to do the actual work they hired you to do.

That's what made this project interesting to me.

The problem wasn't simply, "How do we automate some emails?"

It was: How much of the client experience can we make clear before the season starts, so Anissa doesn't have to personally recreate it every single time things get busy?

Because in a seasonal business, you're going to run whatever you built before the rush. If it isn't there, now you're building it while serving everybody at once.

The Client

Anissa Paige is a tax professional, which means her business has a very specific rhythm. There is a season, there is a deadline, and there is a whole lot of client activity packed into a relatively short period of time.

The demand itself wasn't the question.

What we needed to look at was everything surrounding the tax preparation: what clients needed to know, when they needed to hear from her, what they were likely to ask, what Anissa would otherwise have to remember to send, and where we could create more consistency before volume picked up.

That's the part people miss when they talk about systems.

The tax return is the service. The experience includes everything happening around it.

The Starting Point

We started before tax season because that was really the whole point.

There are certain moments Anissa knows are going to happen with client after client. Intake is going to happen. Documents are going to come in. Some documents are going to be missing. Clients are going to want confirmation. They're going to wonder what happens next. There will be status questions, filing communication and follow-up.

None of that is surprising.

But if the answer to those moments lives mostly in the business owner's head, then every predictable question becomes another thing she has to stop and personally handle.

That's manageable when volume is low. It becomes a very different experience when everybody needs you at once.

So instead of waiting for tax season to tell us where the pressure was, we looked at the journey beforehand and asked: What can already be decided, written and ready before the first client needs it?

The Approach

We started with a 90-minute strategy session and walked through the client experience as it actually happens. Not the neat version on paper. The real version.

Where does the client enter? What do they need from Anissa? What does she need from them? Where are they likely to have questions? What has to happen next? What communication shouldn't depend on her remembering it during the busiest part of the year?

From there, I built the Tax Season CX System around the repeatable parts of that experience.

That included client journey automation for the communication that could happen consistently without Anissa manually sending it each time.

We created branded email sequences in her voice because automation doesn't need to sound like automation. The client should still feel like they're working with Anissa, not like they got dropped into somebody's software.

We also created support scripts around the kinds of questions that come up repeatedly during tax season. If you're going to answer something over and over again, there's no reason to rewrite the answer every single time. Write it once, make sure it's good, and make it easy to use again.

Then we walked through the finished system before the season picked up so Anissa could see how everything connected.

The goal wasn't more technology.

The goal was fewer things that required Anissa to stop doing tax work just to keep the client experience moving.

The Transformation

The biggest change happened before we could even talk about season results: the communication no longer had to begin from scratch with every client.

The repeatable moments had been identified. The messages were written. The automations had a job. The common questions had prepared responses. And Anissa had a client journey designed around what she already knew was going to happen during tax season.

That's different from trying to automate everything just because you can.

We weren't removing Anissa from her client experience. We were removing some of the unnecessary remembering, rewriting and manual communication around the work only she could do.

Now the system had something to carry.

The bigger performance question, how that experience held up across the full season, is something I'll let the actual season and Anissa's experience answer rather than writing a result for her before we have it.

The Standard

Seasonal businesses make one of my favorite CX lessons very obvious: you cannot wait until the experience is happening at full volume to decide what the experience should be.

If you already know clients are going to ask the question, decide how you want to answer it.

If you already know a transition is going to happen, design the transition.

If you already know communication needs to go out, don't make yourself responsible for remembering it 200 times.

That's what we built here.

Not a bunch of automation for the sake of saying the business is automated. A client experience designed before Anissa needed it, with systems underneath it that could help carry the repeatable parts when the season got busy.

Because the experience is the system.

And the system should make it easier to deliver the level of experience you intended in the first place.