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%

x

Impact2.6 / 3

x

Goal90%

x

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 powers product decision confidence

Capture every signal, from everywhere

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

Slack

Text input

Paddi Chat

File upload

Email forward

For agent / developer

Straight into the terminal

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

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

Codebase read, never retained

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

Never used for training

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

Encrypted end to end

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