Incubics

Products

Content Studio

Content Studio turns a brief into the piece. The same piece can be translated and read aloud. Nothing is published until a person says so.
Illustrative footage, Mixkit. Not a piece we have released.

Problems

What we solve.

  • Every article, campaign, script or social post starts from a blank page.

    A brief becomes a draft. The team can still edit it. Publish waits for someone named.

  • The same piece has to exist in another language, or as something a person can hear.

    Translation and narration stay with the draft. A reviewer checks the language. Someone listens before it is published.

  • Source files are quietly used to train a model other customers share.

    Files for this work are not used to train a shared model.

Tech stack

What we build on.

Open weights and paid models for the draft. The person who approves publish is not a model.

  • Llama
  • Mistral
  • Qwen
  • OpenAI
  • Anthropic
  • Gemini

Llama mark via selfh.st, CC BY 4.0.

What it does

Content Studio is a product for written work your team already knows how to ship. A brief goes in. A draft comes out in the shape of that brief: an article, a campaign, a script, a social set. The draft waits. A named person edits it and is the one who publishes.

Translation of that piece, and a spoken reading of it, live here. A live conversation — someone on a call, a lesson that listens and answers — is Conversation, not this product.

The brief

The brief is the job. Audience, channel, length, the claim you are allowed to make, the claim you are not, the source that must be respected, the words you do not use. A draft without a brief is a chat. We do not ship that.

Your team writes briefs in the form the app asks for. The form is short on purpose. If a field is empty, the draft does not invent it. It asks, or it stops.

  • Who it is for, and where it will appear.
  • The point of the piece, in one or two sentences you approve.
  • The source: a page, a note, a previous piece, a product fact.
  • Length, format and the lines that must appear.
  • What must not be said, including claims you have retired.

Voice and the pieces you already ship

The app learns the shape of your work from pieces you choose and from rules you write: how a headline works, how a caption works, how a script opens, which phrases are yours and which are banned. It does not invent a new voice on every run.

Those examples stay yours. They are not used to train a model we offer to anyone else. If you later want a model trained for this voice and kept as weights you own, that is Model Training.

Articles, campaigns, scripts, social

An article is a longer piece with a source and a structure: opening, argument, close. A campaign is a set: the line, the variants, the lengths each channel needs. A script is spoken-shaped writing, for a person or for a later narration. Social is the short form, still tied to the same brief so the short line does not contradict the long one.

The first release is one of these, the one your team ships most often. The others are later increments on the same brief and the same review. We do not open four formats on day one and leave review as a slide.

Translation

Translation is the same piece in another language, not a new piece that happens to share a topic. A reviewer who can read the language it lands in checks meaning, tone and the claims. A translation nobody qualified has read does not publish.

You name the languages in scope. The first release includes the language you publish in now, and at most the next language you already have a reviewer for. Further languages wait until that review is real.

Narration

A spoken version reads the approved words. Someone listens before it ships: the names, the numbers, the emphasis, the close. Narration here is a finished piece. It is not a live call. Live speech is Conversation.

Graphics for the same campaign — the picture, the layout, the crop — are Graphics Studio. Content Studio writes. Graphics Studio pictures. They can share a brief. They do not replace each other.

Review before publish

Every draft has a state: writing, in review, changes asked, approved, published. The app can hold a draft in any state except published. Publish is a person’s action, in the channel you already use or in the one we connect.

Version history keeps the brief, the draft, the edit and the approval. If a claim is later wrong, you can see which version went out and who cleared it. That record is part of the product, not an export you assemble afterwards.

Sources

A draft may start from a note, a previous piece, or a page Documents has already read and a person has checked. It may not start from a scan nobody has looked at. If the source does not support a sentence, the sentence does not stay.

We do not attach invented citations. If a fact needs a source and none was given, the draft marks the gap.

Who it is for

Marketing, media and product teams that already know what they need to say and need that saying to be repeatable. Publishers and newsrooms that want a draft in their structure, with an editor still publishing. Product companies that want this as an application under their own brand, for their own users.

What you get

  • An application tuned to your formats, your voice and your banned claims.
  • A brief the draft cannot ignore.
  • One content type in the first release, connected to the way you publish.
  • Translation with a named reviewer for the language it lands in.
  • Narration of the approved words, with a listen before it ships.
  • Human review, version history and a record of who published.
  • Your unpublished work kept out of any shared model.

What we will not ship

We will not ship an app that publishes without a named reviewer. We will not train a shared model on your unpublished work. We will not treat a chat window as a content system. We will not invent a quote, a customer or a number to make a paragraph close.

How it meets the other work

Documents supplies a checked page when the source is a scan. Graphics Studio supplies the pictures for the same brief. Conversation is the product when someone must speak live and be answered. Education Apps is the studio when the reader is a student and a teacher approves the lesson. Model Training is how a voice or a format becomes a model you keep.

The first release

One content type your team already ships. The brief for that type. The review states. A path into the channel you publish from. A small set of examples you chose, used only for this app. Translation or narration joins the first release only if you already have the reviewer or the listener. Otherwise it is the next increment.

Commercials

Fixed-scope build. The first increment is dated once we have seen a real brief, a real piece and the publish path. Further formats, languages and narration are later increments. Optional run, after go-live, is a separate agreement.

Questions

Is translation a separate product?

No. Translation of a written piece is part of Content Studio, with a reviewer for the language it lands in. A live spoken conversation is Conversation.

Who approves publish?

A named person on your team. The app can hold a draft. It does not publish it.

Can it write in our voice?

Yes, from pieces and rules you provide. Those examples stay in this engagement. They are not used to train a shared model.

Where does a scanned source fit?

Documents reads the page and a person checks it. Content Studio drafts from that checked text.

Who makes the pictures?

Graphics Studio, from the same brief when you want them. Content Studio does not pretend a caption is a layout.

Will it invent a customer or a statistic?

No. If the brief has no source for a claim, the draft marks the gap.

Can our users use this under our brand?

Yes. The product can be the application your team uses, or an application you offer. Review before publish stays either way.

What is in the first release?

One content type, the brief, review, and the publish path. Other formats and languages follow.

Next step

Start with two weeks.

A fixed-fee discovery gives you a ranked use-case portfolio, a target architecture, a cost model and a build proposal you can take to your board. If we don't find a case worth building, we tell you.