/

CASE STUDIES

/

2026

/

PayKit

Organizing R&D workflows and project visibility in ClickUp for a POS platform

Byte&Kite migrated a POS platform's R&D from Jira to ClickUp, restructuring 8 spaces into one system with workload tracking and AI reports.

Byte&Kite migrated a POS platform's R&D from Jira to ClickUp, restructuring 8 spaces into one system with workload tracking and AI reports.

/

CLIENT

/

TIMELINE

2 months

/

SERVICES

ClickUp Implementation

/

OVERVIEW

CHM Software is the company behind Chameleon POS and PayKit POS, two POS solutions built for automating retail and HoReCa business processes — including sales, inventory, finance, and CRM. As the company scaled, the marketing team grew alongside it, and needed an operational system that could connect strategic planning with day-to-day execution.

/

CHALLENGES

Jira had outgrown the team's needs


Before the project, PayKit's R&D team worked in Jira, set up as a flat task list without automations or dashboards to support sprint planning at scale. Documentation and communication were scattered across other tools, including Google Drive. As the team grew, work stayed spread across Jira and these disconnected tools, without a single source of truth.

Time wasn't split out by client

Hours were logged at the team level rather than by client or internal task, which made it harder to see how effort was distributed across accounts.

Workload wasn't visible in real time

There was no way to see who was overloaded until issues had already surfaced elsewhere.

Some tasks kept causing delays

Certain tasks kept slowing down releases and reporting, but without data, it was hard to tell which ones or why.

With Jira, we weren't seeing what was happening with workload or progress on team goals. Byte&Kite set everything up so well that ClickUp now gives me full control over clients, the team, and finances.

Dmytro Agapov

CEO of PayKit & CHM

/

SOLUTIONS

One workspace instead of eight scattered projects


We consolidated all Jira projects into a single ClickUp workspace, organized into 2 to 3 spaces with clear folders and product tags. Client work and internal work were separated into their own structures, each with its own lists, views, and rules.

  • Each product got its own lists with one shared status flow. Backlog moves to Planning, then In Progress, Review, and Done

  • Fake sprints were replaced with a Kanban board using WIP limits, making progress and blockers visible immediately

  • Recurring processes such as development, testing, and reporting got templates and checklists to standardize work across tasks

Communication and documentation inside ClickUp


We brought communication and documentation into the same system as the tasks, removing the split between Google Chat and Google Drive.

  • Chat views were activated for every project and department, putting discussions next to the relevant tasks

  • ClickUp Docs replaced Google Docs for specs and guides, attached directly to tasks instead of living in a separate Drive folder

  • Support forms now turn client bug reports into tasks automatically, with all fields filled in.

Automations, workload tracking, and AI reporting


We set up automations to handle the manual work PMs were doing by hand, including auto assigning tasks, escalating statuses stuck in "Blocked" or "Overdue," and sending reminders when a task moved into Review.

  • Workload views were configured for every team member, paired with Timesheets vs Workload reports comparing planned and actual hours

  • Goals were linked to tasks so it's visible which work is actually moving OKRs forward and which is just accumulating

  • AI agents generate daily R&D progress reports, flagging anomalies and stuck tasks before they become release risks

/

RESULTS

The new ClickUp setup gave PayKit's R&D team a single system to plan, track, and report on its own work


Operational effect

The team can now see real workload and plan realistic volumes of work instead of estimating from memory. Client and internal tasks are separated, and the whole team follows the same process for statuses and deadlines. Delays surface earlier, and automations cut down on manual reminders and repeated overdue tasks.

Business level

Management gets release progress, per developer and per client workload, planned versus actual hours, and OKR progress without building manual spreadsheets, plus a daily AI report on risks and anomalies.

-3h

WEEKLY ON REPORTING

20+

AUTOMATIONS

8 to 1

TOOLS UNIFIED

Looking for a better way to work?

Let's explore what could work for your business.

Oleksandr Vivchar

Looking for a better way to work?

Let's explore what could work for your business.

Oleksandr Vivchar