Byword vs US Tech Automations: Agency 2-Way 2026

Byword is an article-batch generator. US Tech Automations is a workflow layer that can hold, review, and publish those articles (or any other CMS object) once your own QA passes. They are not substitutes. Agencies lose money when they buy the second thinking they have bought the first.

Agency RFP win rate: 28% according to AAAA (2024). Inbound and relationship-led wins run higher (40–50%) in that study's usage note. A tool that only raises article count does not raise the 28% unless the articles are in a proposal someone can defend.

COMPARISON template earn rate: 17.8% according to first-party mix-config (2026), versus a 12.2% site base on 12,514 pages (941 COMPARISON pages), counted 2026-08-24. That is a mix figure, not a claim that this page outranks Byword.

Article mill versus workflow spine

Byword expands a title pattern such as "best {service} in {city}", writes long-form articles, and pushes to WordPress, Webflow, Ghost, Shopify, HubSpot, or Notion as draft, pending, or live. Higher plans can submit URLs to Google's indexing API. Prismic's 2026 programmatic-SEO roundup (HTTP 200) lists Byword Starter $99/month for 25 articles, Standard $299 for 80, Scale $999 for 300, matching the vendor pricing title fetched 2026-09-06 ("Plans Starting at $99/month"). Byword's about page (pack receipt, HTTP 200, 2026-09-04) claims 3M+ articles generated and 85K+ users — vendor claims, not our count.

The workflow product on pricing is scoped automation: Solo $96/mo (3 active flows), Growth $372/mo (5), Scale $1,371/mo (10), Performance custom. No per-execution fee on the public page. It does not write 80 articles.

TL;DR: Buy Byword when the deliverable is article bodies at a known cap. Buy a workflow seat when the deliverable is "draft stays draft until plagiarism, brand, and client approval pass." Many agencies need both. Some need neither — Google Docs plus a VA still ships retainers.

Who this agency comparison is for

SEO directors and ops leads at content-led agencies who already sell monthly blogs or programmatic article sets and are choosing whether to add a writer API, a publish gate, or both.

Red flags: Skip Byword Scale at $999/mo if the retainer is four posts. Skip a $372 Growth flow if Byword's own draft status is the only gate you will honor. Skip both if the client still pastes into WordPress by hand and likes it.

Weighted criteria

Feature matrix with first-party earn rates

Marketing agencies are not in the vertical earn-rate table (financial 17.2, logistics 14.6, general_smb 13.8, saas 13.8, accounting 9.5, insurance 8.0, healthcare 8.7, mortgage 5.8). Use 10 as the mix-config default, not a vertical.

Byword Starter: $99/mo for 25 articles according to Prismic (2026), matching the vendor pricing title.

Byword pricing floor: $99/mo according to Byword (2026), from the live title on 2026-09-06.

Byword volume claim: 3M+ articles according to Byword (2026), plus 85K+ users on the about-page receipt dated 2026-09-04.

Byword public prices versus scoped flows

Byword Standard: $299/mo for 80 articles according to Prismic (2026). That is the second Prismic citation.

Workflow Solo: $96/mo according to the public pricing page (2026), 3 active flows.

The workflow layer would typically sit after Byword: pull the draft, run house QA, set WordPress post_status to publish only when the client Slack emoji lands. It should not replace Byword's writer.

Sibling comparisons on live URLs: Byword for SaaS companies, Jasper vs Byword for SaaS, Jasper vs Byword for real estate.

RFP win-rate context

The 28% AAAA figure is about new-business from RFPs, not about article velocity. If your pitch deck still cannot name a unique dataset, buying Scale at $999/mo will not move the 28%. If you already win on process, a visible QA gate (run history, reviewer, rollback) is the artifact procurement teams ask for.

Worked example: an agency with 12 retainers and a 28% RFP hit rate buys Byword Standard at $299/mo (80 articles). Each client gets 6 posts; 12×6=72, inside the 80 cap. A flow watches WordPress post_status=draft, waits for a 2-person QA (brand + facts), then publishes. Figures: 12 retainers, $299, 80-article cap, 72 planned posts.

