u/Agreeable-Scratch999

I don't usually post personal things online, especially not like this. But I've reached a point where I'm willing to put myself out there and ask for help.

I got laid off a couple of months ago, and despite applying every day, reaching out to people, and trying just about everything I can think of, I'm running out of options.

I'm not from Canada, but I'm posting here because I've primarily worked with North American agencies and clients for the past 4–5 years, including Canadian agencies. I've honestly had some of my best working experiences with North American teams, so I figured this might be a good place to reach out.

I've spent more than 8 years writing for SaaS companies, ecommerce brands, and agencies. I've been a Content Writer, Content Manager, and Head of Content. I've built SEO content strategies, managed writers, edited thousands of articles, created content briefs, worked directly with clients, and helped companies grow their organic traffic.

More recently, I've also been working on GEO/AEO and writing content designed to perform well in AI search.

I'm not saying I'm the best writer in the world. There are plenty of incredibly talented people out there. But I know the quality of my work, the ownership I take, and the results I've helped clients achieve.

That's what makes this situation so difficult.

I'm not looking for someone to hand me a job. I'm looking for a chance to get back to doing what I'm good at.

If you know of a company or agency hiring for content writing, content management, SEO content, or content strategy, I'd genuinely appreciate a referral, introduction, or even a lead I can follow up on.

And if you can't help directly, an upvote or share could help this reach someone who can.

If you've been through something similar, I'd also love to know what actually worked for you.

Thank you for reading.

P.S. My last full-time role paid quite well. I'm mentioning that because I don't want this post to make it seem like I'm new to the industry or struggling because I lack experience. I had a career I was genuinely proud of. I'm simply in a situation I never expected to be in, and I'm trying everything I can to get back to work.

I don't usually post personal things online, especially not like this. But I've reached a point where I'm willing to put myself out there and ask for help.

I got laid off a couple of months ago, and despite applying every day, reaching out to people, and trying just about everything I can think of, I'm running out of options.

I'm not from Canada, but I'm posting here because I've primarily worked with North American agencies and clients for the past 4–5 years, including Canadian agencies. I've honestly had some of my best working experiences with North American teams, so I figured this might be a good place to reach out.

I've spent more than 8 years writing for SaaS companies, ecommerce brands, and agencies. I've been a Content Writer, Content Manager, and Head of Content. I've built SEO content strategies, managed writers, edited thousands of articles, created content briefs, worked directly with clients, and helped companies grow their organic traffic.

More recently, I've also been working on GEO/AEO and writing content designed to perform well in AI search.

I'm not saying I'm the best writer in the world. There are plenty of incredibly talented people out there. But I know the quality of my work, the ownership I take, and the results I've helped clients achieve.

That's what makes this situation so difficult.

I'm not looking for someone to hand me a job. I'm looking for a chance to get back to doing what I'm good at.

If you know of a company or agency hiring for content writing, content management, SEO content, or content strategy, I'd genuinely appreciate a referral, introduction, or even a lead I can follow up on.

And if you can't help directly, an upvote or share could help this reach someone who can.

If you've been through something similar, I'd also love to know what actually worked for you.

Thank you for reading.

P.S. My last full-time role paid quite well. I'm mentioning that because I don't want this post to make it seem like I'm new to the industry or struggling because I lack experience. I had a career I was genuinely proud of. I'm simply in a situation I never expected to be in, and I'm trying everything I can to get back to work.

I don't usually post personal things online, especially not like this. But I've reached a point where I'm willing to put myself out there and ask for help.

I got laid off a couple of months ago, and despite applying every day, reaching out to people, and trying just about everything I can think of, I'm running out of options.

I'm not from Canada, but I'm posting here because I've primarily worked with North American agencies and clients for the past 4–5 years, including Canadian agencies. I've honestly had some of my best working experiences with North American teams, so I figured this might be a good place to reach out.

I've spent more than 8 years writing for SaaS companies, ecommerce brands, and agencies. I've been a Content Writer, Content Manager, and Head of Content. I've built SEO content strategies, managed writers, edited thousands of articles, created content briefs, worked directly with clients, and helped companies grow their organic traffic.

More recently, I've also been working on GEO/AEO and writing content designed to perform well in AI search.

I'm not saying I'm the best writer in the world. There are plenty of incredibly talented people out there. But I know the quality of my work, the ownership I take, and the results I've helped clients achieve.

That's what makes this situation so difficult.

I'm not looking for someone to hand me a job. I'm looking for a chance to get back to doing what I'm good at.

If you know of a company or agency hiring for content writing, content management, SEO content, or content strategy, I'd genuinely appreciate a referral, introduction, or even a lead I can follow up on.

And if you can't help directly, an upvote or share could help this reach someone who can.

If you've been through something similar, I'd also love to know what actually worked for you.

Thank you for reading.

P.S. My last full-time role paid quite well. I'm mentioning that because I don't want this post to make it seem like I'm new to the industry or struggling because I lack experience. I had a career I was genuinely proud of. I'm simply in a situation I never expected to be in, and I'm trying everything I can to get back to work.

I don't usually post personal things online, especially not like this. But I've reached a point where I'm willing to put myself out there and ask for help.

I got laid off a couple of months ago, and despite applying every day, reaching out to people, and trying just about everything I can think of, I'm running out of options.

I'm not from Canada, but I'm posting here because I've primarily worked with North American agencies and clients for the past 4–5 years, including Canadian agencies. I've honestly had some of my best working experiences with North American teams, so I figured this might be a good place to reach out.

I've spent more than 8 years writing for SaaS companies, ecommerce brands, and agencies. I've been a Content Writer, Content Manager, and Head of Content. I've built SEO content strategies, managed writers, edited thousands of articles, created content briefs, worked directly with clients, and helped companies grow their organic traffic.

More recently, I've also been working on GEO/AEO and writing content designed to perform well in AI search.

I'm not saying I'm the best writer in the world. There are plenty of incredibly talented people out there. But I know the quality of my work, the ownership I take, and the results I've helped clients achieve.

That's what makes this situation so difficult.

I'm not looking for someone to hand me a job. I'm looking for a chance to get back to doing what I'm good at.

If you know of a company or agency hiring for content writing, content management, SEO content, or content strategy, I'd genuinely appreciate a referral, introduction, or even a lead I can follow up on.

And if you can't help directly, an upvote or share could help this reach someone who can.

If you've been through something similar, I'd also love to know what actually worked for you.

Thank you for reading.

