LinkedIn Post Ideas for Freelance Designers

The client said make the logo bigger. I said yes. Here's why I didn't fight it. Their homepage had the logo at 100px, tucked in a corner, doing absolutely no work. My instinct as a designer was "trust the hierarchy, resist the request." But I asked one question first: "what's it competing with when you look at it?" Turned out the client's own answer mattered more than mine: they'd just done a rebrand, and their team kept second-guessing whether the new mark actually shipped, because it barely registered on the page. "Bigger" wasn't a taste request. It was "make me confident this rebrand actually happened." I bumped it to 160px, added breathing room around it, called it done in fifteen minutes. Client's response: relief, not vanity. The fix wasn't a compromise on my craft. It solved the actual problem, which had nothing to do with pixels and everything to do with confidence in a decision they'd already paid for. The lesson that changed how I take feedback: ask what the request is a symptom of before deciding whether to push back. Half the time, "bigger" means something completely different than "bigger."

Round fourteen. Same logo project. The client still wasn't happy, and neither was I. What went wrong: no revision limit in the contract. "Unlimited revisions until you're happy" sounded generous when I wrote it. In practice, it meant the project had no finish line, because the goalpost kept moving with each new stakeholder who saw a draft. The fix I built after that project, now in every contract: — Two structured revision rounds included in the base price, each with a written list of specific changes, not open-ended "make it feel more premium" notes. — Anything past round two: billed hourly, quoted upfront per round, invoiced before I start the work. — A required single point of contact clause. No more collecting feedback from four stakeholders who each want something different. The first client I used this policy with pushed back initially — "that feels restrictive." I explained it protects them too: it forces internal alignment before feedback reaches me, instead of me becoming the battleground for their internal disagreements. That project finished in three rounds. Total time: a third of what round-fourteen took. Scope-protection clauses aren't about being difficult. They're the difference between a project with an ending and one that doesn't.

Before: a plumbing company's logo was a clip-art wrench, Comic Sans phone number, a van that looked exactly like every unmarked van customers are taught to be wary of. After: a clean mark, a consistent color system across the van, uniforms, and yard signs, a redesigned Google Business Profile with real photos instead of stock images. The client's own reporting, three months post-rebrand: a 22% increase in inbound calls that customers specifically attributed to "found you online" versus referral. Not something I can claim as pure attribution — seasonality and their own marketing push played a role too — but it's the number they track, and it moved. What actually drove it, in my read: trust signals. A plumber shows up at your house, sometimes when you're not home, often for an emergency. A branded van and a professional-looking profile do real work reducing the "is this a scam" hesitation before someone calls. This is the version of a portfolio piece that gets a freelancer hired: not "here's a pretty logo," but "here's the business problem, here's what changed, here's the number that moved." Aesthetics-only posts get other designers' likes. Outcome-anchored posts get client inquiries. What's your best before-and-after with a number attached?

Three ways I've priced design work, and why I mostly use the third one now. Hourly: transparent, easy to explain, terrible incentive structure. I'm penalized for getting faster and better, which is backwards. Clients also fixate on the hourly number instead of the outcome. Value-based: price to the business impact — what's a rebrand worth if it moves conversion 2%? Sounds smart in theory. In practice, it requires a client sophisticated enough to model that impact with you, which most small-business clients aren't equipped to do, and the negotiation gets adversarial fast. What I actually use: scoped flat-rate, calculated backward from an internal hourly target, quoted as a fixed number per deliverable. My real math, disguised project: a brand identity package quoted at $4,800, built assuming roughly 40 hours at my target rate, with buffer built in for one structured revision round. The diagnostic questions that reveal real budget before I quote: "what have you paid for design before, and how did that go?" and "is this funded from a specific budget line, or are we figuring out the number together?" Both surface more truth than "what's your budget" ever does. Flat-rate scoped pricing gives clients certainty and gives me the upside of getting efficient. That alignment is the whole reason it works better than either extreme.

I quote clients $85/hour. I tracked every single hour of my business for a full year — proposals, revisions, admin, invoicing, unpaid discovery calls, everything — and divided total income by total hours worked. My actual effective rate: $41/hour. Where the gap came from: 11 unpaid proposals for every 3 that converted. Roughly six hours a week on admin and invoicing that never got billed. Scope creep on nearly every project that I absorbed rather than invoiced, because I didn't have the revision policy I have now. And two clients who paid 60 days late, which doesn't show up in the income number but absolutely shows up in the stress and cash-flow cost. The wake-up call wasn't the number itself. It was realizing my quoted rate had nothing to do with my real economics — I'd set it once, years ago, and never revisited it against what was actually happening in the business. What changed after this audit: quoted rate went up 30%. Proposal process got shorter and more selective, so I stopped burning hours on low-probability quotes. Revision policy tightened, per the scope-creep lesson. A year later, my effective rate is $58/hour. Still a gap from quoted, but half the previous one. Track your real hours for a month. The number will be uncomfortable, and it will be useful.

