How Punch Trade hands its product roadmap over to the trader community
Most product roadmaps at retail trading platforms sit inside a private Notion page or a Jira board, ranked by an internal product manager balancing engineering capacity against business priorities. Punch Trade, the deep discount broker run by Market Pulse Securities,...
Most product roadmaps at retail trading platforms sit inside a private Notion page or a Jira board, ranked by an internal product manager balancing engineering capacity against business priorities. Punch Trade, the deep discount broker run by Market Pulse Securities, has taken a different route. The company runs Builder's Lab — a public-facing tracker where active traders raise feature requests, vote on what other traders have logged, and watch each item progress from a request through to a shipped build. What ships next on the platform is decided by the votes that accumulate from active users — roadmap-setting handled as a community-led process rather than a closed internal exercise.
The public roadmap is split across two boards — one for Punch's Android app and one for the desktop terminal. The Android Roadmap is published at Punch Android Roadmap and the Desktop Roadmap at Punch Desktop Roadmap. Both pages are open without login — anyone can read what is queued, what is in build, and what has already shipped. Each item carries the request that triggered it, the vote count it has received, and where build is complete, the live date. Most retail trading platforms keep this kind of detail private. Builder's Lab makes it public. Builder's Lab is also where bug reports and product issues live. A trader who hits a problem files it on the same board as a new-feature request, with the same public visibility on votes and build status. This puts the trader in direct contact with the product team — not routed through a support layer that translates the issue before it reaches the people building the product.
The mechanics are deliberately simple. A trader who wants a specific capability — a new order type, an indicator, a UI change, a behaviour adjustment — files the idea publicly on Builder's Lab, where it becomes visible to other users. Other traders endorse it with a vote, add comments or refine the request, and the aggregate vote count becomes the public ranking that informs the engineering sprint queue. Punch reports more than 500 distinct feature requests filed on Builder's Lab to date — a stand-in for the kind of structured product feedback that is not commonly collected at scale across the discount broking industry in India.
The shipped items put concrete numbers behind the approach. Trade-wise PnL — the per-trade profit-and-loss breakdown, distinct from a daily aggregate — drew 247 votes before Punch began work, and the build closed in 9 days. The drag-and-drop SL-and-target flow on the chart, filed inside Builder's Lab as Drag & Drop SL/TP, has accumulated 471 community votes. The side-by-side layout for the spot index and its options chart, filed as Split Charts, drew 189 votes and shipped within 11 days of prioritisation. Scalper Joystick — the one-tap option order tool with preconfigured exit levels — drew 258 votes; the build took 30 days, reflecting deeper engineering work on the underlying order layer.
The reason this model is uncommon in Indian retail broking has less to do with technology and more to do with operating posture. The conventional approach across the industry has been to keep roadmap-setting as an internal product function, with user feedback collected through
support tickets, Telegram groups or periodic surveys rather than converted into a published, ranked queue. Punch's decision to publish the queue, vote counts and shipped-versus-pending status against each item turns roadmap-setting into a transparent process — traders can see which requests entered a sprint and which remain near the back of the line. The company describes the orientation as treating an active trader as a product collaborator, not a feedback source.
Three platform-level facts sit alongside the Builder's Lab boards. Brokerage runs at ₹1 per executed order, the same rate across every segment the broker supports, with no paid plan on top of the trading app. The charting engine is a Punch-developed module, shipped inside the trading app rather than licensed from a third-party charting service. And the trading layer keeps risk-control settings on by default — pre-trade SL/TP, attached protective legs, a trader-set trading lock — wired into the order path itself.
For Indian retail traders who care about being heard inside a product they use every day, Builder's Lab is a structural choice rather than a marketing line. The roadmap, the vote tallies and the ship-times sit on pages anyone can open; what gets built next on Punch is, by design, an outcome of the ongoing conversation the company has agreed to have with the traders already on the platform.
