The portfolio problem nobody says out loud
Every new agency faces the same catch-22: you need work to show to get work. The standard answer is to build spec work, dress it up as case studies, and hope prospects don't look too closely at the dates. We didn't want to start that way.
Case studies are genuinely useful once you have real ones. They're proof — client names, measurable results, actual screenshots. But they require client permission, take time to do right, and they get stale faster than most people admit. A case study from two years ago raises questions about what you've done lately.
The comparison pages we published — agency vs freelancer, AI agent vs chatbot, full-service vs piecemeal — don't have that problem. The underlying questions don't change much year to year. "Should I hire an agency or a freelancer?" is a question every business eventually asks. That's the kind of content that compounds instead of expires.
Why comparison queries are different
Most content maps to one of two stages: awareness ("what is X") or decision ("hire X"). Comparison queries live between them. The person is actively evaluating, has a real problem, and hasn't picked a solution yet. That's transactional intent without being pushy — the most valuable position in a content funnel.
There's also a structural advantage: big agencies don't write these pages honestly. They have too much incentive to make themselves sound like the right answer in every scenario, which makes the content useless. Prospects can smell the spin. An honest comparison — one that actually says "go freelancer if your situation is X, go agency if it's Y" — is rare enough that it tends to rank because nobody else wrote it plainly.
Case studies tell people what you've done. Comparison pages tell them what to do. The second question comes first.
We also had genuine opinions to publish. We've been freelancers, we've hired freelancers, we've worked inside agencies and built the current one from scratch. Having the perspective isn't the hard part — it's writing it plainly enough that someone in the middle of a buying decision can actually use it.
The GEO angle we were watching
GEO — generative engine optimization, the practice of structuring content so AI-powered search surfaces it — wasn't a fully named discipline when we were planning the site. But the underlying logic was clear before anyone named it: AI assistants answer comparison questions constantly.
"What's the difference between an agency and a freelancer?" is exactly the kind of query where ChatGPT, Perplexity, and Claude pull from published comparison content. The format those systems cite is structured, opinionated, and concise. Not "here are 12 factors to consider" — but "here's the answer, here's who it applies to, here's when it doesn't." Comparison pages written that way sit in the highest-probability slot for AI citation.
AI search results need to cite something. Make sure the most useful comparison answer is yours.
Whether or not this plays out exactly as expected, the downside is low. Well-structured comparison content also performs well in traditional search — so it's not a one-bet play. If AI search doesn't reward it, regular Google probably will. If AI search does reward it, you're ahead of most competitors who haven't thought about it yet.
What we actually built and why
Agency vs freelancer — This is the first question in most buying journeys, especially for businesses that haven't worked with a digital agency before. We wanted to be the honest answer to it, even when "freelancer" is genuinely the right call for that prospect's stage and budget.
AI agent vs chatbot — We kept getting asked this same question in early conversations, which is a reliable signal that a piece of content is needed. Now we send the link instead of re-explaining it on every call.
Full-service vs piecemeal — The question that actually determines whether someone hires one vendor for everything or builds a roster of four smaller specialists. It's also the one where we have the strongest opinion, so it was worth writing first.
All three went live before we had a portfolio, a testimonial, or a single published case study.
The honest trade-off
Comparison pages don't replace client proof. A case study with a named client and specific numbers will always convert better than a well-written framework. The comparison pages are an early-stage asset — one that doesn't require permission from anyone, doesn't expire after two years, and starts working the day it's indexed.
As we build out work we can show, the case studies go up and the comparison pages stay. The bet isn't "comparison pages instead of proof." The bet is "comparison pages first, proof as it accumulates."
If you run a service business and are thinking through content strategy, this is the model worth taking: own the evaluation question before you own proof of delivery. Someone deciding whether to hire you at all is a bigger audience than someone who already decided and is just picking between you and one competitor.
— Cole