Featured on this episode:

• Join the wait list for The Designers Edge and my May 5th workshop.
• Grab Your Free Script Guide here
• Access the full video interview with Elana Steele of Steele Appliance here

What you will learn from this episode:

• The 4 moments that signal you’ve crossed from interior designer to project manager

• Why your role (not your scope) is what’s quietly expanding

• What to say when the slide has already happened

---

The Slide Nobody Talks About

Last week, I talked about the real cost of undercharging. And if you haven’t listened to Episode 273, I really encourage you to go back because these two conversations are connected in ways that really matter.

What I talked about last week was the financial gap. What we’re going to talk about today is one of the biggest reasons that gap exists in the first place. And that’s the consulting-to-managing slide.

It doesn’t happen in one big dramatic moment. There’s no meeting where someone hands you a new job description. There’s no contract amendment. There’s no conversation where the scope of your engagement formally changes.

It just happens.

And honestly, I’ve found that it happens in four quiet moments. Each one is easy enough to rationalize in isolation. But each one also builds on the last until one day you look up and realize you are running a project you never formally agreed to run, with a fee that was never built to support it.

So today, we’re going to name those four moments. Not to make you feel badly about the times you’ve missed them, I have missed all of them countless times. But so that you can catch them earlier next time.

Because the later you catch it, the more it costs you in time, in money, and in the kind of quiet resentment that builds when you’re giving everything to a project but the project isn’t giving you back what it should.

---

Role vs. Scope: The Confusion at the Root of It All

Before we get into those four moments, I want to anchor this whole conversation in something that I think is at the root of why this slide happens so quietly and yet so consistently.

And that is the confusion between role and scope.

These two things are not the same. And I want to say that very clearly because I get emails about this pretty regularly now, and I think it’s one of the most misunderstood dynamics in our entire industry.

Your scope is what your project includes. The rooms. The phases. The deliverables.

Your role is how you show up inside that scope. Are you consulting or are you managing?

Those are two completely different engagements, even though they sound the same. And they require two completely different conversations, along with two completely different fees.

Here’s what’s really important to understand: the client defines the scope with you. You define your role on that project.

You, the designer. You choose the role you are willing and equipped to offer on any given project. That is solely your decision. It absolutely belongs to you. Only you. Not the client. And definitely not the contractor.

And yet this is one of the most common misunderstandings I hear about from designers, and it is costing designers authority and income every single day.

This has become such a common topic that I’m going to dedicate a full episode to the role versus scope conversation very soon, because it really deserves that kind of depth. But for today, what I need you to hold on to is this:

The slide we’re talking about today is almost always a role problem, not a scope problem.

The project didn’t get bigger. Your role got bigger. And nobody named it. Including you.

So let’s talk about the four moments where you could have named it, and what was actually happening in each one.

---

Moment 1: The Job Site Signal

This is the earliest moment and the easiest to miss. And it’s easy to miss because it doesn’t feel like a problem. It feels like helping.

You’re on site. A trade you’ve never met before walks up and asks you a question about sequencing. Or a subcontractor you do know wants to know when the tile is arriving. Or the contractor turns to you in front of the client and asks how you want to handle something that is clearly a construction logistics decision rather than a design decision.

And of course, you answer it. You’re standing there. It’s easier to answer it than to redirect, because the project needs to keep moving and you are physically in the room and you know the answer.

That moment is easy. You’re helpful. You honestly barely notice it.

That’s your first signal.

Your role just expanded. And nobody said a word about it. Not the contractor. Not the client. And not you.

Let me be clear about something. Answering the question is not wrong in itself. Being present and knowledgeable on a job site is part of what makes us valuable. The issue isn’t the answer. The issue is whether that kind of involvement was part of the role you defined and agreed to, or whether it’s the beginning of a role that’s being assembled around you without your explicit consent.

One question answered on a job site doesn’t make you a project manager, especially if you’ve included consulting hours in your estimate. But if you’re answering questions like that regularly, if trades are coming to you, if sequencing questions are landing on your plate or in your inbox, if you’re being treated as the hub for information on a job site, that is information you have to pay attention to.

