The 70/30 split, and why creators keep the bigger half
We break down how the templates marketplace pays creators, why we landed on 70/30, and what that means for the catalogue you browse.
Each network has its own quirks — aspect ratios, caption limits, best-time windows. A good scheduler hides that without lying to you.
Every social network is convinced it's the only one you use. Instagram wants square or 4:5. TikTok wants 9:16 and a hook in the first second. LinkedIn rewards a paragraph; X punishes one. A scheduler that ignores all this and blasts the same asset everywhere looks efficient and performs terribly.
The naive model is one composer, one "post" button, six identical outputs. It demos well and it teaches your audience that your brand has nothing network-specific to say. The opposite extreme — a separate tool per network — is where most teams actually live, and it's exhausting.
We wanted a third option: one idea, six native posts, from a single composer that knows the difference between the channels.
The goal is to remove busywork, not authorship. Octonity proposes network-appropriate variants; you stay in control of every word that ships.
When you draft once, the composer handles the per-channel reality:
The output of all that adaptation lands on a single calendar. You see the whole week across every channel in one grid — drag to reschedule, click to edit the variant for just that network. The complexity is handled; it's not hidden from you when you want it.
That's the line we try to hold: do the tedious adaptation for you, but never pretend the channels are the same when they aren't.
We break down how the templates marketplace pays creators, why we landed on 70/30, and what that means for the catalogue you browse.
Learn how GPT works using vectors, dot products, attention, and softmax, starting from concepts familiar to game developers — no PhD required.
العربية ليست لغة واحدة بل لهجات متعددة. نشرح لماذا يحتاج الإشراف الذكي إلى فهم كل لهجة على حدة بدلاً من الترجمة المسبقة.