Everything people ask before they say yes.

You can, and for one post it is fine. The difference is not the writing.

The work is knowing which of your facts are current, what each channel does with a caption, and what has to stop and wait for a person. A blank chat box has none of that, so it answers every question with equal confidence, including the ones it should refuse.

If your agency is doing the thinking, keep them. We are not trying to replace judgement that already works.

What we replace is the production line under it: writing the same topic for every channel, briefing the designer slide by slide, and chasing which number is current. Several clients run both.

No. A scheduler moves finished posts to a time. It has no opinion about what the post says.

From September we do hand the approved week to a scheduler, so the two sit next to each other rather than compete.

Today, no. You approve the pack and your team publishes.

From September the approved week can leave for the schedule from inside your workspace, published at the time each channel does best. You keep the approval step either way.

One questionnaire, 3 to 4 hours, once. Everything you already publish we read ourselves: the site, the accounts, the posts that are live right now.

After that, one decision a week.

The first month of any market is the setup month, and it is charged at half rate. Inside it we build the knowledge base, agree the plan and ship packs.

There is no separate setup fee and no month where you pay and receive nothing.

Also on /#price

Tell us once. Tone lives in the knowledge base, not in a prompt, so a correction applies to every build after it rather than to one post.

The first two or three weeks of any market are where most of that gets settled.

We write the month and you change it. Topics come from what you actually sell, what changed, and what your audience asked about.

Any open slot takes a topic you type in. The next pack builds it.

Platform copy for each channel it belongs on, a designer brief slide by slide, a video script scene by scene, an assembly checklist, and a quality report.

Real field names, real character counts, real posting times. Not a draft to rewrite.

Also on /pack

Up to 8 per market, chosen from 17 supported.

Not every topic belongs on every channel. The system writes only where a topic has a reason to exist, and builds it for that channel rather than copying it across.

Yes, all of it. It is your document.

Edits that are really rules, like a tone correction or a phrase you never use, are better sent to us once so they apply to everything after.

Every image and video comes with a brief and with options: stock picked against the topic, or a prompt to generate one. Or you upload your own.

The brief carries your own brand colours, sizes and safe zones, so a designer can work from it without asking.

A pack stops when something in it cannot be traced to a record we hold: a price, a service, a name, a claim.

It does not guess and it does not soften. It stops and waits for a person. That is the whole reason the thing exists.

From you, once, and from what you already publish. They live in the knowledge base as records, not inside prompts.

That is why a correction sent on Monday is in Thursday's post.

You send it once. Every build after that reads the new record, in every market and every channel.

Anything already written against the old one stops at HOLD instead of going out.

Then we fix the record it came from, not just the post, so the same mistake cannot come back next week.

While one client is in production, every pack that stops is read by Taras personally.

A country plus a language. Poland in Polish is one market. The same company in Ukraine in Ukrainian is a second.

A second market is not a translation: it gets its own plan, its own rules and its own documents.

Also on /#price

Yes. 30 days notice, no long-term contract, and no charge while paused.

The knowledge base stays yours and does not go stale on its own, but facts do, so a long pause usually means a short refresh.

30 days notice. The knowledge base and every pack ever built are yours, and they leave with you.

No export fee, no hostage format.

Yes. Copy, briefs, scripts, checklists, the plan and the knowledge base.

We keep nothing you would need to ask us for later.