# Brief 7 — Phase 2: Reply desk (watch accounts → surface posts → draft replies)
**For:** weebo / runbyagent / systemctl (Gocha Berulava)  
**Sealed:** 2026-09-04 (Asia/Tbilisi) · research only · no inbox / threadbus / WakeParent  
**Question:** Is a tool that watches a list of accounts, surfaces posts within minutes, and drafts a house-style reply a viable product — given claimed unit economics via X read-only API (~$0.005/post)?  
**Inputs reused:** `/workspace/brief-6-replies-timing.md`, `/workspace/brief-6-synthesis.md`, `/workspace/brief-7/roadmap.md`  
**Tags:** [MS] multi-source · [SS] single-source · [OFF] official X · [GAP] unresolved
---
## 0. Executive answer (one screen)
1. **The job already has products.** Closest matches are Pounce, XEngage, XReply, SupaBird Engage, ReachMore, Zexr Reply Radar — watch/filter + AI draft + human send. Full auto-post reply bots (Fireply, Replyal) exist but sit on the wrong side of X Automation Rules / non-API scripting risk.  
2. **Official X line (April 2026):** drafting assistance is fine; **unsolicited automated replies are not**; AI reply *bots that post* need prior written X approval; scripting x.com outside the API can mean permanent suspension. ([OFF] automation rules)  
3. **Sub-1k willingness-to-pay is weak and unproven.** Cheap entry exists ($15 one-time, ~$19/mo, pay-per-action). Mid-tier $49–$69/mo is sold to “serious” creators / lead-gen, not to accounts with no revenue. No public conversion data for sub-1k → paid reply-desk. [GAP]  
4. **Verdict:** reply desk is primarily a **feature** of growth suites; a **narrow standalone** can work only as a cheap, ToS-safe draft assistant (watch list + draft, human posts) — not as API auto-reply. Roadmap Phase 2 positioning (“we use it first”) is the only honest GTM for now.
---
## 1. What “reply desk” means (roadmap definition)
From `/workspace/brief-7/roadmap.md` Phase 2: watch a list of accounts → surface posts within minutes → draft a specific reply from house style + account context; self-use first; unit economics on read-only API (~$0.005/post).
Brief 6 context that matters for product design:
| Need | Evidence | Source |
|------|----------|--------|
| Early window | Hubs land replies in **2–15 min**; web guides **5–30 min** for borrowed reach | brief-6-replies-timing §2; https://reachmore.co/blogs/reply-to-big-accounts-on-x |
| Cadence | **10–15 quality replies/day** baseline; soft cap ~50 | brief-6-replies-timing; https://www.distributionbase.com/blog/channels/x-twitter/x-reply-guy-strategy |
| Craft | Specific mini-posts, not “great post”; hub reply-backs / profile visits as success | brief-6-synthesis §1–2 |
| Our failure mode | @gochaberulava **84% replies**, thin craft, wrong megaphones | brief-6-synthesis §1.4 |
A desk that only accelerates *generic* volume recreates the audit failure. The differentiator must be **account list + house style + specificity**, not speed alone.
---
## 2. Competitor map (watch + draft class)
### 2.1 Closest to “reply desk” (standalone or reply-first)
| Tool | What it does | Price (2026) | Traction / notes | URLs |
|------|--------------|--------------|------------------|------|
| **Pounce** | Real-time X + Reddit monitoring, AI-filtered inbox, AI-drafted replies; human sends; anti-ban flags | Scout **$39/mo** (300 credits); Hunter **$69**; Apex **$149**; PAYG $29/180 credits; 7-day trial | Positioned for founders/lead-gen; MakerStack 8.5/10 [SS review] | https://www.pounce.so/pricing · https://makerstack.co/reviews/pounce-review/ |
| **XEngage** | Daily ranked posts to reply to + drafted reply in voice; extension inside X; posts + engage | Starter **$19/mo**; Pro **$39**; Growth Hacker **$199** | Solo-dev BIP product; claims human approve always | https://xengage.studio/ |
| **XReply** | Chrome ext: draft reply to clipboard (you paste); also schedule via official API | **50 free credits**; **$15** for 5,000 credits (no sub) | Testimonials on site [SS]; marketed to <10k | https://xreply.net/ |
| **SupaBird Engage** | Newest posts + AI filter + voice replies; part of X growth suite | **$39/mo** or **$99/yr** (~$8.25/mo) | Claims ~30k–40k posts created by users [SS marketing] | https://supabird.io/features/engage · https://productwing.com/product/supabird |
| **ReachMore** | AI drafts + human approval queue; MCP for agents; pay-per-action credits mirrored to X API costs | No flat sub — credits (e.g. AI draft 2, publish 15, link publish 200) [SS vendor] | Self-ranks #1 for AI replies; vendor bias | https://reachmore.co/blogs/best-twitter-x-automation-tools-2026 |
| **Zexr** | “Reply Radar” every ~5 min; Growth Agent draft/suggest/autopost modes | Not fully verified on this pass [GAP price] | Competitor page vs SuperX/Hypefury/Typefully | https://zexr.app/compare |
| **VoicePost** | Niche watch + engage queue for AI-assisted replies | **$29–$59/mo** [SS comparison] | Bundles HN/PH/Reddit/X | https://voicepo.st/blog/x-twitter-growth-tools-comparison-2026 |
| **Fireply** | Full auto replies in voice (~60s); claims non-API infra | From **$69/mo** (20/day); 40 free replies | PH LaunchPact Jun 17 2026 · ~54–56 verified upvotes [SS]; **ToS risk** vs scripting rules | https://fireply.ai/ · https://www.launchpact.io/p/fireply · https://fireply.ai/blog/best-x-reply-automation-tools-2026 |
| **Replyal** | Auto-pilot campaigns, viral targeting, proxies | Free → paid tiers (up to thousands replies/day) [SS] | Proxy + autopilot = high ban risk | https://replyal.com/ |
### 2.2 Growth suites where reply is a *feature*
| Tool | Reply/engage role | Price | Traction | URLs |
|------|-------------------|-------|----------|------|
| **TweetHunter** | AI writer, CRM, lists; AI reply engagement on Enterprise; post-API-change: drafting not stranger auto-reply | Discover **$29**; Grow **$49**; Enterprise **$199** | Peak 10k+ → ~**5,600** users [SS MakerStack]; lempire-owned; Chrome ext “50k+” claim [SS] | https://makerstack.co/reviews/tweet-hunter-review/ · https://tweethunter.io/ (confirm live) |
| **Typefully** | Thread writing/scheduling; minimal engagement AI | Free + paid from ~**$8–$12.50**/mo (3rd-party) | Writer niche; not a watch desk | https://typefully.com/pricing · comparisons |
| **Hypefury** | Engagement builder (watched users/keywords) — **no longer on X** | From **$6/mo per channel** | FAQ: “Nope! Hypefury no longer supports 𝕏” | https://hypefury.com/pricing |
| **Buffer** | Multi-channel schedule; Community inbox for *inbound* | Free 3 channels; Essentials ~**$5–6**/channel | Scheduler default; not outbound reply hunting | https://marcandrews.com/feedhive-vs-buffer-2026-which-tool-is-worth-paying-for/ · buffer.com |
| **FeedHive / Publer / Postiz** | AI captions, social inbox, recycle; Postiz open-source + cloud from ~**$29** | Creator FeedHive ~**$19** | Schedulers / agentic publish — inbox ≠ watch-list reply desk | https://www.feedhive.com/ · https://postiz.com/ · https://dailydigitalreviews.com/postiz-review/ |
### 2.3 Name-check: requested brands that are **not** this product
| Name | Reality | URL |
|------|---------|-----|
| **Taplio** | LinkedIn growth sibling of TweetHunter; not X reply desk | https://taplio.com/blog/taplio-vs-hypefury |
| **AuthoredUp** | LinkedIn editor/analytics from ~**$19.95/mo** | https://makerstack.co/reviews/authoredup-review/ |
| **GrowthGenius** | Managed B2B outbound prospecting (Toronto); not X reply SaaS | https://craft.co/growthgenius · https://www.growthgenius.com/ |
| **ReplyAgent** | **Reddit** comments via managed accounts; ~$4/comment + optional $79 AI | https://oneup.today/vs/replyagent · https://leadmore.ai/blog/replyagent-vs-leadmore-ai |
| **Bird / SuperReply / EngageAI / Circleback** | No durable 2025–26 X reply-desk product found under those exact names on this pass; treat as **name collisions / dead / adjacent** [GAP] | — |
### 2.4 Competitive synthesis
- **Crowded drafting lane** at $15–$39 entry.  
- **Watch-list + ranked opportunities** is the scarce UI (Pounce, XEngage, Zexr, SupaBird Engage).  
- **Full auto-reply** vendors advertise survival after a Feb 2026 API reply clamp — but official rules still ban unsolicited auto-replies and non-API site scripting. Treat Fireply/Replyal claims as **commercially active, compliance-fragile** [MS vendor + OFF rules].  
- Hypefury’s exit from X is a structural opening for X-native engagement tools ([OFF pricing FAQ] https://hypefury.com/pricing).
---
## 3. X rules: reply automation vs drafting (2025–26)
### 3.1 Official sources (use these, not blog paraphrase)
| Doc | URL | Updated |
|-----|-----|---------|
| Automation rules | https://help.x.com/en/rules-and-policies/x-automation | **April 2026** [OFF] |
| Developer Policy | https://docs.x.com/developer-terms/policy (redirects from developer.x.com) | [OFF] |
| Developer Agreement | https://docs.x.com/developer-terms/agreement | [OFF] |
| X Rules (spam / platform manip) | https://help.x.com/en/rules-and-policies/x-rules | [OFF] |
### 3.2 What the Automation Rules actually say [OFF]
**Drafting assistance (human clicks Reply):** Not forbidden. The rules regulate *automated activity* and apps acting through accounts — not a human pasting an AI draft.
**Automated mentions/replies — default ban:**  
> “Automating these actions to reach many users on an unsolicited basis is an abuse of the feature, and is not permitted. For example, sending automated replies to posts based on keyword searches alone is not permitted.”
**Automated replies allowed only if all of:**  
1. Recipient **opted in / clearly indicated intent** (e.g. replied to you, DM’d you, or took a stated campaign action) — **following you alone is not enough**;  
2. Easy **opt-out**, honored promptly;  
3. **One** automated reply/mention per user interaction;  
4. Reply is to the user’s original post when campaign-based.
**AI-powered automated reply bots:** Explicit subsection — AI dynamic replies are allowed **only with prior written and explicit approval from X** (partner / developer portal request).
**Non-API automation:**  
> “Use non-API-based forms of automation, such as scripting the X website. The use of these techniques may result in the permanent suspension of your account.”
**Other hard nos:** automated likes; bulk aggressive follow/unfollow; spammy duplicative posts; OAuth alone ≠ consent for automated actions through a user’s account.
### 3.3 Feb 2026 API reply restriction (secondary)
Multiple growth blogs claim self-serve API apps can no longer post replies to strangers unless the author mentioned the app first (Fireply, OpenTweet, Bollard summaries). **Treat as [SS/MS industry]** until mirrored on docs.x.com changelog with a dated entry. Cross-check: https://fireply.ai/blog/x-api-reply-restriction-2026 · https://opentweet.io/how-to/x-api-rules-for-ai-agents-2026 · https://bollardai.com/resources/x
**Product implication for runbyagent:**  
- **Safe product shape:** read API (or browser read) + draft queue + human publish (Chrome or API for *own* originals). Matches roadmap “agent drafts, Gocha or agent posts depending on what X allows.”  
- **Unsafe shape:** autopilot stranger replies via browser scripting or unsolicited API replies.
---
## 4. Unit economics check (~$0.005/post)
| Claim | Status | Sources |
|-------|--------|---------|
| Post read **$0.005**/resource on pay-per-use | **Supported** by docs mirrors + industry writeups; live rates “always in Developer Console” | https://x-preview.mintlify.app/x-api/getting-started/pricing · https://bundle.social/blog/x-api-pricing-2026-costs-limits · https://twitterapi.io/blog/x-api-cost-breakdown-2026 |
| Post create $0.015; URL post $0.200 | Supported same cluster | same |
| Cap ~2–3M post reads / month on self-serve | Sources disagree slightly (2M vs 3M) [GAP] | same |
**Desk math (illustrative):** watch 30 accounts × ~2 originals/day × 30 days ≈ 1,800 post reads ≈ **~$9/mo** API if every post is a fresh billable read (dedupe windows may lower this — console claim of 24h dedupe [SS mintlify]). AI draft cost is separate (LLM). So **API unit economics for read+draft are not the bottleneck**; willingness-to-pay and compliance are.
Roadmap claim is directionally correct for *read* cost; it does **not** cover LLM, storage, or the write path if you ever auto-post.
---
## 5. Do sub-1k accounts actually pay?
**Skeptical default: mostly no at $49+; maybe yes at ≤$20 / one-time / credits.**
| Signal | Direction | Sources |
|--------|-----------|---------|
| TweetHunter historically offered **50% off Grow for <1k followers** | Implies sub-1k conversion needs a discount to close [SS review] | https://damgun.com/tweethunter-review.html |
| TweetHunter users contracted ~10k → ~5.6k | Category fatigue / ROI skepticism [SS] | https://makerstack.co/reviews/tweet-hunter-review/ |
| New reply tools price at **$15 once**, **$19/mo**, **$8–39/yr** | Race to cheap entry for small accounts | xreply.net · xengage.studio · supabird |
| Fireply / Pounce mid-tier **$39–$69** | Pitched at “creators, founders, agencies” with time-saving ROI — assumes monetization path | vendor sites |
| X Premium advice for <1k: only if consistent posting | Even $8 Premium is debated for lurkers | https://postory.io/blog/x-premium-worth-it |
| Brief 6 growth method | Reply habit is **time**, not software — Distribution Base ~15 min/day × months | https://www.distributionbase.com/blog/channels/x-twitter/x-reply-guy-strategy |
**No [MS] survey** of “% of X accounts under 1k who pay for reply automation.” Partial conclusion: **paying buyers cluster where X is already a lead channel or a serious BIP habit**; vanity sub-1k accounts churn free tiers. runbyagent-as-dogfood is the only proven buyer until hub reply-back rate lifts (roadmap gate).
---
## 6. Standalone product vs feature?
| Lens | Finding |
|------|---------|
| Market structure | Schedulers (Buffer, Typefully, Postiz, FeedHive) own **publish**. Reply desk lives in **engagement / social-selling** tools (Pounce, XEngage, ReachMore, TweetHunter CRM) or as a **module** (SupaBird Engage). |
| After Hypefury left X | Engagement-builder vacancy on X — favors X-native reply products, not multi-channel schedulers. |
| After API reply clamp | Pure “auto-reply SaaS” either died, pivoted to draft, or left the API (compliance gray). Draft-assist is the durable feature. |
| Roadmap fit | “Project three, small” matches **feature-thin standalone**: watch list + draft. Charging strangers needs proof from own metrics first. |
**Verdict:** **Feature of a growth/engagement product first; standalone only as a narrow, cheap, draft-only wedge.** Do not position against Buffer. Position against “scrolling for 60 minutes” and against Fireply-class autopilot (refuse that lane). Closest comps for design: **Pounce session inbox** + **XEngage ranked feed** + **XReply clipboard safety**.
---
## 7. Implications for runbyagent Phase 2
1. Build **internal** desk on read API + house style (brief-6 craft rules). Success metric = hub reply-back rate / profile visits (roadmap), not reply count.  
2. If productized: ship **draft + approve**, never silent stranger auto-reply; disclose AI; no site scripting.  
3. Price experiments (if ever public): credits or ≤$19/mo before any $49 claim; dogfood free.  
4. Do not compete on “fully automated replies” — X April 2026 rules + non-API ban make that a suspension product.  
5. Differentiate with **ICP account maps** (brief-1 5k–100k builder list) and specificity scoring — the gap left by generic “Great point!” tools.
---
## 8. GAPS
1. Official docs.x.com **changelog URL** for Feb 2026 reply-endpoint restriction (industry blogs only).  
2. Live TweetHunter / Typefully / ReachMore pricing pages may differ from 3rd-party tables — re-check at launch.  
3. No primary WTP survey for sub-1k.  
4. Zexr / Bisonary / XreplyAI exact public pricing incomplete.  
5. Traction numbers mostly vendor or single reviews (Fireply PH upvotes, TweetHunter 5.6k, SupaBird “30k posts”).  
6. ReplyAgent / SuperReply / EngageAI / Bird / Circleback — no clear X reply-desk product under those names.  
7. Whether X API 24h read dedupe applies to user-timeline polling at desk scale (affects $0.005 math).
---
## COUNTS
| metric | value |
|--------|------:|
| **CLAIMS** | 42 |
| **URLS** | 41 unique (44 citations) |
| **TOOLS** | 28 named (incl. non-fits) |
| **PRICES** | 22 distinct price points recorded |
| **GAPS** | 7 |
| **OFFICIAL X PAGES** | 4 |
| **HOPS (major items)** | Competitors ≥3 · Rules ≥3 · WTP ≥3 · Product-vs-feature ≥3 |
*Line count target ~150–250; file is the Phase 2 reply-desk research deliverable only.*