Client transparency shouldn't cost you your planning.
Makkro gives your client one place to follow everything that matters — and your team one place the client can't walk into. Two views, one operation, zero status meetings.
Everything unlocked. No card. Your clients never pay a cent.
Giving the client full access isn't transparency. It's losing control of execution.
The tools on the market solve silence the easy way: they show everything. They invite the client into the same board where the team works.
What follows is predictable. The client talks straight to the developer. Re-prioritizes in a comment. Asks for “just a tiny tweak” from someone with no authority to say no. Two weeks later Monday's plan no longer exists, and nobody can point to where it came apart.
Stakeholder
- Follows and requests
- Never sees the internal queue
- Approves what needs approving
Member
- Executes with context
- Takes no work from side channels
- Sees the documented rule
Manager
- Decides what gets in
- Triages everything
- Distributes the week
Following and executing are distinct roles, and the tool has to reflect that. The client still sees everything that matters. They just can't reshuffle your week without going through you.
Agencies don't lose clients over delivery. They lose them to silence — or to interference.
- The brief lives in a PDF nobody has opened since kickoff
- The rule agreed two months ago is now oral folklore
- Status scattered across a board, a spreadsheet, email and WhatsApp
- Requests arrive through any channel and become scope with nobody deciding
- The team finds out it's late when the client complains
- And opening the board to the client just trades one problem for another
The visibility is for the client. The gain is yours.
Task management that fits your operation
Tasks are classified by markers — stage, type, priority, blocker — and the views assemble themselves from that. A task can be in development and waiting on the client at the same time, because in real life it is.
Deliverables defined without ambiguity
Every deliverable has a planned date, an actual date, an owner and an audience: internal, which only the team follows, or external, which the client sees. End of the argument over what counts as delivered.
Real progress, not reported progress
You open it and see where each project stands. No asking for status, no waiting on a spreadsheet, no trusting an “it's going fine”. Progress is the state of the system, not the opinion of whoever got asked.
The team's week on one screen
Each person with the tasks they're carrying and their last deliveries right next to their name. The backlog of every project sits in a side panel: drag, drop, and the task lands in someone's week.
A monitor for the whole agency
Load per person, deadlines at risk, delivery pace, requests sitting still. At indicator level, updated while the team works — not a report somebody has to generate.
Time trackingcoming soon
Hours per task, project and person, tied to the deliverables they produced. For agencies that bill by the hour, and for those that need to know what each fixed-scope deliverable costs.
None of this holds up if the client can re-prioritize from the inside. A trustworthy progress view requires that nobody is rearranging the queue from outside — which is why the separation comes before the features.
What gets recorded, what the team executes, what crosses over to the client.
The separation between client and execution isn't a permission toggle. It's how the entire product is organized.
Execution
Where the client doesn't go.
Planning
The team's week on one screen, with a unified backlog and drag and drop across people and projects.
Tasks
Classified by markers, not by a fixed column. The views assemble themselves from the markers.
Continuous review
A recurring project-health checkpoint, with a history you can compare across cycles.
Monitor
Indicators for the whole operation: load, deadline risk, delivery pace and bottlenecks.
Context
What can't be allowed to become folklore.
Overview
The project's living brief: objective, scope, assumptions, owners and contract limits in a document that keeps up, not a PDF that ages.
Topics
Tree documentation with unlimited sublevels — Users › User registration › Registration validation. Sign-off happens against a document.
The boundary
What crosses over to the client.
Deliverables
Internal and external, marked item by item by you. The client only sees what crossed over.
Requests
The only path a demand can take: it arrives structured, goes through triage, and ends in a recorded decision — including when the decision is no.
Portal
What the client sees, defined by you. Planning and tasks stay on your side by architecture, not by a setting someone can forget.
Automations
Trigger and action in place of manual coordination. Every run recorded: what fired it, when, which rule, what changed.
Invite the whole client. None of them costs a thing.
The board, marketing, legal, the people on the client side who just want to watch from a distance — they all get in, they all follow along, none of them shows up on the invoice.
That isn't generosity, it's a consequence of the thesis. If inviting one more person from the client costs money, you invite fewer people — and the problem Makkro solves comes right back through the side door.
Recognize the scene?
Marketing agencies: the bottleneck is approval, not production
The client sends a change straight to the designer at 6pm on a Friday. Nobody knows which version was approved. At month end, proving the agreed volume shipped takes more work than producing it did.
In Makkro the request enters through Requests, the manager triages it, and the planned queue stays standing. At closing, the history of external deliverables is the report — you don't assemble one.
Tech companies: the business rule is the most fragile asset
The rule was agreed on a call, never documented, and comes back different at sign-off. The change request arrives on WhatsApp and becomes scope with nobody deciding.
The Topics tree keeps the rule at the right level, linked to the task that implements it and the deliverable that ships it. The client signs off against a document; the change is recorded with a decision and a date.
It was a method before it was a product.
Makkro was built inside a software agency that has been running since 2019, to solve a problem no tool on the market solved: giving the client visibility without handing them the team's planning.
Six operating rules, applied to every project for months, on top of a borrowed tool. The software came after — each module arrived in the order the pain did. That's why there are no spare screens: none of them was built to fill space on a pricing page.
And before you ask
Makkro is a software company, separate from the agency it was born in. We don't take on client projects and we won't compete with you for accounts.
Our product is the platform. The roadmap answers to whoever uses it.
15 days. Everything unlocked. Nothing crippled.
There is no free plan in Makkro, and that's deliberate: a transparency tool tested halfway proves nothing. You test it with the real operation or you don't test it.
Seat
- Same price for manager and member
- Free stakeholders, unlimited
- Unlimited projects, tasks, topics and deliverables
- Every module, nothing locked behind a tier
White label
- Your own logo, colors, typography and domain
- Dedicated, isolated infrastructure
- User management under your control
- Stakeholders stay unlimited and free
The math is simple. An agency of 8 people serving 20 clients pays for 8 seats: US$ 152 a month. The 20 clients, however many people they bring, never enter the equation.
Questions everybody asks
Will my client be able to touch the team's tasks?
No. Stakeholder and executor are roles separated by architecture. The client follows and requests; they neither see nor change the planning.
What if they want to talk to someone on the team directly?
They can talk. The difference is that a request only becomes work after triage. Your queue stops being rearranged by informal messages.
Does my client have to pay?
No. Stakeholders are free and unlimited on every plan, white label included.
Do managers and members cost the same?
Yes. US$ 19 per seat, no difference by role.
Is there time tracking?
It's in development. Hours per task, project and person, tied to the corresponding deliverables.
Why is there no free plan?
Because the value shows up with the whole operation running inside the platform, not with a test project and three tasks.
Are you an agency? Will you compete with me?
No. Makkro was born inside an agency, but it's a separate software company with its own team and roadmap.
What happens when the trial ends?
Your data stays there. You pick the number of seats and carry on.
Transparency isn't a risk. It's your commercial edge.
15 days with everything unlocked. Take the messiest project you have and invite the client — they pay nothing, and they won't wreck your planning.
No card. No onboarding project. Nothing locked.