Writing
Finance systems, delivery & building AI products — 158 pieces so far
How I Decide What to Build Next
Deciding what to build next isn't the loudest feature request or the most satisfying refactor — it's the recurring problem I decided mattered, on purpose.
How I Get My First Users as a Solo Builder
How to get first users: don't broadcast to strangers. Go where people with the exact problem already are, show the solution, let content compound.
How I Handle Auth, Security and User Data as a Solo Builder
Solo SaaS authentication done right: don't roll your own auth, collect the least data you can, and do the boring custodial parts deliberately.
How I Handle Support as a Solo Builder
Solo SaaS support isn't a cost to minimize — early on it's the highest-signal feedback. Do it personally, treat every ticket as product research.
How I Onboard Users to a Solo SaaS
SaaS onboarding has one job: get the user to the core outcome fast. Design it backward from that outcome — the shortest path from signup to real value.
How I Position a Product (What It Actually Does)
Positioning is the one sentence that makes exactly the right person say 'that's for me' — a chosen problem and a chosen who, not a list of features.
How I Scope an MVP
How to scope an MVP: not the smallest thing you can build, but the smallest that's actually useful — one core result for one real user, everything else cut.
How I Stay Sane Building Products Solo
Solo founder sustainability: narrow scope so there's less to hold, kill dead experiments, and refuse to read a product's numbers as a verdict on yourself.
How I Think About Distribution as a Solo Builder
Solo founder distribution is the part builders skip, then wonder why nobody came. Make it a first-class decision and let the writing be the distribution.
How I Turn a Rough Idea into a Claude Code Ticket
My Claude Code workflow for turning a rough idea into working code: write the outcome first, slice the smallest piece, and spec it tightly for an AI agent.
How I Use Analytics as a Solo Builder
Analytics for a solo SaaS: track the few metrics that change a decision — activation, retention, revenue — and ignore the vanity numbers that inform nothing.
How I Write a Product Landing Page
A product landing page that converts names the visitor's problem and the outcome in the first line — not a hero of adjectives and features nobody reads.
My Kill Criteria for Product Experiments
Product kill criteria set in advance — what 'not working' looks like: no signal, no pull, no path to mattering — are what let you run many experiments.
How I Decide Subscription or One-Time Pricing
Subscription vs one-time pricing comes down to the shape of the value: ongoing use means subscription; a one-off result means one-time. Match price to value.
Why I Build in Public
Why build in public: for a solo expert, the writing is distribution, trust and accountability at once. Sharing decisions brings in the right people.
Why I Build Narrow: Choosing Who a Product Is For
Choosing a niche makes a product sharp: a product for everyone is for no one. Pick exactly who it's for and every decision gets easier. Narrower is clearer.
Why I Don't Offer a Free Plan
Why no free plan: they attract people who'll never pay, create heavy support, and dilute focus. For a solo builder it's a tax on attention. A trial, yes.
Access Management and User Provisioning in Treasury Systems
A treasury system can move money, so who can do what inside it is a first-order control. Access management is the foundation segregation of duties stands on.
Agile vs Waterfall for Finance-Systems Delivery
How to choose a delivery approach for finance systems — why pure agile strains against a hard cutover, and why a hybrid spine usually wins.
Audit Trails and Logging in Treasury Systems
A treasury audit trail must capture who did what, when, and to what — the tamper-evident record that proves segregation of duties and approvals actually worked.
Bank Communication Management (BCM) in SAP
SAP Bank Communication Management (BCM) is the controlled gateway between SAP and the banks for payments — batching, approval workflow, signatures, monitoring.
Bank Guarantees and Letters of Credit
Bank guarantees and letters of credit are a bank's promise to pay if a counterparty fails or documents are presented — and both consume credit lines.
Bank Relationship Management
How a company deliberately manages which banks it uses, for what, and the value exchanged both ways — because the bank relationship is two-way, not one-sided.
Business Partner Configuration for SAP Treasury
The SAP Business Partner is the master-data object for the counterparties, issuers and banks a treasury deals with — and every TRM deal is captured against it.