Four kinds of work. All of it on systems you already own.
Most engagements start with reporting and end up touching integration or infrastructure, because that's usually where the real obstacle turns out to be.
Custom dashboards & reporting
Reporting interfaces built around your questions rather than a vendor's template. Gross profit and true cost visibility, productivity and throughput metrics, multi-location rollups, and date bucketing on your terms — daily, weekly, monthly, year to date, or a range you define.
Data integration & pipelines
Scheduled extraction from vendor APIs, databases and file exports into a warehouse you control. Combining sources your platforms were never designed to connect — operations with accounting, payroll with scheduling, supplier data with job costing.
Legacy modernization
Older applications that still run the business and can't simply be switched off. Incremental modernization — routing traffic away from the old system piece by piece while it keeps serving — rather than a rewrite that risks everything at once.
Hosting & infrastructure
Windows Server and IIS environments, database administration, DNS and CDN configuration, migrations, performance troubleshooting, and security review. Ongoing support for the systems we build and the ones you already have.
Discovery first, always.
Every engagement begins with a scoped, paid discovery phase before anyone commits to a build. It's a fixed, small piece of work with a defined end, and it produces a written findings document you keep regardless of what happens next.
There are two reasons for this. The first is that you shouldn't have to sign a large contract with someone you haven't worked with. The second is more practical: nobody can accurately quote this kind of work without looking at the actual data first. What a vendor's API exposes, how clean the underlying records are, whether cost data is even being captured — those determine the shape of the project, and you can't know them from a sales call.
Sometimes discovery concludes that the reporting you want is achievable inside your existing platform, and the honest answer is that you don't need to hire anyone. That's a legitimate outcome and you'll be told so plainly.
The technical part, for whoever asks.
Business owners rarely care about this section. IT directors and technical evaluators always do, so here it is.
Data
SQL Server and T-SQL, schema design, query and index tuning, ETL pipeline design, Oracle-backed systems, reporting layers over transactional databases.
Application
ColdFusion and Lucee across every version from CF4.5 to CF2023, JavaScript, Vue 3 with Pinia, jQuery, REST API integration, Node.js at the configuration and proxy layer.
Platform
Windows Server, IIS, PowerShell automation, FusionReactor, Git and Azure DevOps, Cloudflare DNS and CDN, VPS provisioning and hardening.
Development here is AI-augmented as a matter of routine — used for design iteration, refactoring and review. It shortens the distance between a described problem and a working prototype, and it's part of why a one-person practice can deliver work that normally requires a team.