ERP & finance
Orders, invoices, inventory, purchase orders, product masters, and bills of materials.
OPENLOCK THE DATA FOUNDATION
A governed enterprise data foundation for the AI you choose.
One governed foundation. Your choice of AI.
A governed enterprise data foundation connects approved information while your ERP and CRM keep their operating roles. OpenLock preserves the business meaning that makes those records useful together.
01 HOW OPENLOCK FITS
One foundation.
No single required model.
Three layers from existing systems to chosen AI
THE CONNECTED FOUNDATION03 LAYERS
03
Agentic Agnostic Layer
Model-neutral governed access for approved AI models, agents, applications, and business tools.
Private AIApproved external AI*Business tools
Governed access
02
Harmonic Layer
OPENLOCKOpenLock’s governed, customer-controlled, AI-ready data foundation and business context layer.
PreserveOrganizeConnectGovern
Approved replication
01
Chaos Layer
Disconnected ERP, CRM, spreadsheets, email, documents, photos, operational systems, and authorized external data.
ERPCRMExcel / Google SheetsEmailFiles / PhotosOperational data
The core OpenLock contribution
The Harmonic Layer connects your existing information with your chosen intelligence. It is designed around approved data, reviewed meaning, and governed access.
Source systems keep their jobs
The starting approach is approved, read-only replication. An ERP can remain authoritative for orders and inventory while a planning workbook supplies an approved forecast.
One governed experience
Structured records, original files, and their relationships may use different stores. One platform means a coherent way to work with them together.
02 APPROVED SOURCE CATEGORIES
Start with the question.
Connect the data it needs.
CRM & commercial systems
Accounts, opportunities, quotes, contacts, and activity history.
Excel & Google Sheets
Forecasts, planning assumptions, product crosswalks, and operating lists.
Communications
Authorized email, attachments, call metadata, and approved recordings or transcripts.
Documents & files
Contracts, specifications, procedures, technical files, photos, and service records.
Operational & authorized external data
Databases, application interfaces, asset records, identifiers, and relevant enrichment.
These are source categories, not a catalog of ready-made connectors. Access, licensing, source quality, and integration requirements are assessed during discovery.
03 BUSINESS MEANING
The important connection
is not always obvious.
Entity resolution distinguishes the same entity from a related entity.
Two records can share a company name and still represent different delivery branches. An invoice can belong to a billing account without identifying the delivery location. A current specification may not apply to an older order.
OpenLock’s design makes these distinctions explicit, with source evidence, approved definitions, and uncertainty available for review.
BILLING RELATIONSHIPOne billing account
Delivery branch A
Delivery branch B
04 INTERNAL BUILDER AGENTS
AI helps map the business.
People approve what it means.
Internal Builder agents are designed to help consultants, engineers, and business owners inspect approved information, ask clarifying questions, propose relationships, and develop tests.
- 01Profile
- 02Propose
- 03Test
- 04 · HUMAN REVIEWApprove
- 05Apply
Illustrative intended workflow. Conventional software performs extraction, arithmetic, validation, and controlled application of approved changes.
A correction becomes an asset.
“Keep these branches separate” should become a documented relationship, affected-record examples, and a test that prevents an incorrect merge.
Knowledge outlasts the model.
Approved definitions, mappings, rejected matches, and tests persist outside a single model’s weights. They can remain useful when models or project team members change.
05 GOVERNED ACCESS
A foundation for
the tools you choose.
The model helping organize the data does not dictate the model serving your users.
Approved models, agents, and applications connect through governed interfaces. Each connection needs permission, compatibility checks, and data-handling validation.
Transactional actions, changes to source records, and specialized applications require separately authorized and tested workflows.
Understand agentic sovereignty06 COMMON QUESTIONS
Clear scope. Useful answers.
Does OpenLock replace our ERP, CRM, or warehouse?
Not as the default approach. Existing systems keep their operating roles and source authority. Existing data infrastructure can be assessed for reuse.
Do we need to connect everything first?
No. Start with a defined business question and the minimum useful set of sources. Add information when it improves the answer or supports the next justified use case. Known gaps remain visible.
Is this simply a data warehouse?
Storage is part of the foundation. OpenLock’s intended role also includes business definitions, reviewed relationships, source evidence, controlled access, and ongoing operation.
Does the Builder automatically decide what our data means?
No. Builder agents assist with profiling, questions, proposed relationships, and tests. Consequential interpretations and changes require appropriate human review and approval.
What happens when information is missing or uncertain?
The workflow should expose missing sources, ambiguous relationships, stale information, and failed checks. A qualified answer or a request for review can be the correct result.
NEXT START WITH A REAL QUESTION
What should your business be able to answer?
Tell us the question, where the information lives, and what a useful result would change.