Web development and .NET software for working businesses
From public-facing websites to the desktop applications running behind the counter. Here's what each service covers and how it usually works in practice.
Business websites
For contractors, service businesses, and small studios that need a website to actually bring in work, not just exist online. Every site is written by hand: no page builders, no theme dependencies that break on the next update, no plugin sprawl to babysit.
Typically includes
- Marketing sites, multi-page service sites, and focused landing pages
- On-page SEO, schema markup, sitemap, and local search targeting, included by default
- Optimized images, minimal JavaScript, and strong Core Web Vitals from day one
- Content updates, security patching, and hosting setup after launch
Stack: PHP · MySQL · HTML/CSS · JSON-LD schema
.NET desktop software
The software that runs a business behind the scenes: quoting tools, dispatch systems, inventory, custom reporting, internal admin apps. Built with WinForms for straightforward line-of-business work and WPF where richer interfaces make sense, targeting .NET Framework or modern .NET depending on where it needs to run.
These apps get designed for the people doing repetitive work quickly: fast keyboard flows, sensible defaults, clear error states. Not generic SaaS patterns crammed onto a desktop.
Typically includes
- Quoting and estimation tools, inventory tracking, time and job logging
- Dispatch utilities, custom reporting, and form-based data entry apps
- An organized codebase another developer could pick up later
- Installers, deployment, and version updates handled for you
Stack: C# · WinForms · WPF · .NET Framework & modern .NET · SQL
Legacy application takeover
A lot of businesses run on WinForms apps built years ago by developers who are no longer around. I take over those projects. Most takeovers start with a code review and a short report on what's safe to change and what isn't, before committing to anything.
Typically includes
- Bug fixes, dependency updates, and OS compatibility patches
- Small feature additions to keep the app matching the business
- Selective refactoring and framework upgrades that don't break what works
- An honest recommendation: sometimes the right answer is keep maintaining, sometimes it's rebuild. I'll tell you which, not whichever bills more hours.
Stack: C# · .NET Framework · WinForms · legacy SQL
Internal tools & integrations
Custom builds that remove manual work, sync data between systems, or give a team better visibility into what's happening. Relative to what it costs, this is often the most valuable work a small business can commission.
Typically includes
- Internal dashboards and admin views for seeing and acting on business data
- API integrations between CRMs, accounting platforms, scheduling tools, and custom databases
- Automation for the manual steps worth cutting, built as an actual workflow rather than another subscription
- Recurring reports, PDF generation, scheduled email summaries, and data exports
Stack: PHP · C# · MySQL · REST APIs · scheduled jobs
Not sure which of these you need?
Tell me what you're trying to build and what's in the way. If it's a good fit, a written proposal follows. If it isn't, I'll say so quickly.