---
title: "How to win on daily.dev"
url: https://docs.daily.dev/how-to-win-on-daily-dev/
description: "How company pages grow on daily.dev: teach from your own work, write about your problem space, write it yourself and show up every week. With real posts from company pages that did well."
lastUpdated: "2026-11-19T13:40:00+02:00"
llmsTxt: https://docs.daily.dev/llms.txt
---

Developers open daily.dev to learn something or keep up with their field. The company pages that grow here publish posts a developer would read even if they never bought the product. This page shows what that looks like, with real posts from company pages.

## What works

**Teach something from your own work.** What you learned building your product is worth more to readers than the product itself. Share the problem, what you tried, what failed and the numbers.

**Write about your problem space, not your product.** Your readers care about the problem you solve. A post about that problem reaches developers who have never heard of you. Mention the product where it is part of the story.

**Give your take on news in your field.** When something changes in your ecosystem, explain what it means for developers, from your experience.

**Write it yourself.** Developers spot AI-written posts quickly, and the feed gives them limited reach. Your own experience, numbers and opinions are what make a post worth reading. See [Write in your own voice](/what-the-feed-recommends/#ai-written).

**Show up every week.** One good post a week builds an audience. Five posts in one week followed by silence doesn't.

## Posts that did well

- [How to De-Slop an AI-Generated Codebase](https://app.daily.dev/posts/5attel6t7) on the Builder.io page: a practical guide to a problem many teams have right now. 70 upvotes, 12 comments.
- [This Speech Model Went From 1.2GB to 178MB](https://app.daily.dev/posts/this-speech-model-went-from-1-2gb-to-178mb-psrvr0ooi) on the Better Stack page: a deep dive into someone else's technology. 115 upvotes.
- [Inaudio: offline dictation and read-aloud](https://app.daily.dev/posts/inaudio-offline-dictation-and-read-aloud-for-your-desktop-your-voice-never-leaves-your-machine-drcaoj6pk) on the JigJoy page: a launch told in the first person, about why the maker built it. 27 upvotes.
- [metamorph](https://app.daily.dev/posts/o5joia7r5) on the JigJoy page: an open-source tool developers can try in a minute. 12 upvotes.

## What doesn't work

- Posts that read as AI-written, even when the topic is good.
- Feature announcements and "why we built X" posts with nothing a reader can use.
- "X vs Y" and "X alternatives" pages written for search engines.
- Analyst reports and awards about the company.

<span id="get-help-from-your-agent"></span>

## Get help from your agent

On [daily.dev for Startups](/startups/), your coding agent can plan with you using the content strategy skill: it interviews you, reads your [weekly intel](/weekly-intel/) and saves a strategy for what your page publishes. The other [agent skills](/startups-agent-skills/) then suggest ideas from it, review your drafts and report on how it's going. They never write posts for you.

## Related pages

- [What the feed recommends](/what-the-feed-recommends/)
- [Content guidelines](/content-guidelines/)
- [Agent skills for Startups](/startups-agent-skills/)