Krato
Tickets, projects, time tracking, and contracts in one place, with limited and revocable sharing.
The context
Following a request across different tools.
For an MSP, a request can span tasks, time entries, contracts, and billing. When every step lives in a different tool, reconstructing what happened creates extra work.
The challenge
Connecting tasks and managing access.
Keep operational and administrative work in the same system without giving clients and collaborators access to information that does not concern them.
The solution
Moving data from one task to the next.
I designed Krato so information can move from one task to the next without duplication. Every share is limited, can expire, and remains revocable.
The outcome
From request to report, with ownership and time in plain view.
Krato supports the workflow from request to report and makes responsibilities, time, and financial status visible. The product is launching and accepting access requests.
Inside the project
A closer look at the project.
From the ticket queue to the project board
The ticket queue, a request with its SLA and conversation including an internal note, then the project board: a task moves to Completed, and the summary shows 50% progress and five open tasks. Demo data, English interface in the Notte theme.
Enlarge the screen Milestones, tags and documents
Three milestones with status and due date, three tags and two documents with author and date on the Customer operations rollout project page. Same demo data as the video.
Enlarge the screen Tasks on a timeline
The Timeline view brings together the project’s ten tasks and three milestones, with work periods and deadlines. Same demo data as the video.