Spend is a design decision, Pilfer is there to make sure you treat it like one.
Joined April 2026
- Tweets15
- Following2
- Followers2
- Likes0
quick update:
banking integration is in progress.
soon you’ll be able to pull transaction data directly into Runway instead of logging everything manually.
every purchase needs two receipts:
one for finance,
one for future-you asking “what were we thinking?”
Pilfer is for the second.
bad buys don’t look expensive on day one.
they look expensive 30 days later when they block better purchases.
spend on high-leverage decisions, not loud requests.
New: Runway Monthly Plans
Align monthly spending with a company goal, set a savings target, and track whether spending actually supports that direction.
some purchase requests need serious discussion.
some purchase requests need adult supervision.
The new “NEVER” status for scouts is live now.
For those “we should buy this” requests that should never be considered
real-time collaboration is fun until two people make opposite “essential” purchases at once.
merge conflict in code is annoying.
merge conflict in procurement is expensive.
most teams repeat purchase mistakes because the context disappears after approval.
if you want better decisions, keep a record of the reasoning,
then review outcomes against what you expected.
no memory, no learning.
buying a camera body without the right lens is peak impulsive procurement.
force a dependency check up front:
what else must exist for this to be effective?
without both, it’s not a camera system.
it’s an expensive paperweight.
we ship.
we forget to announce.
we ship again.
Catch all this (or not) and more on the new changelog: changelog.getpilfer.com/
most tools merge everything into "expenses" and call it a day
pilfer splits the ontology on purpose:
- runway transactions = what already happened
- scouts/assets = long-term planning + procurement intent
