Norte clienthealthy
Workload on point · on schedule
Creative operations for whoever runs the business
The next client cannot become the next bottleneck.
Wikimee expands your people's capacity, your deliveries, your margins and the health of every client. Teams work inside coherent operations and the business grows sustainably.
Portfolio · business viewHealthy enough to grow
aggregate reading
01The portfolio shows what it can actually carry.
Operation healthHealthy
reading up to date
Healthy operational base
Leadership sees the whole without tracking tasks.
capacityadequate
deadlineprotected
marginmonitored
Pulsar clientwatch
High workload · deadline at risk
Vértice clienthealthy
Stable workload · on schedule
New clientintake
Scope estimated · margin assessed
management decisionRead the portfolio before taking on the next promise.
Why you ask for status all day long
Bottlenecks happen
where leadership cannot see.
The talent is already in the house, but it is busy accounting for the progress of every job. With no visible context, priority or capacity, the week of whoever leads turns into this:
you ask
You ask for status. Each answer is one person's reading, and none of them matches another.
you gather
The weekly meeting turns into an update. You leave the room with a map of what happened and no decision made.
you chase
Without seeing workload, pressure replaces priority. Everything comes in as urgent, and the team decides on its own what gets left out.
you find out
Overload shows up once quality has already dropped. A client complains, or someone good resigns.
you repeat
The following week you ask again, because last week's answer was never kept anywhere.
Chasing does not create capacity, it consumes it. People at their limit deliver worse, and the good ones leave. 77% of professionals report an unmanageable workload and 84% report digital exhaustion. Source: Parabola, 2025.
Why one more subscription did not fix it
Productivity is lost
in the gap between the tools.
Each app solved the problem of whoever asked for it. None of them sees the handover, and that is where rework is born.
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 sign-off of whoever decides, on record.
Library and approval apps
- Approved file and versions
- Taxonomy, search and usage rights
- Chain of approvers
What they do not solve: the request that originated the asset, the queue, the stage, the role and the hours it cost.
Stitching things together over APIs connects databases. It does not connect the request to the asset, nor the asset to the sign-off. In Wikimee it is a single data model, by architecture.
How much of this is money
You already paid
for this this month.
Rework has no line of its own in any budget. It goes out as an hour paid and not billed, and that is why the margin tightens without the spreadsheet explaining why.
0,4%
billable utilisation in the sector
healthy is 75%
0,8%
sector EBITDA
the lowest in a decade
0to 20h
per week, per person
on work that is not the work
Our own estimate, not survey data. Move the three controls and the maths is redone with your own assumptions.
- hours of rework per week, per person16 h
- 44 working weeks a year, the whole team2,816 hours
- cost of those hours in a yearR$ 309.760
- half of it comes from incomplete requests or approvals with no trail R$ 154.880 per year
Fixed assumptions: a 40 hour week and 44 working weeks. The final half is the share that structured intake and traceable approval address.
Billable utilisation and sector EBITDA: SPI Research, 2025. Hours per week on non-core work: McKinsey, IDC and Robert Half. The calculator is our own estimate, with the assumptions on screen.
And there is a second drain: the stack invoice, the pile of apps the agency subscribes to, one for each piece of the work.
What does it cost to keep each function in a different app?
Add up the average monthly fees per category and compare them with a single subscription. Adjust the team size and the yearly figure is redone.
Average market prices per user, per month, in each app category. Wikimee: price per user according to the subscription's seat table; the bigger the team, the lower the unit price.
estimated savings per year
R$ 151.142
with 30 people on the team
The maths is on screen for you to redo with your own numbers. This already leaves the bank account, it just never shows up on the spreadsheet.
Turn that alarm off
Demand, approval and capacity
in the same place.
The Wikimee platform is that place.
Built by people who live the agency routine.
Brief, Demand, 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.
What changes with the Wikimee architecture
The operation runs on its own, without taking up whoever runs it.
In Wikimee the platform guides how the work is run, and each role decides at its own level. Whoever leads creative looks after quality. Whoever leads the business looks after clients, pricing and growth.
Timetrack built into the operation
Tap each stage to follow what changes.
three roles running the work
operation in progress
The platform guides. Each role decides at its own level.
executionAssigneereceives, executes and records in context
▶
Demand 184 · taskCampaign rollout
02:1702:1802:19
time tied to the Demand, stage, Initiative and client
core of the operationEditorguides flow, workload and delivery
team A
team B
team C
capacity × workloadrebalancing
operations managementOperations Managerorchestrates portfolio and risk
Initiative Abottleneck in approval
Initiative Bwithin capacity
Initiative Con schedule
risk located · assignment reallocated
components · Portals and Demands
What if the client asked better
The first deliverable
is the client's.
request
PULSAR · Above the Limit
objective & acceptance criteria
audience: 25 to 40, road runningacceptance: brand ruler and legibility
links & references
↗ previous campaign↗ market research
attachments
moodboard.pdfbrand-guide.pdflogos.zip
reviewed on intake: understood and agreed. on record.
The accepted request becomes a Demand
lands on the Board with an owner, a deadline and stages
The Portal accounts for the request
sent, adjusted, returned, accepted or converted
or a full Initiative
the client's entire campaign, with goals, teams and schedule
Each client asks through your agency's Portal, with their own brand up front. The completeness ruler holds the submission until the request is whole, so whatever comes in is already ready to become a Demand.
Account handlers go back to looking after the account, and stop writing the brief the client did not write. And the client, who used to send voice notes, comes in and decides what matters.
components · Demands, Canvas and Content
What the payroll actually buys
The capacity you pay for
finally shows up.
The Demand arrives together with the objective, the audience, the acceptance criteria, the references and the brand memory. The day yields what the payroll promises: creative work.
intake (4)
Lettering tweak · Pulsar
Anniversary key visual · Splash
4x3 banner · Nord storefront
POS kit · Vela, 40 stores
in progress (6)
Catalogue · Nord, July editionnew client
in approval (5)
15s film · Nord
POS poster · Nord, brand ruler
final deliveries (312)
Approve once, roll out without redoing.
The approved master carries the decision into every format. Approval becomes a quick check, not another round of debate.
the one that was going around
pulsar_limite_v07
Rafael client
Bianca account
Camila client
the one that was approved
approved by Camila · Thu 14:32 · v_final
annotations resolved: 2 of 2
annotations resolved: 2 of 2
Who approved what, when and how. All inside the Demand. This is the screen that ends the conversation in a minute instead of a day.
The mistake is caught before it reaches you. Being the quality control for everything stops being your job.
components · Dashboard and Timetrack
Who accounts for the status
The meeting goes back to being about decisions,
not follow-ups.
what got stuck this week, and for how many days?
demand · Nord, July catalogue · stuck for 4 days, waiting on client content
workload · Creative team · three Demands above this week's capacity
approval · Splash, key visual · with the client since Tuesday, no answer
hours · Vela, POS kit · logged above the Initiative's estimate
Nobody asks, because the status already arrived: what is pending per Team, what got stuck and for how many days, and overload showing up while it is still workload and not yet a drop in quality.
Demands on schedule
in real time, no manual reporting
Time in approval
in real time, no manual reporting
Workload per Team
in real time, no manual reporting
Team data is there to improve the operation, not to watch people.
Status arrives before the question. And capacity is now read per Team, which is what lets your operation scale.
Who already works this way
Creative operations
running on Wikimee
I centralise demands, deliveries and everything that comes off them.
I would never go back.
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.
The three that always come up
Will it lock down
the team's creative work?
“It will lock down the creative work.”
Whoever creates keeps creating where they already create. The brand guideline is set once, and you only read the exceptions that step out of line.
“How do I test this without betting the agency?”
One client, one Initiative, no long contract. You measure before and after with the logged hours.
“We tried a management tool before and the team dropped it.”
A tool that only asks for status gets dropped because it gives nothing back. Here, whoever fills it in is whoever stops being asked.
It does not have to be everything at once. One real client, 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
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
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
Browse the categories and find the plan that fits your operation. Guest is the free seat, included in every paid plan.
| Feature | Guest | Pro | Business | Enterprise |
|---|---|---|---|---|
| Account | ||||
| Additional Seat | ||||
| Additional Workspace | ||||
| Additional Storage | ||||
| Access profiles | ||||
| Native Integrations | ||||
| Custom Logo | ||||
| Custom Colors | ||||
| Custom Domain | ||||
| Custom Login Page | ||||
| Relationship Portal | ||||
| API Integrations | ||||
| People Management | ||||
| Time-Tracking | ||||
| Sub-accounts by brand or unit | ||||
| Organization-wide Permissions | ||||
| Single Sign-On / SAML | ||||
| Metrics and B.I. Dashboard | ||||
| Custom Integrations | ||||
| Seats and storage on request | ||||
| Workspaces | ||||
| Private Workspace | ||||
| Own branding | ||||
| Activity Feed | ||||
| Filters and Advanced Search | ||||
| Public Workspace | ||||
| Access profiles | ||||
| Members and Guests | ||||
| Groups and Hierarchy | ||||
| Initiatives | ||||
| Own branding | ||||
| Bio and Publication | ||||
| Activity Feed | ||||
| Files and Related Demands | ||||
| Goals | ||||
| Filters and Advanced Search | ||||
| Access profiles | ||||
| Schedule | ||||
| Demands | ||||
| Agile boards | ||||
| Follow-up Plan | ||||
| Timeline and Calendar | ||||
| Filters and Advanced Search | ||||
| Simple Approval | ||||
| Advanced Approval | ||||
| Files | ||||
| Sharing | ||||
| Shareable Folders | ||||
| Filters and Advanced Search | ||||
| Real-time preview | ||||
| Versioning | ||||
| Versions Comparison | ||||
| Auto Tagging of Image with A.I. | ||||
| Auto Tagging of Video with A.I. | ||||
| On-demand Closed Caption with A.I. | ||||
| Support | ||||
| Help center | ||||
| Chatbot | ||||
| Ticket submission | ||||
| Human support | ||||
| Priority support | ||||
| Success manager | ||||
| Onboarding program | ||||
| Training program | ||||
| Account manager | ||||
| Custom SLA and support | ||||
Seat, workspace and storage limits can be adjusted within each plan. On Enterprise, the environment is designed together with your team.
Thirty minutes with your operation
A pilot the size
of one client.
Pick one client. We build their operation live, inside your own environment. That way you follow what is in production, what got stuck and how much workload each Team is carrying. You measure before and after.
Bring whoever coordinates the operation with you. Just add them when you book.