Cenelirainstagram · FEEDacme_officialResolved and ready to publishOK
linkedin · FEEDAcme Studio (company)Two LinkedIn company accounts are connected. Choose the right one.REFUSED
x · FEED@acmestudioResolved and ready to publishOK
Controlled social publishing
Know where your post goes. Before it publishes.
Cenelira verifies the destination account, binds approval to the exact version, gives clients a review link with per-platform decisions, and keeps a signed record of what actually happened.
Destination verified. Approval bound to version. Proof leaves the app.
§ 01 · Expensive failures
The failures buyers actually pay for.
Five failures that get agencies fired. What Cenelira does to stop each one.
The failure
Post went to the wrong client account.
One ambiguous destination is enough to get an agency fired.
What Cenelira does instead
Preflight refuses the publish when the target is ambiguous and shows the repair path before anything goes out.
The failure
Version one was approved. Version three got published.
A timestamped approval is useless if edits keep moving underneath it.
What Cenelira does instead
Approval stays bound to the exact version. Edit after approval and the receipt marks itself superseded.
The failure
The post failed overnight and nobody owned it.
Slack archaeology is not a recovery system.
What Cenelira does instead
Exceptions land in an owned queue with a typed cause, a named owner, and a replay path.
The failure
The client asked what they actually approved.
Screenshots and email threads do not survive pressure.
What Cenelira does instead
Review links, receipts, and proof bundles keep the approval path and publish record tied together.
The failure
Work moved by hand and the audit trail disappeared.
Manual handoffs usually drop the version, target, or scope.
What Cenelira does instead
Handoff packs carry approved version, target, and scope so the manual path still closes back into the record.
Read the wrong-account refusal mechanics
Read how approval is bound to the exact version
Read how failed publishes get a typed cause and a typed owner
Read how the manual-completion fallback is recorded on the proof
§ 02 · Who it is for
Three lanes. One product.
Agencies are the primary ICP. Brand teams get the same control layer without the agency pricing model. High-control teams need approval rigor, proof, and recovery without guessing what the system will do next.
Agencies
Many clients, one workspace each. Per-platform proof.
Run five, ten, twenty brands in one account. Clients approve by link, no login. Each platform lands its own decision. Every period produces a signed PDF archive per client.
- External review by link. Per-platform decisions.
- Signed PDF proof archive per client, per period.
- Handoff packs carry approved version, target, and scope.
Brand teams
Protect the brand accounts. Own the recovery.
Publish to your own brand’s accounts. Legal reviews the sensitive ones. Protected destinations refuse to publish without the required reviewer. Stale approvals mark themselves invalid the moment the copy changes.
- Internal review with version-bound approvals.
- Protected destinations refuse publish without the required reviewer.
- Per-account workspace health surfaces degrading accounts early.
High-control teams
Approval rigor, proof, and recovery without guesswork.
For teams where the cost of the wrong publish is high. Keep destination certainty, version-bound approval, signed proof, and an owned recovery queue in one operational surface.
- Version-bound approval with an auditable receipt trail.
- Signed PDF + CSV proof export that leaves the app.
- Typed exceptions, named owners, and replay paths.
§ 03 · What it does
Everything a serious scheduler has. And then the control layer.
The base product. Before any differentiation claim lands, these all have to be real.
✓ IncludedSchedule creation wizardhybrid · guided or compact
✓ IncludedPlatform coverage
✓ IncludedList and calendar viewslist first · calendar toggle
✓ IncludedMedia compositionper-platform framing envelopes
✓ IncludedInternal approvalsversion-bound queue
✓ IncludedExternal review by linkper-platform decisions
✓ IncludedOwned exception inboxcause · owner · replay
✓ IncludedPersonal workspace modeone seat · supported accounts
✓ IncludedSigned proof exportsPDF + CSV signed bundle
✓ IncludedPer-schedule audit logreceipt · timeline · scope
✓ IncludedHandoff packstarget · version · scope
✓ IncludedWorkspace operational healthper-account signal
§ 04 · The system
How Cenelira works, six surfaces.
Click a surface. Each one is a screen that ships today.
instagram · FEEDacme_officialResolved and ready to publishOK
linkedin · FEEDAcme Studio (company)Two LinkedIn company accounts are connected. Choose the right one.REFUSED
x · FEED@acmestudioResolved and ready to publishOK
threads · FEED@acme_officialGrant expired. Reconnect before publish.FIX
Δ 01 · Preflight
Publish refuses before it can go wrong.
Every schedule resolves destination before publish. If two candidate accounts exist, a grant is missing, or the account belongs to the wrong workspace, the row is refused and the operator is told what to repair.
- Runs on create, edit, approval, handoff, replay, and publish.
- Refusal reasons are specific enough to act on, not generic red banners.
- The fix path sits beside the refusal, not in a buried log.
What it prevents: posting to the wrong brand account, posting after a permission expired, posting when the target belongs to another workspace.
§ 05 · What makes it different
Three product claims you can verify in the first week.
Three things no other tool in this category does today. All verifiable in the first week.
Δ 01
Refusal is a feature.
If two LinkedIn company accounts are connected, Cenelira refuses the publish and tells the operator what to repair. Generic schedulers let that mistake escape.
Δ 02
Approvals are bound to the version.
Edit after approval and the receipt marks itself superseded. The point is not a timestamp. The point is that the approved version and the published version stay tied.
Δ 03
Proof leaves the app.
Signed PDF + CSV twin. Human-readable for clients, machine-readable for operations. The record stays useful after the subscription ends.
§ 06 · What the category cannot copy
Structural positions, not a slogan about moats.
Six reasons the gap gets wider the longer a team runs on Cenelira.
M1
Exact target authority
Every schedule resolves to one authoritative account per platform. Ambiguity is refused, not silently picked.
M2
Version-bound approval integrity
Approvals bind to a content fingerprint. Any edit invalidates the receipt with a typed reason.
M3
Delivery-set truth
The set of destinations is a first-class artifact. Scope changes supersede links with explicit reasons.
M4
Owned exceptions
Every failure has a typed cause, a named owner, and a replay path. No silent errors.
M5
Handoff provenance
Manual packs carry approved version, target, scope, and reviewer. Completion receipts close the loop.
M6
Exportable proof
Signed PDF + CSV twin. The record survives outside the app and keeps its value over time.
§ 07 · Personal workspace
Serious solo operators get the same system. Scaled down.
Personal workspace is one seat, one workspace, one account per supported platform. No assignees, no handoff packs, no review-by-link. You still get preflight before every publish. You still get a signed personal record after. The system scales down cleanly without becoming creator-tool fluff.
- Target resolution before every publish.
- Same typed state vocabulary. Same row grammar.
- Personal signed record export when you need it.
- One person, supported platform accounts, no team chrome.
Thu 04-1811:20 ZSpring post · v2REFUSED · publish_fail
Thu 04-1812:00 ZThought of the day · v1QUEUED
Thu 04-1807:00 ZMorning post · v1PUBLISHED
§ 08 · Pricing
Three public tiers. Enterprise by contact. Per seat, not per workspace.
Operators pay. Clients do not. Public review links and signed proof archives are in every paid plan. Enterprise is a contact path for teams that need a heavier rollout.
Yearly saves 2 months
Personal
One seat£29per seat · month
Serious solo operators who still need preflight, proof, and a record they can trust.
- One seat, one workspace, one account per supported platform.
- Preflight on every publish. Personal signed export.
- No assignees, no handoff packs, no team chrome.
Team
£69per seat · month
Brand teams running controlled publishing across their own accounts.
- Up to ten connected accounts.
- Internal review and protected destinations.
- Exception inbox with per-account health.
- Signed CSV proof export.
Agency
Primary ICP£109per seat · month · unlimited client workspaces
Agencies running multiple clients with external review and signed proof.
- Unlimited client workspaces and connected accounts.
- External review by link. Per-platform decisions.
- Signed PDF proof archive per client, per period.
- Handoff packs carry version, target, and scope.
- Per-account health and typed exception ownership.
Per seat, not per client. A five-seat agency with fifteen clients pays five seats, not fifteen workspaces. Per-workspace pricing wins for one-client shops and loses everywhere else.
Start with AgencyEnterprise
ContactTalk to us
larger rollouts and procurement-heavy teams. Commercial review, rollout planning, and implementation support without pretending unshipped controls already exist.
- Shared rollout and onboarding plan.
- Commercial and procurement support.
- Priority implementation review.
- Custom commercial terms.
- Direct contact for larger team launches.
Final billing is in GBP. USD and EUR figures are indicative and round to the nearest whole unit at current rates. Yearly billing charges for ten months and covers twelve. If your contract requires localised invoicing, talk to us and we will set it up at signup.
§ 09 · Honest answers
Questions you would ask before you tried it.
Plain answers. No brand theater.
- Is this just another scheduler?
- Cenelira supports controlled scheduling and publishing workflows across the public platform inventory, with auto-publish paths for eligible post types on every supported platform. Cenelira also does the work a scheduler skips: refuses when the destination is ambiguous, when the grant has expired, or when the approved version is stale. Every success leaves a signed record. Every failure has an owner. A scheduler's job ends at "queued." Cenelira's ends at "proven."
- We already have approvals in another tool.
- You probably have one approval that covers every platform. Cenelira adds per-platform decisions on one external link, approvals bound to the exact version, and a signed proof archive that leaves the app. Those are different claims.
- What happens when Cenelira itself fails?
- Nothing publishes silently. The publish path fails closed on ambiguous targets. Every exception has a typed cause, a named owner, and a replay path. You do not wake up to find a post went out that nobody approved.
- Can we leave with our data?
- Yes. The proof archive is the export. Signed PDF plus the CSV record set. You keep it after the subscription ends. The point is that the record is useful outside the app. Read the proof spec.
- Which platforms do you support?
- Today Cenelira supports controlled scheduling and publishing workflows for: Instagram, Facebook, Threads, LinkedIn, YouTube, TikTok, Pinterest, X. Each supported platform has an auto-publish path for eligible post types. The app still checks exact media, account, provider, and delivery-mode requirements before scheduling. If you need a platform that is not on that list, talk to us.
- I work alone. Is there a one-seat option?
- Yes. Personal workspace is one seat with the same preflight and the same signed record, stripped of team chrome. Priced for serious solo operators who want the engine, not the cheapest queue.
- Why is Agency priced per seat instead of per workspace?
- Because agencies scale by operators, not by the number of clients they serve. A per-workspace model looks cheap at one client and turns punitive as the roster grows. Cenelira charges for the team running the work, not the client count.
- Do you already sell enterprise trust controls like SSO and retention policies?
- Not as public product claims today. The current trust layer is refusal before publish, approvals tied to the exact version, owned recovery, and signed proof export. If you need a heavier procurement or rollout path, talk to us directly.
Ready when you are
Stop publishing on hope. Start publishing on record.
Get updates on controlled publishing.
Occasional notes when a new control, proof feature, or platform release ships. No newsletter filler.