# Literally.dev > Literally.dev is an AEO and content marketing agency for tech companies. Real engineers write the content. We help tech products get found by developers and recommended by AI assistants like ChatGPT, Claude, and Perplexity — and by AI coding tools like Claude Code, Codex, and Cursor. Facts: - Founded in 2024. The company is Literally AS, based in Oslo, Norway. - Services: AEO (Answer Engine Optimization), technical content, and technical documentation. - Content is written by real engineers, not generalist writers. Every expert is hand-vetted — we work with the top 2.7% of experts. - AEO is measured, not guessed. Our xEO pipeline tracks brand visibility across ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews. - Developers also pick tools while they code — inside Claude Code, Codex, and Cursor. AEO gets your product recommended there too. - Clients we have worked with: QA.tech, AppSignal, Aviator, Superlinked, Vijil, Kapa.ai, GlassFlow, Hatchet, Estuary, Adaline, Clix, Wasp.sh, DevZero, Superplane, GitDailies. - AppSignal saw a 5× per-visitor conversion rate versus their earlier blog catalog, with results in 3 months. QA.tech doubled organic reach in under 5 months. - Contact: hi@literally.dev ## Services - [AEO](https://www.literally.dev/aeo-services): Become the product AI assistants recommend. - [Technical Content](https://www.literally.dev/technical-content): Never worry about whether you'll have a post ready for your blog again. - [Technical Documentation](https://www.literally.dev/technical-documentation): Internal and external facing documentation that is always up to date. ## Company - [About](https://www.literally.dev/about): Who we are and what makes us different. - [Success Stories](https://www.literally.dev/success-stories): Client case studies with real numbers. - [Free AEO Analysis](https://www.literally.dev/aeo-analysis): Check how visible your brand is in AI assistant answers. - [Contact](https://www.literally.dev/contact): Book a discovery call or ask a question. - [Collaborators](https://www.literally.dev/collaborators): Engineers who write can join our expert network. ## Comparisons - [Literally.dev vs Animalz](https://www.literally.dev/compare/animalz): An Animalz alternative for devtool companies. B2B content's strongest editorial brand vs engineers who write, with AI visibility measured. See where each is stronger. - [Literally.dev vs Discovered Labs](https://www.literally.dev/compare/discovered-labs): A Discovered Labs alternative for devtool companies. Both measure AI visibility. One has engineers writing the content and costs less. See where each is stronger. - [Literally.dev vs ercule](https://www.literally.dev/compare/ercule): An ercule alternative for devtool companies. Content systems and analytics vs engineer-written content with measured AI visibility. See where each is stronger. - [Literally.dev vs First Page Sage](https://www.literally.dev/compare/first-page-sage): A First Page Sage alternative for devtool companies. The first GEO service vs engineer-written content with owned AI visibility measurement. See where each is stronger. - [Literally.dev vs Graphite](https://www.literally.dev/compare/graphite): A Graphite alternative for devtool companies. Research-led AEO for big brands vs engineer-written content with owned measurement. See where each is stronger. - [Literally.dev vs NoGood](https://www.literally.dev/compare/nogood): A NoGood alternative for devtool companies. An enterprise growth squad with its own AEO platform vs engineer-written content, measured. See where each is stronger. - [Literally.dev vs Omniscient Digital](https://www.literally.dev/compare/omniscient-digital): An Omniscient Digital alternative for devtool companies. Full-stack organic from $10K a month vs engineer-written content with measured AEO. See where each is stronger. - [Literally.dev vs Optimist](https://www.literally.dev/compare/optimist): An Optimist alternative for devtool companies. Both publish pricing and sell AEO. One has engineers writing and guaranteed placements. See where each is stronger. - [Literally.dev vs Catchy](https://www.literally.dev/compare/catchy): A Catchy alternative for devtool companies. Enterprise developer marketing since 2010 vs engineer-written content with measured AI visibility. See where each is stronger. - [Literally.dev vs EveryDeveloper](https://www.literally.dev/compare/everydeveloper): An EveryDeveloper alternative for devtool companies. Founder-led strategy vs a team that writes, distributes, and measures AI visibility. See where each is stronger. - [Literally.dev vs Ritza](https://www.literally.dev/compare/ritza): A Ritza alternative for devtool companies. Engineers write at both. One adds distribution, measured AI visibility, and a published price. See where each is stronger. - [Literally.dev vs Wizard on Demand](https://www.literally.dev/compare/wizard-on-demand): A Wizard on Demand alternative for devtool companies. Two European technical content firms; one measures AI visibility and publishes its price. Where each is stronger. - [Literally.dev vs Draft.dev](https://www.literally.dev/compare/draft-dev): A Draft.dev alternative for devtool companies. Engineer-written content, owned AI visibility measurement, published pricing. See where each one is stronger. - [Literally.dev vs Hackmamba](https://www.literally.dev/compare/hackmamba): A Hackmamba alternative for devtool companies. A developer marketing generalist with no published program price vs an AEO specialist at $4,990 a month. ## Resources - [How to Get Your Product Into ChatGPT's Answers](https://www.literally.dev/resources/how-to-get-your-product-into-chatgpts-answers): ChatGPT builds recommendations from live third-party pages, not your homepage. Here is where it looks, who it listens to, and how to earn a mention. - [Docs That Perform in AI Search](https://www.literally.dev/resources/docs-that-perform-in-ai-search): AI answer engines don't read docs the way people do. Here is how to structure, chunk, and serve your documentation so ChatGPT and friends retrieve it and cite you. - [The Dev-Tool AEO Checklist](https://www.literally.dev/resources/the-dev-tool-aeo-checklist): Where do you show up when a developer asks ChatGPT for the best tool? A practical AEO checklist for dev-tool teams: measure, structure, earn citations. - [How Open Source Companies Actually Make Money](https://www.literally.dev/resources/how-open-source-companies-actually-make-money): In this guide, we break down OSS business models, monetization strategy, and draw a roadmap for turning open source adoption into revenue. - [How Literally.dev Created Growth Dashboards in PostHog for Hatchet](https://www.literally.dev/resources/how-literally-created-growth-dashboards-in-posthog-for-hatchet): Learn how Literally.dev implemented a privacy-friendly PostHog analytics system for Hatchet, aligning content, product usage, and revenue metrics. - [How to Build and Grow a Developer Community](https://www.literally.dev/resources/how-to-build-and-grow-a-developer-community): This guide explains why most developer communities on Discord die and how to build one that actually works. - [How Literally.dev Built a Technical Content Engine and Manages Content End-to-End for QA.tech](https://www.literally.dev/resources/how-literally-built-a-technical-content-engine-and-manages-content-end-to-end-for-qa-tech): Learn how Literally.dev helped QA.tech grow their online presence and convert developers faster. - [Developer Content Marketing Metrics & Interactive Charts](https://www.literally.dev/resources/measuring-developer-content-marketing-performance): See how to measure developer content with Dirty Pirate Metrics: which numbers to track at each funnel stage and what your dashboards should show. - [Dirty Pirate Metrics Guide for Tech Founders and Open Source Developers](https://www.literally.dev/resources/dirty-pirate-metrics-guide-for-tech-founders-and-open-source-developers): Learn the basics of Dirty Pirate Metrics, a practical framework for tracking growth and success of open-source tools beyond SaaS vanity metrics. - [Trust Technical Writers, Not LLMs](https://www.literally.dev/resources/trust-technical-writers-not-llms): Good documentation drives adoption, unsupervised LLMs create poor docs that cause churn. Skilled technical writers make the difference. - [How to Find the Right Developer Audience for Your Product](https://www.literally.dev/resources/how-to-find-the-right-developer-audience-for-your-product): Learn how to target the right developers, avoid generic content, and create technical posts that attract potential users. - [Marketing to Developers Done Right](https://www.literally.dev/resources/marketing-to-developers-done-right): Developer marketing isn’t a buzzword, it’s knowing the user, showing real value, and being transparent - [Developer Marketing Metrics That Actually Matter](https://www.literally.dev/resources/developer-marketing-metrics-that-actually-matter): Most dev marketers chase vanity metrics. Learn why your data’s flawed, what to track instead, and how to drive real product engagement. - [Developers Don’t Want to Talk to Your Sales Team](https://www.literally.dev/resources/developers-dont-want-to-talk-to-your-sales-team): Developers won't book a call to try your product. Learn how to build a website that sells for you, and when a sales team actually helps. - [How Literally.dev Works with Clients](https://www.literally.dev/resources/how-literally-works-with-clients): From discovery call to distribution: the exact process we run with every client, step by step. - [How to Create a Plan for Reference Documentation](https://www.literally.dev/resources/how-to-create-a-plan-for-reference-documentation): Learn how to plan reference docs for APIs, SDKs, and CLI tools: what to cover, how to structure it, and how to keep docs useful as your product grows. - [How to Create a Technical Content Marketing Plan](https://www.literally.dev/resources/how-to-create-a-technical-content-marketing-plan): A step-by-step guide to building a technical content marketing plan: set real goals, know your audience, and plan distribution before you write. - [How We Write: The Literally.dev Style Guide for Technical Content](https://www.literally.dev/resources/how-we-write-the-literally-style-guide-for-technical-content): See how the Literally.dev style guide works: the style hierarchy, voice and tone rules, and why consistent writing builds reader trust. - [Technical Content Types and Deliverables](https://www.literally.dev/resources/technical-content-types-and-deliverables): See the content types Literally.dev creates, from tutorials to videos and docs, and the exact deliverables you get with each piece we ship. ## Optional - [llms-full.txt](https://www.literally.dev/llms-full.txt): This file plus the full text of every article. - [Privacy Policy](https://www.literally.dev/privacy-policy) - [Terms and Conditions](https://www.literally.dev/terms-and-conditions)