Splotch is a platform centered on a knowledge graph, used to manage changes to core systems (starting with NetSuite ERP). It is designed to solve the "black box" problem of ERP/CRM systems: system owners cannot clearly see the components, rules, and automation logic actually running, causing every change to begin blindly, making changes slow, expensive, and high-risk, while also lacking a reliable source of truth.
Main capabilities
Splotch's ingestion engine can open the black box, visually map business processes and every customization, and index each component into documentation readable by business people. It generates "diffs" between the system's current behavior and desired behavior, producing a change plan already scoped and ordered by dependencies, ready for deployment. The platform provides governance capabilities, preserving a complete version history for the system itself, so users always know what changed, who approved it, and how to undo it.
The knowledge graph sits beneath everything. Splotch builds a persistent, real-time system map and the business logic layered on top of it, providing a trusted layer of action for humans and agents. Before a change, it can show the "blast radius": what the change directly affects, as well as the more distant areas that depend on it. It also becomes a change record, tracking every change, its scope, approvers, and rationale; this memory persists after company personnel leave, enabling teams to attempt operations they previously dared not risk, because every change is traceable, versionable, and failures can be rolled back.
How to use it
Splotch runs across core systems, showing how the system currently works, helping identify parts that do not meet expectations, and translating business goals into confident system changes, while always preserving a record of what changed and why. It works directly with Claude, GitHub, and other tools in the existing tech stack. The knowledge graph supplements the relationships between components that these tools cannot see on their own, and uses this analysis to ensure tools comply with system patterns and handle all components affected by a change. Within the Splotch interface, users get a human-friendly graph, can follow AI operations, and can visualize, govern, and collaborate on changes. This is an agent-driven approach to ERP change, with every step approved by a human.
Applicable scenarios
Splotch is aimed at change leaders, system owners, and implementation service providers. For change leaders, it provides a real-time map of the ERP, shows what a change will touch before approval, records what happened after completion, and provides a process for managing changes. For system owners, it solves the problems of being unable to see inside the system, needing a meeting for every change request, and the map of the system's actual behavior existing only in someone's head. For service providers, it can scope the required changes before the client discovers them in a meetingand discover adjacent work that needs to be completed, and connect directly to the existing delivery stack without changing the way they work. Officially described as "half the work, twice the sales," because the change itself is not difficult, only changing safely is difficult.
Limitations
Official materials do not provide specific pricing, a complete list of supported ERP systems, deployment methods, platform compatibility, data storage locations, and other information; these contents are not yet available.
