“Did the client approve this?” should not be a hard question.
Canopy gives every client a content calendar, captions and visuals for each platform, and one thread where they approve the work or ask for a change. One place, one status, one answer.
Ridgeway Coffee
Tue 13 October
Single origin — October release
Priya Raman · client · Mon 09:14
Can we swap the second slide? The espresso shot reads darker than the roast actually is.
Right now
Your approval process is four tools and a group chat.
#halden-ridgeway · 23:47
did the client ever sign off on the Tuesday carousel?
October content plan · D14
Inbox · 4 replies
Re: Re: Fwd: October content – a few small tweaks
In Canopy
The same approval, in one thread.
The request, the reply, the revision and the decision sit on the post they are about. Nobody has to reconstruct what happened from four places.
Single origin — October release
Ridgeway Coffee · Tue 13 October · Carousel
Three farms, one harvest window. October's release lands Thursday — notes of blackcurrant, cocoa, and a finish that stays put.
TikTok
Three farms, one harvest window. October's release lands Thursday.
Revision thread
Priya Raman · client · Mon 09:14
Can we swap the second slide? The espresso shot reads darker than the roast actually is.
Ines Okafor · Mon 11:02
Reshot it against the lighter background. Second slide updated.
Priya Raman · client · Mon 14:38
That's the one. Happy to go with this.
The loop
Ten statuses, and everyone reads the same one.
A post moves through named stages your client can see. Here are five of them; the full sequence is on how it works.
- Caption Needed
The month is planned, one workspace per client.
- Captions Pending Approval
Captions are written per platform and sent for review.
- Revision Needed
The client asks for a change, in the thread, on the post.
- Visual Approved
The revision is made. The thread keeps the history.
- Scheduled
Approved and ready. You post it with whatever you use today.
For your team
Three things that stop happening.
The designer stops working from a superseded file
The visual on the post is the current one. There is no v4_USE-THIS to find, and no question about which file the client actually saw.
The project manager stops chasing
Approval state has a name and a colour. Nobody has to ask in a channel whether Tuesday is signed off.
Feedback stops living in one person's inbox
The client writes on the post. Everyone assigned to that client can read it, including whoever picks the work up next.
Confidentiality
What you put in Canopy belongs to your client, not to us.
Canopy holds unpublished campaigns that are often under an NDA between you and the company you made them for. Every agency's data is separated in the database itself, so the boundary holds even if the application is bypassed. There is deliberately no administrator account that can read across agencies. Visuals are stored privately, with no public link to a client's unlaunched work.
A full write-up of where the boundary sits, how files are stored, and what we do not claim is being finished now. Ask on a call and you will get the same answers early.
Scope
Canopy does not post to social platforms.
You schedule and publish with whatever you use today. Canopy is where the work gets planned and approved before it gets there.
No publishing
Nothing goes to Instagram, Facebook, TikTok, LinkedIn or X from here. Scheduled and posted are statuses a person sets.
No analytics
Canopy has nothing to say about how a post performed. That belongs to the tool that published it.
No mobile app
It works on a phone in a browser, which is how your client will open it. There is nothing to install.
Fit
Built for agencies of roughly 3 to 25 people
Running content for somewhere between 5 and 50 clients, with a real approval relationship for each of them. That is the shape of team Canopy is designed around.
Your clients are free, on every plan, always. They never count against a seat, however many of them you have.
Probably not for you if
- You work alone. A spreadsheet costs nothing and one person can hold the whole month in their head.
- You are an in-house team. Without an external client to approve the work, most of Canopy has nothing to do.
- You are over 25 people and need SSO or a custom contract. We have not built either, and saying so now saves us both a call.
Book a 20-minute call
A conversation, not a demo. Tell me how your approvals work today and I'll tell you plainly whether Canopy would help.