The client you're afraid to fire is costing you the most. Just not in dollars.
You know which one. The calls you let go to voicemail. The inbox you check with your stomach already tightened. The late nights dealing with it so the rest of your week can stay clean.
That client is costing you something the invoice doesn't capture: the energy that never makes it to the clients who are actually worth it.
Before we get to firing, though: some of those clients aren't difficult. They're uninformed.
The client who texts you the same question on Tuesday and again on Thursday isn't necessarily high-maintenance. They have no window into their own project. They don't know where the countertops are. They don't know if the vendor confirmed the timeline. They're not trying to be a problem - they just have nowhere else to look.
Archen's client portal changes that. You control what they see - they're not looking at everything, only what you've chosen to share. But what they can see, they can check themselves. The question that would have landed in your inbox at 9pm doesn't get sent.
Some firings never happen because the client finally had somewhere to look.
The ones that do have to happen are a different story.
Six weeks in. The client is texting daily about things that haven't changed since last week. A vendor was confirmed two weeks ago - the client has now started calling them directly, changing specs without telling you.
The conversation that has to happen:
“I want to talk about how this project is going for both of us. Here's what we agreed at the start. Here's what's been delivered. I don't think I'm the right fit for where this is going - here's what I'd need to continue, and here's how we close out if we decide to part ways.”
That conversation is impossible without the record. Most designers don't fire when they should for this exact reason - they feel trapped by what was promised verbally and never confirmed, or they can't clearly show what's already been delivered. Both are documentation problems dressed up as relationship problems.
If scope was set verbally and nothing was written down, the exit becomes a dispute about what was said. You remember it one way. They remember it another. And if you can't account for what you've delivered, the exit feels risky - what if they dispute the invoice? You want to leave but you can't prove why you're leaving.
The client you should fire is the one that's costing you the clients you want.
Archen builds the record from the communications that already happened. The portal gives the right clients a window into their own project - so they stop needing one from you. And when the conversation that has to happen finally comes, you're reading from the record. Not arguing from memory.
Fire the client. Keep the record.
