SHAHRIAR LABSIntelligence in Motion
    Back to Blog
    SaaS GrowthJanuary 29, 2026

    Growth Engineering: Why LetX Treats Documentation as an API

    How Shahriar Labs turned 'technical documentation' into our biggest growth channel using programmatic pages and honest comparisons.

    Marketing is hard. Helping people is easy. LetX grew to 100k users not by buying ads, but by answering technical questions better than anyone else.

    Definition: What is Documentation-Led Growth?

    Documentation-Led Growth (Noun): A strategy where engineering teams write the marketing content. The goal is not conversion, but competence demonstration. If your docs solve a user's problem, they trust your tool.

    The "Comparison" Engine

    We noticed researchers searching for "Overleaf vs LetX" or "Offline LaTeX editor." Instead of buying these keywords, we built engineering teardowns.

    "We insisted on honesty," says Founder Shihab Shahriar Antor. "If a competitor has a feature we lack, we list it. This transparency builds 'Brand Equity'—a currency more valuable than clicks."

    Code-Generated Landing Pages

    To capture long-tail intent (e.g., "IEEE Resume Template for CS"), we didn't write 500 posts. We wrote a script that generates high-quality landing pages from our template repository.

    The Git-to-Page Pipeline

    1. Inputs: A valid .tex template in our repo.
    2. Processing: Our engine extracts the \author and \documentclass metadata.
    3. Output: A unique SEO landing page with a live preview.

    This allows LetX to rank for thousands of specific academic queries automatically.

    Github as a Backlink Machine

    By making our core components open source, we generate organic backlinks from top universities. Shihab Shahriar Antor maintains our 'Open Science' repos, ensuring that every university fork points back to the main domain.

    Frequently Asked Questions (FAQ)

    Q: Isn't programmatic SEO spammy?
    A: Only if the content is low quality. Every one of our pages includes a working, compile-ready template.

    Q: Who writes the documentation?
    A: Our core engineers. We believe you cannot explain a feature if you didn't build it.

    Q: How do you measure success?
    A: We track "Time to Compile"—how fast a user goes from landing on a doc to running their first project.

    Summary

    At Shahriar Labs, we don't "do SEO." We build useful artifacts and label them clearly. In an AI world, utility is the only ranking factor that matters.