[ A NexusMind service · Montréal ]
NexusMind rescues the software your business already runs on — the Access database, the VBA workbook, the PHP application from 2012. We understand it, stabilize it and modernize it. No rewrite required.
From $500 · 1–5 days · a report you own whether or not you continue.
Rescue board · week 1 → week 6
Promise 01
Most of this trade asks you to take an assessment on faith. Here is a complete sample health check — findings, evidence, what happens if you wait, and a priced roadmap — written for a business that does not employ an engineer. If it does not look useful, do not book one.
Promise 02
The system you have holds eleven years of data and every rule the business ever agreed to. We stabilize it where it stands: backups that restore, holes closed, a small service beside it when something new is needed. It keeps running and keeps its job. Nothing inside it changes unless the report says it must.
Promise 03
Fixed scope, fixed price, one to five days. You end it with a report you own and can hand to anyone — including another supplier. Anyone quoting repair work on code they have not read is guessing, and you will pay for the guess.
Promise 04
The last step is the part most suppliers leave out. Source in your own repository, every credential rotated and in your hands, a runbook a new developer can follow, and recorded walkthroughs for the people who use it. Ongoing support is available. It is optional.
You already know there is a problem. You do not need convincing — you need someone to open the hood without flinching.
The backup has never been restored.
Three moments at three zoom levels: the message that starts it, the report that scopes it, and the fix that lets the old system keep its job. Specimen figures throughout.
Saturday · 08:12
The first thing we do is copy, not fix. Nothing is changed until there is a full image to go back to.
Health check · day 5
The report is the product. One score per area, worst first, and a price against each fix.
Bypass · one old system, three new doors
The old system keeps running and keeps its job. New doors are built beside it, not through it.
The first two steps are the health check, and you can stop after them with a report you own. The last one is the part most suppliers leave out: handing it back so you are not stuck with us instead of stuck with the old system.
01 · Discover
Read-only access first, and a full snapshot before anything else. Then an inventory: every server, repository, database and integration that runs the business, including the ones nobody remembered.
02 · Assess
Ten areas, one score each, worst first. Every finding comes with evidence you can verify, what it costs on an ordinary bad day, and a fixed price to close it. This is the report, and you can stop here.
03 · Stabilize
The critical findings first, in the order the report set. Backups that restore, credentials rotated, holes closed, monitoring that calls your phone. The system you have, made dependable.
04 · Modernize
One module, one integration, one screen at a time, each beside the old one until it is proven. No switchover weekend. If a piece is fine, it stays; modernization is a decision per part, not a vote on the whole.
05 · Empower
Source in your repository, credentials in your hands, a runbook a new developer can follow, and recorded walkthroughs for the people who use it. Ongoing support is available and optional.
Despite the numbering this is not a sequence. The health check is always first; the other three are answers to what it finds, and a system needs one or two of them, rarely all three. Two carry a price before we start and two do not — anyone quoting repair work on code they have not read is guessing, and you will pay for the guess.
A structured inspection of architecture, source, dependencies, infrastructure, security, database, integrations and deployment. You get a plain-language risk report and a modernization roadmap — what is fragile, what is urgent, and what it costs to fix.
We stop the bleeding: recover source code and access, fix the failures that wake you up at night, close the security holes, and put backups, monitoring and documentation in place. The system you have, made dependable.
When the problem is real but the system is not worth opening — no budget for a rewrite, or too critical to touch — we build a small service beside it and route the traffic through that. The old system keeps running and keeps its job. Nothing inside it changes.
Gradually replace pieces of the old system while it keeps running — one module, one integration, one screen at a time. No switchover weekend, no bet-the-company rewrite.
Legacy applications, broken integrations, abandoned projects, outdated technologies, performance issues and security vulnerabilities — usually two or three of them at once.
If it runs your business, it qualifies — whatever it was written in. PHP, Access and VBA, MySQL, .NET, Java, Python, Node.js, WordPress, Go, Delphi and VB6, FileMaker, and more.
Reliable, secure and maintainable software. Reduced technical debt and operational risk. Improved performance and user experience. A solid foundation for future growth.
Most of this trade asks you to take an assessment on faith. Here is a complete sample health check — findings, evidence, what happens if you wait, and a priced roadmap — written for a business that does not employ an engineer. If it does not look useful, do not book one.
From the sample report · section 4
The summary page: one score per inspected area, worst first, so the problems are the first thing you see. Specimen figures — the subject is illustrative, not a past engagement.
Zero to a hundred per area, worst first. The overall score is the mean of the ten — not a weighting you cannot check. Scores exist to focus the conversation, not to grade anyone's past work.
A shipping platform a business had built years earlier to move parcels for a larger warehouse system: several carriers, tracking numbers, package records. It ran, and nobody wanted to be the one to touch it.
Before
After
Dmitry Kuznetsov · founder & engineer
Fifteen years as a senior software engineer across fintech, healthcare, retail and e-commerce — C# and .NET, Go, PHP and Laravel, Vue and React, and the older things they replaced. Most of those years were spent inside systems someone else built. That is the job here: read it, judge it, fix it, hand it back.
The studio also builds new software for small firms, in fixed-price phases. That side lives here ↗
Thirty minutes, no commitment. If a health check is the right next step, it is from $500, one to five days, and the report is yours whether or not you continue.