Ciny AI

The Ciny AI platform shows you what happens where.

Overwatch is the workspace the Ciny team uses to run the agreed marketing work.

Overwatch · Data Hub · Brand Social · Client Dashboard

Keep the context with the work.

The Client Dashboard gives you a focused view of content, planning, available reporting and requests. They serve different roles within the same operation.

Operators coordinate delivery in Overwatch. Client stakeholders review content, planning and available reporting through the Client Dashboard.

  • Data Hub: the approved business context
  • Modules: research and production work
  • Client view: feedback and next decisions

See the work.
Understand the next step.

Overwatch connects the work behind the scenes. Your Client Dashboard brings the relevant content, calendar, requests and available reporting into one view.

  1. Business contextAudience · offers · voice · evidence
    • Brand Social
    • SEO & AI Search
    • Website Optimiser
  2. Client DashboardContent · calendar · reporting · requests
01

An operating workspace and a client view.

Your team does not need to learn every production tool to work with Ciny. Internal operators coordinate the jobs and connections; client stakeholders review the work and supply business decisions.

These are parts of one operating model, not three unrelated subscriptions. The actual views and connected functions depend on the agreed scope and client setup. A feature name is not evidence that a particular account is already connected.

The main parts of the platform
AreaUsed forWho it serves
OverwatchClient setup, connected modules, jobs and reviewCiny operators
Data HubApproved facts, source material and brand contextWork within the client workspace
Client DashboardAvailable analytics, content, calendar and requestsClient stakeholders
02

The Data Hub gives work a business foundation.

A good draft needs more than a company name and a target keyword. The Data Hub holds the information that helps distinguish your offer: who it is for, how it works, the language you use and the evidence available for a claim.

Context is kept within the client workspace; it is not presented as a shared pool of all clients' information. Supplying a source does not eliminate the need to review its relevance to the particular asset. Avoid sending passwords or sensitive records as content material.

Facts and boundaries

Keep offers, exclusions and approved examples together. Identify claims that need a business owner to confirm them.

Voice and terminology

Record preferred language and explain specialist terms. Style guidance should not change the meaning of a technical statement.

Source material

Preserve the documents and context behind a useful example. Note when an input is historical, confidential or no longer accurate.

03

Brand Social runs in the Ciny Marketing Hub.

Brand Social runs in the Ciny Marketing Hub, which the Ciny team operates, and it appears under Modules in Overwatch for each client. It connects research, recurring planning, production studios, review, the content library and calendar. It is the wider content operation, not just a social scheduling screen.

R&D and The Loop

R&D turns research signals into briefs and weekly priorities. The Loop runs a daily production cycle and holds its output for review. A queued job still needs a completed output.

Evergreen and studios

Evergreen plans monthly ideas and keywords for recurring article, static and carousel production at fixed daily slots. Studios support individual pieces and revisions, and completed work can be reviewed and organised in the library.

The Eye and newsletters

The Eye is a panel of AI reader personas, 20 by default, that scores The Loop's content after it is written. It does not block publishing. Newsletter drafting is available. Neither feature replaces factual approval.

Publishing is review-first. A claims guard blocks critical claims by default, stock photos are screened by alt-text keywords, a keyword freeze holds blog drafts on terms under measurement and a publish ledger stops the same post going out twice within 24 hours.

Follow the Brand Social production workflow
04

Search findings can become page work.

The search area helps the team inspect available reporting and develop priorities. Website Optimiser supports page and link audits, performance investigation and discussion of proposed changes. These activities can inform the same brief.

Website reviews can distinguish Live, Draft and Code views. That distinction matters: a proposed draft is not a released website change. Audit coverage and implementation still need to be agreed, and not every page or workflow is automatically inspected.

From an audit finding to a reviewed change
05

Use the Client Dashboard for the decisions that need you.

The client view brings together captured enquiries, visitors and Search Console impressions with the content plan and a place to raise requests. Ask Ciny answers questions about the report on your screen and says plainly what it cannot see, such as revenue or qualified leads. Client approval that releases publishing is in build, so publishing is approved inside Ciny for now. Its purpose is to make the work reviewable without exposing every internal production step.

A useful request includes the page or asset, the question or correction and any source material needed to resolve it. If something is not reflected in the available reporting, ask what evidence is missing rather than assuming the value is zero.

How to interpret common work states
What you seeWhat to confirm
An idea or topicWhether its purpose and audience are right
A draft or revised assetWhether the actual text and visuals are ready
A planned calendar itemWhich revision and channel the plan refers to
A reported resultIts source, date window, filters and limitations
06

Agree capabilities before depending on them.

A connected workflow depends on its provider, permissions and deployed setup. Before starting, confirm which formats, channels, reporting sources and review responsibilities are in scope.

This service description does not promise autonomous advertising, completed video production, every social integration or verified citation monitoring across all AI systems. It also does not claim a security certification or a universal approval automation that has not been verified for the deployment.

For a buying decision, the useful questions are practical: what work will we receive, where will we review it, who will release it and which source will show the result? Those answers belong in the agreed engagement.

What to agree during onboarding

What the system delivers.

Start with six capabilities that have run on Ruh AI's own marketing and website.

Compare every capability and its status
Live

Posting Automation

Platform-specific captions and an approval-led publishing calendar.

Keep an agreed cadence without recreating the schedule for every channel. Publishing requires the relevant channel connection.

Live

Creative Automation

Static images and carousels using your brand pack.

Carry the same identity across formats while reviewing the actual asset before it is released.

Live

Content Automation

Article drafts, supporting visuals and relevant internal links.

Review a complete piece against its brief and sources, rather than assembling disconnected copy and assets.

Live

Keyword Discovery Automation

New Search Console queries listed at each sync, with brand-fit scoring available from onboarding.

Find relevant questions in your own data and assign them to useful pages. Withheld queries cannot be recovered.

Live

Rank Tracking Automation

Search Console average position per query, period comparisons, movers and lost keywords.

Identify changes worth investigating without treating a position change as proof of its cause. This is the averaged position Google reports, not a live rank check.

Live

Content Audit Automation

A saved audit of on-page basics, answer structure and thin content for each scanned page.

Plan work on existing pages before adding more. Refresh, merge and redirect verdicts are in build, so those decisions stay with your team.

Your account scope, connections and approval responsibilities are agreed before activation.

Newsletter drafting, brand-fit keyword scoring and the page-speed experiment loop for Next.js sites are available. Social reporting, on-page fixes and competitor research are in build. Scheduled email, video, Local SEO and automated AI-answer monitoring are planned.

A few good questions.

Prefer to talk it through? Email hello@ciny.ai.

Is Overwatch a self-service subscription?

The offer described here is a managed Ciny service. The team runs the operating workflows; client stakeholders use a focused view to review and coordinate the work.

Do we have to use all three modules?

No. Content, search and website work can be scoped separately. Connecting them is useful when the work genuinely overlaps.

Does the calendar prove that a post is live?

No. A planned or scheduled item describes a workflow state. Confirm publication using the actual channel or an appropriate delivery confirmation.

Will the dashboard include every analytics source?

Only describe reporting that is available for the connected setup. Confirm the source, coverage and filters; do not assume full attribution or every provider is included.

Start with your actual priorities.

Tell us what you sell, who you need to reach and where the work gets stuck. We can discuss the scope from there.