// share.gitpitcher.com
Git PitcherLaunch Plan WebpageShared artifact
April 23, 2026
Stirling-Tools/Stirling-PDF★ 77,609TypeScript

Go-to-market action plan

Ship a self-hosted, privacy-first PDF workspace that edits, signs, redacts, converts, OCRs, and automates PDFs from one Docker run or desktop app.

Position the product and pick the launch wedge

This version is optimized for action. It leans into first-week sequencing, channels, messaging, and what to measure once the product is live.

Launch days

7

Channels

6

Day 1 tasks

4

Success metrics

5

Launch brief

Launch brief

Pricing recommendation

Start at $29/month for the smallest paid server plan, because the clearest paid value is private deployment support, SSO/auditing, and operational convenience for teams already self-hosting but needing reliability and admin features.

Outreach target

The first 50 users should be small-to-mid-sized IT teams, privacy-sensitive consultants, and engineering-led organizations that already self-host Docker or Kubernetes and process PDFs internally. Prioritize firms in healthcare, legal, finance, education, and agencies where document upload to third-party SaaS is a blocker. Best triggers are: migrating off Adobe or paid PDF SaaS, new compliance or data residency requirements, repeated manual PDF tasks (merge/split/sign/redact/OCR), and a desire to expose internal PDF tools through a private API or no-code workflow without adding another vendor.

First week

First-week rollout

Day 1

Position the product and pick the launch wedge

  • Audit README.md, docs/stirling.png, and docs.stirlingpdf.com links to extract the three clearest value props: self-hosted privacy, 50+ tools, and automation/API.
  • Create a launch landing page draft that leads with `docker run -p 8080:8080 docker.stirlingpdf.com/stirlingtools/stirling-pdf` and the no-external-services/privacy promise.
  • Define the first use case to market first: IT/admin teams and consultants who need secure PDF processing without Adobe or SaaS upload risk.
  • Pull screenshots from `images/home-light.png` and 1-2 tool flows from the app to support the hero and feature sections.
Day 2

Build the conversion page and demo path

  • Write a one-page site around the existing docs: headline, subhead, CTA, and a short feature block focused on browser, desktop, and self-hosted server.
  • Add a quick-start section that mirrors README.md and `Taskfile.yml` onboarding: Docker, desktop, and docs links.
  • Record a 60-90 second demo showing merge, redact, sign, and OCR from the UI, and embed it prominently.
  • Add trust signals from repo signals: 77k stars, 100 contributors, OpenSSF Scorecard badge, Discord, and recent releases v2.9.x.
Day 3

Package the launchable offer

  • Decide the offer split: free open-source self-host + paid enterprise/server plan tied to SSO, auditing, and deployment support already referenced in README.md and docs.
  • Draft a simple comparison of community vs server plan using only supported capabilities from docs/README, avoiding unsupported claims.
  • Create a starter onboarding checklist for new users: install via Docker, open localhost:8080, try merge/split/sign/redact, then enable API or workflows.
  • Prepare a FAQ for common objections: data privacy, deployment, supported languages, and whether it can run on-prem.
Day 4

Acquire early users from existing communities

  • Post the launch in the project Discord, GitHub Discussions/issues, and relevant self-hosting communities with the demo video and one-click Docker command.
  • Target admins and developers who already search for `pdf-tools`, `pdf-editor`, `pdf-ocr`, `docker`, and open-source alternatives to Adobe/Smallpdf.
  • Open a short feedback form linked from the landing page to capture deployment type, top task, and blockers during first use.
  • Create a pinned GitHub Discussion asking for the top 3 workflows people want automated with pipelines/APIs.
Day 5

Turn repo signals into proof

  • Surface the strongest recent work in release notes and social copy: file sharing, group signing, desktop no-login, thumbnail regeneration, and PDFium thumbnail rendering.
  • Add a changelog-style section on the landing page that highlights active development from the last 30 days and frequent releases.
  • Use issue backlog signals (#6140 side-by-side PDFs, #6147 compression network error, #6153 redact bank PDFs) to show responsiveness and invite testers.
  • Prepare a short thread or post showing before/after on compare tool, OCR, and signing with explicit mention of self-hosted privacy.
Day 6

Launch and support

  • Publish the landing page and announce the launch across GitHub README, Discord, LinkedIn, Hacker News/self-hosted forums, and relevant Reddit communities.
  • Monitor install issues around Docker, desktop, and API auth; reply with exact commands and docs links from the repo.
  • Triage early feedback into three buckets: install friction, missing workflow, and performance/compatibility bugs.
  • Collect testimonials from first adopters who use the app for internal document workflows, scanning/OCR, or client-facing PDF edits.
Day 7

Iterate and lock in retention

  • Update the homepage copy based on the most-clicked CTA and most common use case from first users.
  • Ship one follow-up improvement that reduces activation friction, such as clearer quick-start, better sample files, or a workflow template.
  • Publish a short launch recap with installs, active demos, top requested feature, and next planned improvements.
  • Set a weekly cadence for releasing bug fixes and small UX wins, using open issues and recent release patterns as the roadmap input.

Messaging

Landing page messaging

Headline

The open-source PDF platform you can self-host in one Docker command

Subhead

Edit, sign, redact, convert, OCR, and automate PDFs on any device without sending documents to external services.

CTA

Start with Docker

Feature line

• 50+ PDF tools for merge, split, sign, redact, convert, OCR, compress, compare, and more • Runs in browser, desktop, or self-hosted server with private API • No external document upload; built for privacy and on-prem use • No-code workflows plus REST APIs for automation • 40+ languages and active community support

Channels

Distribution channels

GitHub README + Releases

Rank 1

The repo already has massive star traffic and release momentum; converting that attention with a clear CTA is the highest-intent channel.

Discord community

Rank 2

Existing users and contributors can validate the launch quickly, surface bugs, and spread word-of-mouth to self-hosting peers.

Self-hosting and DevOps communities (Reddit, Hacker News, forums)

Rank 3

The privacy-first, Docker-first positioning fits audiences actively looking for open-source replacements for SaaS PDF tools.

LinkedIn / IT admin outbound

Rank 4

Admin, compliance, and operations buyers care about on-prem PDF workflows, SSO, auditing, and data control.

Product Hunt

Rank 5

Useful for broad awareness and indie traction, especially with a polished demo of browser + desktop + self-hosted modes.

Open-source directories and alternative lists

Rank 6

High-converting long-tail discovery from users searching for PDF editors, OCR, and redaction tools.

Metrics

Success metrics for day 7

  • 50+ unique landing page signups or waitlist joins
  • 20+ successful Docker installs or demo completions
  • 10+ actionable feedback submissions from target users
  • 3+ public testimonials or quotes from early adopters
  • 1 launch post or thread reaching 1,000+ impressions or equivalent community views
    Launch Plan · Stirling-Tools/Stirling-PDF