There’s a moment in any content-heavy product where the numbers start to feel absurd. For us, it was somewhere around page sixty-seven.
I remember staring at the sitemap in our CMS, scrolling through rows of published pages — competitor comparisons, use-case guides, LP-focused landing pages, resource hubs — and thinking: we built all of this in under five months.
PipelineRoad.com crossed 100 pages a few weeks ago. Not 100 blog posts. Not 100 scraped-and-spun articles. One hundred substantive, research-backed pages designed to serve a very specific audience: fund managers across private equity, venture capital, real estate, and credit who need to raise capital more efficiently.
Here’s what that actually looked like, week by week.
The Starting Point
When we decided to go all-in on PipelineRoad.com as a product, the site had about twelve pages. A homepage. A few feature pages. A pricing page that was mostly aspirational. An about page that read like a LinkedIn summary.
We had the agency running at full capacity — eight clients, eleven brands. Building the product site meant carving time out of an already-packed schedule. Bruno and I made a deal: we’d dedicate Wednesday through Friday mornings to PipelineRoad.com, no exceptions.
The first thing we did was throw away most of what we had. Not the code — the copy. The positioning was wrong. We were describing PipelineRoad like a SaaS tool when it needed to feel like an institutional platform. Fund managers don’t buy tools. They adopt platforms.
The Keyword Architecture
Before we wrote a single new page, I spent two weeks doing what I do for every agency client: keyword research and clustering.
I pulled every relevant keyword I could find — fundraising software, LP management, capital raising CRM, deal origination platform, investor relations tools. Thousands of terms, organized into clusters based on intent.
The clusters told us what to build:
- Competitor vs. pages — fund managers comparing us to Dakota, Altvia, Juniper Square, DealCloud. These had the highest conversion intent and surprisingly low keyword difficulty.
- Use-case pages — how PipelineRoad works for PE fundraising, VC fund operations, real estate capital markets.
- Educational content — what is deal origination, LP due diligence process, capital call management.
- Industry pages — specific verticals within fund management.
We mapped every cluster to a page. That gave us a target of about 120 pages. We decided 100 was the milestone.
The Production System
Here’s where it gets real. You don’t publish 100 quality pages by sitting down and writing whenever inspiration strikes. You need a system.
Ours looked like this:
Research phase (Monday-Tuesday): I’d spend two hours per batch of pages pulling competitor data, reading industry reports, checking what existing content ranked for our target terms. I’d write a brief for each page — target keyword, search intent, key points to cover, internal linking targets.
Drafting phase (Wednesday-Thursday): We used AI for first drafts — heavily. But here’s what most people get wrong about AI content: they treat the output as the final product. We treated it as a starting point. Every AI draft went through what I call the “practitioner pass” — I’d rewrite the opening, add specific examples from our actual work with fund managers, remove the generic filler, and restructure the argument.
Review and publish (Friday): QA, internal linking, meta descriptions, OG images. We’d publish three to five pages per week.
At that pace, 100 pages took about five months.
The Compound Effect
The interesting thing about building a content-heavy site isn’t the individual pages. It’s the network effect between them.
Around page forty, something shifted. Our internal linking became dense enough that Google started treating PipelineRoad.com as an authority in the fundraising software space. Pages that had been sitting on page three started climbing to page one. New pages would index faster and rank higher out of the gate.
This is what I mean when I talk about content that compounds. The first twenty pages feel like shouting into a void. The next twenty feel like slow progress. And then somewhere around page sixty, the flywheel catches and everything accelerates.
Our organic traffic went from about 200 monthly visits to over 3,000 in that same five-month window. Not viral numbers, but for a B2B platform targeting fund managers — a market with maybe 50,000 total addressable buyers — it was significant.
The Competitor VS Pages
The biggest ROI came from the competitor comparison pages. We built seven of them, targeting fund managers searching for alternatives to established players.
The combined monthly search volume for those terms was around 4,500, with an average keyword difficulty of 3. That’s essentially free traffic.
But the real value wasn’t the traffic — it was the intent. Someone searching “PipelineRoad vs Dakota” or “Juniper Square alternatives” is actively evaluating solutions. They’re in buying mode. Those seven pages drove more demo requests than the other ninety-three combined.
Lesson: not all pages are created equal. Build the high-intent pages first, then fill in the educational content around them.
What Took Longer Than Expected
Plenty.
The voice. We rewrote the site voice three times before it felt right. Fund managers have a specific register — institutional but not stuffy, precise but not jargon-heavy. They’re sophisticated buyers who can smell marketing copy from a mile away. Finding the right tone took weeks of iteration.
Internal linking. With 100 pages, the internal linking architecture became genuinely complex. We built a spreadsheet to track which pages linked to which, and we still found orphan pages during audits. This is the unglamorous work that most content teams skip, and it matters enormously for SEO.
OG images. We wanted custom Open Graph images for every page, not auto-generated ones. Andre, our designer, pushed back initially — he had enough on his plate with client work. We compromised: custom images for the top thirty pages, templated ones for the rest.
Quality control at scale. When you’re publishing five pages a week, quality drift is real. We caught ourselves publishing a page around week twelve that read like every other B2B SaaS page on the internet — generic value props, meaningless statistics, hollow CTAs. I pulled it, rewrote it, and we added a checklist to our process.
The Technical Foundation
Content doesn’t exist in isolation. The technical SEO had to be right, or the content wouldn’t perform.
We built PipelineRoad.com on Astro with an Astro-based blog system. Fast page loads, clean HTML, proper heading hierarchy. We added structured data for every page type — FAQ schema for educational content, product schema for feature pages, review schema where appropriate.
The sitemap was auto-generated and submitted to Google Search Console weekly. We set up custom caching headers through Vercel to serve static assets with immutable cache controls.
None of this is glamorous. But a site that loads in 1.2 seconds with clean markup and proper schema will outperform a beautiful site that loads in 4 seconds every time.
What It Feels Like
Crossing milestones matters more than I expected.
Page twenty-five felt like a real website for the first time. Page fifty felt like we were building something substantial. Page seventy-five felt like we’d crossed a point of no return — too much invested to stop, too much momentum to slow down.
Page one hundred felt quiet. We didn’t celebrate. Bruno sent me a message that said “100” with no context, and I replied with a thumbs up. That was it.
The next morning, I opened the analytics dashboard and saw a demo request that came in from someone who’d read four of our competitor comparison pages in a single session. They converted without ever talking to a human.
That’s the moment it clicked. We hadn’t built 100 pages. We’d built a sales team that works while we sleep.
What I’d Tell Someone Starting This
Start with the high-intent pages. Competitor comparisons, specific use cases, direct product pages. These convert. Everything else is supporting content.
Build a production system before you start writing. If you’re winging it, you’ll burn out at page fifteen.
Use AI for drafts, but never for final copy. The practitioner perspective — the specific details, the hard-won opinions, the nuance — that’s what makes content worth reading. AI gives you structure. You give it soul.
Be patient with the compound effect. The first forty pages will feel thankless. Keep going.
And measure the right things. Not traffic — demos. Not rankings — revenue. The vanity metrics will come. Focus on the ones that pay the bills.
We’re at 107 pages now, and we’re not stopping. The roadmap has another fifty planned for the next quarter. The flywheel is spinning, and our only job is to keep feeding it with content worth reading.
One page at a time.