P.S. My last full-time role paid quite well. I'm mentioning that because I don't want this post to make it seem like I'm new to the industry or struggling because I lack experience. I had a career I was genuinely proud of. I'm simply in a situation I never expected to be in, and I'm trying everything I can to get back to work.

I don't usually post personal things online, especially not like this. But I've reached a point where I'm willing to put myself out there and ask for help.

I got laid off a couple of months ago, and despite applying every day, reaching out to people, and trying just about everything I can think of, I'm running out of options.

I'm not from Canada, but I'm posting here because I've primarily worked with North American agencies and clients for the past 4–5 years, including Canadian agencies. I've honestly had some of my best working experiences with North American teams, so I figured this might be a good place to reach out.

I've spent more than 8 years writing for SaaS companies, ecommerce brands, and agencies. I've been a Content Writer, Content Manager, and Head of Content. I've built SEO content strategies, managed writers, edited thousands of articles, created content briefs, worked directly with clients, and helped companies grow their organic traffic.

More recently, I've also been working on GEO/AEO and writing content designed to perform well in AI search.

I'm not saying I'm the best writer in the world. There are plenty of incredibly talented people out there. But I know the quality of my work, the ownership I take, and the results I've helped clients achieve.

That's what makes this situation so difficult.

I'm not looking for someone to hand me a job. I'm looking for a chance to get back to doing what I'm good at.

If you know of a company or agency hiring for content writing, content management, SEO content, or content strategy, I'd genuinely appreciate a referral, introduction, or even a lead I can follow up on.

And if you can't help directly, an upvote or share could help this reach someone who can.

If you've been through something similar, I'd also love to know what actually worked for you.

Thank you for reading.

P.S. My last full-time role paid quite well. I'm mentioning that because I don't want this post to make it seem like I'm new to the industry or struggling because I lack experience. I had a career I was genuinely proud of. I'm simply in a situation I never expected to be in, and I'm trying everything I can to get back to work.

Drop your blog URL below. I'll take a look at your content strategy and point out one opportunity I'd prioritize if I were responsible for growing your organic traffic.

Could be content gaps, search intent, BOFU opportunities, internal linking, competitor gaps, or something else entirely.

No generic "write more content" advice. If I spot something, I'll tell you exactly what I'd do and why.

If I had a $ for every time someone said "SEO is dead," I won't be selling my content strategy and writing services. I'd be one rich stay at-home cat mom. What about you?

I’ve been in the content game long enough to watch people go from obsessing over exact-match keywords and stuffing focus keywords into every heading, to the AI content boom, and now the shift towards AEO/GEO and being visible across search, AI answers, Reddit, and everywhere else people research products.

I’ve written for companies including TxtCart, Campaign Monitor and HeatmapAI, and if I were starting a SaaS blog from scratch today, this is where I’d put my first 90 days.

Days 1–30: answer the questions your ICP is already asking

Before doing much keyword research, I’d spend time collecting questions. Go through Reddit, sales calls, demos, support tickets, customer interviews, G2 and competitor reviews, founder conversations, community posts, and anywhere else your potential customers are talking about the problem.

I’d put every useful question into one big database. What are they trying to accomplish? What have they already tried? What keeps going wrong? What are they worried about before buying? What do they compare?

Then I’d start turning those questions into useful resources. Some will be blog posts, but some might make more sense as product pages, use-case pages, guides, calculators, templates or other resources. The format should follow the question, not the other way around.

You’ll also start seeing patterns in those questions. Those patterns are incredibly useful because they tell you what your customers care about in their own words.

Days 31–60: go hard on alternatives

https://preview.redd.it/39d3us66mzih1.png?width=336&format=png&auto=webp&s=2cf10c60ec51c4bf971f629174b0bf15a3b9c860

This is where I’d start getting much more commercial.

Find the products your ICP already uses, researches, complains about, or is considering replacing. Then build genuinely useful “[Competitor] alternatives” pages around them. There’s a reason these pages exist. Someone searching for “X alternatives” has already identified a problem and is now looking at what else they could buy.

Don't make every page “10 alternatives, and obviously our product is #1.” Explain who each option is good for, where it falls short, pricing, important features, integrations, and what kind of buyer should consider it.

And don't limit yourself to the biggest competitors. Look at the tools your customers are actually switching from, tools that are too expensive for a certain segment, tools that don't serve a particular use case well, or older products people are actively looking to replace.

Pro tip: Reddit is part of this strategy.

People don't only search Google for alternatives. They ask other people. Search Reddit for things like “Klaviyo alternatives, “what should I use instead of [competitor]," “[competitor] is too expensive," “[competitor] vs," and variations around the problems your product solves.

If people are already asking those questions, you want to be part of that conversation. And I don't mean dropping your link under every thread. That's the fastest way to get ignored. Read the thread, understand why they're looking for an alternative, and contribute something genuinely useful. If your product is relevant, mention it naturally. If it isn't, don't.

Days 61–90: get into comparison searches that already have demand

Here's the problem with comparison content for a new SaaS: nobody is searching for “YourBrand vs Competitor” yet.

So don't wait for them to.

Find two direct competitors in your category that your ICP already compares. For example, if you’re building an email marketing platform, you might find people searching for Mailchimp vs Brevo, Klaviyo vs Omnisend, or ActiveCampaign vs HubSpot Marketing Hub.

Create the comparison those people are already looking for. Go beyond a feature table. Look at pricing, core features, integrations, ease of use, limitations, ideal customer, and the situations where one genuinely makes more sense than the other.

Then find the gap. Maybe both products are too expensive for a certain type of customer. Maybe neither handles a particular use case well. Maybe your product takes a completely different approach. Maybe you're better suited to a specific industry or company size.

That's where you introduce your product. The point isn't to hijack the comparison and declare yourself the winner. It's to put your product into a buying conversation that already exists.

I’ve been in the content game long enough to watch people go from obsessing over exact-match keywords and stuffing focus keywords into every heading, to the AI content boom, and now the shift towards AEO/GEO and being visible across search, AI answers, Reddit, and everywhere else people research products.

I’ve written for companies including TxtCart, Campaign Monitor and HeatmapAI, and if I were starting a SaaS blog from scratch today, this is where I’d put my first 90 days.

Days 1–30: answer the questions your ICP is already asking

Before doing much keyword research, I’d spend time collecting questions. Go through Reddit, sales calls, demos, support tickets, customer interviews, G2 and competitor reviews, founder conversations, community posts, and anywhere else your potential customers are talking about the problem.

I’d put every useful question into one big database. What are they trying to accomplish? What have they already tried? What keeps going wrong? What are they worried about before buying? What do they compare?

