About CarryFeed
Built around visible work, not growth promises.
CarryFeed brings your X drafts, Voice Memory, content calendar, and Growth Insights together in one browser workspace. Write and plan your posts, then see what gets a response.
What CarryFeed keeps
-
01
Voice Memory
The preferences, examples, hard rules, and banned phrases you explicitly save.
-
02
Saved revisions
The exact Post, Longer Post, or Thread revision selected for later work.
-
03
Calendar
Prepared times, scheduled content, timezone, and the current delivery state.
-
04
Exact confirmation
The account, revision, media, time, timezone, and action bound to approval.
-
05
Delivery state
Scheduled, published, failed, or reconciliation-required outcomes that need attention.
The source, point of view, final wording, timing, relationship choices, and whether anything is published.
- One connected X account
- Supplied static images
- No engagement automation
Your writing and schedule, in one place.
Open your saved drafts, organize your calendar, and check delivery from the same CarryFeed workspace. Your work stays available when you return.
What exists today
This register describes the launch contract. It separates a supported workflow from the boundary beside it.
Write, plan, and review your X content in your browser.
Sign in to keep your drafts, preferences, and calendar in one CarryFeed account.
Create and review a Post, Longer Post, or Thread with optional Voice Memory.
Voice Memory changes only when you explicitly save or restore it.
Review supplied JPEG, PNG, and WebP images with crop and alt-text guidance.
GIF and video publishing are outside the current Growth promise.
Inspect one calendar, prepare a time, and approve scheduling or publication.
The launch workflow supports one connected X publishing account.
Read a 30- or 90-day public-history report with coverage and freshness beside it.
It is not private X Analytics, complete X coverage, or a forecast.
Use research and writing support while keeping the final point of view.
No auto-reply, auto-follow, like, direct-message, or guaranteed growth.
Proof, not promises.
The most credible explanation is the one you can inspect. These pages own the price, data handling, responsibility, evidence standard, and public-source boundary.
Built by Chris Bennett
CarryFeed is an independent product. I use failed links, partial results, delivery exceptions, support questions, and changes in public source behavior to decide what to improve next.
When a capability, dependency, or boundary changes, the public contract should change with it, rather than stay frozen as marketing copy.
Tell me where the workflow broke- Product contract reviewed
- September 13, 2026
- Contact
- contact@carryfeed.com
- Ownership
- Independent product
The work is visible. The decision stays yours.
Start with the product contract, then open CarryFeed when the workflow matches the way you want to work.