# Should I Take the Freelance Gig? The Money Would Help. So Would a Boundary.
The message came from a former colleague on a Tuesday evening: "Hey — we're slammed. Would you be open to some freelance on the side? Good budget, flexible hours, your call on scope." Good money. Flexible. My call on scope. It was, by every measurable metric, a free yes. The kind of opportunity you tell your friends about.
I said yes within the hour. And then I spent the next three weeks doing something very strange: dreading it.
Not the work — the work was fine. I knew the domain, I knew the team, I could do the job in my sleep. The problem was the other hours. The evening hours. The weekend hours. The hours I'd promised myself I was going to protect, for the novel, for the gym, for the friends I kept rescheduling. I'd said yes to a thing that ate the very hours I'd been complaining I never had enough of.
And I couldn't explain to myself why I'd done it. The money? I didn't need it. Not desperately — it would be nice, but the math didn't change my life. So why did I say yes to something that would consume the exact resource I'd been guarding?
The three tells it wasn't about the money
- I didn't negotiate the scope. The message said "your call," and I accepted the first scope they proposed without changing a word. Someone who wants money pushes for more. Someone who wants something else doesn't push at all.
- I checked my phone for their replies the way I used to check for someone's texts. The anticipation was the reward — being wanted, being needed, being the person they came to.
- When my partner asked why I'd taken it, I said "it's good money," and heard myself lie. The money was fine. It wasn't the reason.
What the reading said
I did a reading. The question: should I take the freelance gig?
The reading didn't run the numbers. It asked: what are you hoping they'll pay you in, exactly?
That was the question I'd been unable to ask myself. Because the invoice I was trying to collect wasn't money.
I'd spent a lot of recent years feeling like my value was unproven. At my job, I'm competent but invisible. In my personal life, I'm the one who shows up but never gets asked to the thing. Somewhere along the way I'd started collecting proof of worth the way other people collect interest — and this gig was proof. A former colleague, out of the blue, saying you're good enough that I'd pay for you. That was the paycheck. The money was just the envelope it came in.
And that's why I couldn't set a boundary. Boundaries are for things you want on your terms. I didn't want this on my terms — I wanted it at all. Saying "here's my scope, here's my rate, here's my schedule" would have meant risking the yes. And I needed the yes more than I needed the boundaries.
What happened
I kept the gig — for now. But I went back and set the boundary I'd skipped: a capped number of hours, a defined scope, a deadline on the timeline. It was one message, and it was the hardest message of the whole engagement, because it risked the thing I was collecting.
He said "totally, makes sense, that's why I said your call." That's it. The boundary I'd been terrified of losing the job over cost me nothing.
Here's what the reading showed me. The gig was never about money — it was about proof, and proof can't be collected from other people no matter how many gigs you take. The invoice I was trying to collect was for a debt no one owed me. The boundary wasn't the thing I was sacrificing. The boundary was the practice — the practice of knowing my time was worth protecting, with or without someone else's validation.
Anyway. I'm still doing the gig, on my terms now. And the novel is still not written, but I got two evenings back, which is two more than I had. The money helped. The boundary helped more.
If you keep saying yes to things you don't really want — and you can't explain why — try a reading. Three numbers. No account. It won't set your boundaries for you. But it might show you what you're actually being paid in, and whether the currency is one you can cash.
FAQ
Q: How do I know if I'm saying yes for the money or for something else? A: Test it. If the money changed — if it was half as much — would you still want it? If yes, it's the work. If you'd drop it instantly, the money was never the point. And if you'd keep it and resent it, the thing you're collecting isn't in the invoice. See also: They Asked Me to Take On Another Project. I Said Yes Before I'd Even Decided. — the reflex yes and the fear underneath are the same in both.
Q: Isn't it good to say yes to opportunities? A: It's good to say yes to opportunities you want. It's different when the yes is a reflex — a way of collecting proof that you're wanted. Opportunities taken to prove your value don't build your life; they eat it. The question isn't "should I say yes?" It's "what am I saying yes for?"
Q: How do I set boundaries without burning the relationship? A: Boundaries protect the relationship. The request that can't survive a boundary wasn't a relationship — it was a transaction where you were the only one giving. "Here's the scope I can commit to" is not a rejection. It's how you make the thing sustainable. The people who actually value you will hear it fine.
Q: How does a reading help with a money decision like this? A: It ignores the dollars and asks about the desire underneath. I thought I was deciding whether to take on paid work. I was actually deciding whether I could stop collecting other people's approval as proof of my worth. The reading named the invoice — and once I could see what I was really being paid in, the boundary got easy to set.