Then I’d start turning those questions into useful resources. Some will be blog posts, but some might make more sense as product pages, use-case pages, guides, calculators, templates or other resources. The format should follow the question, not the other way around.

You’ll also start seeing patterns in those questions. Those patterns are incredibly useful because they tell you what your customers care about in their own words.

Days 31–60: go hard on alternatives

https://preview.redd.it/qotmpvwfmzih1.png?width=336&format=png&auto=webp&s=614c5a9f5b72af5d370f8bf47fac01aa04014668

This is where I’d start getting much more commercial.

Find the products your ICP already uses, researches, complains about, or is considering replacing. Then build genuinely useful “[Competitor] alternatives” pages around them. There’s a reason these pages exist. Someone searching for “X alternatives” has already identified a problem and is now looking at what else they could buy.

Don't make every page “10 alternatives, and obviously our product is #1.” Explain who each option is good for, where it falls short, pricing, important features, integrations, and what kind of buyer should consider it.

And don't limit yourself to the biggest competitors. Look at the tools your customers are actually switching from, tools that are too expensive for a certain segment, tools that don't serve a particular use case well, or older products people are actively looking to replace.

Pro tip: Reddit is part of this strategy.

People don't only search Google for alternatives. They ask other people. Search Reddit for things like “Klaviyo alternatives, “what should I use instead of [competitor]," “[competitor] is too expensive," “[competitor] vs," and variations around the problems your product solves.

If people are already asking those questions, you want to be part of that conversation. And I don't mean dropping your link under every thread. That's the fastest way to get ignored. Read the thread, understand why they're looking for an alternative, and contribute something genuinely useful. If your product is relevant, mention it naturally. If it isn't, don't.

Days 61–90: get into comparison searches that already have demand

Here's the problem with comparison content for a new SaaS: nobody is searching for “YourBrand vs Competitor” yet.

So don't wait for them to.

Find two direct competitors in your category that your ICP already compares. For example, if you’re building an email marketing platform, you might find people searching for Mailchimp vs Brevo, Klaviyo vs Omnisend, or ActiveCampaign vs HubSpot Marketing Hub.

Create the comparison those people are already looking for. Go beyond a feature table. Look at pricing, core features, integrations, ease of use, limitations, ideal customer, and the situations where one genuinely makes more sense than the other.

Then find the gap. Maybe both products are too expensive for a certain type of customer. Maybe neither handles a particular use case well. Maybe your product takes a completely different approach. Maybe you're better suited to a specific industry or company size.

That's where you introduce your product. The point isn't to hijack the comparison and declare yourself the winner. It's to put your product into a buying conversation that already exists.

I never thought I'd be making a post like this, but here we are.

I've been looking for my next role after being laid off a couple of months ago. I've been applying, reaching out directly, and trying different approaches, but I'm realizing that I don't want to keep putting all my energy into finding another full-time role.

I've finally made the decision to move more seriously into freelance and project-based work instead.

A big reason is honestly pretty simple: whenever I was working full-time, by the time I finished work, I didn't have much energy left to build my own presence, look for clients, or work on my own career outside of my job. I don't want to fall into that cycle again.

For context, I've spent 8+ years working in content across SaaS, ecommerce, and agencies. I've been a Content Writer, Content Manager, and Head of Content. I've built SEO content strategies, managed writers, edited thousands of articles, created content briefs, worked directly with clients, and worked on content for organic search as well as GEO/AEO and AI search.

I've recently started using Reddit as one part of my outreach, and it's actually led to some interesting conversations. That got me wondering where everyone else is finding freelance or project-based work these days.

Are you finding clients through Reddit, LinkedIn, cold outreach, communities, referrals, agency directories, or somewhere else?

And if you've made the move from full-time work to freelancing, what actually worked for you? I'm especially interested in things that led to real conversations and projects rather than just sending hundreds of applications.

I'd genuinely love to hear what's working for people right now.

I never thought I'd be making a post like this, but here we are.

I've been looking for my next role after being laid off a couple of months ago. I've been applying, reaching out directly, and trying different approaches, but I'm realizing that I don't want to keep putting all my energy into finding another full-time role.

I've finally made the decision to move more seriously into freelance and project-based work instead.

A big reason is honestly pretty simple: whenever I was working full-time, by the time I finished work, I didn't have much energy left to build my own presence, look for clients, or work on my own career outside of my job. I don't want to fall into that cycle again.

For context, I've spent 8+ years working in content across SaaS, ecommerce, and agencies. I've been a Content Writer, Content Manager, and Head of Content. I've built SEO content strategies, managed writers, edited thousands of articles, created content briefs, worked directly with clients, and worked on content for organic search as well as GEO/AEO and AI search.

I've recently started using Reddit as one part of my outreach, and it's actually led to some interesting conversations. That got me wondering where everyone else is finding freelance or project-based work these days.

Are you finding clients through Reddit, LinkedIn, cold outreach, communities, referrals, agency directories, or somewhere else?

And if you've made the move from full-time work to freelancing, what actually worked for you? I'm especially interested in things that led to real conversations and projects rather than just sending hundreds of applications.

I'd genuinely love to hear what's working for people right now.

I've been noticing a pattern in SaaS communities lately: a lot of founders have clearly put serious work into building the product, but then hit a completely different problem: figuring out the marketing side. And that's completely understandable. Building the product and figuring out how to get the right people to find it are two very different problems.

I've spent 10+ years working in content, and if I were starting the content side of a SaaS from scratch, I wouldn't begin with "let's publish 12 blog posts this month." I'd first figure out what is actually worth publishing, then make sure every piece has a reason to exist.

First things first, I wouldn't wait before thinking about SEO. I'm not an SEO specialist, but organic search takes time to build, so I'd rather have the groundwork in place early than decide six months later that we should probably start publishing.

For the blog, if you're not sure how to go about it, here's what I'd do.

1. First, figure out what is actually worth writing

Your keyword strategy should lead the way, but if you don't have one yet, I'd start much closer to the customer. Talk to prospects who are considering your product. What are they asking you? What are they unsure about? What are they comparing? What problem are they trying to solve before they get to your product?

Those questions are content opportunities.

One sprint I'd almost blindly look at is alternatives and comparison content. Got competitors? Those businesses are constantly losing customers, and some of those customers are actively looking for better options. If you're a project management SaaS, for example, I'd look at things like "Asana alternatives," "Asana vs X," "Asana alternatives for small teams," "Asana alternatives for agencies," pricing alternatives, migration questions, feature comparisons, and so on.

