Platform Foundry wants clients to understand what is included, what may cost extra, and how additional work is approved. Our aim is to remain a dependable digitalisation partner—not to create commercial uncertainty after a platform becomes important to the client.
The applicable proposal, order, subscription plan, deployment agreement, or statement of work remains the primary commercial reference. This page explains the general approach Platform Foundry intends to follow.
A connection may allow another system to read Platform Foundry data, send data into a Platform Foundry application, or exchange information in both directions. The price depends on the number of endpoints, authentication method, data mapping, validation, error handling, security, testing, documentation, and coordination required with the external provider.
Normally one documented endpoint or scheduled exchange, modest field mapping, standard authentication, limited transformation, and straightforward testing.
Typical examples include exposing an approved read-only data set, receiving a simple status update, or sending a controlled notification payload.
Indicative setup: $1,500–$3,500 USD
May involve several endpoints, more substantial data mapping, scheduled synchronization, custom validation, error logs, retries, permissions, and coordinated testing.
Typical examples include exchanging customers, jobs, orders, assets, statuses, or workflow events between systems.
Indicative setup: $4,000–$9,000 USD
May involve bidirectional or near-real-time flows, complex transformations, multiple systems, high security requirements, sandbox and production environments, detailed auditability, recovery controls, or significant third-party coordination.
Advanced work is treated as a focused implementation project rather than a small configuration task.
Indicative setup: $10,000–$25,000+ USD
GET / read access: another approved system retrieves selected information from a Platform Foundry endpoint. This is often the simplest direction where the data set and permissions are clearly defined.
POST / inbound submission: another system sends approved records or events into a Platform Foundry application. This normally requires validation, rejection handling, duplicate control, and clear ownership of incorrect data.
Outbound delivery: Platform Foundry sends data or events into the client’s system or a third-party platform. This depends heavily on the receiving system’s API quality, documentation, limits, and availability.
Two-way synchronization: both systems create or update related records. This is usually more complex because the parties must agree which system owns each field, how conflicts are resolved, and what happens when one system is unavailable.
These items are not automatically chargeable in every engagement. They are highlighted so clients understand where additional work or external costs may arise.
Basic template imports may be included where stated. Cleansing spreadsheets, removing duplicates, mapping legacy records, transforming data, handling poor-quality source information, or repeating imports may require additional work.
Email delivery, SMS, AI usage, maps, payment processing, external software licences, specialist APIs, hardware, legal services, and customer-selected providers remain additional unless expressly included.
Dedicated databases, private application instances, isolated infrastructure, custom domains, white-labelling, customer-managed controls, or higher-assurance environments require separate setup and ongoing pricing.
Basic platform branding may be included where stated. Custom design systems, substantial interface redesign, public websites, SEO content, multilingual content, or specialist accessibility work may require a separate scope.
Formal questionnaires, penetration testing, compliance mapping, customer-specific retention, specialist legal review, regulated-industry controls, and extensive assurance work may involve additional internal or external costs.
Additional workshops, staff training, process documentation, on-site visits, priority SLAs, after-hours support, emergency intervention, and dedicated account management are priced separately where required.
Standard exports may be included. Custom file structures, large archive preparation, extended retention, database transfer, migration support, or preparation for another provider may require a reasonable fee.
Clients remain responsible for timely decisions, clean data, authorised contacts, access credentials, licences, test participation, and internal process ownership. Material rework caused by incomplete or changed inputs may affect cost and timing.
Taxes, payment-processing costs, foreign-exchange charges, travel, shipping, and external professional services remain separate where applicable unless a written offer states otherwise.
Platform Foundry distinguishes routine service obligations from requested expansion of the platform.
| Type of request | Typical treatment | Commercial approach |
|---|---|---|
| Confirmed defect | The agreed capability does not operate as intended within its supported scope. | Normally handled through the applicable support or maintenance arrangement. |
| Routine maintenance | Reasonable technical upkeep, platform continuity, and supported-environment maintenance. | Normally covered by the agreed monthly service where included. |
| Small configuration change | A minor adjustment that does not materially alter the data model, workflow, permissions, or risk. | Handled proportionately; may be included where practical or quoted as a small task. |
| New feature or changed requirement | A new page, role, workflow, report, interface, rule, integration, or material expansion. | Explained and approved through a written change request, estimate, or new phase. |
| Third-party change or failure | An external provider changes its API, pricing, authentication, limits, or service behaviour. | Impact is explained; required remediation or additional external cost may be quoted separately. |
| Emergency or priority work | Accelerated response, after-hours work, or intervention outside the normal support arrangement. | Subject to availability and separately priced unless included in an agreed SLA. |
Smaller matters may be handled through email confirmation. Larger changes should be recorded through a proposal, change request, statement of work, or agreed development phase.
Platform Foundry aims to build long-term client relationships based on fair, transparent commercial treatment. We do not believe a client should become commercially vulnerable simply because an application has become important to its operation.
Where a client requests a new feature, additional workflow, integration, report, role, interface, or material change, we will explain the requirement, likely impact, and expected cost before additional work begins. Where practical, smaller configuration changes are handled proportionately rather than automatically treated as major development projects.
If external provider costs, infrastructure charges, or third-party service fees change, we will explain the reason and provide reasonable notice before passing on a material increase where practicable. Standard recurring-price changes will normally receive at least 30 days’ notice unless an urgent external event, legal obligation, or separately agreed arrangement makes that impracticable.
Unless a different fixed term is clearly agreed in an applicable proposal, order, checkout page, or written agreement, Platform Foundry month-to-month platform, hosting, support, maintenance, and service arrangements may be canceled at any time by written notice.
Paid discovery is $295. Where useful, POC/MVP validation starts from $2,950, with 50% credited toward an agreed production setup when the client proceeds under the stated offer terms.
