Services · Iowa first. Available nationwide.
Custom business software and internal tools.
When the work depends on a clipboard finding the right person, another brochure site will not help. I build custom business software for Iowa organizations, with remote projects welcome across the United States.
Based in Dubuque. Serving Iowa. Remote projects welcome nationwide.
A shared workflow, not just another screen
A spreadsheet can be a good tool. The problem starts when different people need to act on the same information, exceptions get lost between shifts, or staff have to enter the same thing in several places.
A custom internal tool can give that work a shared place to happen. Start with the handoff that breaks: what comes in, who acts on it, and what must be visible before it can move on.
The warehouse example
For a disaster-relief nonprofit, intake, inventory, and handoff had outgrown clipboards. The product brings bins, donation lots, and exceptions onto a warehouse screen, with phone screens for work at the dock.
That is the kind of operational problem I take: software shaped around the people doing the job. It is not a claim that every organization needs a custom warehouse system.
What to bring to the conversation
A useful starting brief describes:
- The current process, including the paper forms or spreadsheet steps people rely on.
- Who needs to see or change information and where they do the work.
- Exceptions, approvals, and handoffs that cannot be lost.
- Existing data, required integrations, and any migration or reporting needs.
- The smallest usable first version and the budget available to build and maintain it.
Work you can look at
- Nonprofit warehouse and donation inventory platform — A hold at the dock is on the screen instead of on a clipboard that left with third shift.
Questions before a build
Should I replace my existing software?
Not automatically. If an existing product can handle the workflow, use it. A custom build is worth considering when important rules or handoffs do not fit the available options.
Can this work on computers and phones?
The warehouse example does. Your project’s devices, access, and connectivity requirements need to be agreed during scoping rather than assumed from that example.
What happens after the build?
Monthly care covers agreed hosting, updates, support, and ongoing features as the job changes. You own the product, code, and accounts, with handover if care stops.
Built, then looked after
You work directly with me, from the first brief through the build and monthly care. Read how I work for hosting, updates, support, and what you own. If you are comparing options, start with custom software vs. off-the-shelf.