5
4 Comments

We built a scheduler that argues with its own AI

Postlia is a social media scheduler: write a post once, tailor the caption per platform, schedule it to LinkedIn, Instagram, TikTok, Bluesky and more. That part is table stakes, and we know it.

The part we actually care about: AI made publishing cheap, and feeds are filling with text nobody really wrote. So we built the product to push back on itself. First Draft plans your posting week from your own ideas and past posts, in your voice. Then the AI Slop Detector scores every draft for how machine-written it sounds before you publish. Our own AI gets graded by our own detector. The rule set is deterministic and public on our site, not another LLM guessing.

Where we are, honestly: live product, paying plans ($29/$49), a handful of users, and a distribution playbook we're grinding through one directory at a time (this page is part of it). Bootstrapped, two founders, no employees.

Also on the site: 25+ free tools (username checkers, bio generators, best-time data), no signup. They're the top of our funnel and free forever.

Happy to answer anything about the scheduling APIs (TikTok's approval process deserves its own post), the slop-scoring rules, or what it's like marketing a scheduler using the scheduler.

posted toAvatar for product Postlia
Postlia
  1. 2

    Git saves the code, but not the invisible environment around it.

    The AI agent memory angle is especially interesting as more developers rely on local context. Curious whether you see Densar as a backup tool or a migration workflow.

  2. 1

    “Simple value prop. Curious though — what makes someone stick vs using native schedulers on each platform?”

    1. 1

      Honest answer: if you post to one network, use the native scheduler, we are not for you.

      The stick is multi-platform. Native tools each solve their own silo: Meta Business Suite, TikTok's scheduler, LinkedIn's button, and Bluesky has no scheduling at all. That's four tabs, four calendars, captions retyped with different limits, no view of your week.

      With us the whole week lives in one calendar, captions stay in sync in one composer, and First Draft drafts the week from your own past posts for you to approve. People come for the cross-posting, stay for the calendar habit. Going back to four tabs feels like a downgrade

      1. 1

        That positioning is sharp — ‘we’re not for you’ actually makes the value clearer.

        The multi-platform pain is very real, and the habit loop angle is strong.

        What we’ve seen though: people adopt for consolidation, but stick when one platform becomes their default creation layer, not just a bridge.

        Curious if users are actually composing inside your tool first, or still drafting elsewhere and pushing in — that usually determines long-term retention.