Nine answers below. If yours is not here, read Terms first — half the inbox repeats what is already written there.
FAQ exists so the same arguments do not restart in every inbox. Read it before you ask us to repeat it in a call.
Nine answers below. If yours is not here, read Terms first — half the inbox repeats what is already written there.
You do. We configure approved credentials in accounts you control. Shared donor keys are a refusal — not a “maybe if we trust you”.
No. We build the system your editors run. You bring editorial direction, lawful sources and approval. Empty sites waiting for a miracle content fairy are not a launch.
AI may assist drafts inside editorial workflows you control. It is not an excuse to ship unreviewed spam at scale. If you wanted an article mill, you wanted a different studio.
Free tiers ship in the base kit. Pro licences are client-owned and billed to you unless the written proposal says otherwise. ACF Pro is effectively required for serious repeaters.
Typically 1–2 weeks to production once hosting, lawful access and scope lock are ready. Discovery, client silence and “surprise requirements” are not part of that clock.
Discussed after the first production delivery — not as a hidden clause inside a launch invoice. One install, many clones without agreement is how support tickets go to die.
English, Polish and Russian content paths are in our wheelhouse. Extra locales are scoped and priced — not absorbed because “WordPress is multilingual anyway”.
Handover of the operating paths, then optional care under a separate agreement — updates, monitoring and new features. Launch support is not infinite free labour.
Because a honest custom scope under that floor is either a lie or a future rebuild billed twice. The floor is a filter, not an insult.
Still have a real publishing problem after reading this? Send a scoped brief — not a one-line price check.