What shipped each release, in cadence — AP+AR on one ledger, two-sided cash forecasting, AI invoice chasing, dispute escalation, the contact form, and Stripe checkout. Written for SaaS finance leads evaluating Paymind.
Launched /blog as the cash-flow content hub for SaaS CFOs, with three posts on AP+AR unification, small-team cash forecasting, and why a spreadsheet-only forecast misses the negative week before it hits the bank. The hub index emits an ItemList JSON-LD so the posts surface alongside the comparison cluster, and the reading order matches the /forecast methodology.
The dispute queue on /dashboard now ships with an admin-only AI draft-reply endpoint that drafts a tone-appropriate response straight into the thread, reason-coded routing that sends repeat reasons on the same customer to the right owner, and a tamper-evident audit trail covering every status change, override, and write-off.
Pricing now routes through Stripe’s hosted checkout via createCheckoutSession — both the fixed one-time and the recurring subscription tiers. Prices are computed server-side from the active plan, the redirect is generated per-request, and verifyCheckoutSession confirms the success page so we never rely on a hardcoded Stripe URL.
Added the public /contact page backed by a zod-validated POST /api/contact route. Submissions persist to the ContactMessage table and are delivered via the Polsia email proxy to the company inbox, so the same surface that ships the first reply is the one that owns the queue on the controller side.
Shipped the chasing-dispute schema and the reminder engine’s first cron-bridge surface on top of the same AP+AR ledger. The public /chasing explainer lands on top, walking through how the AI chasing agent reads an overdue invoice, drafts a tone-appropriate follow-up in your house style, and hands each message back to a human before it goes out.