Rank Science

Ryan Bednor was a software engineer who accidentally became an SEO expert. At previous startups, he found himself managing SEO because nobody else was doing it. After one startup shut down, he became an SEO consultant for companies in his network—including YC startups and Fortune 500 companies. His unique advantage: unlike traditional SEO consultants who sent PDFs of recommendations, Ryan could actually execute the changes himself because he was a programmer. This proximity to the work revealed a massive gap: companies couldn't measure whether their SEO changes actually worked.

Ryan started building in-house A/B testing tools for his consulting clients so they could measure the impact of on-page changes—title tags, HTML tweaks—on rankings and click-through rates. He then attempted to productize this as an API, thinking companies would integrate it into their front-ends. That didn't work. "Nobody actually wanted to use it," Ryan recalls. "It was just tricky because it would require in-house engineers to integrate this API into their logic."

Instead of giving up, Ryan pivoted. He realized that if Rank Science built a CDN, they could route traffic through their infrastructure and automatically make HTML changes for customers—no integration required. This insight came from understanding his customers' real friction points, not just what they said they wanted.

Rank Science faced a chicken-and-egg problem: convincing established businesses to route all their website traffic through a new, unproven CDN. Ryan solved this by leaning on his network. "We had a number of people who trusted me, who I had helped grow their sites before. And they were willing to give Rank Science a try and kind of take that leap of faith," he explained. The first customers came for free—Ryan needed to validate that the CDN actually worked at scale before charging.

Once he had proof of concept, referrals started trickling in. But the real breakthrough came when Dylan (his co-founder, who he'd met at a previous startup) published a case study about Coderwall—showing how a single A/B test on title tags drove 57% traffic growth. They posted it on Hacker News, and it exploded. "That got a lot of attention and we started getting customers from there through Hacker News."

The API approach failed because it required too much customer effort. But Ryan didn't see this as failure—he saw it as validation of a critical insight: companies won't integrate complex tools, even if they say they will. The CDN pivot removed friction entirely.

Content marketing became their killer channel. That single Coderwall case study, combined with a few Twitter ad dollars (a couple hundred bucks promoting the post), drove significant customer acquisition. TechCrunch also picked them up—with a sensational "Rank Science is coming for your jobs" angle that Ryan initially disliked but which drove 1,500 signups.

Ryan also learned sales from YC partners. A small but pivotal lesson: always schedule a follow-up call to review proposals rather than just sending them out. That one change increased their close rate by 30%. He went from zero sales experience to having a direct phone sales process that worked.

Y Combinator itself was transformative. Ryan entered with $28K MRR and was told to hit $80K in three months. "I don't know if that's possible," he thought. But the forcing function, the network, and the group office hours (where he learned from other founders' challenges) made it happen.

Rank Science hit $80K MRR within three months of YC. Their pricing ranges from $2,000 to $8,000/month depending on traffic volume, positioned between what a CDN costs and what hiring an SEO consultant costs. They employ five people: Ryan, Dylan, a lead engineer, a director of SEO, a data scientist, and an account manager.

Ryan believes they're just getting started. "We've kind of validated this idea or this space. We really believe that the opportunity here is big, but now we really have to execute." Their next goals: scale 2-3X over the next year by improving the product, hiring more engineers, and moving upmarket to larger websites. They're also working on moving from sales-heavy onboarding to more self-service automation—a natural evolution as they scale.