TEAM

Built by one person, in public

AEOlens is a bootstrapped, one-person product. The same human writes the code, answers support, and updates the roadmap. No team page mockups, no fake bios. Here's what that actually looks like.

TS
FOUNDER · ENGINEER · SUPPORT

Thankaselvan S

Started AEOlens in early 2024 after watching too many SaaS pages with strong SEO get skipped by ChatGPT and Perplexity. Most existing AEO tools were either too enterprise (sales-led, five-figure annual commits) or too shallow (one-off audits without a fix loop). AEOlens is the bootstrapped middle: deep enough to actually move the score, cheap enough that an indie founder can afford it.

Day-to-day, I write the code, run the crawler, answer support emails, and curate the changelog and roadmap. If you email contact@aeolens.ai, you're emailing me directly.

Honest about scope

What's solo-built, what's outsourced

A one-person team can't build everything from scratch — and shouldn't pretend to. Here's the honest split.

BUILT IN-HOUSE

Solo-engineered

  • Crawler, scoring engine, and the 48 structural checks
  • AI Buyer Simulation pipeline across the 5 models
  • AI Agent Analytics server-side capture
  • All product code (web app + API + worker)
  • Marketing site, docs, glossary, vs-comparisons
  • Customer support and onboarding
NOT SOLO

Outsourced (vendor list)

The boring-but-important pieces handled by specialists. Same vendor list shown on the security page.

  • Hosting and infrastructureRender + Supabase + Upstash + Cloudflare
  • Payments and taxDodo Payments
  • Email deliveryResend
  • AI model routingOpenRouter
  • Error monitoringSentry
What this means for you

The pros and the trade-offs

The pros

  • Fast iteration. A bug you report Monday morning is usually fixed by Monday afternoon.
  • Direct contact.You email the founder. No tier-1 support, no "passing this to engineering."
  • Honest pricing. No VC pressure on growth means we can price the platform at SMB-friendly levels and keep it that way.
  • No corporate noise. Decisions about the product happen in one head, not in a quarterly all-hands.

The trade-offs

  • Bus factor.If I'm sick for a week, the email queue grows. Sentry alerts route to my phone, but a multi-week incident response is realistically tougher than at a 20-person SaaS.
  • Enterprise pace. Long procurement cycles (SOC 2 reviews, custom DPA negotiation) move slower than they do at companies with dedicated GRC teams.
  • Roadmap depth. A feature behind a paywall at Profound or Writesonic might be a quarter away here. The roadmap is transparent about what's queued.
  • Time zones. Email response on weekends and holidays may be slower.

Have a question for the founder?

Email contact@aeolens.ai. Same address for sales, support, and feature requests — they all go to the same inbox. I read every one.