Loading
We put engineers inside regulated businesses, build against their real systems and data, and leave behind software the client runs.
Source: github.com/maximilliangrand, refreshed every six hours
Four products on one core. Each deployment configures the same platform for the sector and the client. Nothing is built that does not land in the core or a sector pack.
The screen staff work from all day.
Inbox, queue, dossier and search in one operator console, wired into the systems already in use. Keyboard shortcuts are printed on screen and the source of every figure is one key away.
Reads documents and data, computes, ranks, shows sources.
The intelligence engine. It ingests filings, contracts, calls and market data, keeps a point-in-time record so any figure can be reproduced as of any past date, scores and ranks, and attaches the source to every number. A person makes the call.
Answers the phone and the messages.
Voice and chat agents on the practice’s or the club’s own line and channels, in German and English. Bookings, enquiries and follow-ups handled around the clock, every conversation logged where staff can read it.
Validated signals for investment firms.
The division that turns research into forecasts and tests them the hard way: purged cross-validation, calibration, and a hash-chained record of every prediction written before the outcome is known. The work is in validation and carries no performance claims.
Every engagement leaves behind the same pieces. Building them once is the product; deploying them inside the client is the work.
| Layer | What it is | Where it runs |
|---|---|---|
| Core | Point-in-time data layer, validation suite for anything predictive, hash-chained audit ledger, document reader, deployment kit for agents, dashboards and portals. | Every deployment, one codebase |
| Sector pack | Data model, prompts, connectors and workflows for one vertical. | Healthcare practices run on it today; corporate finance and investment data are in build |
| Client configuration | The client’s systems, data, hosting and exceptions. The only bespoke layer. | On site, by forward-deployed engineers; the client hosts |
| Compliance | Audit trail and evidence layer. A property of every product, never a separate one. | Inside every deployment |
Eight industries, described by what runs today and what is specified. Client references on request.
Voice and chat agents on the practice line, patient inboxes, booking flows, statutory records.
DeployedStatutory training portals with the evidence records the insurer expects.
BuiltMember and guest agents, booking systems, operations dashboards.
DeployedComparable-company engines, document reading over filings and data rooms, source-linked output.
SpecifiedEvidence and register systems for NIS-2 and DORA obligations, supervisor-ready portals, change tracking across systems.
CapabilityValidated alternative-data signals and a scoreboard that records every prediction before the outcome.
In validationThe operating layer after close: data, dashboards and agents installed in the first hundred days.
CapabilityDocument intelligence and audit-grade records inside regulated workflows.
CapabilityA fixed fee. Data access confirmed, the current process reverse-engineered into a written specification the client owns, and a fixed price for the build. You can stop here.
Fixed scope, fixed price. The pilot runs alongside the current process until the numbers agree, then the remaining scope follows as configuration.
Runs in the client’s infrastructure with a runbook their IT provider can operate. Defects in the delivered scope are fixed under warranty.
MYG owns the engine; the client holds the licence and owns its data, specification and outputs. Changes after handover are quoted individually.
Every deployment carries the discipline a regulated buyer can audit: a point-in-time data layer, a tamper-evident record, a figure that can be reproduced as of any past date. If it cannot survive a check, it does not ship.
The platform exists because we needed it for our own hardest work first. We sell what we run, and we say plainly what is deployed, what is specified and what is still in validation.
The front desk, the analyst, the caller on the line. Software is judged by the person who works in it all day, so the console shows its sources, keeps the shortcuts on screen, and a person keeps the final call.
Forward-deployed means our engineers sit inside the client’s environment until it runs, hand over something their own IT can operate, and stay answerable for the result under warranty.
One week at a fixed fee. It ends with a specification you own and a fixed price for the build, and you can stop there if it does not make sense.
Growth, content, paid media and conversion sites, run as a separate team under the same standards. For companies that already run on our software, and for those that do not yet.