BLUE DOT TECHNOLOGY

Journal

Stories about how work gets done in Texas, and how it gets better.

BUILD NOTES

How the tools get built, one decision at a time.

You've probably been promised a lot by software that didn't deliver. These notes skip the promises. Each one takes a single decision from a build that runs, explains it in plain language, and links to the working demo so you can check.

I started building with a small invoice parser, mostly to learn how the pieces fit together. These notes are what I've learned since.

  1. No. 05 What if you could just click the number?A TikTok about corporate reporting described the loop perfectly: a dashboard, more metrics, a report to explain them, then the raw data in Excel. So I built the fix from my couch, before bedtime. FRICTION → FIX · TRACEABLE METRICS
  2. No. 01 Approved isn't the same as payable.In a lot of finance teams, a signed purchase order quietly becomes permission to pay. In the procurement build, those are two different questions with two different answers. TRACEABLE PROCUREMENT
  3. No. 02 Gaps are stated, not filled.A report that always looks complete is hiding something. In the traceable-metrics build, a missing approval shows up as a missing approval. TRACEABLE METRICS
  4. No. 03 Why the warning comes before the phone call.The best control against payment fraud is a phone call. The build makes sure it's the right phone call. VENDOR ONBOARDING & PAYMENT CONTROLS
  5. No. 04 No AI writes these documents.For compliance paperwork, producing the same answer twice matters more than sounding good once. CMMC CONTROLS GENERATOR

THE TEXAS ADDRESS

Got a version of this problem? Let's figure out what we can build.

GET IN TOUCH

Built, based & serviced in Dallas. Happy to come to your office.
Or write to bluedottechnology [at] outlook [dot] com