And I wouldn't stop at the first "alternatives" article. Map the whole decision around that competitor. What makes someone look for an alternative? What are they unhappy with? What are they trying to do that the competitor doesn't handle well? What questions do they have before switching? What could stop them from switching?

Now you're not just producing a list of keywords. You're learning about the actual buying decision. That can influence your comparison pages, landing pages, positioning, CTAs, product messaging, and even what you decide to improve in the product.

That's the kind of content work I'd want to do before sitting down and saying, "Okay, we need 12 blog posts this month."

2. Once you've picked the topic, use this checklist for every article

This is where I'd stop worrying about AEO, GEO, schema and every other new acronym for a minute. Get the basics right first. A lot of content isn't failing because it isn't "optimized" enough. It's failing because the reader has to work too hard to get something that should have been obvious.

Answer the actual question immediately. If someone searches for "cart recovery strategies," don't spend the first 400 words explaining why abandoned carts are bad for ecommerce. They know. That's why they're searching for cart recovery strategies. Get into the strategies. Give them the answer first, then add the context, examples and reasoning where they're actually useful.

Same logic with almost any query. Someone searching "how to migrate from X to Y" doesn't need a history lesson on why migrations matter. Someone searching "X alternatives" already knows what X is. Don't explain the problem they've already told you they have. Solve it.

Add a TL;DR that actually answers the question. I like TL;DRs, especially for longer pieces. But don't use them as a vague summary of everything the article covers. Make the TL;DR answer the primary question. If the article is about cart recovery strategies, the TL;DR should give me the main strategies. If it's about choosing between two tools, give me the key differences and who each one is best for. If it's "how to fix X," give me the key steps.

There's a strange fear that if you give people the answer upfront, they won't read the rest. That's fine. The point isn't to force someone to consume 2,500 words. If they got exactly what they needed from your TL;DR in 30 seconds, you did your job. If they want the examples, data, screenshots, reasoning or deeper explanation, they'll keep reading.

Look at the first 10 results and find what they're missing. This is where I think the AEO/GEO conversation gets interesting, but I'd put it after the fundamentals. Look at the pages already ranking and ask: what would make my version more useful?

Maybe all 10 have the same generic list. Maybe nobody has actually tested the recommendations. Maybe everyone recommends the same tools but nobody explains which one works for different use cases. Maybe they're all making the same claim without showing the data. Maybe nobody has included screenshots. Maybe the answers are technically correct but completely impractical.

That's your opening. If the first 10 results say the same thing, don't become the 11th result saying the same thing. Add something: original research, customer data, screenshots, experiments, examples, expert input, a useful comparison table, first-hand experience, a framework, or simply a better explanation.

The value doesn't have to be groundbreaking. Sometimes it's just answering the question everyone else skipped.

Make it easy to skim. Don't avoid tables, lists or short sections because you've heard that structured content looks like AI. Who cares? If a table makes the information easier to understand, use a table. If I'm comparing five products, show me the important differences before making me read five 500-word sections. If there are seven steps, show me the seven steps. If there are three options and the right choice depends on the situation, make that easy to see.

You're writing for a person who has somewhere else to be. Make their job easier.

Don't be afraid to talk about your product. This is where companies usually go wrong in one of two directions. They either turn every article into a sales pitch, or they're so scared of being promotional that they won't mention their own product even when it's directly relevant.

Talk about your product when it actually helps answer the question. If the article is discussing a problem your product solves, mention the specific feature that solves it. If a customer got a great result from that feature, show it. If you've got a case study that proves the point, use it.

A random "Try our platform" CTA at the bottom isn't very persuasive. "Here's the problem we just discussed. Here's how our product handles it. Here's what happened when a customer used it." That's a much stronger product mention. A product plug without backing doesn't go very far.

Use case studies inside the article. If you have case studies, don't hide all of them on your case study page. Turn relevant ones into in-content callouts or cards and put them next to the section where they're actually useful.

For example, if you're explaining how a SaaS improved activation rates, and you have a customer who improved activation using that exact feature, that's where I'd surface the case study. Not five screens later.

Technically, these can just be HTML callout blocks or cards. They don't need to be some crazy interactive experience. The important part is the placement. The reader should see the proof at the exact moment they're thinking, "Okay, but does this actually work?"

Add FAQs for the questions that remain. Don't add an FAQ because someone told you every article needs one. Use it to answer the questions that naturally remain after the main article.

I'd pull those questions from real places: search results, Reddit, sales calls, customer support, reviews, comments, and questions prospects keep asking. The goal isn't to squeeze five more keywords onto the page. It's to remove the questions still sitting in the reader's head.

Internal link like you're helping the reader, not checking a box. Don't add three internal links because your SEO checklist says you need three. Add the link because the reader has a reason to click it.

If I'm reading about one part of a problem and you have another article that answers the question I'm likely to have next, link to it. If you're talking about a category and have a relevant comparison page, link to it. If you've just explained a problem and have a guide that shows me how to solve the next stage, link to it.

Internal links become much more useful when you think about the reader's next question, rather than the number of links you need to place.

Give the reader a logical next step. Before publishing, I'd ask: someone just finished this article. What should they do now?

Maybe it's another article. Maybe it's a comparison page. Maybe it's a case study. Maybe it's a product feature. Maybe it's a demo or signup. It depends on the topic and where that reader is in the buying process.

That's also why I don't love one generic CTA slapped onto the bottom of every article. If the relevant next step becomes obvious halfway through the article, put it there. Don't make the reader finish the article, find the navigation, hunt down your product page and figure out the connection themselves.

Finally, read it like a customer, not a content marketer.

Forget the word count. Forget whether you hit the "ideal" number of headings. Forget whether you've used the keyword enough times. Forget whether your article looks like the pages ranking above you.

Read it as someone who actually has the problem. Did I get my answer quickly? Did I learn something? Did I get something I can actually use? Did you show me evidence instead of making a bunch of claims? Was it easy to get through? Did I understand what to do next?

And most importantly: did this make me trust this company more?

If yes, you're already doing a lot right.

I'd much rather publish something genuinely useful, with clear thinking, real examples and a sensible next step than spend hours trying to reverse-engineer whatever the latest AEO/GEO checklist says we're supposed to do.

I've been noticing a pattern in SaaS communities lately: a lot of founders have clearly put serious work into building the product, but then hit a completely different problem: figuring out the marketing side. And that's completely understandable. Building the product and figuring out how to get the right people to find it are two very different problems.

