Client sign-off, built into the workflow itself

Software that makes a client sign-off a required, enforced step in a project rather than something tracked in an email thread. In Harmny, a phase in a campaign blueprint can carry a client-approval gate: the next phase does not open until the client approves it in their own portal. The workflow itself blocks progress, so there is no ambiguity about whether sign-off happened.

Email approval is not enforced anywhere. The next person on the team can start work regardless of whether the client actually replied, and six months later there is no clean record of when sign-off happened or on which version. A structural gate removes that gap: the phase cannot move forward, in the tool everyone is already working in, until the approval is logged.

Yes. Approval gates are set per phase, per blueprint. A radio campaign and an influencer campaign can have gates at completely different points in their process, because they are different blueprints with different phases. Toggling a gate on or off, and picking who approves it, is done in the blueprint editor directly, no developer required.

No. Clients approve from a branded portal opened with a magic link, the same portal used for deliverables and activity updates. No password, no signup form. If a client would rather not open another web app, the same approval flow is also available through a dedicated Telegram bot.

The phase stays blocked, which is visible on the board rather than hidden in an inbox. Because the workflow surfaces exactly where a project is stuck and why, an account manager can see a pending approval and follow up, instead of discovering the delay days later when someone asks why the campaign has not moved.