I recently acquired a surplus Nvidia GPU from a data center and installed it in my home to run local artificial intelligence models. My objective was to determine if old hardware typically reserved for large-scale operations could be repurposed to create practical, cost-saving applications for personal and business use. By pairing the OpenCode harness with the Qwen 3.8 27B model, I have been able to develop several functional software tools that run entirely on my own hardware – including a Quickbooks Replacement !
Check it out in my latest local AI video!
One of the more significant projects involved developing a replacement for QuickBooks which in my opinion gouges small business customers like me. I found that exporting data from QuickBooks results in spreadsheets that are formatted in a way that is difficult to import into a competing product. In fact, most Quickbooks competitors don’t even offer history import as an option. However, by using the local AI model to analyze the exported data, I was able to rebuild my entire general ledger and chart of accounts and have them balance to the penny against Quickbooks.
I then had the model build a Node.js project which handles all of my transaction logic. It also synchronizes with my bank accounts through a service called SimpleFin that charges only $1.50 per month – a small fraction of what I was paying Intuit. To ensure the accuracy of the financial logic, I utilized a high-end frontier models from Claude and ChatGPT to perform a code and security review. This second set of eyes confirmed that the local model had correctly handled the transaction calculations and had only missed a few minor bugs. I also ran it alongside Quickbooks for a few weeks to make sure everything was being calculated properly.
I also applied this local AI setup to address a lack of transparency in local utility reporting. Following a storm, the power company’s outage map provided limited information unless a user drilled deep into the interface:
I used the Qwen model to identify where the raw data was stored on the power company’s website. In under an hour, it generated a PHP-based interactive map that provides more granular detail than the utility’s default interface. This was achieved without a public API; instead, the model analyzed the source code of the existing outage map and repackaged the information into a more accessible format.
Another app I developed is a utility to streamline the creation of chapter markers for my YouTube videos projects. Converting markers from Final Cut Pro into a format suitable for web descriptions previously required several manual steps. The local model produced a small application that automates this process just by dragging a Final Cut Pro XML file to the app. While it is a niche utility, it represents a significant reduction in the minor frictions that accumulate during a workday.
To test the model’s ability to handle more complex, native software development, I tasked it with building a native Mac Space Invaders clone coded in Swift. The model managed the coding and the compilation process, resulting in a functional game with sound effects and a complete instruction manual. While there were minor interruptions during the development process that required prompts to resume, the result demonstrated that local hardware can execute tasks that previously required a much larger cloud model.
The current state of local AI is comparable to the late 1970s and early 1980s, when personal computers first brought the capabilities of mainframes into the home. We are at a point where a 32GB GPU or a high-memory machine like the Mac Studio can handle sophisticated development tasks privately and without recurring subscription fees. As these models become more efficient, the ability to turn a specific idea into a working application becomes an increasingly accessible reality for home users, allowing for a more customized and efficient computing environment.
