I BUILT CLERIYO BECAUSE I WAS TIRED OF MY SUNDAY NIGHTS

For years I owned and operated Banana Blossom — a small group of franchise restaurants. I loved almost all of it: the kitchen, the regulars, the controlled chaos of a Friday night. What I didn't love was Sunday night.

Every week after close I'd sit with a stack of supplier invoices — Bidfood, produce, linen, the POS subscription, a dozen others — and start keying. Right account. Right tax. Split across venues. Chase the invoice the statement swore existed. Watch chicken quietly get more expensive. About an hour and a half, every single week, of work that needed a brain but felt like data entry.

The filing apps were fine at turning a photo into a draft — then they handed the real thinking straight back. They never learned. I'd code the same Bidfood bill the hundredth time, or wrestle a rule-builder for something I could explain to a new starter in one sentence.

So I built what I actually wanted: something that reads every supplier bill when it lands, codes it the way the business really codes, and when it's wrong, lets me say so in plain English — “that's Kitchen, not Equipment” — and remembers. No setup theatre. No maintenance hobby. A little sharper every week.

Now weekly AP is about ten minutes. I look at what needs me. I approve. That's it.

Bookkeepers and accountants get the same idea at firm scale: keep the client fee, hand the grind to Cleriyo, spend your talent on judgment and advice.