Building a finance context layer in-house means more than a metric catalog. You need mapping across your source systems, an approval workflow finance will use, version history, lineage, access controls and connections to AI tools, plus a team to maintain them. Building makes sense when you have that team and unusual needs. Otherwise, buying can get finance to governed definitions sooner, at the cost of a subscription, a vendor review and some dependence on the vendor.
In-house projects often start as a JSON file or spreadsheet catalog. The hard part is keeping it current as definitions and systems change.
Preql's agents propose mappings across your systems, business owners approve them, and every change is versioned and auditable. Lineage traces numbers back to source systems, and Preql inherits your existing access controls.
Can we keep our existing catalog?
Yes. An existing catalog is a useful starting point for mapping, whichever route you take.
What does maintenance look like?
Owners approve changes. With Preql, agents monitor source systems and flag changes that need attention.

