Who it's for / Agencies & tech
Retainers billed by hand, scattered tools.
Digital agencies, software houses and tech teams with retainer clients, sprints and a lot of client communication.
Agile kanban with epics and waves, team chat, goals and recurring billing for your clients.
A digital agency with 30 retainer clients
Before: Tasks in one app, conversations in another, client requests over WhatsApp and monthly billing done by hand.
After: One place for the team, another for the client, and billing that no longer depends on memory.
Illustrative example, built with the features Tesselys has today.
- 1
Each client gets its own channel in the workspace and sprints in the project
Workspace → - 2
The retainer becomes a recurring contract; invoices and charges go out on their own
Contracts → - 3
Client requests come in as HelpDesk tickets
HelpDesk → - 4
The SLA warns you before a deadline is missed
SLA →
You probably recognize this.
Disconnected tools
Tasks in one place, chat in another, billing in a spreadsheet and the client asking on WhatsApp.
Retainers billed by hand
Every month someone has to remember to issue the invoice and send the boleto to each fixed client.
Scope that grows without being charged
The client asks for more, the team delivers, and no one records the extra work.
Step by step, for Agencies & tech.
- 1 Projects →
Agile kanban with epics and waves
Sprints, dependencies and owners, with each person’s workload visible.
- 2 Workspace →
Team chat in the same place
Channels by team and by client, direct messages and video calls next to the task.
- 3 Contracts →
Retainer as a contract
Monthly fee in a contract with price adjustment; invoices and charges go out on their own every month.
- 4 HelpDesk →
Organized support
Client requests become tickets with an SLA instead of lost messages.
What you get to track
- Profitability by retainer client
- Hours by sprint and by client
- Tickets within SLA
- Team goals
Common questions for Agencies & tech
Does it integrate with the tools we already use?
Yes: a REST API with 45 resources and inbound and outbound webhooks.
What about support over WhatsApp and Instagram?
They land in the Omnichannel Inbox, with a queue and history on the client record.