Can a prompt replace Planable?

Build a social content approval tool where publishing is the final step, not the main feature.

Content model: a campaign holds posts. A post has text, attached media, a target network, an intended publish time and a status: draft, in review, changes requested, approved, scheduled, published, failed.

Review flow, which is the core of this build. Generating a review link creates a signed, expiring URL that opens a read-only board with no account required. The reviewer sees each post rendered in an approximation of its target network's layout, and can approve it or request changes with a comment. Every action writes an immutable event: who (by the name they typed on first visit), what, when, and against which version of the post text. Editing an approved post resets it to draft and records why — this rule is the whole point, and it must not be bypassable from the admin side either.

Collaboration: internal comments visible only to the operator, separate from reviewer comments. A diff view showing what changed between the version the reviewer approved and the current text.

Publishing: connect exactly one network through its documented OAuth flow. Only posts in the approved state can be scheduled. A background worker publishes at the scheduled time with an idempotency key, stores the returned post ID, and moves the post to published or failed with the error text preserved. A failed post is never retried silently.

Export: a per-campaign PDF or HTML report containing every post, its final text, and its full approval trail with timestamps. This is what gets attached to an invoice.

Out of scope: connecting a second network, scraping or unofficial APIs, analytics on published posts, a shared asset library, and multi-stage approval chains. One reviewer, one approval, one record.