The models come from the minds of your quants: statistical time series, Bayesian priors, regression-tree ensembles, sometimes reinforcement learning or agent-based models. But as soon as those models need to be used by someone who doesn't open an R prompt, the real problems begin: parameter validation, version control, authorisation per scenario, reproducibility of last month's run, and an audit trail that DNB or the AFM will accept.
We build econometrics apps for quant consultancies, policy and research institutes, insurers with an actuarial team, banks with PD/LGD/EAD models, pension funds with ALM challenges, energy and utility companies, and advisory firms that deliver their scenario models to clients under white label. Not a clickable prototype that half does what it should somewhere, but a production environment that fits into your modelling, validation and governance workflow. For enterprise asset managers we don't replace Domino Data Lab or Databricks; we build the specific links the platform doesn't cover, such as a client-facing model front end, a reporting engine for regulators or an API layer that lets your own clients consume the models.
The market below us, with small research groups and individual consultants, relies on R Shiny, Streamlit or Dash. That works fine for one researcher with one model. The market above us, with large banks, Robeco and ASR, builds in-house on SAS, Domino or its own JupyterHub stack. In between is a group for whom Shiny is too limited and building in-house too expensive: mid-market quant consultancies, research institutes that want to open up their models more widely, and insurers or pension funds that want to lift their actuarial tools to production-grade UX. That's our sweet spot.
In practice, we work for target groups such as quantitative consultancies that put R and Python models into production for clients, policy and research institutes in the style of CPB, NIBUD, RIVM or PBL that want to make their scenario models accessible to policy staff and stakeholders, insurers with an actuarial team working on Solvency II pillar calculations, banks that want to expose their PD, LGD and EAD models for IRB purposes, pension funds and implementation organisations with asset-liability challenges, energy and utility companies with demand and price forecasting models, advisory firms that deliver impact assessments and scenario analyses, universities that want to make research output self-service for partner institutions, B2B data providers that want to sell their models as a service, marketing and media agencies doing media mix modelling, and sports analytics suppliers working in the Hudl or Oodle context. Not every project calls for the same thing (an MMM platform for a media agency is a different beast from an ALM tool for a pension fund), but the underlying technology stack and governance challenges overlap strongly.