Robb Sadler MozzCat Services
I help small and midsize businesses repair, improve, replace, and build the software they depend on. You get experienced, hands-on judgment and development on a limited, part-time basis—without executive-level CTO theater.
Software Consulting
I have more than 20 years of professional software development and consulting experience, from enterprise environments to direct work with small-business clients. I personally handle the analysis, architecture, development, troubleshooting, and delivery.
Most people know the work they care about extremely well, even if they do not describe it in software terminology. My job is to listen, understand how the business actually operates, and turn that knowledge into practical requirements and working software. All good business is personal; clear communication is part of the deliverable.
Where I Can Help
I can take over incomplete, unreliable, or poorly understood software. Investigation sometimes exposes more than expected, so I also look for a simpler replacement, workaround, or focused repair when that solves the real problem sooner.
Turn repetitive, spreadsheet-heavy workflows into shared, database-backed systems with current information, fewer repeated steps, and less dependence on one file or one employee.
Design and build practical web applications that support the way your business needs to operate, either independently or connected to the software and data you already use.
Build and test APIs that move data, automate work, support front ends, and expose business functions safely. I have built hundreds of endpoints and treat thorough testing as part of the work.
Evaluate whether an older .NET system should be upgraded, simplified, partially replaced, connected to something newer, or retired. For unreliable systems, I use logging, reproduction, data inspection, controlled testing, and root-cause analysis.
Get a second opinion on code, architecture, vendor work, or a proposed solution. I can advise a developer, clarify tradeoffs, prioritize improvements, and write or modify the code personally.
Selected Case Study
A customer-support group depended on an internal .NET case-tracking application connected through SQL Server to a legacy account system. They had been told their requested changes were impossible, leaving the people who used the software every day frustrated and stuck.
After listening to the users, I found that the requests were achievable—but the underlying delivery problem was serious. Three codebases—local development, integration, and production—had diverged, and the provenance of the deployed application could not be trusted. I carefully investigated and reconciled the versions, restored a structured repository and delivery process, and implemented the capabilities the group needed.
The result was more than a feature release: users had a system that supported their work, the application was maintainable again, and trust had begun to return.
Working Philosophy
If communication breaks down, I have a responsibility to correct it. Understanding what you need and explaining the work clearly are part of delivering the software.
Good code can be better than perfect code when cost, business value, maintenance, and the consequences of waiting are considered. That is engineering judgment, not permission to be careless.
I naturally look for ways to simplify a process, reduce cost, improve reliability, remove unnecessary steps, and make a product easier to use and maintain.
How an Engagement Works
Share the business problem, current process, desired outcome, timing, and as much technical detail as you comfortably have.
I make a limited initial review. When responsible estimating requires deeper investigation, I propose paid discovery or scope definition as a useful deliverable.
You receive the work, deliverables, assumptions, exclusions, billing method, terms, schedule, and scope for approval before implementation.
I work independently and share suitable written updates, commits, demonstrations, working increments, or time records. Larger efforts are divided into approved phases.
Each phase is demonstrated or delivered, reviewed, approved, and paid before the next phase is authorized.
A Good Working Fit
I work best with established organizations that have a serious business need, a clear decision-maker, and comfort with remote collaboration and independent professional work.
Engagements commonly range from a few advisory hours to approximately 5–20 hours per week. Continuous 24-hour support is not a standard engagement.
Small, predictable projects may be fixed-price. Larger projects are divided into separately approved and paid phases. Troubleshooting and uncertain legacy-system discovery may be hourly until the scope becomes predictable.
Experience & Trust
Technical Details
Database-backed business applications, web applications, APIs, integrations, reporting, and PDF generation using .NET, C#, SQL Server, JavaScript, and related web technologies.