Ship the right features out of raw user feedback

Get early access Request a demo

Paddi is an PM agent that digests messy user feedback into clear specs for both human & coding agent.

Bulk CSV export for the Reports dashboard

Priority Score92

#1 of 24 requests

Reach74%

Impact2.6 / 3

Goal90%

Effort2

Relative effort

Analysis

Nine customer interviews and three support calls over the past two months point to the same gap: Reports has no export path, so finance and ops teams fall back to screenshots or manual copy-paste. The existing ReportsTable component already renders the exact rows and columns customers want — csv.ts in the reports exporters folder has an unused stub from an earlier attempt, and EXPORT-142 has sat in the icebox since Q1. Wiring the table to that stub is most of the work; the open question is where an export action belongs in the toolbar and whether large exports need to run asynchronously.

Solution paths

How large should this feature be scoped?Question 1 / 2

Export the current view onlyWire the existing ReportsTable to the csv.ts stub, respecting whatever filters are applied. Ships this sprint — ~1 day.Export with saved filter presetsSame core export, plus letting users save and re-run common filter combinations. ~3 days, closes the loop with the Q3 interview asks.Full export center with schedulingStandalone exports page supporting CSV/XLSX, filters, and recurring scheduled emails. ~2 weeks, matches the H2 roadmap.Custom approachDescribe your own implementation

Asked again for CSV export instead of manual copying

“Northwind asked again this week if they can export the whole Reports dashboard to CSV instead of copying rows out by hand.”

Requesting bulk CSV export for month-end close

Enterprise customer (Northwind Traders, $180k ARR) is requesting bulk CSV export for their finance team's month-end close.

4 of 9 interviews mention wanting CSV export

4 of 9 interviewed customers independently brought up wanting to export reports data instead of screenshotting or copy-pasting it.

StatusIn review

TypeFeatures

CategoryReports

Activity

Logged after three support calls asking for CSV export14:40

Re-scored priority14:42

84 → 92

Paddi makes product decisions at agent speed

Agentic workflow that carries every request from raw feedback to buildable spec, with each decision backed by your code and data.

Capture

Capture every signal, from everywhere

Connect where your feedback lives, or add it through built-in inputs.
Paddi groups related feedback into structured requests.

Text input

Paddi Chat

File upload

Email forward

#customer-feedback

Just now

Alex: 能不能把訂單匯出成 CSV?每次都要手動複製,真的很累…

Jamie Lin

Just now

客訴:希望能批次匯出訂單成 CSV — 使用者來信詢問是否能整批下載…

Captures

SlackPending

剛剛

用戶希望可以批次匯出訂單 CSV

Alex: 能不能把訂單匯出成 CSV?每次都要手動複製,真的很累…

EmailPending

剛剛

用戶希望可以批次匯出訂單 CSV

客訴:希望能批次匯出訂單成 CSV,使用者來信詢問是否能整批下載

GitHubProcessed

2 小時前

Dashboard 載入速度太慢,超過 5 秒

使用者反映報表頁面在資料量大時載入緩慢,體感超過 5 秒。

NotionProcessed

昨天

希望能支援深色模式

多位使用者於訪談中提到介面在夜間使用時太刺眼。

Diagnose

Every request gets investigated, not executed

A request tells you what was asked, not why. Paddi pulls evidence from your codebase and product knowledge to surface the root cause, then reframes the request around it.

Alex: 能不能把訂單匯出成 CSV?每次都要手動複製,真的很累…

搜尋 GitHub 相關程式碼

orders/export.ts — 沒有分頁,超過 1 萬筆就會逾時

查詢 Jira 相關票證

PROJ-114 — 本月已有 3 起相同回報

推理根本原因

Analysis

Alex 和信件裡的客戶問的是同一件事:能不能批次匯出訂單。Export 端點其實已經存在,只是 orders/export.ts 沒有做分頁,資料量一大就直接逾時——不是缺功能,是舊程式碼沒補完,PROJ-114 也已經躺著同樣的回報。

Prioritize

Rank by what matters most

Paddi scores every request across four dimensions, including how well it aligns with the business goals you set. Adjust the goals and the order recalculates.

ReachShare of users affected

ImpactExpected impact per user

GoalAlignment with your business goals

EffortRelative build cost, scored against your codebase

Requests

Request	Score
Checkout fails intermittently after payment step	92 x
Add bulk export for order history	85 x
Dashboard charts don't refresh in real time	78 x
Support SSO login for enterprise teams	65 x
Improve search relevance for product catalog	58 x

這個功能該做多大範圍?

Question 5 / 5

