Partners and documents
Connection count does not tell the whole story. One partner may require several messages and versions; multiple customers may share reusable work. Guidelines, documents, exchange directions and rules determine the actual adaptation needed.
Your software interface
A documented API, an existing import and an application without an interface require different work. Permissions, documentation, vendor availability and test environments need checking. Software adaptations should be explicit.
Testing, go-live and support
A quote should identify who prepares data, coordinates testing and accepts the result. It should explain maintenance coverage, incident handling and changes treated as additional scope.
Ask for a comparable proposal
Provide software details, partners and documents to exchange. Request a breakdown of implementation, adaptations, possible third-party costs, recurring conditions and exclusions. The commercial proposal is prepared with an explicit scope and conditions.
Before you choose a provider
Is a fixed price published?
There is no validated public tariff yet. Assessment enables a proposal with a defined scope and conditions.
Can we start with one flow?
A limited initial phase may make operational sense. Its standalone result and later extensions need defining.
Can we start with one customer?
A limited useful flow can be scoped, with boundaries and extension conditions defined.
Who maintains the connection?
Agree responsibilities across Ecofin Cloud, your team, software vendor and partners, including changes and incidents.
Are software-vendor costs included?
Identify third-party work and whether it is included or contracted separately from integration.