Cross-Promoting SaaS: How My Job Board Feeds AutoDetective Traffic

Last month I was looking at my analytics for AutoDetective.ai and noticed something I wasn't expecting. A non-trivial chunk of referral traffic was coming from my own job board on Grizzly Peak Software. Not a massive flood — we're talking indie numbers here — but consistent, daily clicks from people browsing remote tech jobs who then ended up reading about car diagnostics on a completely different site.

That shouldn't work. A burned-out software engineer looking at remote gigs has no obvious reason to click through to an automotive AI tool. But they were doing it. And when I dug into the data, I realized that I'd accidentally stumbled into one of the most underrated growth strategies for indie builders: cross-promotion between your own products.

---

Why Most Indie Builders Ignore Cross-Promotion

Here's the thing about running multiple products as a solo founder: you're so busy keeping each one alive that you rarely stop to think about how they can help each other. Each product lives in its own mental silo. The job board is over here. AutoDetective is over there. Grizzly Peak Software is the mothership. And they all compete for the same limited resource — my time and attention.

But that siloed thinking leaves money and traffic on the table. If you've got multiple properties generating any traffic at all, you've got a built-in distribution channel that costs you exactly nothing to use. No ad spend. No cold outreach. No begging for backlinks. Just your own audience, moving between your own properties.

The big SaaS companies understand this intuitively. Atlassian cross-sells Jira users into Confluence. Google pushes Workspace users toward every other Google product. Microsoft bundles everything into everything. But indie builders? We build three things and treat them like they exist on different planets.

---

The Grizzly Peak Ecosystem

Let me lay out what I'm working with so the cross-promotion strategies make sense:

Grizzly Peak Software (grizzlypeaksoftware.com) — My technical content hub. 500+ articles, a library of in-depth technical resources, and a remote tech job board. This is the highest-traffic property I own because content SEO has been compounding for over a year.

AutoDetective.ai — A programmatic SEO site with 8,000+ pages of AI-generated automotive diagnostics content. It targets people searching for things like "2019 Honda Civic check engine light P0420" and gives them genuinely useful troubleshooting guides.

My book — A technical book about training LLMs, sold through the site and Amazon.

These audiences overlap more than you'd think. Someone reading articles about career burnout on Grizzly Peak is often someone who tinkers with cars on weekends. Someone searching for car diagnostic info on AutoDetective might be a technically-minded person who'd find my software engineering articles useful. And both audiences are potential book buyers.

The trick is finding the natural connection points instead of forcing awkward cross-sells.

---

Strategy 1: Contextual Sidebar Ads

The first thing I did was set up an internal ad system on Grizzly Peak Software. I built a lightweight ad rotation system that serves sidebar and inline ads across the site. Some of those slots are for affiliate products and sponsors, but I reserve a percentage for my own properties.

On the job board pages, I run a sidebar ad for AutoDetective.ai with copy like: "Built by the same engineer who runs this job board. Check out AutoDetective.ai — AI-powered car diagnostics." On article pages about AI and automation, I run ads highlighting how AutoDetective uses AI to generate diagnostic content at scale.

The key insight: context matters more than volume. An AutoDetective ad on a random JavaScript tutorial converts terribly. But the same ad on an article about building programmatic SEO sites? That converts at 3-4x the baseline rate because the reader is already thinking about AI-generated content systems and AutoDetective is a live example.

Here's what the click-through rates look like for internal cross-promotion ads:

| Placement | CTR | Notes | |-----------|-----|-------| | Job board sidebar | 0.8% | Low intent but high volume | | AI/automation articles | 3.2% | High relevance, good conversion | | Career/burnout articles | 1.4% | Surprising — car people overlap | | General tech articles | 0.3% | Basically noise |

Those numbers are small in absolute terms, but they compound. The job board serves hundreds of page views daily, so even 0.8% CTR adds up to a steady trickle of referral traffic.

---

Strategy 2: Content Cross-Pollination

This is the strategy that's worked best for me, and it requires almost zero extra effort once you understand the principle: write content that naturally references your other products as real-world examples.