修好現有匯出的分頁 bug補上 orders/export.ts 缺的分頁,解決逾時問題,對應 PROJ-114改成非同步匯出 + Email 通知大量資料改在背景處理,完成後寄信通知,避免再次逾時打造完整匯出中心支援 CSV/XLSX、篩選預設與排程匯出,對齊 H2 roadmap自訂做法

先把匯出限制在 5000 筆以內,超過就導去非同步匯出流程,和 PROJ-114 的回報一起收斂。

Decide

Review the analysis, choose the path

You review Paddi's full analysis, then pick from the solution paths it mapped out or spell out your own. Your choice tells Paddi exactly what to build and how far to go.

Human in the loop

Paddi captures, diagnoses, and prioritizes on its own. Before it writes a spec, it hands the decision back to you.

PROJ-114

Draft

訂單批次匯出限制與非同步流程

Overview

此次改為限制同步匯出筆數,超過需求改走非同步匯出流程Paragraph

。目前匯出功能在資料量超過 1 萬筆時會逾時,本月已有 3 起相同回報(PROJ-114)。

Acceptance Criteria

同步匯出維持現有 CSV 格式與欄位順序
同步匯出上限為 5,000 筆,超過需求自動導向非同步流程
非同步匯出完成後以 Email 通知使用者下載連結

Rollout

第一階段先於內部帳號啟用同步匯出上限,觀察一週無異常後對所有帳號開放;非同步匯出的通知信沿用現有客服信件模板,不需額外設計。

Spec

AI drafts the spec, you refine it

Paddi turns your decision into a complete spec. Refine it side by side with Paddi in the built-in WYSIWYG editor until it's exactly what you want to ship.

Human on the loop

Paddi drafts the spec on its own. You're on the loop to accept it as-is or reshape any part.

For agent / developer

Straight into the terminal

Specs reach coding agents and developers where they already work.

dev — bash

npx paddi

Pull from the CLI to fetch any spec straight from the command line, no context switch, no waiting on a handoff.

Run Paddi as a skill and coding agents fetch the specs they need on their own, ready to execute.

For teams

Ask questions right on the spec

Every shared spec has Paddi built in, ready to answer the team.

ACAlex Chen

Fix checkout button overlap on mobile

Problem / Motivation

On narrow viewports, the primary CTA button overlaps the order summary total once the cart grows past two line items with a discount applied. Reported by 3 users this week, all on iOS Safari between 375–390px widths.

3 reports this week, all iOS Safari between 375–390px — the same viewport band.
Checkout is the highest-traffic screen on mobile; every added click here costs conversions.
The sticky footer hasn't been touched in 8 months and has no regression coverage below 400px.

"The button was literally on top of the price, I couldn't tell what I was paying."
— user feedback

Goals

Button stays clear of the summary total at every width under 400px.
No layout shift when the cart updates or a discount line is added.
Fix ships without touching the desktop layout or the CheckoutSummary component's public API.

Non-Goals

Redesigning the checkout summary — this is a targeted overlap fix, not a layout overhaul.
Extending sticky-footer regression coverage beyond the breakpoints named in this spec.
Changing button copy, sizing, or placement on tablet and desktop.

User Stories

As a mobile shopper with a full cart, I want the CTA button to stay visible above the total, so I can confirm my order before paying.
As an engineer on-call for checkout, I want the fix scoped behind a flag, so a bad rollout can be reverted without a hotfix deploy.

Acceptance Criteria

Summary and CTA never overlap at 375px, 390px, or any width in between.
Layout holds with 1 line item and with 6+ line items, discounts included.
No regression on tablet (768px) or desktop (1280px+) breakpoints.
Automated screenshot test added for the 375–390px band.

Rollout

Ship behind the existing mobile-checkout-fix flag, enabled for 10% of sessions first. Watch checkout completion rate and rage-click events on the CTA for 48 hours before rolling out to everyone.

Chat about this spec

What's the button's position once the cart is empty?

Same fix — the button clears the summary block whether the cart shows 0 or 5 items, so the empty state doesn't need a separate layout.

Any edge case with the sticky footer on iOS?

Only below 400px width — checked against 375 and 390 explicitly, since that's where the prior reports came from.

Type @ to mention...

Developers ask how a decision maps to the code and which edge cases to watch.

Designers ask what the change means for the flow and the states to cover.

Anyone asks and gets the reasoning behind every call, without pinging you.

Security built into every step

Paddi reads your codebase to ground its analysis, then releases it, your source is never retained.

Your code and feedback stay out of every model's training pipeline.

Everything moving through the pipeline is encrypted end to end.

Working toward SOC 2 Type II and ISO 27001

We're building to those standards from day one and pursuing formal certification as Paddi grows.

Ship the right features, starting today

Get early access Request a demo

Early access is open, bring your feedback backlog and walk away with specs your team can act on today.