●Work

Systems built for real operations.

Each case study explains the problem, what was built, and how it works, in terms that make sense whether or not you write software.

01Azure · Data ingestion · Proof of concept

Industrial asset management platform

An Azure-based platform that reads equipment information from PDF, Excel, and CSV files, matches it to existing records, and keeps each asset’s service history intact.

  • Microsoft Azure
  • PDF / Excel / CSV
  • Record matching
  • Service history

02Desktop app · NetSuite integration

Repair management with NetSuite

A desktop application that runs the repair workflow, pulls order information from NetSuite instead of retyping it, and generates PDF documents from each repair.

  • NetSuite
  • Repair workflow
  • Order data
  • PDF generation

Client names, data, and screenshots are kept confidential. Illustrations are drawn to explain each system and contain no customer information.

→What the work has in common

Different problems, the same principles.

  • 01

    Messy in, dependable out

    Real business information arrives as PDFs, spreadsheets, and ERP records. The job is turning it into something people can trust.

  • 02

    Fits around what already works

    Both systems connect to existing tools and data instead of asking a business to start over.

  • 03

    Verified, not assumed

    The asset platform’s proof of concept was checked with 27 independent audit checks. Confidence should come from evidence, not a demo.

→Next step

Have something you want to build, fix, or automate?

Tell me what you have in mind. I’ll tell you honestly whether custom software is the right answer, and what it would take.