Katie L. Thomas, CPA

Things I've built.

Much of the most consequential work I've done belongs to the companies where I did it. What I can share here are a few projects that illustrate how I think, what I build, and what I learn along the way.

VERA

A finance tool designed to move month-end reviews beyond the obvious.

The problem

Budget-to-actual reviews can consume a surprising amount of time explaining things everyone already knows. Payroll is higher because of a third pay period. A vendor invoice hit a different month. An expense shifted between departments. Someone has to find the variance, document the explanation, and move to the next one.

There's value in doing that accurately. But if the whole process stops at narrating movement, finance has spent a lot of time describing the past without getting much closer to a decision.

What I wanted to test

Could a tool do the first pass (retrieve the numbers, surface exceptions, draft the routine explanations) so the people doing the review could spend more time on the questions that actually required judgment?

The idea came from a seminar where Anthropic's finance team showed what they had built for their own work. I took extensive notes, went back to my own environment, and built a version around the problems I wanted to solve.

What it does

VERA connects financial information from an ERP to a budget-to-actual review, highlights variances worth investigating, and generates first-pass explanations for a person to examine and refine.

The broader workflow also addresses accruals: identifying potentially missing expenses, proposing entries, and routing them for review rather than assuming the software should be able to post whatever it decides.

The design choice that mattered

Automation should move work forward without obscuring accountability. The workflow keeps approval with a person: the system prepares a proposed entry, and the general ledger doesn't change without an authorized review.

  1. ERP dataFinancials pulled from the ERP
  2. First passVariances flagged, explanations drafted
  3. ReviewA person investigates and refines
  1. Proposed accrualA missing expense is identified
  2. ApprovalAn authorized person signs off
  3. PostingThe entry reaches the ledger
A conceptual illustration of the workflow. VERA was created in a work setting, so there is no public demo and no internal screenshot here.

Flo

A practice app built to distinguish playing the flute from sitting next to one.

The problem

My daughter was supposed to practice the flute for 15 minutes a day. The trouble was that 15 minutes with the instrument out of its case wasn't necessarily 15 minutes of practice.

I wanted a way to track actual playing time without becoming the household practice monitor.

What I built

Flo tracked practice sessions and counted time when notes were being played. It also gave my daughter a reason to come back: she could earn digital charms for a virtual bracelet as she met milestones.

It was a small app with a specific user, a real behavior to support, and a simple test: would it make practice easier to track and more appealing to do?

Screenshot: Timer
Screenshot: History
Screenshot: Charm bracelet
Flo screenshots: timer, history, and the charm bracelet.