---

Moment 2: The Behavioral Shift

If the job site moment is subtle, this one is less so.

This is the moment someone’s behavior toward you makes it undeniable that they see you as a project manager, regardless of what your contract says or what role you intended to play.

The contractor starts copying you on every email. Or the client stops calling the contractor and starts calling you instead. Trades are texting you directly with questions that have nothing to do with design. Your client is forwarding you contractor invoices and asking if they look right. Scheduling questions are coming your way. Budget questions. You are being treated as the central point of contact for a project that you may have originally engaged with just as a design consultant.

Here’s the complicated part. It feels like a compliment. It feels like trust. It feels like authority. It feels like proof that you are the most confident person in the room and everyone knows it.

And honestly, in some ways, it is all those things. And that feels validating, amazing, and downright fun.

But here is the problem. It’s also a role you didn’t price your fee for. And it is a role that someone else, the contractor, the client, or the momentum of the project itself, assigned to you, rather than one you consciously chose, agreed to, and priced for.

This is the moment where that role conversation needs to happen. And I don’t mean defensively. Not with resentment. I mean clarity.

Because right now, the project still has enough runway ahead of it that a direct conversation can reset expectations without a lot of drama. But the longer you wait, the harder that conversation becomes. Because the longer you play that role without naming it, the more everyone around you assumes it’s permanent.

---

Moment 3: The Invoice Moment

While we talk about this moment a lot in other contexts, this is also where it becomes impossible to ignore when your role has shifted.

The job site moment, you could rationalize. The behavioral shift, you could tell yourself was temporary.

But the numbers don’t lie. And they don’t care about your rationalizations.

So what does this look like in practice?

You sit down to prepare an invoice, or you’re looking at your flat fee and doing the math on your actual hours. And the gap is right there in front of you. The work you have been doing does not match the fee you agreed to or the hours you estimated.

That’s because the role you have been playing is not the role you contracted for.

And in that moment, you have two choices. You can bill hourly, accurately, for that month and then have the conversation you’ve been avoiding. Or you can trim the invoice, absorb the difference, tell yourself the project is almost over and that you’ll handle it differently next time.

And look, I say this with complete compassion because I have made that second choice countless times. Most designers choose that second option because in that moment, it feels easier. It avoids an awkward conversation and it keeps the peace.

There is no judgment in taking that option.

But that decision, made quietly at your desk, repeated across multiple projects over multiple years, is how the gap I talked about last week gets built.

It does not happen in one dramatic moment of undercharging. It happens over hundreds of small ones, each one feeling like a reasonable choice in that moment. But the totality of it takes an enormous hit on your business and your profitability.

---

Moment 4: The Emotional Signal

And then the last moment, the fourth moment, is the emotional one. And this one typically hits last, but in my experience, it hits the hardest.

It’s one that designers recognize most deeply, even if you’ve never had the language for it.

Because it’s not a job site moment. It’s not a billing moment. It’s a Sunday afternoon moment when you genuinely don’t want to look at your phone because you know there’s a project issue waiting for you and you don’t have the bandwidth or the energy or the desire to deal with it.

It’s the way your stomach drops when a specific client’s name appears on your screen. Or it’s the resentment that builds quietly, not loudly, not dramatically, but steadily. You don’t even notice it in the moment. But you feel it when you are giving everything to a project and it is not giving back what it should.

It’s the exhaustion that comes not from working hard, because we work our asses off and we know the difference, but from working hard in the wrong role, at the wrong fee, for too long, without naming it.

So here’s what I want you to hear about that feeling, because I think we misread it a lot.

That emotional signal is not weakness. It is not evidence that you’re not cut out for this work, or that you took on the wrong project, or that you should have seen it coming.

It is information. No judgment.

It is your nervous system telling you clearly and loudly that something in the structure of this engagement is wrong. The role you are playing and the agreement you made at the beginning of the project are no longer the same thing.

And that is what needs to change.

---

What to Do When You Finally Acknowledge It

