Practical software, built with Claude and tested in daily use.

I build tools for real workflows, then keep them small, private and offline-friendly. Most are free. The ones that took the most work are paid.

Software

Release dates are rolling out over the next few days. Each product gets its own page with downloads, screenshots and a live demo where one makes sense.

ClockRoute

Progressive web app · any phone

Time clock and pay tracker for nurses, tradespeople and local drivers. Tracks your hours and shows what you actually earned per hour. Your data stays in storage you own.

Removes ads · monthly or lifetime

CORE

Windows app · offline

Runs a department's staff training, credentials and scheduling from one file. Replaced 12 spreadsheets in daily use at a healthcare department. Configuration packs adapt it to other industries.

One-time license

Benchdrop

Windows app

Drop in a project folder or repo link and it installs, launches and tests the app for you, using Claude to spot what looks broken. Never fills passwords or clicks destructive buttons.

Free · coming soonWindows SmartScreen will warn on first run

ChatScribe

Chrome extension

Exports AI conversations from Claude, ChatGPT, Gemini and Perplexity to PDF, Word or Markdown. Runs entirely in your browser.

Free · coming soonChrome Web Store

Deskside Dial

Chrome extension

Control playback, seek and use global shortcuts across every media tab. No network requests, no analytics.

Free · coming soonChrome Web Store

How I build

Every project is built with Claude Code. I define the problem, set the constraints, test against real users and decide what ships.

Local-first

Your data stays on your device or in storage you control. My servers don't hold your records, and the software works without a connection wherever possible.

Small permissions

Extensions ask for only what they need. No analytics, no tracking, no accounts unless the tool can't work without one.

Honest about limits

Everything is provided as-is. I read every report and I usually fix things, but I don't promise a fix or a feature. The terms say so plainly.

Sixteen years of fixing systems, now building them

I'm Rick Griffith, based in Vinton, Virginia. I spent 16 years diagnosing and rebuilding technical systems, from a 250-room national laboratory to enterprise conference rooms, after serving as a U.S. Army signal specialist. Since 2024 I've been building software around large language models.

I still drive a truck for a living, which is why these tools are built for people who have real work to do and no time for software that gets in the way.

Found a bug or want a feature?

Tell me what broke or what's missing. I read everything, though I can't promise a fix or a timeline.

Send feedback