Not a brochure — a recording of a working system. Six real admin screens in two minutes nineteen seconds, including a RoadMap board with vote counts — but not one screen is a public, no-login page or a customer notification screen. Then the honest India price, and why this recording is an internal feedback log, not a public product-feedback portal.
Customer feedback management software, at least the working system recorded here, is an internal feedback log for a product or support team — not a public voting board or roadmap page a customer would ever see. The video below is a recording of a working system, not a slideshow: 6 real screens in 2 minutes 19 seconds. In India, deployment starts at ₹1,00,000 with maintenance from ₹3,000/month, and a from-scratch build that adds a public voting board, a roadmap and changelog page, and customer status emails is a 6–16 week custom project. One honesty check first: this video names five features — of those, one is fully shown on screen, two are half-shown, and two do not appear at all.
Full walkthrough · 2 min 19 sec · English
ZoopCoder’s Hindi channel recorded the identical admin panel — the same six screens, the same features — for anyone who would rather watch the walkthrough in Hindi than English.
Full walkthrough · 2 min 27 sec · Hindi
Every screen recorded here — Dashboard, Manage Feedback, Products, User, Archives, and a RoadMap board — is something an admin or support agent opens, not something a customer ever sees. The RoadMap screen genuinely shows a Kanban-style board (Under Review, Planned, In Progress, Completed) with a vote count against each item — the closest thing in the recording to the public feedback boards a tool like Canny or Frill is built around. But it is only ever opened from the admin login: the recording never once shows the public, no-login version of that same board, so whether an anonymous customer sees the same thing, a locked-down view, or nothing at all is not demonstrated.
ZoopCoder is paid to deploy and to custom-build these systems, and the rule above tells a share of readers — someone who wants an internal tool to log and tag customer feedback for their own product team, and does not need a public-facing board — that this demo is close to what they need already. A public, no-login render of the roadmap board already shown is a different build, and pricing it as if this admin panel already exposes it publicly would be dishonest.
Want this priced for your team?
Tell us whether you need the internal feedback log shown here, a public render of the roadmap board with voting, or both. We come back with a fixed, itemised number — on WhatsApp, within one working day.
Six recorded screens in total, all opened from the admin login — including a RoadMap board — but none of them is the public, no-login view a customer submitting feedback would actually see.
| Screen | What it actually does |
|---|---|
| Dashboard | A single-screen summary of open feedback and recent activity |
| Manage Feedback | The core feedback list, with Category, Vote and Public Page columns visible on every row — where an admin reads each submission and updates its status, all from the admin login |
| Products | The list of products or projects a feedback item can be filed against — one of two categorisation axes in the recording, alongside the Category column on the Manage Feedback list |
| User | Registered accounts able to submit feedback, managed from the admin side |
| Archives | Feedback items moved to a closed state and out of the active queue — the only status-tracking evidence in the recording |
| RoadMap · Overview | A Kanban-style board with Under Review, Planned, In Progress and Completed columns, and a vote count against each feedback card — opened from the admin login, with no public, no-login version ever shown |
This video names five features in its description. Judge each against what is actually opened on screen, not the description.
| Claimed feature | On screen in the recording? | What is actually shown |
|---|---|---|
| Feedback boards and voting | Shown | The RoadMap board shows a vote count against every card, and Manage Feedback shows a Vote column on every row — both from the admin login, never a public no-login view |
| Status updates for customers | Not shown | Archives shows an internal closed state, but no email, notification or customer-facing status screen ever appears — whether the submitter is told is not shown |
| Tagging and categories | Half-shown | Products and the Manage Feedback list’s own Category column both categorise by product, but no separate tag or label management screen appears |
| Roadmap and changelog | Half-shown | The RoadMap board (Under Review/Planned/In Progress/Completed) is genuinely there, but only from the admin login; no separate public changelog or shipped-features page ever appears |
| Response analytics | Not shown | What was assumed to be an analytics screen is actually the RoadMap board — no per-product, per-status, or resolution-time breakdown, and no exportable report, is ever opened |
Net result: one of five claimed features is fully shown, two are half-shown, two do not appear at all. What the recording actually demonstrates well is an internal admin experience — a feedback list, product tags, an archive, and a voting RoadMap board — but never the public, no-login side that a real customer-feedback product like Canny or Frill is built around.
Three things sit between this recording and a product your own customers would actually use directly: a public, no-login render of the RoadMap board already shown, so an anonymous visitor can browse and vote on it rather than only your admin staff; automatic email or in-app notifications when a submission they made changes status; and an embeddable widget so feedback can be collected from inside your own product rather than a separate site. A standalone changelog page — a simple chronological list of what shipped, distinct from the Kanban board already shown — is a smaller addition on top of those three. None of the six recorded screens is public-facing — all six, including the RoadMap board, are things your internal team opens, not your customers.
These are ZoopCoder’s own published numbers, from the pricing page — not a market survey. Your exact figure comes from a fixed written quote, returned in 24–48 hours.
| Route | What you get | Price | Time |
|---|---|---|---|
| Deploy & configure the system in this video | Feedback list, product tagging, user accounts, archive, your branding, staff trained | From ₹1,00,000 | Weeks, not months |
| Custom build from scratch | Built to include what this demo does not — a public, no-login render of the roadmap board already shown, a standalone changelog page, customer status notifications and an embeddable widget | Custom software, from ₹1,00,000 | 6–16 weeks |
| Keeping it running | Security updates, backups, bug fixes, support — Basic / Professional / Enterprise | ₹3,000 / ₹8,000 / ₹15,000+ per month | Ongoing |
| Included either way | Full source code and database ownership, documentation, 30 days post-launch support, staff training | ₹0 extra | — |
Payments follow the standard schedule — 30% at kickoff, 40% at the mid-project milestone, 30% on delivery. Build times match the window in our timeline guide, where every three days you take to approve a stage adds roughly a week to the calendar.
Not the internal feedback log. Four things, in this order:
The working system ZoopCoder recorded is a small internal admin panel for logging and tracking product feedback — 6 real screens in 2 minutes 19 seconds covering a dashboard, a feedback list, product tagging, registered users, an archive of closed items, and a RoadMap board with vote counts. That board only opens from the admin login — there is no public, no-login version, and no separate changelog page anywhere in the recording.
Deployment and configuration starts at ₹1,00,000, maintenance runs ₹3,000 / ₹8,000 / ₹15,000+ per month by plan, and a from-scratch custom build that adds a public render of the roadmap board, a standalone changelog page and customer notifications is 6–16 weeks and priced as custom software.
Partly. The admin panel has a RoadMap board with a vote count on every card and status columns (Under Review, Planned, In Progress, Completed) — but only from the admin login. The recording never opens a public, no-login version of that board, and there is no separate changelog screen.
There is no evidence of that in the recording. Archives shows items moved to a closed state internally, but no email, notification or customer-facing status screen ever appears.
A small product or support team that wants an internal system to log, tag by product, and archive customer feedback. It is not, as recorded, a public feedback portal for a SaaS product — that needs the roadmap board’s public render, plus a changelog page, added as a custom build.
Tell us whether you need the internal feedback log shown here, a public render of the roadmap board with voting, or both. We come back with an itemised, fixed-price quote within 24–48 hours — including what we would leave out to bring the number down, and what year one costs to run.
All software demos · Helpdesk ticketing software · How long it takes to build · What maintenance really costs · What a quote must include · ZoopCoder pricing · All guides