Engineering & Maintenance
Custom Software & Legacy Migration
New web applications and cross-platform desktop applications (Windows, macOS, Linux) for small businesses, or migrating an existing system — including reverse-engineering undocumented C#/.NET legacy applications and rebuilding on Python/Flask + PostgreSQL.
1. What we build
Web applications and desktop applications built for a specific business need, not a generic template — and not locked to one operating system. NaruBase™ Wireless already ships on Windows, macOS, and Linux from the same codebase, using Tauri; the rest of the suite is Windows-first with the same cross-platform path available on request. This also covers migrating an existing system to a modern stack, including reverse-engineering undocumented legacy applications — tracing logic, data flows, and APIs — before rebuilding anything.
2. Requirements come first
This kind of work requires a precise, documented set of requirements before development starts — what the software needs to do, who uses it, and what "done" looks like. We scope this together before committing to a timeline or cost, since underspecified requirements are the most common reason custom software projects go over budget.
3. By request, scoped case-by-case
Unlike the maintenance retainer, this work is project-based and taken on selectively — larger builds and migrations are scoped individually before either side commits to anything. Pricing is hourly at the same $65–85/hr rate as other work, billed against the agreed scope.
Frequently asked questions
How long does a custom build or migration take?+
It depends entirely on scope — a small internal tool might take a few weeks, while a full legacy migration can take a few months. We won't give a timeline until requirements are documented.
Will I lose data during a migration?+
No — migrations include validating record counts, checking referential integrity, and running old and new systems in parallel long enough to catch discrepancies before the old system is retired.
What if I don't have written requirements yet?+
That's normal — most small businesses don't. Part of the process is working with you to turn what's in your head into a documented spec before any development starts.
Have a project in mind?
Tell us what you're building or what's breaking — we'll follow up with scope and next steps.
Contact us