For people who publish long-form on X
Turn one good idea into everything you publish.
Pilcrow is the writing desk for long-form creators. Draft X Articles in a calm editor, schedule them to the minute, turn each one into threads, posts and a newsletter, and see what actually worked.
The demo is an isolated workspace with sample content. It never touches your X account.
The one-Article-a-week system
A calm pipeline from idea to published, in five short sessions.
Most creators do not have a writing problem. They have a pipeline problem: ideas arrive at random, drafts stall at 70 percent, and publishing happens whenever there is a spare evening.
Monday: pick from the backlog
Every idea goes into a backlog the moment it shows up. [[Add the example from last week]]
The progression
From a sentence in your head to a week of content.
01
“I have an idea.”
Capture it in a second. The backlog keeps the note that made it matter, tagged by topic.
02
“I can turn it into something worth publishing.”
Go from idea to headline, thesis and key points, then to a full draft in an editor built for long-form.
03
“I know when it will go out.”
Pick the minute in your own time zone. A checklist catches what is unfinished. You confirm exactly what goes out.
04
“I can get several pieces from one Article.”
A thread, standalone posts and a newsletter issue, made from your own sentences and fully editable.
05
“I can collaborate without losing control.”
Editors write, reviewers approve, and an approval is bound to the exact text it approved.
06
“I can see what worked.”
Your publishing rhythm, the posts that performed and the topics that carry, from data that actually exists.
Repurposing studio
One Article. A thread, posts and a newsletter, in your own words.
Pilcrow restructures what you wrote instead of rewriting it. Threads split on sentence boundaries and stay under X's weighted 280-character limit. Every piece stays linked to its source, so you know when the Article changed after you made it.
The thread on the right was produced by Pilcrow's own repurposing code from the sample Article above.
- 198/280
The one-Article-a-week system A calm pipeline from idea to published, in five short sessions. 1/4
- 2188/280
Most creators do not have a writing problem. They have a pipeline problem: ideas arrive at random, drafts stall at 70 percent, and publishing happens whenever there is a spare evening. 2/4
- 3196/280
Monday: pick from the backlog: Every idea goes into a backlog the moment it shows up. On Monday I pick one and write a one-sentence thesis. If I cannot write the thesis, the idea is not ready. 3/4
- 479/280
If this was useful, follow along. The long version is coming as an Article. 4/4
Honest publishing
We tell you exactly what happens at the minute you chose.
Nothing is marked published until it is. Nothing posts twice because a network call timed out. Nothing goes out that you did not confirm.
Assisted, live today
A reminder in Pilcrow and by email with the finished Article: formatted copy, images to download and a short checklist. You press Publish on X and paste the link back.
Automatic, built and waiting
X documents Article draft and publish endpoints. Pilcrow implements them, and switches them on only after paid API access and account eligibility are verified.
Coming upEurope/Ljubljana · UTC+01:00
09:00
Tue
The one-Article-a-week system
Assisted09:30
Tue
Teaser: the one-Article-a-week system
Waits for the link12:00
Thu
Thread: one Article, five pieces
Assisted
The details that make it trustworthy.
Daylight saving, handled
If 02:30 does not exist on the night clocks change, Pilcrow says so and offers the next valid time. If it happens twice, you choose which.
Every version, restorable
Autosave every few seconds, a version on every save, and one click to restore. A copy is kept in your browser if the connection drops.
Exact-content authorization
Scheduling records the precise text you confirmed. Edits afterwards are not published unless you confirm again.
Approvals bound to text
An approval covers the words it approved. Change a sentence and it clears automatically. Editors cannot approve their own work.
Evergreen without repeats
Recycle a strong Article with new angles on a weekly rhythm. Identical or near-identical posts are rejected.
No invented numbers
Analytics show what exists. Missing metrics say “not available”, and best-time advice waits until there is enough data.
Approved by Rowan
Any change to the text clears this approval.
- Sam requested a review
- Rowan requested changes: “The ending needs a question.”
- Rowan approved
For teams and agencies
Collaborate without losing control.
Owners, editors and reviewers, each with permissions enforced on the server. Comments on drafts, review requests, a full approval history and an activity log of everything that went out.
Free to use.
No subscription and no payment details. Write, plan, schedule and publish with assisted publishing, within fair-use limits.
- Editor with cover and inline images
- Full version history
- Templates and the content pipeline
- Calendar and scheduling
- Assisted publishing at your minute
- Repurposing and evergreen plans
- Review and approvals
- No X API needed
Questions
Does Pilcrow publish X Articles automatically?
Not for your account on pilcrow.pro. It needs an X developer app, X bills that app's owner for every request, and X's developer terms do not allow a hosted service to use your app's credentials. So Pilcrow uses assisted publishing: at the minute you chose, you get the finished Article ready to paste, and it counts as published once you confirm the link. Automatic publishing here is limited to the founder's own account.
What if X adds Article scheduling?
Then scheduling gets easier, and the rest of Pilcrow stays useful: the outline-to-draft workflow, version history, the pre-publish checklist, repurposing into threads and newsletters, review and approval, evergreen recycling and analytics. Scheduling is the entry point, not the product.
Will it ever post something I did not approve?
No. Every schedule records who confirmed it, when, and the exact content. Later edits are not published unless you confirm again. Evergreen plans run only after an explicit approval of every variant, and never repeat a post.
What happens to my X account tokens?
Signing in reads your profile and discards the tokens. If you connect an account for publishing, its tokens are encrypted with AES-256-GCM, never sent to the browser, and revoked at X when you disconnect.
What does it cost?
Nothing. Pilcrow is free to use, with fair-use limits so the free hosting it runs on is shared fairly. There is no subscription, and no payment details are collected. Pilcrow never asks you for X API keys either.
Which platforms besides X?
LinkedIn, Medium and Substack are planned. Articles are stored once in a platform-neutral format, with platform versions as separate drafts, so new destinations are adapters rather than a rebuild. None of them is connected yet.
Start the next paragraph.
Try the live demo