Roast my site

Cold outreach scales linearly - same effort per reply every week. It's necessary for early traction but the founders who get to $10k+ MRR almost always layer in a compounding channel underneath it. SEO, community, partnerships, or product-led growth.

What's the channel you're betting on to build independently of your outreach?

Hey Abe, took a proper look at api.carsxe.com. You've built something substantial here — the API suite is genuinely comprehensive. Here's what the landing page needs:

The hero tries to do everything at once. "Access specifications, VIN & License Plate decoding, market value, history, images, OCR, and more" — that's 7+ things in one sentence. When everything is highlighted, nothing is. Pick your strongest use case (VIN decoding seems to be it based on the code example) and lead with that. You can expand the full suite further down the page.

Your comparison table vs Carfax/KBB/Polk is a killer section but it's buried way below the fold. That table alone answers the "why you over the big guys" question instantly. Move it higher — developers evaluating API providers want to see competitive positioning early, not after scrolling through feature lists.

The testimonials are your strongest conversion asset and they're actually named and specific (Andy Liakos CTO of MotorTango, Samee Khan of Pam). That's rare and valuable. But the "Senior Director of Engineering, Major Parking App" one is anonymous — it's your most enthusiastic quote and it carries the least credibility because there's no name attached. If you can get permission to name them, do it.

"Just $99/mo + API call fees" in the hero is good transparency, but "+ API call fees" is vague. Developers want to see per-call pricing before committing. Even a "starting at $0.01/call" would reduce friction.

The code example in the hero is smart — developers love seeing actual implementation. But it's JavaScript only. A language switcher (Python, Ruby, cURL) would show the breadth of your SDK support without taking more space.

Biggest win: restructure the page flow to Hero (single strongest use case) → Comparison table → Testimonials → Full API suite → Pricing. Right now the information hierarchy doesn't match how a developer evaluates an API provider.

I do full prioritized teardowns as a service — https://aidenvale3.gumroad.com/l/roast

Happy to hear if this was useful.

There’s a lot done right here — the effort shows. What’s holding it back feels less like execution and more like decision friction.

As a visitor, I understand what you do, but I don’t immediately feel confident about where to focus or what matters most. When everything sounds important, the brain pauses instead of acting.

One thing that often helps is prioritizing a single, high-stakes outcome in the hero section and letting everything else support that story. When the path feels obvious, conversions usually follow without changing the offer.