For anyone approving creative work with many hands on it

Version 4 approved Version 2 published

Between the brief and the media buy, a job goes through five handoffs or more. At one of them, the right version gets left behind.

requestbriefin an email with 20 people cc'd
productionfilesscattered across a drive
approvalthe sign-off“ok, go ahead” on WhatsApp
librarythe final assetin a shared folder
mediawhat actually went livewhichever file each person had

five handovers, five different places

For marketing teams approving creative work with 3 or more people at the same time.

Where the job gets lost

On average, a job changes hands
five times or more.

Whoever asks writes the brief. You turn it into a Demand. The agency produces. The approvers decide. It comes back to you. Media runs it. Five handovers, and context is lost at every one. An ordinary week in a brand operation:

request

The regional team asks for an adaptation in a DM, with no format and no deadline. You rewrite the brief by hand so the agency can understand it.

production

The agency uploads the layout to a drive link. Nobody knows whether it is v4 or v5 without opening both.

approval

Marketing, legal, trade and the board answer in their own time, and each area is looking at a different file.

chasing

You become the chaser: a reminder by DM, the link sent again, the question raised once more in the meeting. Approval moves at the pace of whoever answers last.

out of step

You are already working on v5 while people are still debating v2 over email. The conversation is never all at the same point.

library

The approved asset is saved in a folder named after the campaign, with no version number and no image rights expiry.

media activation

On Friday at 6pm, whoever runs paid media has to push the ad live. They open the folder and publish whatever file is in there. There was no clear final version and no right place to look for one.

outcome

v2 goes live, and the call from compliance arrives on Monday.

Without the right setup, the handover between stages is never properly solved, and that is where the work gets lost. 44% of agencies still receive briefs by email.

Why your stack never adds up

Two categories of tools
that, side by side, compete with each other.

Productivity apps

  • Project, task and owner
  • Board, deadline and status
  • Progress reporting

What they do not solve: high resolution preview, stacked versions, comments pinned to the exact spot and the decision on record.

Library and approval apps

  • Approved file and versions
  • Folders, taxonomy and search
  • Usage rights and reuse

What they do not solve: request, queue, stage, role and deadline of the work that produced the asset.

Either the operation lives with a patchwork, or it adopts an environment designed for both sides. Stitching modules together over APIs does not make those events talk to each other.

Turn that alarm off

Demand, approval and digital asset
in the same place.

The Wikimee platform is that place.

Built by people who live the marketing routine.

Brief, demand, creative initiative, approval, digital asset and the management of time and people all live in the same data model. Wikimee can take in the whole operation or only the part you need.

component · Demands

The request becomes a Demand

Briefs that arrive complete
and actionable.

brief PULSAR · Above the Limit Camila · Marketing · new runner line · live in three weeks
links & references
↗ previous campaign↗ market research
attachments
moodboard.pdfbrand-guide.pdflogos.zip
reviewed on intake: understood and agreed. on record.
A Demand for the in-house team

lands on the Board with an owner, a deadline and clear stages

tasks handed out

with owners and due dates, no side spreadsheet

or a full Initiative

the entire campaign, with goals, teams and schedule

Regional, product and sales open the request through the platform or through your brand's Portal. It arrives structured, goes through your review and becomes a Demand, with an owner and a deadline.

A poor brief wastes a third of the budget. Source: BetterBriefs and IPA.

component · Boards, inside Demands

The Demand moves along the Board

Production moves with an owner and a deadline.

intake (2)

Regional adaptation · South
Thu2 comments
Key visual · Mother's Day
Thu1 comment
4x3 banner · North storefront
Frino comments
POS kit · 40 stores
Fri3 comments

in progress (5)

4x3 outdoor banner from the Above the Limit campaign
Winter campaign · 4x3 banner
Mon7 comments
9x16 story from the Above the Limit campaign
9x16 story · launch
Mon4 comments
Catalog · July editioninstitutional
Street poster from the Above the Limit campaign
Billboard · mall corridor
Tue2 comments
1x1 post from the Above the Limit campaign
1x1 post · pulse foam
Wed6 comments

in approval (9)

Key visual · national
Tue15 comments
16x9 banner from the Above the Limit campaign
16x9 banner · portals
Tue5 comments
4x5 carousel card from the Above the Limit campaign
Carousel · card 2 of 6
Wed9 comments
Email header from the Above the Limit campaign
Email header · active list
Thu3 comments
POS poster · no-price version
Thu11 comments

final deliveries (214)

