The demo looks great and the quote has three zeros. Meanwhile the thing you actually need might be a week of configuration on tools you already pay for. A buy vs. build analysis is a scoped, two to three week diagnostic: what the team actually needs, what the market sells, what could be built instead, and the honest cost of each path, including the maintenance nobody puts in the deck.
What the team actually needs, separated from what the loudest requirements document says.
What the market sells against that list, including the tools you already own and underuse.
Licence, implementation, and the maintenance nobody puts in the deck, against the cost of building it.
A written call with the numbers behind it, and the conditions that would change the answer.
A scoped diagnostic, priced before it starts, with your real workflow on the table. You'll deal with Damian directly. Tell him where it's stuck, and he'll come back to you with scope and a number.