Internal software is seductive because every messy process looks like a product opportunity. Sometimes it is. Sometimes you are encoding a workflow that has not earned the right to become software.
Before building, prove that the process repeats, that the data model is understandable, and that the team agrees on the decision points. If the workflow changes every week, custom software becomes an expensive record of yesterday's confusion.
Prototype the operating model first. Build the software second.