Five red flags I now catch in the very first email, before a call is even booked. 1. The vague brief. "We need a website that pops" with zero detail on audience, goals, or competitors. Not a dealbreaker alone, but paired with anything else on this list, it usually means undefined expectations I'll be blamed for later. 2. Urgent timeline, no budget mentioned. "Need this in two weeks" with silence on budget almost always means the timeline is the only thing they've actually thought through. 3. Trash-talking the previous designer, unprompted. Everyone has a bad-fit story. Volunteering it in email one, before I've asked, is often a preview of how I'll be described to the next designer. 4. "We're talking to a few people, can you do a free concept first?" A request to work for free framed as a competition. My response now: a paid discovery call instead, which filters this out almost every time. 5. Overly specific creative direction paired with "but we trust your expertise." The contradiction itself is the flag — it usually means approval will be litigated against a vision that was never actually shared with me upfront. None of these are automatic no's alone. Two or more together, and I quote a premium or pass entirely. Each flag paired with a response that filters without burning the relationship, in case I'm wrong about them.

I spent four years as a generalist designer — logos, websites, packaging, whatever came in. Then I niched to one industry: brand identities for independent healthcare practices. Inbound tripled within six months. The fear going in was obvious: wouldn't narrowing my positioning shrink my market? The opposite happened. Before niching, my "portfolio for anyone" read as competent but forgettable. A prospective client scanning ten portfolios in an afternoon had no reason to remember mine specifically. After niching, my headline became "brand identities for independent healthcare practices," and my case studies all spoke the exact vocabulary that audience uses — HIPAA-adjacent trust signals, patient intake friction, referral-based growth. A dermatologist or physical therapist scanning designers now sees someone who's clearly done this exact thing before, not a generalist hoping to figure it out on their project. The referral flywheel effect surprised me most: healthcare practice owners know each other through associations and conferences I'd never have accessed as a generalist. Three of my last five clients came from a single referral chain inside one regional dental association. The premium is real too — clients pay more for a specialist than a generalist doing the identical scope of work, because the perceived risk of a bad outcome is lower. The niching debate never dies online. My lived numbers: worth it, faster than I expected.

AI image generation entered my workflow eight months ago. Here's exactly where it earns its place, and where it quietly doesn't. Where it works: moodboard exploration. What used to be an hour of stock photo hunting across three sites is now fifteen minutes generating direction options, then refining the one that resonates. Client concept revisions also move faster — instead of a two-day turnaround for a new visual direction, I can show three options same-day. Where craft still earns the fee: anything client-facing and final. Generated imagery still has telltale artifacts under real scrutiny — hands, text, brand-specific color accuracy. Every final asset gets rebuilt or heavily reworked by hand before delivery. What clients actually noticed: not the tool, the speed. Nobody's asked "did you use AI for this." Multiple clients have commented "wow, that was fast" on turnaround for concept rounds specifically. How I talk about it with clients, unprompted, before they ask: I mention AI-assisted exploration is part of my process for early concepting, and that everything final is designed and refined by hand. Nobody's pushed back. If anything, the honesty read as more professional than staying quiet about it. The tool changed my speed on the boring 30% of the process. It hasn't changed what clients are actually paying for.

Lost count of how many proposals I've sent. Here's the actual structure of the one that converts best, and the one section that does the real work. 1. Problem restatement, in their words. Two sentences repeating back exactly what they told me on the discovery call, using their own vocabulary. This alone signals "I listened" more than any credentials section could. 2. Approach, three steps, no jargon. What I'll actually do, in plain language, not process-speak. 3. The options table. Three tiers — good, better, best — each with a clear scope difference, not just a price difference. This is the section that wins work. Why it works: a single price forces a yes/no decision, and "no" is easier to choose than "which one." Three tiers turn the decision into "which fits us," which keeps the conversation going even when the top tier feels out of reach. My middle tier converts most often — a known anchoring effect, but it also happens to be genuinely the right scope for most of my clients. 4. Timeline, with real dates, not "6-8 weeks." 5. A single testimonial relevant to their specific situation, not a generic one. Designers undersell with beautiful but vague proposals — gorgeous typography, mushy scope. Mine is plain and specific. Specific wins more often than beautiful does.

Designers — what's the strangest feedback a client ever gave you? Mine: a client asked me to "make the blue more Tuesday." I asked three clarifying questions and got nowhere closer to an actual answer. Eventually I just tried a slightly desaturated, muted blue instead of the vibrant one I'd used. Client's response: "yes, that's the Tuesday one." I still don't fully know what that meant. But translating it mattered more than understanding it. Underneath the strange phrasing was a real preference — something between "calmer" and "less demanding of attention" — I just had to guess my way to the right visual answer instead of the right vocabulary. That's the actual skill hiding in weird feedback. Clients aren't trained in design vocabulary. "More Tuesday," "give it more zhuzh," "less crunchy" — all real feedback I've received, all pointing at something legitimate the client can feel but can't name. The translation layer is the job. Dismissing weird feedback as the client not knowing what they want misses that they usually do know — they just don't have our vocabulary for it. Drop yours below. Bonus points if you eventually cracked what it meant.