Skip to content
digitapulia.com
Fixed-price engagements

A connector at a fixed price

All we need is to connect these two systems, without a project that never ends.
What we do
One connection between two systems, with its scope written down before we start.
How we do it
First we write the scope with you: which two systems are connected, which data pass from one to the other and in which direction, how often, what happens when a piece of data cannot be passed, and what the connection does not include. With the scope agreed we build the connector, test it with real data in a test environment and switch it on. We document it so your team knows what it does and how it is checked, and we monitor it for the period the scope sets.
What you receive
The connector installed, documented and monitored for a period.
What changes for you
Data pass from one system to the other without anyone copying them, and the work has an end: you know from the start what it includes, what it costs and when it is finished. If you need another connection later, it is another engagement, with its own scope.
What we need from you
Access to both systems and to the way each one offers to connect; someone who knows which data have to pass and what they mean; and someone to read and accept the scope before we start.
Who it is for
Operations and IT
How you buy it
At a fixed price: the price is written down before we start and we give it to you when you ask.

Example use cases

These are examples: they do not describe a real client.

  • An agricultural spare parts distributor in Italy with customers in Argentina, whose ERP does not talk to its warehouse program

    The situation

    Orders come into the ERP, and the warehouse works with another program. Every morning someone exports the day's orders to a spreadsheet and types them again into the warehouse program; in the afternoon they do the same in reverse with what has shipped. A supplier has proposed to the company that both programs be replaced with a new one.

    What we do

    We write the scope in a short document: orders pass from the ERP to the warehouse program as soon as they are confirmed, and shipments come back to the order when the warehouse closes them. What is not in that document is not in the engagement. We build the connector, test it with several days of real orders and switch it on. During the monitoring period, every order that fails to pass alerts the warehouse and us.

  • An industrial maintenance company in Spain with customers in Peru, which receives the requests from its website by email

    The situation

    Customer requests arrive by email from the website form, and someone copies them one by one into the system where the company manages its customers. Some stay in the inbox and no one answers them. The company does not want a new project: it wants the requests to go into its customer system.

    What we do

    We write the scope: every request from the form goes into the customer system as a new contact, or into the contact that already exists, with its country, and the person in charge of that country gets an alert. We build the connector, test it with test requests from Spain and from Peru and switch it on. During the monitoring period we check that no request gets lost on the way.

Frequently asked questions

What happens if something that is not in the scope comes up during the work?

It is written down separately. The connector is finished exactly as the scope says, at the agreed price; anything new is another engagement, with its own scope and its own price, and you decide on it.

Which systems can be connected?

Two systems that offer a way to connect: an API, a file exchange or, if the vendor allows it, access to their database. Before writing the scope we check what each one allows, and if something cannot be done, we tell you before we start.

What happens when the monitoring period ends?

The connector keeps working, in your name from day one, with its documentation, so that your team or whoever you choose can look after it.