CAPTURE 01 · grafline.work · LIVE
01 · Business platform
Grafline
Problem. The same order was being typed into three different systems, and nothing agreed with anything by Friday.
Built. One platform: inventory, orders, quotes, invoices, Slovenian e-invoices (eSlog 2.0), bank-statement matching, document sync to OneDrive. Payments auto-apply only when the reference, amount and payer all agree; otherwise a human decides.
Status. It has run the company every working day since launch. Every AI feature I sell was field-tested here first.
grafline.work (opens in a new tab)AI analysis
- Stack
- Next.js front end, Express/Node API, PostgreSQL. Boring on purpose — a company runs on this, so every piece is replaceable and debuggable at 6 a.m.
- Scope
- From stock levels to state-compliant e-invoicing and open-banking reconciliation in one data model. The hard part is not any feature; it is that they all agree.
- Guardrail
- Triple-match rule: payment reference + exact amount + payer name must all agree before money touches an invoice. The AI is never allowed to guess with money.
- Measured
- Public site: ~8 KB HTML, ~0.22 s to first byte. The platform behind the login is measured differently: zero lost orders since launch.
- Verdict
- Software with consequences. The design constraint was not beauty; it was that a real company breaks if this breaks.