In development 2026Sponsored LinkedIn posts with a verifiable agreement.
A platform for sponsored LinkedIn posts: brand and creator sign off on the exact text and terms, then the platform publishes it and pays out on verified milestones.
- Platform
- Web · LinkedIn first
- Stage
- MVP in progress
- Invariants enforced by
- Postgres
- Role
- Founder & engineer
- v1 3f9c2e1
- v2 a71d08b
- v3 c04e5f2
- ✓ signed
Acmecutsreportingtimeby80%.Tryitfreetoday!
The problem
Sponsored posts run on screenshots and trust. The brand approves one text, the creator posts a slightly different one, deletes it after two days, and payment becomes an argument. Neither side has a record they can point to.
Use it to
- Agree with a creator on the exact wording and price of a sponsored LinkedIn post.
- Review a post text and suggest changes like in a pull request, with word-level diffs and comments.
- Prove later what was agreed: the signed text and its terms share one hash.
- Pay or get paid per verified milestone, with automatic refunds for unused days.
What it does
Versions, not email threads
Every change is an immutable version with a short hash. Suggested changes, word-level diffs and inline comments.
The contract is the commit
Price, publish window and days live are part of the snapshot. Both parties sign one fingerprint, and any change voids it.
Published exactly as signed
The platform posts the signed text via the LinkedIn API, then checks that it stays up and unchanged.
Money committed up front
The brand is charged at sign-off. Payouts release on verified milestones, with automatic refunds for unused days.
Git's guarantees without git's vocabulary
A deal's history is a chain of snapshots. A "suggested change" is a branch with a review; "accept" is a fast-forward or a three-way merge; "approve final version" is a signed tag on a hash. Marketers never see those words, but they get the same guarantees.
The database is the referee
Postgres enforces the invariants, not the UI. Every table has row-level security, there are no direct writes, and all mutations go through audited RPC functions. Versions, reviews, sign-offs and the audit log are append-only. The snapshot hash is computed only in a Postgres trigger, so there is no second implementation that could drift.
Tests aimed at logic flaws
Domain logic (merges, diffs, money) has property tests in Vitest. pgTAP tests check privileges, RLS and workflow invariants against a catalogue of logic flaws, and Playwright plays a full brand ↔ creator negotiation end to end.