I've spent 10+ years working in content, and if I were starting the content side of a SaaS from scratch, I wouldn't begin with "let's publish 12 blog posts this month." I'd first figure out what is actually worth publishing, then make sure every piece has a reason to exist.

First things first, I wouldn't wait before thinking about SEO. I'm not an SEO specialist, but organic search takes time to build, so I'd rather have the groundwork in place early than decide six months later that we should probably start publishing.

For the blog, if you're not sure how to go about it, here's what I'd do.

1. First, figure out what is actually worth writing

Your keyword strategy should lead the way, but if you don't have one yet, I'd start much closer to the customer. Talk to prospects who are considering your product. What are they asking you? What are they unsure about? What are they comparing? What problem are they trying to solve before they get to your product?

Those questions are content opportunities.

One sprint I'd almost blindly look at is alternatives and comparison content. Got competitors? Those businesses are constantly losing customers, and some of those customers are actively looking for better options. If you're a project management SaaS, for example, I'd look at things like "Asana alternatives," "Asana vs X," "Asana alternatives for small teams," "Asana alternatives for agencies," pricing alternatives, migration questions, feature comparisons, and so on.

And I wouldn't stop at the first "alternatives" article. Map the whole decision around that competitor. What makes someone look for an alternative? What are they unhappy with? What are they trying to do that the competitor doesn't handle well? What questions do they have before switching? What could stop them from switching?

Now you're not just producing a list of keywords. You're learning about the actual buying decision. That can influence your comparison pages, landing pages, positioning, CTAs, product messaging, and even what you decide to improve in the product.

That's the kind of content work I'd want to do before sitting down and saying, "Okay, we need 12 blog posts this month."

2. Once you've picked the topic, use this checklist for every article

This is where I'd stop worrying about AEO, GEO, schema and every other new acronym for a minute. Get the basics right first. A lot of content isn't failing because it isn't "optimized" enough. It's failing because the reader has to work too hard to get something that should have been obvious.

Answer the actual question immediately. If someone searches for "cart recovery strategies," don't spend the first 400 words explaining why abandoned carts are bad for ecommerce. They know. That's why they're searching for cart recovery strategies. Get into the strategies. Give them the answer first, then add the context, examples and reasoning where they're actually useful.

Same logic with almost any query. Someone searching "how to migrate from X to Y" doesn't need a history lesson on why migrations matter. Someone searching "X alternatives" already knows what X is. Don't explain the problem they've already told you they have. Solve it.

Add a TL;DR that actually answers the question. I like TL;DRs, especially for longer pieces. But don't use them as a vague summary of everything the article covers. Make the TL;DR answer the primary question. If the article is about cart recovery strategies, the TL;DR should give me the main strategies. If it's about choosing between two tools, give me the key differences and who each one is best for. If it's "how to fix X," give me the key steps.

There's a strange fear that if you give people the answer upfront, they won't read the rest. That's fine. The point isn't to force someone to consume 2,500 words. If they got exactly what they needed from your TL;DR in 30 seconds, you did your job. If they want the examples, data, screenshots, reasoning or deeper explanation, they'll keep reading.

Look at the first 10 results and find what they're missing. This is where I think the AEO/GEO conversation gets interesting, but I'd put it after the fundamentals. Look at the pages already ranking and ask: what would make my version more useful?

Maybe all 10 have the same generic list. Maybe nobody has actually tested the recommendations. Maybe everyone recommends the same tools but nobody explains which one works for different use cases. Maybe they're all making the same claim without showing the data. Maybe nobody has included screenshots. Maybe the answers are technically correct but completely impractical.

That's your opening. If the first 10 results say the same thing, don't become the 11th result saying the same thing. Add something: original research, customer data, screenshots, experiments, examples, expert input, a useful comparison table, first-hand experience, a framework, or simply a better explanation.

The value doesn't have to be groundbreaking. Sometimes it's just answering the question everyone else skipped.

Make it easy to skim. Don't avoid tables, lists or short sections because you've heard that structured content looks like AI. Who cares? If a table makes the information easier to understand, use a table. If I'm comparing five products, show me the important differences before making me read five 500-word sections. If there are seven steps, show me the seven steps. If there are three options and the right choice depends on the situation, make that easy to see.

You're writing for a person who has somewhere else to be. Make their job easier.

Don't be afraid to talk about your product. This is where companies usually go wrong in one of two directions. They either turn every article into a sales pitch, or they're so scared of being promotional that they won't mention their own product even when it's directly relevant.

Talk about your product when it actually helps answer the question. If the article is discussing a problem your product solves, mention the specific feature that solves it. If a customer got a great result from that feature, show it. If you've got a case study that proves the point, use it.

A random "Try our platform" CTA at the bottom isn't very persuasive. "Here's the problem we just discussed. Here's how our product handles it. Here's what happened when a customer used it." That's a much stronger product mention. A product plug without backing doesn't go very far.

Use case studies inside the article. If you have case studies, don't hide all of them on your case study page. Turn relevant ones into in-content callouts or cards and put them next to the section where they're actually useful.

For example, if you're explaining how a SaaS improved activation rates, and you have a customer who improved activation using that exact feature, that's where I'd surface the case study. Not five screens later.

Technically, these can just be HTML callout blocks or cards. They don't need to be some crazy interactive experience. The important part is the placement. The reader should see the proof at the exact moment they're thinking, "Okay, but does this actually work?"

Add FAQs for the questions that remain. Don't add an FAQ because someone told you every article needs one. Use it to answer the questions that naturally remain after the main article.

I'd pull those questions from real places: search results, Reddit, sales calls, customer support, reviews, comments, and questions prospects keep asking. The goal isn't to squeeze five more keywords onto the page. It's to remove the questions still sitting in the reader's head.

Internal link like you're helping the reader, not checking a box. Don't add three internal links because your SEO checklist says you need three. Add the link because the reader has a reason to click it.

If I'm reading about one part of a problem and you have another article that answers the question I'm likely to have next, link to it. If you're talking about a category and have a relevant comparison page, link to it. If you've just explained a problem and have a guide that shows me how to solve the next stage, link to it.

Internal links become much more useful when you think about the reader's next question, rather than the number of links you need to place.

Give the reader a logical next step. Before publishing, I'd ask: someone just finished this article. What should they do now?

Maybe it's another article. Maybe it's a comparison page. Maybe it's a case study. Maybe it's a product feature. Maybe it's a demo or signup. It depends on the topic and where that reader is in the buying process.

That's also why I don't love one generic CTA slapped onto the bottom of every article. If the relevant next step becomes obvious halfway through the article, put it there. Don't make the reader finish the article, find the navigation, hunt down your product page and figure out the connection themselves.

