I take real workflows—usually the ones that have outgrown spreadsheets, email chains, generic software, or institutional memory—and turn them into purpose-built systems.
I design the systems. I use ChatGPT to help me code them.
I am not selling myself as a hand-coding software developer. I use ChatGPT as a coding collaborator under my direction. If you hire me, you are hiring my experience in understanding the work, designing the system, directing implementation, testing it against reality, refining it, deploying it, documenting it, and teaching people how to use it.
SELECTED MACHINES
See the actual shape of the work.
For several projects, you can open a demo version of the application shell. These are not simplified “concept demos.” They preserve the navigation, density, workflow structure, and visual language of the real machine while replacing private or operational records with invented data. Nothing is saved.
01
NONPROFIT OPERATIONS
Custom Non-Profit Data Manager
Overview
A customizable nonprofit data and operations manager that brings constituent relationships, gifts, acknowledgements, grants, purchasing, finances, tasks, data health, and institutional knowledge into one connected system.
From me
I started this machine because everything was done in separate spreadsheets that didn't connect to each other, weren't intuitive to update, and were hard to visually understand. Institutional knowledge was all scattered. So, I set out to create a repository that is functional, user-friendly, and customizable to what the non-profit needs it to do. What I love is that the workflows actually connect—a purchase request can become a reconciled bank transaction; a gift can become an editable letter, print pack, and mailing record; rescue history can enrich the same constituent record without losing its own meaning.
A full volunteer workspace: profile and help, operational resources, events, capacity, references, bird identification, structured training, quizzes, scenarios, practice calls, feedback, trainer review, and administration.
From me
I was solving the problem that volunteer training and on-shift reference are really the same knowledge at different moments. I wanted one place where someone can learn the work, practice it safely, qualify on it, and still use the system later when a real caller is on the phone. The fake data-entry and practice-call systems are some of my favorite pieces because people can make mistakes without touching real records.
A training and operations environment for a specialized wildlife hotline, including structured coursework, practice callers, reference material, call feedback, progress tracking, qualification, and call logging.
From me
The hard part was that hummingbird triage is nuanced and lived in the heads of a very small number of experienced people. I wanted to make the reasoning teachable without turning it into a rigid phone script. The practice caller is the part I like most: trainees have to conduct the call, not just recognize the right multiple-choice answer.
A shared workspace connecting contacts, projects, campaigns, expenses, acknowledgements, applications, tasks, relationship ownership, and team administration.
From me
I did not want relationships, campaigns, money, projects, and follow-up living in separate universes. PrideLink is organized around the work people are actually doing together, so a contact can be connected to a campaign, a task, a project, a donation, and the person responsible for the relationship without rebuilding that context every time.
A modular personal operating system spanning daily life, planning, body and health logging, companions, media libraries, reflection, playful reward systems, and a deliberately separate professional environment called Planet Work.
From me
I built ThreadKeepr because my brain does not divide life into neat app-store categories. The part I love is the modularity: serious tracking, books, games, recurring chores, companions, reflection, and weird experiments can all live in one system without pretending they are the same kind of thing. Planet Work even gets its own visual environment so work does not colonize the rest of the app.
An intentionally anonymous family application with distinct private spaces, shared family tools, reminders, personal routines, household care, and shared animal-care records.
From me
The problem here was not just tracking chores. Different people needed different private tools, while some things genuinely belonged to the household. I like that the system can keep a person's private routines and check-ins in My Space while family messages, reminders, and animal-care history remain appropriately shared.
A standalone collaborative project with its own identity, workspace, and infrastructure.
From me
This one is partly an architecture decision: I wanted to explore what it looks like when something graduates from a personal experiment into an independent collaborative system without dragging the rest of my personal ecosystem along with it.
08
EXPERIMENTAL ARTIFACT
AppeaseCthulhu
Overview
A rejected project preserved because the work can still be worth keeping even when the machine never reaches production.
From me
This one was rejected, and I kept it anyway because I still think it is beautiful. Not every machine has to become production software to be useful; sometimes the design itself is the artifact, and sometimes the correct lifecycle state is permanent museum exhibit.
HOW I WORK
The software starts with the workflow.
1
Understand the real work.
I look for handoffs, workarounds, forgotten steps, repeated questions, invisible dependencies, and information people keep having to reconstruct.
2
Build the information architecture.
I decide what belongs together, what should stay separate, which views each person needs, and how information moves through the system.
3
Implement and break it on purpose.
I direct AI-assisted coding, test the workflows, find edge cases, revise the design, and keep iterating until the machine fits the work.
4
Make it maintainable.
Deployment, permissions, documentation, training, and handoff are part of the system—not an afterthought.
WORK WITH ME
Do you have a workflow that deserves its own machine?
I am interested in internal tools, operational systems, training platforms, workflow replacements, and specific problems that generic software handles badly.
What you are hiring: systems analysis, workflow and interface design, implementation direction, testing, deployment, documentation, and training. Coding is AI-assisted.
Accessibility by design
This site uses high contrast, Atkinson Hyperlegible, large controls, predictable navigation, limited color, clear spacing, and no animation or flashing effects.