Built for the work you do every week, not for projects
A project has a start, an end and a plan. Operational work has none of those — it arrives, it is assigned, it changes hands, it repeats, and it has to be evidenced afterwards. That is the shape TaskIt is designed around.
30-day free trial, then ₹45 per active team member per month.
The problems this page is about
If none of these describe your week, a different page on this site probably does.
How it goes today
Project tools assume a project
Gantt charts, sprints and milestones describe planned work with an end date. They have nothing to say about a customer complaint that arrived this morning and has to be resolved by Thursday.
The business runs on WhatsApp and a spreadsheet
One is the notification layer and the other is the record, and neither knows about the other. Both are maintained by hand, and the spreadsheet is always a day behind.
Work spans teams and stalls between them
Something needs Accounts, then Operations, then approval. Each boundary is a message to a person, and each message is a place where work can stop.
The owner is the system
What gets done, by whom, and whether it was done properly all live in one person’s head. That works up to a point and then abruptly stops working.
With TaskIt
Intake that fits your actual work
Build a task form per request type — maintenance, purchase, complaint, onboarding — from eighteen field types, so each kind of work arrives with the information it needs.
Routing that does not depend on the owner
Raise work for a department and let the team claim from the queue, in Single Owner mode when one person should finish it or Collaborative when several genuinely share it.
A lifecycle with an approval in it
Work is accepted, progressed, possibly handed over or blocked, then submitted and reviewed. Nobody approves their own submission, so "done" is somebody else’s judgement.
The repeating half, scheduled
Daily opening and closing routines, weekly reconciliations, monthly filings and annual renewals become schedules with execution histories rather than reminders in one person’s phone.
Evidence when it is needed
Handover history, the task activity timeline and an append-only audit log answer questions about the past without anyone having to remember them.
What the first month looks like
A 25-person business moving off WhatsApp and a shared sheet.
- 1
Week one — structure
Departments, three roles built from real permissions, the team imported from a spreadsheet, and two task forms for the two most common request types.
- 2
Week one — the routine
The six jobs that repeat every week become schedules. This is usually the change people notice first, because it removes an hour of retyping.
- 3
Week two — notifications
Task creation and handover alerts to the team’s WhatsApp group, so the channel people already read carries the alerts and the app carries the record.
- 4
Week three — the daily report
An 18:00 summary of what was assigned, what progressed, what completed and what is blocked, delivered whether or not the owner is in.
- 5
Week four — the first real question
"Why did that job take nine days?" is answered by opening it: two of those days were Blocked, waiting on a supplier.
The result
The owner has stopped being the routing table, and the parts of the business that used to live in their head are now readable by anyone with the right permission.
The result
No percentages, because nothing here has measured yours — these are the changes the mechanism produces.
The business keeps running when key people are away
Queues, schedules and recorded handovers mean absence is an inconvenience rather than an outage.
One record instead of three systems
The task is the record. WhatsApp becomes the alert channel, and the spreadsheet becomes an export rather than a source of truth.
Questions about the past are answerable
What happened, who had it and when are all recorded as the work is done, rather than reconstructed afterwards.
Costs scale with the team, not with the feature list
The three plan terms are feature-identical, so nothing is gated behind a more expensive tier — you only choose how often you are invoiced.
Frequently asked questions
No. There are no Gantt charts, no sprints, no milestones and no dependency planning. It is built for ongoing operational work: requests that arrive, get assigned, change hands, repeat on a cadence and need to be evidenced afterwards.
Departments, roles and an imported staff list are usually an hour. Task forms and recurring schedules take another hour or two, and are worth doing before the first real task rather than after fifty of them.
There is no plan fee. You pay ₹45 per active team member per month, plus 18% GST, and choose whether you are invoiced monthly, every six months or annually. WhatsApp and cloud storage are optional add-ons. The count follows your active team automatically.
Yes, and most teams should. Pair your own number and TaskIt will send task creation, handover and completion alerts plus scheduled reports to a person, a group or both. The difference is that the record lives on the task rather than in the thread.
Where to go next
The capabilities behind this page, and the neighbouring situations they also cover.
Run a month of real operations through it
The trial is thirty days on purpose — long enough for a full monthly cycle, including the parts that only happen at month end.