Content approval for agencies, inside Google Docs.
Your writers stay in Google Docs. Your clients approve on their phone without logging into anything. You stop asking people whether they ever sent that blog to Henderson.
This is what your client will get. Try it.
A September calendar for a fictional heating engineer, running here in your browser. Nothing is sent anywhere. This is the part we are building next.
What it replaces
Most agencies run approval on memory. A writer finishes a draft and messages someone. That person reads it when they can, replies in a thread, and the writer finds the reply two hours later. The client gets a PDF calendar by email and answers in a way that is neither a yes nor a list of changes. Nobody can say what was approved, by whom, or when.
How it fits together
This is the shape of the product. The next section says which parts run today.
- The add-on will make one folder. It will create an ApprovalBird folder in your Drive on first install and work only inside it. It will never read the rest of your Drive.
- Writers work in Google Docs. Approve and request changes are buttons in the sidebar, in the real editor they already use.
- Slack will carry the handovers. The next person will be told it is their turn, with the buttons in the message. Anyone not in Slack will get an email instead.
- Clients get a link. There is no account to create and no password to set. A blog opens as the full text they can highlight and comment on. A content calendar will open as the deck above.
- Approved work publishes to WordPress. Images are re-uploaded to the client's own media library, because the ones Google exports stop working. On anything else, approved simply means approved and you publish the way you already do.
What is true today
A working version of this runs. The Google Docs sidebar, the approval routing, comments becoming the writer's task list, the client page with highlight-and-comment, and WordPress publishing are all built and tested.
Not built yet: the installable add-on, the content calendar deck, user accounts, the Slack buttons end to end, and email notifications. Every future tense in the list above is one of these.
That is why this is a waiting list rather than a signup form. We would rather know who wants it before we finish deciding what it is.
What it costs
Not settled. It will be priced on how many clients you run. Charging per seat taxes the people you want using it, and charging per post taxes the work. Expect a free tier that covers one client properly.
Join the waiting list
Two questions beyond your email, because they decide what gets built first.