DIY: Make or n8n can take Byword's export, post to WordPress, retry on 500s, and keep an execution log. You own idempotency (do not double-publish), access to the Byword seat, retention of drafts, and the escalation path when a client hates a batch. A proposed workflow design adds the two-person review and a rollback, prerequisites being REST credentials and a named editor. Details on pricing.

When NOT to use US Tech Automations: when Byword draft status is the only gate; when 5 free Byword articles are the whole test; when the agency already runs a mature n8n library and does not want a second orchestrator.

The homepage is the company root.

SOW language, QA, and an 80-article calendar

Agencies lose the 28% RFP (AAAA 2024) when the proposal cannot name the QA path. Write the SOW in two columns: what Byword will produce, and what will not go live without a human.

Byword column: Starter $99/mo = 25 articles; Standard $299 = 80; Scale $999 = 300; five free to test. Output is long-form bodies. Destinations include WordPress, Webflow, Ghost, Shopify, HubSpot, and Notion. Batches can schedule across 3–180 days (Prismic). Higher plans can ping Google's indexing API. Vendor about (2026-09-04 pack) claims 3M+ articles and 85K+ users — treat as vendor claims.

Gate column: Solo $96/mo is 3 active flows, 1 scheduled run/day per flow, 50 API calls/flow/day. Growth $372 is 5 flows. Scale $1,371 is 10 flows with hourly runs. The job is post_status, Slack ack, rollback, and a log. The job is not 80 first drafts.

Calendar for Standard $299 (80 articles): 10 retainers × 8 posts = 80 on the nose. 12 retainers × 6 posts = 72, which leaves 8 for experiments. 15 retainers × 6 = 90, which does not fit — buy Scale at $999 or cut the SLA. Do the math before the kickoff call.

