BYstudio
RU/EN
Back to selected work

PRODUCT / AI / Web products

ContentOS

Plan and approve content for several brands in one workspace.

BYstudio’s role
Product design · Interface engineering · Workflow
Status
Published project
Request a walkthrough

Explore and discuss the product

A public demo uses fictional data to show topic selection and three text variants. Demo changes are not saved. Discuss live sources, AI and publishing connections separately.

Illustrated editorial workflow. The public demo uses fictional data.Original screen

The challenge

Each brand has its own topics, voice and schedule. Editors need to review material and see what has been approved.

Solution

We built a brand workspace with a content queue, editor and calendar. Text moves through review and approval. AI helps draft it using the brand’s topics and examples.

A source becomes a publication.

From context and a topic to editorial review.

Sources

Sources

Collect context for the next topics.

Topics

Topics

Choose a topic and prepare variants.

Review

Review

Review meaning and tone before publication.

System architecture

Brand context
Topics, tone of voice, sources and writing examples.
Content workflow
Draft preparation and structured context for AI.
Editorial queue
Editing, review and approval.
Planning
Batch actions and a calendar.

What we delivered

  • Brand workspaces
  • Content queue and editor
  • Review, approval and batch actions
  • Calendar and AI workflow

Why this approach

  • Use the brand as the core context so different businesses’ content stays separate.
  • Keep draft, review and scheduling as distinct states so each transition can be checked.
  • Treat integration readiness separately from content readiness. Publishing depends on connected accounts and configuration.
  • AI workflows require a configured provider; the local workflow and editor are not presented as proof of live generation.

Result

The workspace is deployed. Brand content can be edited, reviewed, approved and scheduled. External publishing requires the relevant service connections. An anonymous public demo uses fictional data. Live workspace access is discussed separately.

Tools and technology

ReactTypeScriptVitePostgreSQL

Discuss ContentOS?

The initial task discussion is free. Describe it in your own words. A BYstudio specialist or Yan Bunin will respond.

  1. Read your description.
  2. Clarify the goal and constraints.
  3. Suggest the scope of the first stage.

For example: @username, a phone number or name@company.com

Describe your use case. We will clarify terms and access together.

Add a detail (optional)

Please do not send passwords, tokens, customer databases or bank files.