How many concurrent Tally users should you plan for?

Under-sizing Tally on Cloud is a common cause of “Tally is slow today” tickets. The plan you buy should match how many people work in the company file at the same time — not how many people have an email address in the firm.

Named users vs concurrent users

Five accountants on payroll does not always mean five concurrent sessions. One may be on leave, one only posts vouchers in the evening, and two may share peak mornings. Concurrent count is: “how many people open the live company at 11 AM on a busy day?” Size for that peak, not the quiet Friday afternoon.

A simple sizing rule of thumb

• Count branches or desks that need live books during office hours
• Add 1–2 seats for CA / auditor / owner login during GST weeks
• If you already queue for a company lock on local multi-user, you are already past single-seat comfort

When in doubt, start honest about peak concurrency and leave a small buffer — upgrading mid-filing season is harder than planning one seat early.

What feels like “need more seats”

Logins that hang, reports that crawl only when three people are in, or remote users timing out while the office PC feels fine. Before blaming the internet, check concurrency and whether someone left an idle session open overnight. Pair this with sane remote access habits.

Talk numbers, not vague “multi-user”

When you enquire, tell us company size, peak concurrent users, and whether GST / audit weeks spike. That is enough to recommend a practical cloud Tally footprint without overselling hardware.

Ready to size a plan? Contact KC Cloud or open a support ticket. Watch status if logins already feel off before you change capacity.