The question is, what do you do when you finally acknowledge it?

Because none of these moments make you a bad designer or even a bad business owner. They make you someone who cares deeply about the project, the client, and the outcome. They make you someone whose instincts are to show up fully, fill the gaps, and keep things moving.

And those instincts are part of what makes us exceptional at this work.

The issue is not the instinct. The issue is that the instinct has been running ahead of the agreement.

Let me repeat that: the issue is that the instinct has been running ahead of your agreement.

So the fix is not to stop showing up fully. The fix is to make sure the agreement catches up with the reality of what you’re actually doing.

Here’s what that looks like in practice.

---

Moment 1: The Job Site Signal

This is a simple internal check. I call it cataloging, not critiquing.

Ask yourself: Is what I just did part of the role I agreed to play?

If the answer is yes, move on.

If the answer is no, or “I’m not sure,” catalog it. Make a note.

One moment does not require a conversation. A pattern does. That’s when you start switching from cataloging to critiquing.

---

Moment 2: The Behavioral Shift

When the behavior around you shifts, that is your cue for a direct and calm conversation. Because that is a pattern.

I’m not talking about a confrontation or a renegotiation. This is a moment for clarification.

Say to your client something like: “I want to make sure we’re all aligned on how decisions are flowing on this project. Let me walk you through how I see my role from here on, and we can make sure everyone is on the same page.”

That is not a confrontational conversation. That’s a conversation that takes five minutes. It alerts the client that something needs to be reviewed, and then depending on that review, that’s the next conversation.

Having this initial conversation will save you months of misalignment and underbilling for services you are rendering.

---

Moment 3: The Invoice Moment

This conversation gets much harder. But it is still possible.

This is where you address the gap directly with your client. It is not an apology. It is not blame. It’s clarity.

Something like: “The scope of my involvement has expanded beyond what we originally agreed to, and I want to have an honest conversation about what that means going forward.”

Here’s the reality. Most clients will respect that conversation because most clients want to know what they’re paying for and why.

That conversation may result in: “Pull back on your responsibilities, Renee. Go back to consulting.” Okay.

But it also may be: “Renee, I like you in that role. I have appreciated it. I’m leaning on your expertise. What does this mean financially going forward?”

You need to understand: your clients don’t know what they don’t know. And if we are not willing to share what we see happening with our role, a client will assume everything is fine. And it’s not from a negative perspective. It’s because you are behaving like everything is fine.

---

Moment 4: The Emotional Signal

When that fourth moment hits, that emotional signal, that blinking red light, the conversation is the most important and often the most overdue.

But it starts not with your client. It starts with you. With an honest acknowledgment that something in this project isn’t working. And that you have both the right and the responsibility to address it.

Because the most important thing for you to walk away from every project is not relief. It’s pride.

Sure, you can be tired. But I’m talking about that bone-aching sense of dread that so many projects leave us with because we are so incredibly burned out from them and we didn’t do anything about it.

That is what I want you to put an end to. Not just for the projects, because they do expect and need you to show up fully engaged, but for your own peace of mind and your own sanity.

---

The Root Is Always in the Beginning

Here’s what I want you to take away from everything I’m talking about today.

That slide from consulting to managing, the reason it happens so quietly and so consistently, is almost always rooted in how the project was defined at the very beginning.

When your role is clear, and I mean crystal clear from day one, and your fee is built on what management actually requires, and that agreement reflects the reality of what you’re bringing to the project, those four moments I talked about today either don’t happen or they’re really easy to address when they do.

Because everybody already knows what the role is.

Remember: you and you alone define your role. And then you have the control to communicate it fully and clearly and ultimately price it appropriately to cover your costs, not for the best-case scenario, but for the reality of a construction project.

---

Like this Episode?

Be sure to check out Episode #273: The Real Cost of Undercharging: A Q1 Audit for Interior Designers

Be sure to check out Episode #180: How To Stop Losing Money On Construction Projects

Be sure to check out Episode #214: LuAnn Nigara on Leadership, Profitability, and Owning Your Role