Finally, read it like a customer, not a content marketer.

Forget the word count. Forget whether you hit the "ideal" number of headings. Forget whether you've used the keyword enough times. Forget whether your article looks like the pages ranking above you.

Read it as someone who actually has the problem. Did I get my answer quickly? Did I learn something? Did I get something I can actually use? Did you show me evidence instead of making a bunch of claims? Was it easy to get through? Did I understand what to do next?

And most importantly: did this make me trust this company more?

If yes, you're already doing a lot right.

I'd much rather publish something genuinely useful, with clear thinking, real examples and a sensible next step than spend hours trying to reverse-engineer whatever the latest AEO/GEO checklist says we're supposed to do.

I've been noticing a pattern in SaaS communities lately: a lot of founders have clearly put serious work into building the product, but then hit a completely different problem: figuring out the marketing side. And that's completely understandable. Building the product and figuring out how to get the right people to find it are two very different problems.

I've spent 10+ years working in content, and if I were starting the content side of a SaaS from scratch, I wouldn't begin with "let's publish 12 blog posts this month." I'd first figure out what is actually worth publishing, then make sure every piece has a reason to exist.

First things first, I wouldn't wait before thinking about SEO. I'm not an SEO specialist, but organic search takes time to build, so I'd rather have the groundwork in place early than decide six months later that we should probably start publishing.

For the blog, if you're not sure how to go about it, here's what I'd do.

1. First, figure out what is actually worth writing

Your keyword strategy should lead the way, but if you don't have one yet, I'd start much closer to the customer. Talk to prospects who are considering your product. What are they asking you? What are they unsure about? What are they comparing? What problem are they trying to solve before they get to your product?

Those questions are content opportunities.

One sprint I'd almost blindly look at is alternatives and comparison content. Got competitors? Those businesses are constantly losing customers, and some of those customers are actively looking for better options. If you're a project management SaaS, for example, I'd look at things like "Asana alternatives," "Asana vs X," "Asana alternatives for small teams," "Asana alternatives for agencies," pricing alternatives, migration questions, feature comparisons, and so on.

And I wouldn't stop at the first "alternatives" article. Map the whole decision around that competitor. What makes someone look for an alternative? What are they unhappy with? What are they trying to do that the competitor doesn't handle well? What questions do they have before switching? What could stop them from switching?

Now you're not just producing a list of keywords. You're learning about the actual buying decision. That can influence your comparison pages, landing pages, positioning, CTAs, product messaging, and even what you decide to improve in the product.

That's the kind of content work I'd want to do before sitting down and saying, "Okay, we need 12 blog posts this month."

2. Once you've picked the topic, use this checklist for every article

This is where I'd stop worrying about AEO, GEO, schema and every other new acronym for a minute. Get the basics right first. A lot of content isn't failing because it isn't "optimized" enough. It's failing because the reader has to work too hard to get something that should have been obvious.

Answer the actual question immediately. If someone searches for "cart recovery strategies," don't spend the first 400 words explaining why abandoned carts are bad for ecommerce. They know. That's why they're searching for cart recovery strategies. Get into the strategies. Give them the answer first, then add the context, examples and reasoning where they're actually useful.

Same logic with almost any query. Someone searching "how to migrate from X to Y" doesn't need a history lesson on why migrations matter. Someone searching "X alternatives" already knows what X is. Don't explain the problem they've already told you they have. Solve it.

Add a TL;DR that actually answers the question. I like TL;DRs, especially for longer pieces. But don't use them as a vague summary of everything the article covers. Make the TL;DR answer the primary question. If the article is about cart recovery strategies, the TL;DR should give me the main strategies. If it's about choosing between two tools, give me the key differences and who each one is best for. If it's "how to fix X," give me the key steps.

There's a strange fear that if you give people the answer upfront, they won't read the rest. That's fine. The point isn't to force someone to consume 2,500 words. If they got exactly what they needed from your TL;DR in 30 seconds, you did your job. If they want the examples, data, screenshots, reasoning or deeper explanation, they'll keep reading.

Look at the first 10 results and find what they're missing. This is where I think the AEO/GEO conversation gets interesting, but I'd put it after the fundamentals. Look at the pages already ranking and ask: what would make my version more useful?

Maybe all 10 have the same generic list. Maybe nobody has actually tested the recommendations. Maybe everyone recommends the same tools but nobody explains which one works for different use cases. Maybe they're all making the same claim without showing the data. Maybe nobody has included screenshots. Maybe the answers are technically correct but completely impractical.

That's your opening. If the first 10 results say the same thing, don't become the 11th result saying the same thing. Add something: original research, customer data, screenshots, experiments, examples, expert input, a useful comparison table, first-hand experience, a framework, or simply a better explanation.

The value doesn't have to be groundbreaking. Sometimes it's just answering the question everyone else skipped.

Make it easy to skim. Don't avoid tables, lists or short sections because you've heard that structured content looks like AI. Who cares? If a table makes the information easier to understand, use a table. If I'm comparing five products, show me the important differences before making me read five 500-word sections. If there are seven steps, show me the seven steps. If there are three options and the right choice depends on the situation, make that easy to see.

You're writing for a person who has somewhere else to be. Make their job easier.

Don't be afraid to talk about your product. This is where companies usually go wrong in one of two directions. They either turn every article into a sales pitch, or they're so scared of being promotional that they won't mention their own product even when it's directly relevant.

Talk about your product when it actually helps answer the question. If the article is discussing a problem your product solves, mention the specific feature that solves it. If a customer got a great result from that feature, show it. If you've got a case study that proves the point, use it.

A random "Try our platform" CTA at the bottom isn't very persuasive. "Here's the problem we just discussed. Here's how our product handles it. Here's what happened when a customer used it." That's a much stronger product mention. A product plug without backing doesn't go very far.

Use case studies inside the article. If you have case studies, don't hide all of them on your case study page. Turn relevant ones into in-content callouts or cards and put them next to the section where they're actually useful.

For example, if you're explaining how a SaaS improved activation rates, and you have a customer who improved activation using that exact feature, that's where I'd surface the case study. Not five screens later.

Technically, these can just be HTML callout blocks or cards. They don't need to be some crazy interactive experience. The important part is the placement. The reader should see the proof at the exact moment they're thinking, "Okay, but does this actually work?"

Add FAQs for the questions that remain. Don't add an FAQ because someone told you every article needs one. Use it to answer the questions that naturally remain after the main article.

