Four ways to work together
The models differ in whose name is on the deliverable.
Whose name appears on the deliverable is the commercial difference between them, so we list them in that order.
ReferralYour client, LegisGate
You introduce the client. The client opens a free account and adds its AI use cases to its inventory (each one a tool used for one purpose). LegisGate shows the laws and obligations that apply to each, and the work carries our name. This is the simplest arrangement and involves no operational overhead on your side. It suits cases where the client should know who produced the research.
White-labelYour client, your deliverable
By agreement, the determination, the list of laws that apply to one AI use case, each cited to the provision, can be presented under your cover, alongside your conclusions. We scope this arrangement with each partner. It is not a setting in the workspace. It suits a practice where the research is part of what it sells.
Embedded (planned)Your product, our determination
A licensed LegisGate API that would put the determination in your platform, so your users get it without leaving your interface, is planned, by agreement. It is not available yet.
Licensed data (planned)Your systems, the Meridian
Licensing structured regulatory intelligence into your own systems is planned, by agreement. It is not available yet.
Referral works today, because it uses LegisGate as it stands.
White-label is made by agreement. Embedded and licensed data are planned and are not
available yet. Each one starts with a conversation.