When I write an article about programmatic SEO, I don't have to invent hypothetical examples. I talk about AutoDetective.ai — how I built it, what worked, what failed, what the traffic numbers look like. That article lives on Grizzly Peak, ranks for programmatic SEO keywords, and drives interested readers to check out AutoDetective as a live case study.

When I write about AI-powered content generation, I reference the pipeline I built for AutoDetective. When I write about indie SaaS metrics, I share real data from both properties. When I write about career transitions and side projects, I mention the job board as something I built in a weekend to serve the same audience.

None of this feels like advertising because it isn't. It's genuine practitioner content that happens to reference my own products because those are the products I actually use and build. Readers can smell fake case studies from a mile away. Real ones — warts and all — build trust and drive curiosity clicks.

The traffic flow from content cross-pollination over the last 90 days:

• Grizzly Peak articles mentioning AutoDetective: ~340 referral clicks to AutoDetective.ai
• AutoDetective footer links back to Grizzly Peak: ~180 referral visits
• Job board to AutoDetective (sidebar ads): ~520 clicks
• Article cross-links to job board: ~890 clicks

That's over 1,900 cross-property visits in 90 days, all organic, all free.

---

Strategy 3: Shared Email Footers and CTAs

I don't run a massive email list — this isn't a newsletter-first business. But I do have a subscriber list from the Grizzly Peak contact form and newsletter signup. Every email that goes out includes a footer with links to all three properties: the main site, AutoDetective, and the book.

More importantly, when I send any kind of update email, I include a brief "What else I'm building" section at the bottom. Something like:

AutoDetective.ai just crossed 10,000 indexed pages. If you've got a car throwing codes, give it a try. And if you're looking for remote tech work, the job board is updated daily with AI-curated positions.

It's two sentences. It takes 30 seconds to write. And it converts at roughly 2.1% — meaning about 2 out of every 100 email recipients click through to one of the cross-promoted properties. For a list my size, that's a few dozen visits per send. Not life-changing, but not nothing.

---

Strategy 4: Shared Technical Infrastructure as Content

This one is more subtle but surprisingly effective. Because I built all three properties myself, I can write detailed technical content about the shared infrastructure patterns. The ad serving system. The analytics pipeline. The deployment setup on DigitalOcean. The PostgreSQL schema design patterns I reuse across projects.

Each of these technical deep-dives is genuinely useful content that ranks for developer queries. And each one naturally references multiple products in the ecosystem because they all share the same underlying tech stack.

Here's a concrete example. I wrote an article about building a lightweight ad rotation system in Node.js and Express. That article:

1. Ranks for "Node.js ad server" and related keywords
2. References Grizzly Peak as the platform where the ad system runs
3. Mentions AutoDetective as one of the products being promoted through the system
4. Includes real code from the actual implementation
5. Links to the job board as an example of ad placement in context

One piece of content, five different cross-promotion touchpoints, all of them natural and relevant.

---

The Audience Overlap You Don't Expect

I mentioned earlier that burned-out software engineers and car tinkerers overlap more than you'd think. Let me elaborate on that because it's important for anyone considering cross-promotion between seemingly unrelated products.

I looked at the demographic data from Google Analytics and the behavioral patterns in my server logs. Here's what the typical Grizzly Peak job board user looks like:

• Male, 28-45
• Currently employed in software engineering
• Browsing remote/alternative positions (suggesting dissatisfaction or burnout)
• Located in suburban or rural areas
• High technical literacy

And here's the typical AutoDetective.ai user:

• Male, 25-55
• Searching for specific vehicle diagnostic information
• Likely DIY-oriented (not searching for "mechanic near me")
• Moderate to high technical literacy
• Often suburban or rural (where DIY car work is more common)

See the overlap? Technically-minded men in suburban areas who prefer to solve problems themselves rather than pay someone else. That's the same person in a lot of cases. The software engineer who's frustrated with their job and browsing remote positions on a Tuesday afternoon is the same person who's going to Google "P0171 lean condition Ford F-150" on Saturday morning.

This isn't a coincidence I engineered — it's a pattern I discovered after building both products and looking at the data. But now that I know it exists, I can lean into it.

---

What's Actually Working: The Numbers

