ColabContentOne working system
A request specified, tested and held, then the nightly check.
Staff ask for a change by email. Somebody has to test it.
Business systems desk
A change request in plain words becomes a short spec with what it touches, the change is made and tested on a copy and held for a person to approve, and a nightly check lists where the order system, the customer list and the bank export disagree.
What it does
Spec, copy, hold, reconcile, in four steps.
A one line request becomes a spec
A receivables lead asks for the credit hold to start sooner. The desk writes down the value today, the value asked for, which screen it affects and how many customers would be on hold after the change.
The change is made on a copy and tested
A full copy of the order system takes the new setting. Tests run the system's own credit rule against it and compare every table with the live one, and the table of results shows what was expected beside what happened.
Release notes are written and the release waits
The notes say what changes and for whom. The live system keeps its current value until a person approves, and approval stops if the live value has moved since the tests ran.
Disagreements arrive with their rows
The nightly check compares the order system, the customer list kept by sales and the bank export. Where a deposit and an invoice differ, both rows are shown under the finding.
Ownership
You own it. All of it.
Specs, test results and release notes are the memory of a business system. Built for you, they accumulate in your own records, so the reason behind every setting can be found years later.
Hire or own
What the hire costs, and what this costs
If your post describes a steady trickle of change requests and a reconciliation someone does by hand, both can be built as a system at a fixed fee. The analyst you hire can then spend the time on the larger projects in the same post.
What this role is paid, and what that comes to with benefits, is on the business systems analyst salary page.
When the hire is the right call
Hire the analyst for an ERP rollout, an integration between systems, or a finance team that needs someone to translate daily. Requirements nobody has written yet need a person in the room.
Read this first
What you are looking at, said plainly
Demonstration system, sample data
The supply company, its customers and its bank lines are invented, and the order system is a set of sample tables inside the demonstration. The desk changes three settings and nothing else, the disagreements in the nightly check were planted, and the overnight schedule is represented by a button.
What it costs
Three public prices. Nothing per user.
Jim Glaser Law takes reference calls.Ask in your note and we set it up.
One step
Send me a version customized for my company
Questions buyers ask
Before you ask for your version
Does it do a business systems analyst's job?
A core part of it: routine change requests and the reconciliation. It does not gather requirements in meetings, write code, build screens or run a rollout.
Which ERP does it work with?
None in the demonstration. It sits on a small sample order system of its own. A version for you would be scoped against the system you run.
What kinds of change can it make?
In the demonstration, three settings. A request for anything else, such as a new screen, is routed to a person with the reason.
What does the nightly check compare?
The order system, the customer list sales keeps and the bank export. It lists what does not agree and shows the rows behind each finding.
What does the customized desk show?
Requests in your staff's words, settings named like yours and a reconciliation between the sources you care about, all on sample data.