Managed Integration Services
Connecting Looplex to your organization’s systems enables you to share information, automate tasks, and keep work moving across applications. Our team can support you throughout this process: understanding your workflows, mapping data, implementing the integration, and maintaining it over time.
Managed Services are the recurring category of Professional Services dedicated to the ongoing support and maintenance of these integrations. Depending on the contracted scope, they include monitoring operations, resolving failures, and making adjustments to keep workflows running as systems evolve.
Standard connectors and custom integrations
A standard Looplex connector is a ready-made integration with a defined set of features and scope of coverage. Its ongoing support and maintenance are included in the platform subscription, with no additional Managed Services fees. Setup work, such as configuration, mapping, and testing for your organization, consumes Professional Services Credits.
All other integrations are subject to Managed Services fees, with the scope and recurring fee defined in the agreement. This allows us to tailor support to each customer’s systems and processes.
| Integration offering | Setup and implementation | Ongoing support and maintenance |
|---|---|---|
| Standard Looplex connector | Professional Services Credits | Included in the platform subscription |
| Other integrations | Fixed price or Professional Services Credits, depending on the contracted scope | Recurring Managed Services fees |
Classification as a standard connector depends on Looplex’s offering, regardless of the technology used. If customization extends beyond the connector’s coverage, the proposal will identify that portion and the corresponding Managed Services.
What types of integrations can we implement?
The connection method depends on the capabilities of the other system and the operations your organization needs to perform. We work with four main approaches:
| Approach | How it works | Implementation effort | Maintenance effort and cost |
|---|---|---|---|
| API with an OpenAPI specification | Connects systems through an interface described using a standard that identifies its operations and the data it receives and sends. | Tends to be lower when the specification is complete, up to date, and covers the required operations. | Tends to be more predictable when the API is stable and its versions are managed. |
| API without an OpenAPI specification | Uses the available API, relying on the vendor’s documentation and validation of how it works. | May require more discovery, testing, and coordination with the vendor. | Varies depending on documentation quality, API stability, and communication of changes. |
| MCP protocol | Allows AI applications to access data and use tools from other systems through a common protocol. | May be lower when a suitable MCP server is already available. Developing or adapting that server adds to the work required. | Depends on the available tools, permissions, and maintenance of the server and the systems it accesses. |
| RPA | Automates actions through the system’s user interface, such as looking up records, filling in fields, and transferring files, when no API is available for the operation. | Requires mapping the sequence of screens, execution conditions, and process exceptions. | Tends to require more intervention, as changes to screens, navigation, or access may require adjustments to the automation. |
This comparison provides general guidance for integrations with similar scopes. An API without an OpenAPI specification may be well documented and stable; a standardized integration may involve complex business rules. Pricing takes all these factors into account.
OpenAPI standardizes the description of HTTP APIs. MCP — Model Context Protocol standardizes how AI applications connect to tools and data sources. These technologies can be combined: an MCP tool, for example, may use an API or RPA automation to perform an operation.
How does implementation work?
1. We understand the process. We identify the systems involved, the information that needs to move between them, and the actions to automate. We also define how often operations will run and which system will serve as the source of truth for each piece of information.
2. We map the integration. We assess the documentation, access requirements, and test environment. We define the fields, data transformations, permissions, and handling of situations such as incomplete records or operations that cannot be completed.
3. We implement and validate. We configure or develop the integration and test it with your team against the agreed delivery criteria. Your organization participates by providing the necessary access, information, and validation.
4. We begin operations and ongoing support. After validation, the integration goes live with the agreed monitoring and support procedures in place.
Mapping may be contracted as an initial phase, particularly when the source system has limited documentation. In that case, its findings inform the scope and pricing of implementation and maintenance.
What can ongoing support and maintenance include?
The scope of Managed Services may include:
- Monitoring executions and identifying failures.
- Diagnosing incidents and assisting with recovery or reprocessing of operations.
- Providing fixes and compatibility adjustments within the contracted coverage.
- Testing after updates to integration components.
- Coordinating technical work with your team and the vendors of the systems involved.
Covered activities, volumes, support hours, and service levels are defined in the agreement. New workflows, system replacements, or significant expansions are subject to scope assessment and approval. Work on third-party systems depends on access, permissions, and cooperation from those responsible for them.
How is pricing determined?
Implementation pricing reflects the work required to map, configure, develop, and validate the integration. The recurring Managed Services fee reflects the expected support and maintenance effort and the contracted support coverage.
In addition to the technical approach, we assess the number of workflows and operations, data transformation rules, usage volume and frequency, system stability, and monitoring needs. Integrations with more exceptions or frequent changes generally require more time and effort.
The proposal or Order, accompanied by a detailed scope when necessary, identifies the covered integrations, the implementation price or how credits will be consumed, the recurring fee, and the Managed Services start date. Any credit estimate will be identified as an estimate, together with the applicable calculation method.
The recurring fee covers the contracted support and maintenance throughout the period, including months when no intervention is required. AI usage, storage, metered calls, and third-party licenses are subject to their own billing terms unless expressly included in the agreed price.
The general terms are set out in the Pricing Policy, the Professional Services Credits Policy, and the Professional Services Terms.