Capital · Cost · Payments
The same dollar tells two different stories
Where technology meets the ledger. How engineering spend lands on the books, what a toolchain or an AI program really costs, how payments and card data are regulated, and how lenders and retailers decide whether to believe the person on the other end.
A technology decision is also a financial one — the board reads it in a language the roadmap rarely speaks.
The writing here is for technology leaders who have to argue with the finance side, and for anyone building software that moves money. It covers how spend is classified and depreciated, what an AI program costs once every line is counted, the rules that govern card and payment data, and the identity signals that decide whether an application is real.
The frame
Four habits that make the numbers hold
Read the Money Language series →Know which line it lands on
Capital or operating, the same spend changes EBITDA, runway and the number the board watches.
Count the whole bill
Tokens, seats, runners and review quota, totalled over months rather than quoted per call.
Card data is a scope problem
PCI compliance is cheapest when less of the system ever touches a card number.
Trust is a set of links
Fraud teams decide on device history and shared signals, not on one clean application.
Flagships
Where to start
The Money Language Series
Ten pieces that teach a technology leader the language finance already speaks: CapEx and OpEx, capitalization, depreciation, vendor commitments, AI spend and headcount.
What Building With AI Really Costs
Five months, nine repositories, about $303 a month: what the whole AI toolchain cost, what the reviewers delivered for it, and the idle server that cut the biggest line.
Field notes
Finance and fintech writing
See all →- What Building With AI Really Costs: The Whole BillAI Toolchain Costs & CI
- EHR Migration Economics: The Cash Trough Nobody BudgetedHealthcare IT Economics
- CapEx, OpEx, and EBITDA: The Same Dollar, Two Different StoriesTechnology Finance & Capital Strategy
- Reading the Financials: The Primer for Everyone Who Never Had To CareTechnology Finance & Capital Strategy
- Capitalize or Expense: Your Jira Board Is Now Audit EvidenceSoftware Capitalization & Audit
- Depreciation and Useful Life: The Chip Outlives Its EconomicsInfrastructure Depreciation & Useful Life
- Placement Economics: The Right Answer, Applied EverywhereCloud, Colocation & Placement Economics
- Lift-and-Shift or Re-Architect: The Two That Modernized LaterCloud Migration Economics
- Vendor Economics: The Email in NovemberVendor Economics & Renewals
- AI Spend: Three Budgets Pretending to Be OneAI Cost & Procurement
- AI and Headcount: Somebody on the Board Did the ArithmeticAI, Productivity & Headcount
- Outsourcing After Section 174A: Eleven Months to Relearn ItSourcing, Outsourcing & §174A
- What AI First Actually CostsAI Cost & Procurement
- The Data Never Leaves the BoxHealthcare & Finance Compliance
- Navigating the Complexities of PCI ComplianceHealthcare
- Unmasking Healthcare Costs: The Urgent Need for TransparencyHealthcare
Engage
Can your technology plan survive the finance review?
A look at how your spend is classified, what your AI and tooling really cost once every line is counted, and how much of your system ever touches money or card data.
This site: HTTPS only · no third-party trackers · no analytics cookies · security.txt