Planner.day is project management software founded in 2026 by Ankit Raj, who owns and
runs it. It started because two things kept being true. Our assistants could describe the
backlog but never change it. And customer feedback lived in a different product from the work it turned into, so
the person who reported a bug never found out it was fixed.
Most tools added an LLM to summarise a screen. That is a demo, not a colleague. We wanted
the product itself to be callable, so we shipped a real MCP server: the same 43
operations the interface exposes, over the same permission checks, reachable by whatever
assistant a team already uses.
Collecting feedback is the easy half. The half everyone skips is telling the person it
shipped. So that is automatic here, including for people whose duplicate report got
merged into someone else’s, who are the ones normally dropped on the floor.
A project tool is judged on the boring parts: what happens when two people save at once,
what happens when the email should have gone out, what happens on the ten-thousandth
task. Four choices, made once, that most of the product then inherits.
3.1
One pipeline, three doors
A click in the app, an MCP tool call and a REST request take the same path: same
permission checks, same validation, same activity record. There is no faster, looser way
in, which is why granting an assistant access is a scoping decision rather than a leap of
faith.
3.2
Side effects come out of the database
Emails, notifications, realtime updates and the activity trail are not fired off inline
and hoped for. They are derived from an outbox row written inside the same transaction as
the change itself, then processed separately. If the change committed, the follow-up is
owed; if it rolled back, nothing was ever queued.
3.3
Two edits, no silent loser
Every record carries a version. When two people change the same task at the same moment,
the second save is told it is stale and gets a merge path, rather than the quiet
last-write-wins that makes people distrust a tool without ever being able to prove why.
3.4
Lists page, always
Every list is read with keyset pagination, around twenty rows at a time, with the totals
computed server-side rather than counted from whatever happens to be loaded. A list with
ten thousand tasks opens like an empty one, and the number at the top is right while the
rows are still arriving.
04 · Who it is for
Built for work that needs an owner
Planner.day is for teams that want every task to carry an owner, a priority and a date,
their AI assistant to work the board under the same permissions they have, and their
users’ feedback to land in the same system as the work. The same summary is written
into llms.txt, the plain-text file answer engines read.
Built for
Ownership
Every task carries one owner, a priority and a date, so “who has this?” has an answer on the board.
Your assistant
Claude, ChatGPT or any MCP client works the board through the same permission checks as you do in the app.
Your users
Bug reports and feature requests from the feedback widget land as tasks, and the people who sent them are emailed when the work ships.
How we run it
Owner
Planner.day is owned by Ankit Raj and run by him with the Planner team.
Billing
Prices are set in Indian rupees and every invoice is a GST invoice.
Releases
Every release is dated and described in the changelog, newest first.
Have a look
Judge it on the boring parts.
Free for up to 5 people, and the first month on Basic or Pro is free. The security page sets
out every control in the same plain terms as this page.