QA checklist that belongs in the SOW: (1) brand voice against a one-page kit, not a vibe; (2) no invented statistics; (3) internal links to URLs that exist; (4) uniqueness vs the last three posts for that client; (5) Fair Housing / regulated claims if the client is in those verticals; (6) client emoji or ticket ID before publish. Prismic calls raw Byword output a first draft. Price the editor hour into the 35–40% margin world (that AMI range is a sibling post's lead stat; here it is context, not the bold).

Onboarding a writer to Byword: lock the title pattern, lock the CMS destination as draft, disable live publish on day one, and run the 5 free articles on a non-hero client. If two of five are unusable, Standard $299 will not save you. If five are usable after a 20-minute edit, Standard is the seat.

Client reporting: do not send "80 articles shipped" as the KPI. Send indexed share, converting URLs, and revisions. The 17.8% COMPARISON earn vs 12.2% base (941 / 12,514) is this site's mix, not the client's. Do not put it in their QBR.

When the client already has n8n: keep it if the graph already logs publishes. Adding Solo $96 on top of a working n8n library is how you pay twice for run history. Adding Byword without any gate is how you pay $299 for live typos.

Title-pattern risk: "best {service} in {city}" with no unique row is doorway-shaped. Byword will still write it. The gate should reject city pages that do not cite a local fact. That is editorial, not a feature checkbox.

Procurement: some RFPs ask for SOC2 and a named reviewer. Byword's article cap will not answer that. A scoped flow with a reviewer node might. Do not pretend otherwise in the 28% game.

Live siblings for the same vendor pair in other verticals: Byword for SaaS companies, plus the Jasper/Byword posts already linked above. Do not clone this page's TCO into those decks without re-checking stickers.

What to tell the client in week one

Tell them the writer and the gate are different invoices. Byword Standard at $299/mo produces up to 80 drafts. Those drafts are not live. Live is a post_status change after brand, facts, and uniqueness pass. If they want live-on-generate, they are buying doorway risk, not speed.

Show the 28% AAAA RFP figure as a reminder that more URLs do not win pitches. Show the 5 free Byword articles as the test. Show Solo $96 only if they asked who logs the ack.

Kickoff artifacts: title pattern, CMS destination locked to draft, editor named, uniqueness rule (no reused paragraph across cities), and a kill switch if two of five free articles fail. If the client refuses an editor, do not sell Scale at $999.

Monthly ops: generate in week 1, edit in week 2, drip in week 3, measure indexation in week 4. Do not generate in week 4 to "use the cap." Unused Starter capacity is cheaper than indexed thin pages.

When a client brings their own WordPress plugin writer, do not stack Byword on top "for volume." Pick one factory.

International sets: Byword supports many languages per Prismic's roundup. Still review in-language. A $299 seat does not include a native editor.

If the SOW is landing pages with a visual layout, Byword is the wrong factory (Prismic said so). Send them to SEOmatic or Prismic, not to Scale.

Agency lead-gen pages are not Byword's job. Those are usually few, designed, and sales-reviewed. Keep them out of the 80-article cap so you do not spend Standard on the homepage rewrite.

Document the run: article ID, client, editor, ack timestamp, live URL. That log is what procurement asked for. A spreadsheet works until it does not; the $96 flow is how you stop the spreadsheet from being the system of record.

Re-fetch byword.ai/pricing before renewal. This write saw a title starting at $99 on 2026-09-06 and Prismic's $99/$299/$999 ladder. If the ladder moves, the 80-article calendar moves.

Renewal meeting: bring the indexed share, the editor hours, and the unused cap. If Standard $299 shipped 40 usable articles and 40 rewrites, the seat is not the constraint — the dataset is. If it shipped 80 live typos, you skipped the gate. Name which failure you had. Do not "upgrade to Scale" as a ritual. Scale at $999 is 300 articles, which is a different agency than 80.

Handoff checklist: title pattern signed, CMS locked to draft, editor named, uniqueness rule written, 5 free articles scored, Standard $299 only after three of five pass, Solo $96 only if the ack must be logged across clients, Scale $999 only when 80 is a documented miss. The 28% RFP win rate does not move because you skipped that list. Keep the homepage link for the company story and the pricing route for a scoped gate — not as a replacement writer. If a client asks for "unlimited AI blogs," rewrite the SOW before you touch Scale. Unused capacity on Starter at $99 is cheaper than 25 indexed near-duplicates. That is the whole week-one speech, and it is how you keep the writer and the gate on separate invoices without pretending they are twins. Cities without a unique fact still do not get a URL, even on Scale. Editors still read the first twenty. Procurement still wants the log. None of that is a Byword feature checkbox, and none of it is optional if you sell programmatic sets. Write it down.

Key Takeaways

• Byword writes articles; the workflow layer publishes them after QA. Do not shop them as twins.

• Public Byword caps: $99/25, $299/80, $999/300, 5 free; vendor about claims 3M+ articles and 85K+ users.

• Public workflow seats: $96 / $372 / $1,371 with 3 / 5 / 10 flows.

• AAAA 2024: 28% RFP win rate (relationship-led 40–50%).

• First-party: COMPARISON pages earned 17.8% vs 12.2% base on 12,514 pages.

FAQ: Byword versus a publish gate

Is this a 2026 bake-off between writer and gate?

No. One generates copy. One orchestrates the path to live. Score them on different jobs.

How do I read the two public price lists?

Byword $99 / $299 / $999 for article caps. Workflow Solo / Growth / Scale $96 / $372 / $1,371 for flow caps. A Standard + Solo stack is $299+$96=$395/mo before people.

Should an agency buy the writer, the gate, or both?

Byword if the SOW is articles. A workflow seat if the SOW is controlled publish across clients. Both if you sell programmatic sets with a QA clause.

Does Byword replace an editor?

Prismic's roundup describes raw output as a first draft. Budget an editor regardless of the $299 seat.

Can Zapier stand in for the workflow seat?

Yes for a single client if you design retries, logs, and a human check. You still own access, retention, and maintenance. Multi-client SLAs are why agencies buy a scoped flow instead of a personal Make scenario.

What is the first experiment?

Run Byword's 5 free articles on one client, keep post_status as draft, and only then decide whether Standard $299 or a Solo $96 gate is the next invoice.