I'd pull those questions from real places: search results, Reddit, sales calls, customer support, reviews, comments, and questions prospects keep asking. The goal isn't to squeeze five more keywords onto the page. It's to remove the questions still sitting in the reader's head.

Internal link like you're helping the reader, not checking a box. Don't add three internal links because your SEO checklist says you need three. Add the link because the reader has a reason to click it.

If I'm reading about one part of a problem and you have another article that answers the question I'm likely to have next, link to it. If you're talking about a category and have a relevant comparison page, link to it. If you've just explained a problem and have a guide that shows me how to solve the next stage, link to it.

Internal links become much more useful when you think about the reader's next question, rather than the number of links you need to place.

Give the reader a logical next step. Before publishing, I'd ask: someone just finished this article. What should they do now?

Maybe it's another article. Maybe it's a comparison page. Maybe it's a case study. Maybe it's a product feature. Maybe it's a demo or signup. It depends on the topic and where that reader is in the buying process.

That's also why I don't love one generic CTA slapped onto the bottom of every article. If the relevant next step becomes obvious halfway through the article, put it there. Don't make the reader finish the article, find the navigation, hunt down your product page and figure out the connection themselves.

Finally, read it like a customer, not a content marketer.

Forget the word count. Forget whether you hit the "ideal" number of headings. Forget whether you've used the keyword enough times. Forget whether your article looks like the pages ranking above you.

Read it as someone who actually has the problem. Did I get my answer quickly? Did I learn something? Did I get something I can actually use? Did you show me evidence instead of making a bunch of claims? Was it easy to get through? Did I understand what to do next?

And most importantly: did this make me trust this company more?

If yes, you're already doing a lot right.

I'd much rather publish something genuinely useful, with clear thinking, real examples and a sensible next step than spend hours trying to reverse-engineer whatever the latest AEO/GEO checklist says we're supposed to do.

I've been noticing a pattern in SaaS communities lately: a lot of founders have clearly put serious work into building the product, but then hit a completely different problem: figuring out the marketing side. And that's completely understandable. Building the product and figuring out how to get the right people to find it are two very different problems.

I've spent 10+ years working in content, and if I were starting the content side of a SaaS from scratch, I wouldn't begin with "let's publish 12 blog posts this month." I'd first figure out what is actually worth publishing, then make sure every piece has a reason to exist.

First things first, I wouldn't wait before thinking about SEO. I'm not an SEO specialist, but organic search takes time to build, so I'd rather have the groundwork in place early than decide six months later that we should probably start publishing.

For the blog, if you're not sure how to go about it, here's what I'd do.

1. First, figure out what is actually worth writing

Your keyword strategy should lead the way, but if you don't have one yet, I'd start much closer to the customer. Talk to prospects who are considering your product. What are they asking you? What are they unsure about? What are they comparing? What problem are they trying to solve before they get to your product?

Those questions are content opportunities.

One sprint I'd almost blindly look at is alternatives and comparison content. Got competitors? Those businesses are constantly losing customers, and some of those customers are actively looking for better options. If you're a project management SaaS, for example, I'd look at things like "Asana alternatives," "Asana vs X," "Asana alternatives for small teams," "Asana alternatives for agencies," pricing alternatives, migration questions, feature comparisons, and so on.

And I wouldn't stop at the first "alternatives" article. Map the whole decision around that competitor. What makes someone look for an alternative? What are they unhappy with? What are they trying to do that the competitor doesn't handle well? What questions do they have before switching? What could stop them from switching?

Now you're not just producing a list of keywords. You're learning about the actual buying decision. That can influence your comparison pages, landing pages, positioning, CTAs, product messaging, and even what you decide to improve in the product.

That's the kind of content work I'd want to do before sitting down and saying, "Okay, we need 12 blog posts this month."

2. Once you've picked the topic, use this checklist for every article

This is where I'd stop worrying about AEO, GEO, schema and every other new acronym for a minute. Get the basics right first. A lot of content isn't failing because it isn't "optimized" enough. It's failing because the reader has to work too hard to get something that should have been obvious.

Answer the actual question immediately. If someone searches for "cart recovery strategies," don't spend the first 400 words explaining why abandoned carts are bad for ecommerce. They know. That's why they're searching for cart recovery strategies. Get into the strategies. Give them the answer first, then add the context, examples and reasoning where they're actually useful.

Same logic with almost any query. Someone searching "how to migrate from X to Y" doesn't need a history lesson on why migrations matter. Someone searching "X alternatives" already knows what X is. Don't explain the problem they've already told you they have. Solve it.

Add a TL;DR that actually answers the question. I like TL;DRs, especially for longer pieces. But don't use them as a vague summary of everything the article covers. Make the TL;DR answer the primary question. If the article is about cart recovery strategies, the TL;DR should give me the main strategies. If it's about choosing between two tools, give me the key differences and who each one is best for. If it's "how to fix X," give me the key steps.

There's a strange fear that if you give people the answer upfront, they won't read the rest. That's fine. The point isn't to force someone to consume 2,500 words. If they got exactly what they needed from your TL;DR in 30 seconds, you did your job. If they want the examples, data, screenshots, reasoning or deeper explanation, they'll keep reading.

Look at the first 10 results and find what they're missing. This is where I think the AEO/GEO conversation gets interesting, but I'd put it after the fundamentals. Look at the pages already ranking and ask: what would make my version more useful?

Maybe all 10 have the same generic list. Maybe nobody has actually tested the recommendations. Maybe everyone recommends the same tools but nobody explains which one works for different use cases. Maybe they're all making the same claim without showing the data. Maybe nobody has included screenshots. Maybe the answers are technically correct but completely impractical.

That's your opening. If the first 10 results say the same thing, don't become the 11th result saying the same thing. Add something: original research, customer data, screenshots, experiments, examples, expert input, a useful comparison table, first-hand experience, a framework, or simply a better explanation.

The value doesn't have to be groundbreaking. Sometimes it's just answering the question everyone else skipped.

Make it easy to skim. Don't avoid tables, lists or short sections because you've heard that structured content looks like AI. Who cares? If a table makes the information easier to understand, use a table. If I'm comparing five products, show me the important differences before making me read five 500-word sections. If there are seven steps, show me the seven steps. If there are three options and the right choice depends on the situation, make that easy to see.

You're writing for a person who has somewhere else to be. Make their job easier.

Don't be afraid to talk about your product. This is where companies usually go wrong in one of two directions. They either turn every article into a sales pitch, or they're so scared of being promotional that they won't mention their own product even when it's directly relevant.