21x9 big-screen artwork from the Above the Limit campaign
Adaptation · lobby screen
pub.3 comments
15s video cover from the Above the Limit campaign
15s video · social
Fri8 comments
Southern regional adaptation of the Above the Limit campaign
South region · approved
pub.4 comments
Reels cover from the Above the Limit campaign
Reels cover · vertical cut
pub.2 comments
July catalogue cover for the Pulsar runner line
July catalogue · closed
pub.12 comments
Point-of-sale poster from the Above the Limit campaign
POS poster · printed
pub.5 comments
1x1 feed post from the Above the Limit campaign
1x1 feed · anniversary
pub.7 comments

Status stops being rebuilt in meetings: whoever requests, whoever executes and whoever approves are looking at the same thing, at the same time.

content approval, inside the Demand

The decision that stays on record

Approval happens on the asset preview.

the one that went live winter_campaign_v07
Rafael, legal
Rafael legal
Bianca, trade
Bianca trade
Camila, marketing
Camila marketing
the one that was approved
approved by Camila · Thu 14:32 · v_final
annotations resolved: 2 of 2

Four, five or six approvers look at the same screen, on the same version. This is the screen you open when compliance calls.

Once approved, the asset moves on to the channels. And this is where versions stop multiplying.

components · Content, Drive and Dashboard

What the next campaign builds on

The published asset becomes a library with a trail.

where is the approved version of the winter campaign?
demand · Winter campaign · approved Thu 14:32 file · winter_master.mp4 · v_final · rights 12m initiative · Winter campaign · on schedule conversation · “approved with a tweak to the lettering”
Demands on schedule
in real time, no manual reporting
Approval time
in real time, no manual reporting
Library reuse
in real time, no manual reporting

Every asset with version, history and usage rights, and the operation measured in real time. Operations with an advanced workflow see 48% more ROI. Source: Canto, 2026.

Who already works this way

Brand operations running on Wikimee

AmbevBoticárioDiageoKenvueLindtMondelezRaízenSearaSicrediStellantis
0k+
active users
0
co-operatives on one portal
−0%
less rework in one operation
0
multi-brand users

Current platform base. A portal with 110 co-operatives across eight years of operation. A 75% reduction in rework and zero publishing errors in a five year operation. Multi-brand catalogues across ten years.

A case result belongs to whoever achieved it. What can be promised is the same mechanism, not the same number.

The three questions that always come up

We already have a tool. Will the team adopt it? Does it integrate?

“We already have a tool.”

Probably several, and they are unlikely to cover every side of your operation. Wikimee can come in only on the side that hurts, approval, and live alongside the rest, giving you time to replace the others at your own pace.

“My team never adopts anything.”

Whoever creates keeps creating where they already create. What changes is where the request, the approval and the final file live. Start with one campaign and measure adoption before going wider.

“Does it integrate with what I use?”

The platform is fully componentised over APIs and integrates with hundreds of apps. You connect what already runs today and swap the rest when it makes sense, without stopping the operation to migrate anything.

It does not have to be everything at once. One real campaign, in thirty days, answers better than any presentation.

Start at whatever size makes sense

Choose the Right Plan.

From organising one team to a multi-brand operation with a Portal. You start at the size that solves today's pain and grow when the operation asks for it.

Pro

Ideal for teamwork, departments or small businesses.

R$ 55 /user

  • Free Guest Seat
  • Professional Workspaces
  • Projects and Campaigns
  • Teams
  • File Management
  • File and Copy Approvals
  • Built-in Messenger
  • Dynamic calendars
  • Ticket Support
Try it for free

Business

Perfect for established businesses ready to scale.

R$ 80 /user

  • Free Guest Seat
  • Relationship Portals
  • White Label
  • People Management
  • Time-Tracking
  • Native Integrations
  • Human Support
  • Priority Support
Try it for free

Enterprise

A customizable environment that adapts to larger organizations.

Let's talk

  • Seats on request
  • Storage on request
  • Hierarchical Organization
  • Organization-wide Permissions
  • Sub-accounts
  • Single Sign-On / SAML
  • Metrics and B.I. Dashboard
  • Custom Integrations
  • Onboarding Program
  • Training Program
  • Success Manager
  • Account Manager
  • Personalized Support
Contact us

Thirty minutes with a job of your own

Test it on real jobs.

Test it on smaller campaigns, with people open to something new. We build the flow live with you, and your operation already looks different.

30 minutes Email confirmation No commitment

Bring your approvers with you. Just add them when you book.