Ship the right features out of raw user feedback

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

Problem

Reports has no export path today, so finance and ops teams fall back to screenshots or manual copy-paste. Nine customer interviews and three support calls over the past two months point to the same gap.

Goals

Export the rows and columns currently visible in the Reports table, respecting active filters.
Ship inside this sprint using the existing ReportsTable component.
Give finance teams a CSV they can drop straight into their month-end close workflow.

Non-Goals

Saved filter presets or scheduled recurring exports — tracked separately on the H2 roadmap.
XLSX or PDF output — CSV only for this pass.

Implementation notes

Wire the existing ReportsTable component to the unused csv.ts stub in src/reports/exporters — the stub already matches the rows and columns customers are asking for. The open question is where the export action lives in the toolbar, and whether large exports need to run asynchronously.

Acceptance Criteria

Export button appears in the Reports toolbar and respects active filters.
Exported CSV column order matches the on-screen table.
Exports over 10k rows complete without blocking the UI.

Rollout

Ship behind a feature flag to Northwind Traders first — the customer who asked most recently — then roll out to the rest of the enterprise tier once the export holds up under their month-end close.

Background

DraftFeatureReports

Bulk CSV export for the Reports dashboard

Enterprise customers keep asking for a way to export the Reports dashboard instead of copying rows out by hand.

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.

Refine with Paddi...

Paddi turns raw feedback into build-ready specs,
with each decision backed by your codebase and documents

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 where coding agents and developers already work

Read the docs

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 Paddi anything 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 why a change was scoped this way and which feedback drove it.

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

Security built into every step

Never retained

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

Never used for model training

None of your data is ever used to train a model.

Encrypted in transit and at rest

Everything moving through and stored in Paddi is encrypted.

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.

Join the first teams building with Paddi

Get early access Request a demo

We're onboarding a small group of teams now. Get in early and start shipping the right features.

Ship the right features out of raw user feedback

Problem

Goals

Non-Goals

Implementation notes

Acceptance Criteria

Rollout

Paddi turns raw feedback into build-ready specs,
with each decision backed by your codebase and documents

Capture every signal, from everywhere

Find the real problem behind every request

Rank by what matters most

Review the analysis, choose the path

AI drafts the spec, you refine it

Ship it however your team works

Straight into where coding agents and developers already work

Ask Paddi anything right on the spec

Fix checkout button overlap on mobile

Problem / Motivation

Goals

Non-Goals

User Stories

Acceptance Criteria

Rollout

Security built into every step

Join the first teams building with Paddi

Ship the right features out of raw user feedback

Problem

Goals

Non-Goals

Implementation notes

Acceptance Criteria

Rollout

Paddi turns raw feedback into build-ready specs, with each decision backed by your codebase and documents

Capture every signal, from everywhere

Straight into where coding agents and developers already work

Ask Paddi anything right on the spec

Fix checkout button overlap on mobile

Problem / Motivation

Goals

Non-Goals

User Stories

Acceptance Criteria

Rollout

Security built into every step

Join the first teams building with Paddi

Paddi turns raw feedback into build-ready specs,
with each decision backed by your codebase and documents