Talk about your product when it actually helps answer the question. If the article is discussing a problem your product solves, mention the specific feature that solves it. If a customer got a great result from that feature, show it. If you've got a case study that proves the point, use it.

A random "Try our platform" CTA at the bottom isn't very persuasive. "Here's the problem we just discussed. Here's how our product handles it. Here's what happened when a customer used it." That's a much stronger product mention. A product plug without backing doesn't go very far.

Use case studies inside the article. If you have case studies, don't hide all of them on your case study page. Turn relevant ones into in-content callouts or cards and put them next to the section where they're actually useful.

For example, if you're explaining how a SaaS improved activation rates, and you have a customer who improved activation using that exact feature, that's where I'd surface the case study. Not five screens later.

Technically, these can just be HTML callout blocks or cards. They don't need to be some crazy interactive experience. The important part is the placement. The reader should see the proof at the exact moment they're thinking, "Okay, but does this actually work?"

Add FAQs for the questions that remain. Don't add an FAQ because someone told you every article needs one. Use it to answer the questions that naturally remain after the main article.

I'd pull those questions from real places: search results, Reddit, sales calls, customer support, reviews, comments, and questions prospects keep asking. The goal isn't to squeeze five more keywords onto the page. It's to remove the questions still sitting in the reader's head.

Internal link like you're helping the reader, not checking a box. Don't add three internal links because your SEO checklist says you need three. Add the link because the reader has a reason to click it.

If I'm reading about one part of a problem and you have another article that answers the question I'm likely to have next, link to it. If you're talking about a category and have a relevant comparison page, link to it. If you've just explained a problem and have a guide that shows me how to solve the next stage, link to it.

Internal links become much more useful when you think about the reader's next question, rather than the number of links you need to place.

Give the reader a logical next step. Before publishing, I'd ask: someone just finished this article. What should they do now?

Maybe it's another article. Maybe it's a comparison page. Maybe it's a case study. Maybe it's a product feature. Maybe it's a demo or signup. It depends on the topic and where that reader is in the buying process.

That's also why I don't love one generic CTA slapped onto the bottom of every article. If the relevant next step becomes obvious halfway through the article, put it there. Don't make the reader finish the article, find the navigation, hunt down your product page and figure out the connection themselves.

Finally, read it like a customer, not a content marketer.

Forget the word count. Forget whether you hit the "ideal" number of headings. Forget whether you've used the keyword enough times. Forget whether your article looks like the pages ranking above you.

Read it as someone who actually has the problem. Did I get my answer quickly? Did I learn something? Did I get something I can actually use? Did you show me evidence instead of making a bunch of claims? Was it easy to get through? Did I understand what to do next?

And most importantly: did this make me trust this company more?

If yes, you're already doing a lot right.

I'd much rather publish something genuinely useful, with clear thinking, real examples and a sensible next step than spend hours trying to reverse-engineer whatever the latest AEO/GEO checklist says we're supposed to do.

I don't usually post personal things online, especially not like this.

A few months ago, I was laid off after working as a Content Manager for a SaaS SEO agency. Since then, I've been reflecting on my career, brushing up on my skills, and figuring out what the next chapter looks like.

I've spent more than 8 years working in content across SaaS, ecommerce, and agencies. During that time, I've been a Content Writer, Content Manager, and Head of Content, building SEO content strategies, managing writers, creating editorial processes, editing content at scale, and, more recently, spending a lot of time learning and working with GEO/AEO and how content is evolving alongside AI search.

Like many people in this industry, I've also been thinking about where content is headed over the next few years. It's pushed me to expand my skill set and rethink how I approach strategy, not just writing.

For those of you who've navigated career transitions in SEO or content, what ended up making the biggest difference?

• Did you stay focused on full-time roles?
• Did you move into contracting or fractional work?
• Did you specialize further, or broaden your skill set?
• Looking back, is there anything you wish you'd done sooner?

I'd genuinely love to hear from people who've been through a similar transition. Thanks for reading.

I don't usually post personal things online, especially not like this.

If you can't help directly, maybe an upvote, a share, or pointing me toward someone who might be hiring could help this reach the right person. I'd really appreciate it.

I got laid off a couple of months ago, and despite applying every day, reaching out to people, and trying just about everything I can think of, I'm down to about one month of savings.

The hardest part is that I don't think I'm bad at what I do.

I've spent more than 8 years writing for SaaS companies, ecommerce brands, and agencies. I've been a Content Writer, Content Manager, and Head of Content. I've built SEO content strategies, managed writers, edited thousands of articles, created content briefs, worked directly with clients, and helped companies grow their organic traffic. More recently, I've also been working on GEO/AEO and writing content that performs well in AI search.

I'm not saying I'm the best writer in the world. There are plenty of talented people out there. But I know the quality of my work, the ownership I take, and the results I've helped clients achieve. That's why this has been so difficult to accept.

And if you've been through something similar, I'd also love to know what actually worked for you.

One last thing, because I think context matters.

My last full-time role paid $2,500/month. I'm mentioning that because I don't want this post to make it seem like I'm new to the industry or struggling because I lack experience. I had a career I was genuinely proud of. I'm simply in a situation I never expected to be in, and I'm trying everything I can to get back to work.

Thank you for reading.

I don't usually post personal things online, especially not like this.

I got laid off a couple of months ago, and despite applying every day, reaching out to people, and trying just about everything I can think of, I'm down to about one month of savings.

The hardest part is that I don't think I'm bad at what I do.

I've spent more than 8 years writing for SaaS companies, ecommerce brands, and agencies. I've been a Content Writer, Content Manager, and Head of Content. I've built SEO content strategies, managed writers, edited thousands of articles, created content briefs, worked directly with clients, and helped companies grow their organic traffic. More recently, I've also been working on GEO/AEO and writing content that performs well in AI search.

I'm not saying I'm the best writer in the world. There are plenty of talented people out there. But I know the quality of my work, the ownership I take, and the results I've helped clients achieve. That's why this has been so difficult to accept.

I'm not looking for sympathy or charity. I'm looking for a chance to work.

If your company, agency, or someone you know is looking for a senior content writer, content strategist, editor, or content manager, I'd genuinely appreciate an introduction.

And if you've been through something similar, I'd also love to know what actually worked for you. Not generic advice, but the thing that finally got you back on your feet.

One last thing, because I think context matters.

My last full-time role paid $2,500/month. I'm mentioning that because I don't want this post to make it seem like I'm new to the industry or struggling because I lack experience. I had a career I was genuinely proud of. I'm simply in a situation I never expected to be in, and I'm trying everything I can to get back to work.

Thank you for reading.