Let me be honest about what cross-promotion is and isn't doing for my business in early 2026.

What it IS doing:

• Generating 600-800 free cross-property visits per month
• Reducing my overall customer acquisition cost to near zero for inter-property traffic
• Creating natural backlink opportunities between my own domains
• Providing real case study material for content marketing
• Building a perception of a broader "brand" rather than isolated projects

What it ISN'T doing:

• Replacing the need for SEO on each individual property
• Generating massive direct revenue (we're talking maybe $40-60/month in attributable ad revenue from cross-promoted traffic)
• Solving the cold-start problem for new products
• Making any single product viable that wouldn't be viable on its own

Cross-promotion is a force multiplier, not a foundation. If AutoDetective had zero organic search traffic, sending it a few hundred visits from Grizzly Peak wouldn't save it. But because AutoDetective already has solid organic traffic from programmatic SEO, the cross-promotion amplifies what's already working.

---

How to Set This Up Without Overcomplicating It

If you're running multiple products and want to start cross-promoting, here's my practical advice:

Start with links, not systems. Before you build an ad rotation engine, just add footer links to your other properties on every page. This takes five minutes and captures the lowest-hanging fruit.

Write about what you know. If you run multiple products, your content marketing should reference them as real examples. Don't write hypothetical case studies when you have actual case studies sitting right there.

Track referral traffic. You can't optimize what you don't measure. Set up UTM parameters on your cross-promotion links so you can see exactly how much traffic flows between properties. A simple analytics setup in Google Analytics or Plausible is sufficient.

Respect the context. Don't shove irrelevant cross-promotion into every page. An AutoDetective ad on a JavaScript debugging article is just noise. An AutoDetective mention in an article about AI content generation is a natural fit. Your readers can tell the difference.

Build shared infrastructure. If you're going to run multiple products, standardize your tech stack so that you can write about shared patterns. This creates content opportunities and reduces your maintenance burden at the same time.

Here's a simple tracking setup I use for cross-promotion links:

var express = require('express');
var router = express.Router();

router.get('/go/:destination', function(req, res) {
    var destination = req.params.destination;
    var source = req.query.src || 'unknown';

    var destinations = {
        'autodetective': 'https://autodetective.ai?utm_source=grizzlypeak&utm_medium=crosspromo&utm_campaign=' + source,
        'jobs': '/jobs?utm_source=internal&utm_medium=crosspromo&utm_campaign=' + source,
        'book': '/library?utm_source=internal&utm_medium=crosspromo&utm_campaign=' + source
    };

    var url = destinations[destination];
    if (!url) {
        return res.redirect('/');
    }

    // Log the cross-promotion click
    console.log('Cross-promo click: ' + source + ' -> ' + destination + ' at ' + new Date().toISOString());

    res.redirect(302, url);
});

module.exports = router;

Nothing fancy. A redirect endpoint that logs the click and forwards with UTM parameters. You could add database tracking if you want historical data, but even console logging piped to your server logs gives you the basics.

---

The Compounding Effect

The thing about cross-promotion that most people miss is that it compounds in the same way content SEO compounds. Each new article that mentions AutoDetective is another entry point. Each new job board visitor who sees a sidebar ad is another potential AutoDetective user. Each AutoDetective visitor who clicks through to Grizzly Peak is another potential newsletter subscriber.

Over time, these micro-connections build a web of internal traffic that makes each property slightly more valuable than it would be in isolation. It's not dramatic growth. It's not "viral." It's the indie equivalent of enterprise cross-selling — boring, consistent, and quietly effective.

I'm six months into deliberately cross-promoting between my properties, and the referral traffic between them has roughly tripled from when I started paying attention. Most of that growth came from content cross-pollination rather than ads or email — which makes sense, because content is what scales without ongoing effort.

If you're building multiple products as an indie developer, stop treating them as isolated islands. They're an archipelago. Build the bridges.

---

Shane Larson is a software engineer and the founder of Grizzly Peak Software. He writes about building indie SaaS products, AI tools, and the business of software from his cabin in Caswell Lakes, Alaska. You can find his work at grizzlypeaksoftware.com and AutoDetective.ai.