saascode
finance, accounting & spend·run 143 · Jun 2026

Feeprune

A read-only payment-cost workspace for agencies, SaaS operators, and platforms that reconciles official charges, balance transactions, fee components, refunds, disputes, currencies, connected accounts, transfers, and payouts; models bounded alternatives under current provider terms; and tracks approved implementation plus matched follow-up while keeping recommendation, provider eligibility, configuration change, acknowledgment, bank cash, accounting result, and realized saving separate.

Genesis score6.90/10
Make Feeprune real.0/500
500 more votes and Feeprune is authorized for build.
0%500 to authorize
Backing is the vote. When an idea crosses 500, we pull it into the build pipeline and ship it for real — the votes decide what gets built next, not an editor.
The opportunity
0Cross-references
2Inbound connections
0Direct connections
The case

Payment costs vary with transaction size, method, geography, currency, refunds, disputes, platform configuration, connected accounts, transfers, and payouts. Feeprune explains observed cost and creates reviewable alternatives without changing provider configuration. Read-only access does not make source data complete, a fee model is not a provider quote, an estimated saving is not a contract or guaranteed result, an implementation checklist is not an approved change, and a lower later fee rate does not prove the recommendation caused the difference. Source event, normalized cost, model assumption, recommendation, finance review, provider discussion, approved change, provider acknowledgment, destination readback, matched observation, accounting review, realized saving, confounder, reversal, and correction remain distinct.

Who pays — and why

A founder, finance, payments, platform, agency-operations, billing, or RevOps owner at a SaaS company, agency, or marketplace with enough transaction and connected-account complexity to make provider fees difficult to explain.

What it unlocks
A payment-cost evidence model linking provider account, platform and connected account, payment attempt, charge, balance transaction, fee component, refund, dispute, recovery, currency conversion, transfer, payout, volume band, source time, availability time, reconciliation, and correction
A versioned scenario contract recording current configuration, proposed change, eligible scope, provider terms and date, assumptions, excluded costs, volume and mix, fee formula, operational consequence, risk, estimate range, confidence, finance reviewer, and correction
A savings-verification lifecycle distinguishing recommendation, approval to investigate, provider quote or eligibility, customer approval, implementation request, provider acknowledgment, configuration readback, observation window, matched baseline, actual fees, mix and volume changes, confounders, finance conclusion, realized saving, reversal, and correction
How Genesis scored it
6.90across seven criteria
tension 6temporal 8blindspot 5buyer 8leverage 8convergence 5why-not 7
8
Temporal window

Several live products establish current category formation, subject to ongoing provider and competitor changes.

8
Buyer persona

Founders and finance or payment owners at agencies, SaaS companies, and platforms have a concrete recurring cost question.

5
Convergence

Zero cross-references, two inbound connections, and zero direct connections provide light graph support.

Why it scored well

Two inbound connections, several confirmed payment-cost products, a direct competitor, a verified gap around layered connected-account and payout costs, a concrete agency and platform buyer, and read-only data access support the direction.

What's holding it back

There are no cross-references or direct connections, the category is already several products deep, no structural copying cost exists, provider terms and fees change, estimates depend on business mix, some changes require negotiation or operational tradeoffs, and savings attribution is difficult.

Signals detected4 sources crossed
SignalSource-run competitor verification

SignalSource-run market synthesis

SignalSource-run provider verification

SignalSource-run gap analysis

Direction brieffeeprune.md
feeprune.md
Want this pointed at your vertical?Point Genesis at your own market and constraints — it invents adjacent, fork-ready ideas, private to you before they hit the public feed.

Discussion

?

No comments yet — be the first to weigh in.