Ten client boards, no single view
Team Cards gathers every person’s live work across accounts. Portfolio rolls active, overdue, due-this-week, unassigned, and completed cards up by workspace and board.
Project management for agenciesEvery client on its own board.
Every client on its own board.
One agency in total flow.
Keep client workspaces securely isolated while giving your leadership team cross-project visibility, automated standups, and hour totals in Table.
A board per client is easy.Running the agency is not.
Clients need one board, not your workspace
A client joins a single board as a guest. They never see your member roster, your other accounts, or any board you did not grant.
Every account set up slightly differently
Boards in a workspace share one set of lists, labels, custom fields, checklist templates, and automations, so the next account starts configured.
Hours recorded where nobody reports from them
Billable hours live in a numeric field on the card. Group a Table by client, sum the field, and the month is already assembled.
Clients want updates in chat, not another login
A chat destination posts that client’s board activity into the Slack, Discord, Telegram, or Zulip channel they already watch, with the events chosen per channel.
Every account notifying you at once
Notification rules are per workspace. Pause the accounts you are not delivering this week, keep mentions coming from the ones you are, and let the in-app inbox hold the rest.
Creative, delivery, new business,and hiring in one system.
Agencies rarely fail on one project. They lose time moving between the tools each department picked. Kanera holds every function in the same structure, so a lead can read across all of it.
Creative and campaign
A board per campaign, shared lists for brief, production, review, and live, and checklist templates that carry the same deliverables into every card.
Web and development
Custom fields for branch, environment, and estimate, with REST API, webhooks, and an MCP server so CI and AI agents update work directly.
Client services
Guest boards per account, nested notes for context and decisions, and Work Done to write the weekly update from what actually moved.
New business
A pipeline board with a list per stage, due dates on follow-ups, and an automation that applies the pitch checklist as a lead is qualified.
Talent and hiring
A board per open role with a list per interview stage, scorecard checklist templates, and interviewers restricted to the candidates assigned to them.
One seat, the whole product
There is no reporting tier, automation tier, or API tier to buy later. A workspace per department, a board per client or role, and one rollup for the agency.
Client and contractor access
Give a client one board.Nothing else.
Guests are external people with board-level access. Access is granted board by board, with a role you choose and an optional restriction to their own cards.
- Editor or Observer, chosen per board
- Assigned items only, for contractors who should see one slice
- Guests are never added to your organisation or workspace roster
- Each guest’s first board is free on Pro; a second board uses one purchased seat
- Remove access the day an engagement closes
Client intake on their board.Delivery on yours.
Mirror one list from a client board into your internal queue. The client keeps reporting where they already work, and your team plans the work where it belongs.
Client boardClient delivery Bugs
Internal boardDevelopment Dev queue
- One-way by design, so the client cannot reshuffle your delivery board
- Titles, descriptions, comments, attachments, checklists, and fields stay aligned
- Your team owns assignees, due dates, and scheduling on the internal copy
- Pause it from the target board whenever a client goes quiet
Client and team comms
Updates reach the channeleach client already watches.
Not every stakeholder will open a board, and an account lead sitting in ten workspaces cannot take alerts from all of them. Kanera separates the two: chat destinations handle the client’s channel, notification rules handle your own.
A channel per account
Paste the connection the chat tool generates and pick the events worth posting. Kanera formats each message for that platform, with the card title linked and its board named.
- Slack
- Discord
- Telegram
- Zulip
- Added from the workspace Integrations tab, on Pro or self-hosted
- Scoped to one workspace or standalone board, so a client channel only carries that client’s work
- Choose the events: card created, status, priority, title, description, or comment
- Map your own Priority field so escalations land where someone reacts to them
- Test, pause, or replace a connection without rebuilding the destination
Ten accounts, not ten times the noise
Account defaults stay strong and the exceptions live per workspace, so the accounts you are actively delivering are the ones that reach your phone.
- Pause an account you are not delivering this week
- Or keep only mentions, so you stay reachable without the traffic
- Standalone boards get a rule of their own
- Your in-app inbox stays complete either way, so nothing is lost
- Route your own alerts to ntfy, Gotify, or a personal webhook if email is not where you look
Delivery and billing reporting
Group by client. Sum the hours.Export the month.
Table view aggregates numeric fields inside any grouping. Group by a Client field, sum Billing Hours, break each total down by teammate or billing month, then hand the workbook to whoever raises invoices.
Sum and average
Aggregate any numeric field inside each group, on one board or across a workspace.
Second dimension
Break each client total down by teammate, work type, label, or billing month.
Month end
Filter completed cards by date range, then export the result to Excel or JSON.
The agency standard, appliedto every new account.
Define the process once
Set the lists, labels, custom fields, checklist templates, and automations that every account in that workspace should follow.
New accounts start configured
Create the client board inside the workspace. It inherits the workflow, the field catalogue, and the automations on day one.
Compare accounts honestly
Because Client, Priority, and Hours mean the same thing on every board, one report can hold the whole roster.
Roll it out across the agency.
Pro is $5 per user each month, or $49 per user each year. Every seat includes the complete product, and a client guest’s first board is free.
Self-hosting runs the same product with no Kanera per-seat fee when policy calls for your own infrastructure.
- Monthly
- $5per user
- Annual
- $49per user
- Trial
- 30days, no card
What Kanera does notdo for you.
Worth knowing before a rollout, not after it.
No stopwatch
Kanera has no built-in timer. Hours are a numeric field on the card, entered by the person doing the work or set by an automation, then summed in Table.
No invoicing or retainer billing
Export the month to Excel or JSON and raise invoices in the finance system you already run.
No Gantt, dependencies, or capacity planning
Planning happens through boards, tables, calendars, due dates, and Portfolio rollups.
No SAML or SCIM yet
Sign-in is email and password. Access is controlled through organisation, workspace, and board roles, with guest restrictions on top.
Agency questions
Can each client have their own board without seeing the rest of the agency?
Yes. Give the client board-scoped guest access as an Editor or an Observer. Guests are not added to your organisation or workspace roster, so they see only the boards you grant.
For contractors and reviewers you can also enable Assigned items only, which limits them to cards they are assigned to, or own a checklist item on.
How do seats work when clients and contractors are involved?
Each active member of your organisation occupies one purchased seat. Pro is $5 per user per month, or $49 per user per year.
External guests are counted differently. A guest’s first board across your organisation is free. Giving that guest a second board uses one purchased seat, and every further board reuses the same seat. Returning them to a single board releases it.
Can Kanera report billable hours per client?
Yes, using custom fields and Table reporting. Put hours in a numeric field on the card, add a Client field, then group a Table by Client and sum the hours. Break each total down by assignee, work type, or billing month.
Filter completed cards by a date range for a month-end view, then export the result to Excel or JSON.
Does Kanera replace time tracking and invoicing?
No. Kanera has no built-in stopwatch and does not raise invoices. Hours are recorded in a numeric custom field, either by the person doing the work or by an automation, and Kanera totals and exports them.
Agencies that need a running timer or a billing engine keep those tools and use the Kanera export as the input.
Can different teams in the agency run different workflows?
Yes. Each workspace has its own lists, labels, custom fields, checklist templates, and automations, so the creative team and the development team can work differently while both roll up into the same Portfolio.
A board that should answer to nothing else can stay a standalone board with a setup of its own.
Can client requests reach an internal delivery board?
Yes. Board syncing mirrors selected lists from one board into another. A client can report requests or bugs on their own board while each new card appears in your internal queue.
The sync is one-way. Source content stays aligned, and your team keeps control of assignees, due dates, and scheduling on the internal copy.
Can each client get updates in their own Slack channel?
Yes. A workspace admin adds a chat destination for Slack, Discord, Telegram, or Zulip, pastes the connection that tool generates, and chooses which card events post: card created, status changed, priority changed, title changed, description changed, or comment created.
Destinations are scoped to one workspace or standalone board, so a shared client channel only ever carries that client’s work. Card links still respect board permissions, so a link does not grant access.
How does an account lead avoid alerts from every client at once?
Notification rules are set per workspace and standalone board. Pause the accounts you are not delivering this week, or keep only mentions so you stay reachable without the traffic.
Rules only ever narrow delivery, and the in-app inbox stays complete, so pausing an account hides the interruptions without losing the history. Each person can also send their own alerts to ntfy, Gotify, or a personal webhook instead of email.
How many people can an agency roll Kanera out to?
There is no seat ceiling on Pro. Agencies commonly run one workspace per department with a board per client or open role, and add seats as teams come on.
Before a large rollout, confirm file volume, attachment storage, and identity requirements. Kanera has no SAML or SCIM today, which some IT teams treat as a gate.
Do you have ChatGPT or Claude prompts for client reporting?
Yes. The prompt library has copy-paste templates for weekly client status, blockers, retainer reviews, kickoffs, change requests, late delivery updates, quarterly reviews, and wrap-ups.
ChatGPT prompts work from pasted notes. Claude prompts can read live Kanera boards when Claude is connected.
Put the whole agency
in one view.
Start with the complete product for 30 days. No card required.
No card required, 30-day Pro trial, free plan available after it