Onboarding problems don’t announce themselves. They show up as mild friction in Week 1, an email that didn’t get answered, a meeting that got postponed, an asset that was “coming soon” for the third day running. These feel minor in isolation. They compound.
By Week 3, mild friction has become a stalled project, a frustrated client, and a freelancer wondering what went wrong. What went wrong was identifiable and fixable in Week 1. The signs were there. Nobody ran the diagnostic.
The six roadblocks below are the ones that appear in every type of freelance project, across every industry, at every price point. The root causes are consistent. The fixes are specific. Spot them in Week 1 and you have a functional project by Week 2.
Roadblock 1: Slow Asset Delivery
What it looks like: You sent the asset request after kickoff. It’s been 5 days. Nothing has arrived. Your contact says “I’ll get to it.”
Root cause: Not urgency failure, prioritization failure. Your asset request is competing with your contact’s actual job. It’s not at the top of their list because the consequences of delay aren’t visible to them.
The fix: When you sent the asset request, you stated a deadline but didn’t explain the impact. Re-contact with specificity:
“Just circling back on the asset request from [date]. My Week 2 deadline for the first draft is [date]. If I don’t have the logo and brand guide by [day], I’ll either build the draft without them and need to rework it later (adding a revision round) or push the Week 2 milestone back to [date+5]. I don’t want to waste your revision budget or delay the timeline. Can you get them to me by [day], or should I plan for the later date?”
This message gives your contact a concrete cost to the delay and two clear options. Most people prefer to find the file than to delay the project. The ones who don’t will tell you, and now you know the timeline needs adjusting before it becomes a missed deadline.
Prevention for next time: In the initial asset request, include the impact statement: “I need these by [date] to deliver [milestone] on schedule.”
Roadblock 2: Missing Decision-Makers
What it looks like: You’re two weeks in. You’ve built something that looks right based on the brief. But then a name you’ve never heard comes up: “Actually, [Name] needs to see this before we can move forward.” That name isn’t in your decision authority matrix because it wasn’t mentioned at kickoff.
Root cause: Your primary contact doesn’t have full approval authority, or they didn’t disclose the full stakeholder landscape at kickoff. This isn’t deceptive, they may not have thought about it, or the internal process is unclear to them too.
The fix: Name the gap immediately:
“I didn’t know [Name] was part of the approval process, I want to make sure I’m accounting for their input correctly. Can you tell me what they need to see, what their perspective typically is, and whether it would be useful for me to present directly to them? I’d rather build in 30 minutes now than do a full rework after their review.”
Then ask for an intro. Meet the person, understand their priorities, update your decision authority matrix. Don’t produce more work until you know what this new stakeholder needs.
Prevention for next time: Ask Question 3 from the alignment conversation at kickoff: “Who outside this room has opinions about the outcome that we haven’t talked to yet?”
Roadblock 3: Vague Brief
What it looks like: The brief you received is 3 sentences. Tone, audience, format, constraints, success metrics, none of it is defined. You could take the work in 10 different directions, all of which are technically responsive to the brief.
Root cause: The client either hasn’t thought through the project at a detailed level or assumes you’ll fill in the gaps with expertise. The latter is a compliment; acting on it is a mistake.
The fix: Send a brief clarification request before starting work:
“Before I begin, I want to make sure I’m going in the right direction, I have a few questions that will shape the approach. Once I have answers, I’ll start right away. Questions:
- Who is the primary audience for this? What do they already know, and what needs to be explained?
- What does success look like in concrete terms, what would you need to see in the output?
- Are there constraints I should know about (tone, length, topics to avoid, regulatory requirements)?
- Can you share 1-2 examples of work you’ve admired in this space?
- Is there anything from a previous attempt at this that I should be aware of?”
These five questions cover 90% of brief ambiguity. Do not start work until they’re answered. The revision cost of a misdirected first draft exceeds the delay of getting answers.
A vague brief is not an invitation to use your creative judgment. It’s a gap that will produce revision requests. Filling it with assumptions is a disservice to both of you. Ask the questions. Then start.
Roadblock 4: Prior-Vendor Baggage
What it looks like: The client seems overly involved in small decisions. They request detailed progress updates mid-week. They ask to review partial drafts before they’re ready. The tone in emails occasionally feels slightly suspicious, like they’re waiting for you to disappoint them.
Root cause: The last freelancer or agency let them down. They’re managing you the way they learned to manage the previous vendor, with preemptive oversight. They haven’t updated their behavior to match your actual track record yet.
The fix: Name it without making it awkward:
“I noticed you’re interested in seeing the draft at the partial stage, happy to share, but I want to make sure we’re using your review bandwidth well. I find partial drafts sometimes generate feedback that would resolve itself in the complete version and can send us in the wrong direction. Would it help if I walked you through my approach in a 15-minute call before I get to draft stage? That way you can course-correct before I’m deep in execution.”
This offer is both practical and communicative. You’re signaling: I’ve heard your concern about being left in the dark; here’s a structured way to address it that doesn’t create revision loops.
Over the first 3-4 weeks, consistent delivery against milestones at the quality you promised will recalibrate their behavior. Baggage from a previous vendor dissolves when the new vendor proves to be different.
Roadblock 5: Competing Internal Priorities
What it looks like: The client keeps canceling or rescheduling meetings. Asset deliveries are late. Their responses to your questions are shorter and less thoughtful than they were at kickoff. The project isn’t being prioritized.
Root cause: Something else at the company took over. A launch, a crisis, a reorganization, a leadership change. Your project went from “important” to “important but can wait.”
The fix: Address it directly rather than pretending nothing changed:
“I’ve noticed the pace slowed from our Week 1 rhythm, totally understandable if there’s a lot going on internally. I want to be useful rather than add noise. Two options: (1) We pause the project formally for [X weeks] and resume on [date], I’ll hold your project files and context. (2) We continue at a lighter pace, focusing only on [lower-priority deliverables] until your bandwidth frees up. What makes more sense?”
Offering a formal pause is counterintuitive but effective. Clients who are overwhelmed are relieved when someone gives them permission to pause. They also tend to remember that you made the offer, which is a strong trust signal.
If the project isn’t paused but continues slowly, document the timeline impact: “Noted, this will push our final milestone from [original date] to [adjusted date]. I’ll update the project plan accordingly.”
Roadblock 6: Budget Approval Gaps
What it looks like: You’re three weeks in and the client mentions, in passing, that the full project budget still needs board or CFO approval. You believed the budget was confirmed when the contract was signed.
Root cause: The person who signed the contract had authority to sign but not necessarily to approve the full budget. Or the budget approval process was still in progress when they signed, and they assumed it would conclude quickly.
The fix: Stop work on anything that requires the unapproved budget and address it immediately:
“I want to flag, based on our conversation, it sounds like the full budget still needs [approval]. I’m comfortable continuing work on [Phase 1 deliverables, which cost $X] but I’d want to hold [Phase 2 work, which costs $Y] until the approval is confirmed. Can you give me a realistic timeline for when that happens? I’ll plan the project schedule around it.”
This is a professional constraint, not an accusation. You’re not suggesting they won’t pay, you’re managing risk that’s now visible. Most clients respect this approach and expedite the approval process once they realize you’re holding a deliverable pending it.
Prevention for next time: Add to your contract or kickoff checklist: “Budget for all phases of this project has been formally approved.” If the client can’t confirm that, stage the contract so each phase requires separate sign-off.
The pattern across all six roadblocks: the fix requires naming the problem directly, offering a concrete path forward, and adjusting the project plan to reflect the new reality. None of these fixes involve working around the problem. They all involve surfacing it and solving it.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
