01
A defined first version
MVP pricing depends on the working use case being delivered. Authentication, integrations, payments and administration are assessed separately, distinguishing the essential first version from later development.
02
The integration starting point
A documented, testable API helps define an MCP implementation. Missing APIs, multiple user roles or write operations may require additional investigation and testing.
03
What the proposal specifies
Scope, acceptance criteria, timing, price and billing are agreed in writing. Platform usage fees, maintenance and future development are itemised separately. All invoicing is handled through FEIM.
04
When scope is still open
We can start with a separate scoping exercise or readiness audit. Its price and deliverables are agreed before work starts, establishing a basis for the implementation proposal.