Writing and content decision
Letterdrop
A small team can build a useful Letterdrop-like minimum (editor + schedule + a couple of channel integrations + simple analytics); there are no evident durable moats on the pages and open-source prior art exists to shorten implementation.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Letterdrop alternatives, with the arithmetic →
What a replacement has to do
- Create content in an editor, schedule/publish to channels, store content and metadata, and view basic engagement metrics
What it still won’t have
- Polished multi-channel native integrations and breadth of supported platforms
- Proprietary analytics/attribution features and enterprise reporting
- Customer support, onboarding, and enablement content
- Polish, UX refinements, and QA across many edge cases
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Letterdrop does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted content marketing service using Node.js (Express), Postgres, Redis (for queue), and S3-compatible storage. Implement: (1) a browser rich-text/markdown editor that saves drafts to Postgres, (2) a scheduler and background worker (BullMQ) that publishes posts via WordPress REST API and LinkedIn API, (3) asset upload to S3 and versioning metadata in Postgres, (4) a lightweight analytics collector endpoint that records UTM-click events into Postgres and exposes aggregate endpoints, (5) basic web UI to create/schedule/list posts and view per-post views/clicks. Out of scope: multi-tenant billing, proprietary AI-powered content generation, enterprise SSO, and a long list of third-party channel adapters. Include unit tests for publish worker and API routes, input validation, error handling and retry logic for failed publishes, and a Docker Compose dev setup.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 4 cited sources+3
- Evidence score60
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 4
Every page the run actually retrieved.
- official productLetterdrop - Competitor Intent
- official pricingLetterdrop - Pricing
- open sourcestrapi/strapi
- open sourcepayloadcms/payload
Integrity checks
What held up, and what did not.
