Ryyu Engine
Content ops built for the agentic web.
Ryyu Engine is the content ops infrastructure your team has been building around — research, planning, writing, review, staging, QA, publishing, and performance tracking. Claude runs 88% of it automatically. Gate tasks write back to your task manager. Your team approves at three gates. Na-Mii operates the rest.
Steps — research through performance tracking
Human gates — the only moments you’re needed
Minutes of your time per published piece
Ryyu Voice is the prerequisite. Before the Engine runs, your writing voice needs to be installed. Every piece the Engine produces is written in your configured voice — the one Na-Mii built in Phase 1. If you haven’t set up Voice yet, that’s where we start.
Task manager integration
Your content calendar
in your sprint.
Content plans fail when the calendar lives in Notion and the team’s work lives in Asana. Ryyu Engine writes deadlines and gate tasks directly into your task manager — automatically, as each gate opens and closes. Task manager integration is optional and configured on your discovery call. Gate approvals can also post to Slack — your team can work from either or both.
Gate 1 Passes
Full content calendar written to your task manager. Every piece in the approved monthly plan becomes a task — publish date, channel, brief link, assigned owner. Your team sees the full month the moment the plan is approved.
Gate 2 Opens
Draft review task created and assigned. Content lead gets a task with the Google Doc link, Review Board summary, and a 24h deadline. One click to review — no hunting for the
right doc.
Gate 3 Opens
QA approval task created. Piece is staged, QA report linked, deadline set. Approval closes the task and triggers publish.
Any gate passes
Task closed automatically. No manual status updates. Your task manager reflects where every piece is in the loop — without anyone touching it.
How it works
6 steps. 3 gates.
One continuous loop.
Claude handles the heavy lifting. Your team approves at every meaningful gate. Na-Mii operates everything else.
- CLAUDE
- AUTOMATED
- HUMAN GATE
- DESIGN
Automated research — SEO, GEO & AEO
Bi-weekly scan of keyword clusters, coverage gaps, ICP pain-point signals, competitor moves, and GEO / AEO opportunities. Strategy Layer surfaces fresh angles and unclaimed territory for the planning step.
Monthly goals & content plan
Claude cross-references upcoming launches, pipeline priorities, and last month’s performance to propose monthly goals and a full content calendar. Tasks write back to your task manager — Asana, Linear, Monday, Jira, Notion, or any other.
Approve the plan
Review goals and calendar in Slack or your task manager. Approve and production begins. Revise and Claude loops back to Step 02. Nothing moves forward without your sign-off.
Content production + review
Claude writes the full draft plus 3 visual concept directions in your Voice Engine. A 4-seat Review Board reads your comments and rewrites in-place. You leave comments; Claude applies them before Gate 2.
Approve the draft
Review the revised draft and Board Report in Slack or your task manager. Approve and staging begins. Revise and Claude loops back to Step 03.
Stage, QA, and score
Claude pushes to your publishing platform. Automated checks run SEO, AEO, GEO, and accessibility scoring. Design is briefed for graphics and data viz. Staged URL and QA score report generated.
Approve to publish
Review the QA report and staged version. Approve and it goes live. Revise and Claude loops back to Step 04. Nothing publishes without a final human sign-off.
Publish & confirm live
HTTP 200 check runs post-publish. Live URL logged back to Notion and your task manager. Slack confirmation sent to the team. Gate task closed.
KPI sync & performance
Weekly scorecard: performance against monthly goals, content surface insights, blind spot flags, and pivot signals. Output feeds directly back into Step 01 — closing the loop.
~35 min
Gate 1 (~15 min) + Gate 2 (~10 min) + Gate 3 (~10 min)
Team: 48h · Org + Enterprise: 24h priority
Na-Mii monitors APIs upstream. Patches deploy before your next gate opens.
Questions we get
Fair concerns.
Direct answers.
These come up in every conversation. We’d rather address them here
than in a follow-up email.
For the content owner
"I own content. I'm not letting a system write it for me."
Good — and Ryyu Engine doesn’t. Your team briefs every piece. They review and they approve QA at Gate 3. Nothing publishes without their sign-off. What the Engine replaces is the ops work around that judgment — scheduling, staging, chasing deadlines, QA checks, performance tracking. The creative calls stay with your team.
For the CMO
"I don't believe you can get me better content than my team."
We’re not trying to. Your team’s creative judgment is the product — Ryyu is the ops infrastructure that makes their output consistent at scale. The Engine means your content lead spends their time on strategy and judgment calls, not scheduling, staging, QA checklists, and chasing approvals. More output, same team, less overhead.
For the technical PMM
"When this breaks, my team will ask me to fix it."
That ticket belongs to Na-Mii, not your team. Model drift, integration failures, scheduling issues, platform API changes — that’s what the retainer covers. Na-Mii monitors the system and fixes issues before your team notices them. The maintenance burden that currently lands on whoever is most technical on your content team disappears. Your PMM never opens a support ticket for the Engine.
For the strategist
"Garbage in, garbage out. How do we make sure the input is good?"
This is the right question. Input quality is Na-Mii’s job, not yours. The Voice Engine is extracted from your team’s actual writing, not a brief document. The Strategy Layer surfaces ICP signals and competitor blind spots so every brief starts sharp. The 2-seat brief check (ICP Voice + Market Sentinel) runs on every brief before production starts — catching bad angles before they become bad drafts. The 4-seat Review Board runs on every draft before Gate 2. The system is only as good as its inputs — which we built loops around getting them right.
Pricing & investment
What it costs. What it recovers.
This isn't replacing writers, it's cutting the work that isn't writing.
Ryyu Engine eliminates the production work that surrounds every piece — scheduling, briefing, staging, QA, tracking. Your team keeps the calls that matter. The system handles the rest.
Series A–C content teams. Voice configured, Engine running, tasks in your sprint from day one.
one time setup Voice + Engine
/ month
- Everything in Ryyu Voice Team (1 voice, 5 channels, 10 configs)
- Ryyu Engine: full 6-step loop + Daily Pulse
- Task manager integration (Asana, Linear, Monday, Jira)
- 4-seat Review Board on every draft
- 3-month minimum
Series C–D organizations with multiple voices, channels, and a content ops function.
one-time setup — Voice + Engine
/ month
- Everything in Ryyu Voice Organization
- Task manager integration — full team assignment
- Strategy Layer — full activation suite
- 4-seat Review Board + Board Report on every draft
- Priority model drift recalibration
- 3-month minimum
Multi-team rollout, restricted stacks, custom SLAs.
Full scope set on a scoping call. Includes Tier E support
for restricted Claude Team environments — skills hosted
in Monday, manual trigger workflows, no shared projects
required.
- Custom platform + channel count
- Multi-team voice configuration
- Works within enterprise security requirements and restricted AI environments
- Dedicated Na-Mii account manager
- Custom SLA
- Skills hosted in restricted environments
- Custom trigger workflows
Setup at 50% ($1,750 Team / $3,750 Org), monthly at full rate, locked for 6 months. In exchange: a named case study, logo rights, and a biweekly feedback call. Invoiced at list with the beta credit shown.
All tiers include a 30-minute scoping call before any contract. Setup pricing assumes standard scope — platform and channel count confirmed on the call. All tiers run on zero-retention commercial API workspaces. Your data is never used for model training.
FAQs
Let's talk about your questions.
What is content operations?
Content operations is everything around the writing — research, planning, briefing, review routing, staging, QA, publishing, and performance tracking. Most teams have a writer and no ops layer, so the writer absorbs all of it. Ryyu Engine runs that layer as infrastructure, leaving the creative calls with the team.
Can AI run a content production workflow from research to publishing?
Yes, with human approval built into the workflow rather than bolted on at the end. Ryyu Engine runs six steps — research, planning, production, staging and QA, publishing, and analytics — with three points where a person approves before anything advances. Claude executes the steps; the team makes the judgment calls.
Does AI-generated content need human review before publishing?
Yes, and the review should sit at defined stopping points rather than at the end of everything. Ryyu Engine has three approval gates: the monthly plan, the draft, and the staged piece before it goes live. Nothing publishes without a person approving it, and any gate can send the work back a step.
What is a human approval gate in an AI workflow?
An approval gate is a point where the system stops and waits for a person to approve or send the work back. Without gates, review happens at the end, when fixing anything means redoing the work. Ryyu Engine’s three gates take roughly 15, 10, and 10 minutes and each one can loop the work back to the previous step.
How much time does automating content operations actually save?
Around 60 to 80 hours a month per content lead, based on the production work that surrounds each piece. Brief creation drops from three or four hours to a 20-minute review; QA and staging from two hours to 30 minutes. The writing time doesn’t disappear — the scheduling, staging, checklist, and tracking time does.
Can an AI content system write tasks into Asana, Linear, Jira, or Monday?
Yes. Ryyu Engine writes the approved content calendar into your task manager as individual tasks with publish dates, channels, owners, and brief links, then opens and closes gate tasks automatically as work moves. Asana, Linear, Monday, Jira, and Notion are supported, and approvals can post to Slack instead or in addition.
How do you keep AI content on brand when you scale up volume?
Voice has to be configured before volume increases, or you scale the drift. Ryyu Engine requires Ryyu Voice as a prerequisite: the voice is extracted from your team’s actual writing and installed into the model before any piece is produced. Every draft the Engine generates comes out of that configuration, not a prompt.
Do you need brand voice configuration before automating content production?
Yes — voice first, then volume. A production system without a configured voice produces more content that needs rewriting, which makes the problem larger rather than smaller. Ryyu Voice is the prerequisite for Ryyu Engine, and Voice setup fees credit toward the bundle if the Engine is added within six months.
How do you QA AI-generated content before publishing?
By running the checks automatically at staging, before a person looks at it. Ryyu Engine scores every staged piece on SEO, AEO, GEO, and accessibility, generates a report, and attaches it to the Gate 3 approval task alongside the staged URL. The reviewer reads a report instead of running a checklist.
What does an AI content operations system cost?
Ryyu Engine starts at $3,500 setup plus $1,200 per month for Series A–C teams, which includes Ryyu Voice configuration and the full loop. Larger builds run $7,500 setup plus $3,000 per month with multiple voices and full team task assignment. Enterprise scope is set on a call, and all tiers have a three-month minimum.
What's the difference between an AI writing tool and content operations infrastructure?
A writing tool produces a draft and stops. Content ops infrastructure covers everything before and after the draft — the research that decides what to write, the review routing, the staging, the QA, and the performance read that shapes the next cycle. Ryyu Engine runs the whole loop; the draft is one step of six.
Who maintains an AI content system when models and APIs change?
Na-Mii does. Model drift, platform API changes, integration failures, and scheduling issues are covered by the retainer, with a 48-hour response for Team and 24-hour priority for Organization and Enterprise. Na-Mii monitors the APIs upstream and patches before the next gate opens, so the ticket never lands on your team.
- WORK WITH US
Let's build something
that actually holds together.
No commitments. Just a conversation about where you want to go.
