A freelance writer can have a clean portfolio and still be a bad fit for your team.
I say that as someone who has been on several sides of the table, writing for B2B software brands like HubSpot, Zapier, Softr, Vimeo, and CoSchedule.
Through the years, I’ve had engagements that worked beautifully and others that got messy because expectations were unclear from the start.
Every question you ask a freelance writer before hiring them boils down to this one: Would working with this person make your content operation lighter, or heavier?
A writer who understands the brief, asks sharp questions, explains their decisions, and meets deadlines without chasing makes your job easier every week. A writer who needs constant direction, gets touchy about feedback, or goes quiet under pressure adds work you didn’t have before you hired them.
This guide will help you tell the difference before you sign a contract and onboard them.
Quick answer: How do you evaluate a freelance writer?
Evaluate a freelance writer by looking at their relevant samples, process, research depth, product understanding, communication style, and ability to work from a brief.
For SaaS content, pay special attention to whether the writer understands buyer intent, product positioning, and the job each article needs to do.
A generalist can write a decent “what is” article. But if you need comparison pages, buyer guides, product-led SEO posts, or content tied to pipeline, you need stronger evaluation criteria.
Start with the job you need the writer to do
Before you judge the writer, define the work.
Are you hiring a writer for:
- SEO blog posts?
- Bottom-funnel content?
- Product-led tutorials?
- LinkedIn content or thought leadership?
- Content refreshes?
- Buyer guides?
Each type of content needs a different skill set.
A writer who is great at founder-led essays might struggle with something like “best customer onboarding software.” While a strong SEO writer might know how to rank a post, they still avoid mentioning the product until the CTA.
So, start by asking: what does success look like for this article?
For example, if the piece is “HubSpot vs Salesforce,” the writer needs to understand why readers are comparing the two solutions, the pricing context, CRM workflows, and how to be fair with a clear POV.
If the piece is “how to automate lead routing,” the writer needs to understand the workflow, the pain behind it, and where your product naturally fits.
Do not evaluate every writer against a vague idea of “good writing.” Evaluate them against the actual work you need done.
Review samples for thinking, not just polish
Portfolio samples are useful, but they can mislead you.
A sample may have gone through three rounds of editing. The writer may have had a detailed outline from an in-house or freelance strategist.
Or the article may look polished because the brand has a strong editorial team behind it.
So, when you review samples, look for signs of thinking.
Check if the article:
- Matches the search intent
- Answers the question the reader came with
- Explains tradeoffs
- Includes examples
- Helps the reader make a decision
- Has a structure that makes sense, or if it feels like a keyword tool arranged the headings
For SaaS content, I’d also look for product judgment.
If the writer is covering a tool or category, do they understand who the product is for? Can they explain where it fits and where it does not? Can they mention the product without turning the article into a brochure?
Your product should not appear for the first time in the CTA. But it also should not hijack the article like an overexcited sales rep.
Good content teaches first. Then it shows where the product fits.
Ask them to explain one sample
A useful evaluation question is:
“Can you walk me through how you approached this piece?”
The answer will tell you a lot.
Here’s what that difference sounds like in practice. Let’s say you asked about a project management piece.
A strong answer might sound along the lines of:
“The reader searching this term already knows they need PM software. They’re comparing options, not learning what project management is.
So I skipped the definition section that most competitors open with and went straight into the comparison.
I put the client’s product first and explain why. I didn’t say our product was the best at everything; instead, I focused on the areas where we’re truly better than the others.
I added a ‘best for’ line under each tool because most competing articles list features without saying who the feature is actually for.
The CTA points to a free trial instead of a demo, since this is a lower-commitment buying stage than someone searching ‘PM software demo.’”
On the other hand, a weak answer would be something like “It’s about choosing project management software. I covered the top tools, their features, and pricing, then wrote a conclusion comparing them.”
The first answer shows reasoning at every decision point: structure, placement, framing, and CTA. That’s what you’re listening for. Not whether they can describe the topic, but whether they can tell you why the page is built the way it’s built.
The second answer was a summary of the article. It tells you nothing about the decisions behind it.
Evaluate their process before the draft exists
You might already get some answers about a writer’s process when you ask them to explain a sample. But you can take it a step further by asking them to explain their typical process.
Ask questions like:
- What do you need before starting?
- How do you evaluate search intent?
- How do you use product docs or SME input?
- Do you create an outline first?
- How do you handle feedback?
- What makes a draft publish-ready for you?
The best freelance writers usually ask good questions early.
They want to know the audience, goal, keyword, product angle, internal links, competitors, examples, and CTA. They may ask for customer calls, sales notes, product access, or SME input.
That is not them being difficult. Instead, they want to avoid sending you a 2,000-word problem with a Google Doc link.
Use a paid trial piece
I’m not a fan of unpaid test articles.
If you want to properly evaluate a writer, give them a real paid trial piece. Not a fake assignment. Not a random “write 500 words about productivity” task. Use an actual topic from your backlog.
A good trial tests the working relationship, not just the writing.
Here’s a simple structure:
| What to test | What to look for |
| Brief understanding | Did they understand the article’s job? |
| Outline quality | Did the structure make sense before drafting? |
| Research depth | Did they go beyond the obvious SERP points? |
| Product understanding | Did they use product context naturally? |
| Communication | Did they ask useful questions and flag gaps? |
| Draft quality | Did the article need tweaks or a rescue mission? |
| Feedback handling | Did revisions improve the piece without drama? |
The trial should answer one question: would working with this writer make your content operation lighter?
If the answer is yes, keep talking.
Test reliability, not just quality
A trial piece with no deadline pressure tells you how someone writes. It does not tell you what happens when a deadline moves up or feedback lands on a Friday.
Quality problems show up in the draft. Reliability problems show up everywhere else: the Slack message that goes unanswered for two days, the “almost done” update that arrives an hour past deadline, the writer who goes quiet the moment you ask for a faster turnaround.
Build this into the trial on purpose.
Ask for the draft a day earlier than you actually need it. Send feedback at an inconvenient time and watch how fast the revision comes back.
Ask directly: “What’s your turnaround on a same-week revision if I need one?”
A writer who gives you a real number, even an honest “that depends,” is more useful than one who says yes to everything. The ones who say yes to everything are usually the ones who disappear when the deadline actually arrives.
Red flags during the trial
Some warning signs won’t show up in a past portfolio. You’ll only catch them by watching someone work in real time.
Here are some that come up often:
They can’t explain their own structural choices. If you ask why a section is ordered the way it is and get a shrug or a restated summary of the topic, that’s a sign the structure came from a template rather than a decision.
They get defensive about feedback. Not pushback, that’s healthy. Defensiveness. A writer who explains their reasoning when you question a choice is engaging. One who treats every note as an attack is telling you what working together long-term will feel like.
They ask zero questions before starting. A writer who takes a one-line brief and disappears for three days usually comes back with a draft that needs a rebuild. The good ones ask about audience, competitors, product angle, or internal links before they write a word.
They oversell speed. “I can turn this around in 24 hours” on a piece that needs real research is a crimson-red flag. Being fast and unprepared is worse than being properly paced.
Need a writer who can take this from brief to publish-ready?
Your evaluation should answer the same question you started with: Does this person make the work lighter or heavier?
Run it. Watch how the writer works, not just what they hand in. If the operation feels lighter by the end of it, you’ve found your writer.
If you’re evaluating writers because your backlog is full and your team is stretched, that’s the exact gap I work in.
I write bottom-funnel content for B2B SaaS companies like HubSpot, Softr, Zapier, etc—the content that shows up when buyers are already deciding.
You bring the topic and product context. I bring the research, the structure, and a draft that’s close to publish-ready on the first pass.
Book a 30-minute call to see if it’s a fit.
