Model ML at Work: Sites

The way work is produced in financial services is changing. Traditionally, deliverables have been built by hand in PowerPoint or Excel and sent as attachments. That approach comes with familiar problems: the data is out of date almost as soon as the file is sent, numbers can't be traced back to their source, multiple versions of the same file circulate, and there's no way to show a new scenario when the client asks for one.

At Model ML, we're moving away from PowerPoint and Excel and building deliverables as Sites instead: live, connected, interactive work product that stays wired to the data behind it and stays current long after you hit send.

How Sites Work

With Sites, you ask your agent once and point it at the sources you already work from: your CRM, the model, the data room, call notes and third-party data. Model ML builds the deliverable as a Site that stays wired to those sources, so when something changes upstream, the Site already knows.

Because Sites are built as code, they bring the benefits of software to deliverables:

• Teams can build on the same Site at the same time, each in their own branch, without overwriting each other's work

• Every change is stored in a version history, so you can roll back at any point

• Every number can be traced back to its source in a single click

• Permissions can be set section by section, so you decide who sees what, using login walls, passwords or expiring links

Sites also play to your agent's strengths. Code is its native language, so when you ask for a Site, it builds faster, more cleanly and to a higher standard. And you're no longer boxed in by whatever format PowerPoint or Excel happens to allow.

Use Cases: Sites In Practice

Example 1: A deal moves in the CRM. The pipeline tracker already knows.

Every fund runs a pipeline. Normally, someone rebuilds it by hand every single week. With Model ML, you ask once and your agent builds the tracker as a Site wired straight into your CRM, whether that's Salesforce or DealCloud. When a deal moves in the CRM, the tracker updates live. The whole team can work on it at the same time, and every change is saved to the same Site, so there's no confusion over which version is the latest. Any change can also be rolled back at any point. What comes back is a pipeline that's always current, without anyone rebuilding it by hand every week.

Example 2: A sell-side process goes out to buyers. Each tier sees exactly what it should.

A typical sell-side process involves a 100-page CIM, a model in a separate Excel file and a set of supporting materials, all sent out to buyers. Your agent builds the whole thing into one Site. Where a PowerPoint deck links to a single Excel file, a Site connects to the model, the data room, the CRM, call notes and third-party data. Any number can be traced back to its source with a click. With access controls, the long list sees the teaser, signed buyers get the full CIM and the short list gets the model. What comes back is one Site for the entire process, something you can't do with a PDF.

Example 3: A client asks for the scenario that isn't on the slide. They drag the lever themselves.

A typical cost transformation ends with the savings case presented in a deck. If the team has identified 200 million in savings, the client sees three frozen scenarios: conservative, base and aggressive. But the first scenario the client asks about is usually the one that isn't on a slide. With a Site, the client can drag the levers and watch the whole picture reshape live in the room. What comes back is a live view of the savings case that the client can explore for themselves, rather than three fixed scenarios.

Want to get started? Book a demo.