Independent software consultant / Georgetown, TX

I build and modernize the .NET, SQL, and automation systems that keep business operations moving.

I help organizations modernize legacy workflows, automate repetitive operations, stabilize data and reporting processes, and ship maintainable internal tools.

Best fit: .NET apps · SQL/reporting · RPA/Selenium · internal tools · workflow automation

13 yrssoftware, IT, and systems experience
Senior engineerenterprise software delivery
MS ISsoftware engineering management
Healthcare opsautomation and reporting experience
What I help with

Focused help where software meets operations.

Service areas stay deliberately narrow: build the internal tool, automate the workflow, stabilize the data path, and leave the system understandable.

.NET application development

Internal tools, Razor Pages interfaces, ASP.NET Core applications, APIs, and maintainable C# delivery.

SQL reporting and data workflows

T-SQL reporting, validation logic, operational reporting, data cleanup, and lightweight dashboards.

Automation and modernization

Selenium/RPA modernization, legacy .NET upgrades, document/file workflows, vendor portals, and scheduled jobs.

Systems troubleshooting

Production issue triage across application, database, hosting, and process layers — with documentation after the smoke clears.

Resume-backed outcomes

Measurable work beats decorative promises.

A privacy-safe snapshot of operational improvements I have delivered: faster workflows, cleaner data paths, and more reliable internal systems.

95%+cycle-time reduction

Workflow automation

Turned a slow, hands-on operational process into a repeatable automated workflow with dramatically faster completion time.

99%+failure reduction

Reliability improvement

Stabilized a high-volume data process by identifying failure patterns, improving validation, and supporting regression checks.

1M+records validated

Large-scale data validation

Built validation tooling for large reporting datasets, improving review speed while keeping error rates low.

How engagements work

Diagnose first. Build second. Handoff always.

01

Diagnose

Map the current workflow, users, data, risks, and failure modes before prescribing code.

02

Build

Implement focused .NET, SQL, automation, or integration work without overbuilding the solution.

03

Stabilize

Test the critical path, reduce operational risk, and make failure states visible.

04

Handoff

Leave clear docs, deployment steps, and maintainable code so the system does not become folklore.

Engagement fit

Useful boundaries make better projects.

This section saves everyone time. Civilization advances when fewer meetings should have been emails.

Good fit

  • Manual workflows consuming staff time
  • Legacy .NET apps needing modernization
  • SQL/reporting processes that need cleanup
  • Vendor portals, uploads, recurring data tasks
  • Internal tools that need reliability without bloat

Not ideal

  • Consumer mobile apps
  • Speculative MVPs with no clear workflow
  • Design-only marketing sites
  • Emergency production support without access or context
  • Projects that need a full agency team
Resume snapshot

A career built across software, healthcare, and IT operations.

C#ASP.NET CoreRazor PagesT-SQLSQL ServerSeleniumREST APIsPower BIWindows/Linux Server

Senior software development engineer

Automation, .NET modernization, RPA capability improvements, T-SQL reporting, and parser reliability.

Application developer

RPA solutions, Razor/Blazor tools, Selenium automation, data validation, secure uploads, and healthcare workflow automation.

Web developer / web engineer

C#, JavaScript, T-SQL, MongoDB, responsive applications, hospital operations tools, and database optimization.

Technology director

IT strategy, infrastructure, device management, network upgrades, and technology curriculum.

Project brief

Tell me what you need fixed, built, or clarified.

Send the current stack, desired outcome, timeline, and constraints. I review fit before scheduling. If it is not a match, I will say so clearly.

Phase 1 note: the intake form is present but not wired to email yet. Use the contact page for the current direct-email instruction.

Ready to start?

Share a concise project brief with the current workflow, target outcome, stack, timeline, and known constraints.

Open project brief

No backend email integration is enabled in this Phase 1 build.