Who should own the software after it ships?

You should own the code, the data, and the hosting accounts. A vendor can operate it for you, but the system should not be trapped in an account you cannot access. Ownership is what lets you change teams later without starting over.

Is a maintenance retainer the same as a new project?

No. Maintenance is keeping the current workflow reliable: bugs, small adjustments, security updates, and watching the number you agreed to improve. A new project is the next workflow. Mixing them in one vague bucket is how both get neglected.

How soon should we plan the second workflow?

After the first one is used every week and the success number has moved. Planning the sequel during the first build is useful. Starting it before the team has dropped the old spreadsheet usually means neither system is trusted.

What drifts if nobody stays on?

Logins break, a browser update exposes a bug, a new hire never gets shown the tool, and someone quietly restarts the spreadsheet. Six months later the software is 'the thing we built' instead of the way work gets done.

Keeping Custom Software Running After Launch | Aurelis

Launch Day Is a Wednesday

The demo goes well. The team tries the new board. Then a real Tuesday arrives: a job type nobody mentioned, a permission the coordinator needs, a status that does not match how the crew talks.

Custom software does not fail because the first release was imperfect. It fails when nobody is responsible for the next month. The spreadsheet comes back because it bends without a meeting. Your system has to bend too, on purpose.

Done Is the Wrong Word

“The project is done” is a useful sentence for an invoice. It is a bad sentence for an operational system. The workflow will change because the business will change.

Three Jobs After Go-Live

Reliability

Logins work. The phone screen opens on site. Backups exist. When something breaks on a Monday morning, someone answers the same day. This is maintenance, and it should be boring.

Decide This Before You Launch

Who owns the accounts — code host, hosting, domain, and database, in your name
Who gets called when the board is down or a user is stuck
What “small” means — a status rename is maintenance; a new department is a project
Which number you will still watch — the same one you used to justify version one
When the next workflow is allowed to start — after the first habit has stuck

After launch	Maintenance	Next project
A bug on the job board	Yes
A field the crew asked for in week two	Yes
Connecting a second department		Yes
A client-facing status view		Yes
Security updates and backups	Yes

Ownership First

You should be able to take the system to another team. A partner who stays on is valuable. A partner you cannot leave is a different kind of spreadsheet.

Where Aurelis Fits

We ship the first workflow and stay on it: fixes, the adjustments that keep the team in the tool, and the next loop when the first one is real. You own the software. If you are about to launch, or you launched and the spreadsheet is creeping back, a systems review is the right place to separate maintenance from the next build.

Book a Free Systems Review What to Build First

After Launch: How to Keep Custom Software Running Without a Second Project

Let's Build Something Together

Products Built

In-House Team

Years in Business

Company

Legal