Before you begin.
Do I have to pay to get a quote?
The enquiry and fit review are free. If the requirements are clear enough, I provide a fixed quote directly. If important questions need investigation, I explain the work first and propose a small planning phase with an agreed price of no more than $500 USD. No paid work starts until its scope and price are agreed and you explicitly approve it.
Does the software need to have an API?
Not necessarily. A supported export, file feed, or agreed database access may provide a practical connection. Reading data and performing an action have different requirements, so I review what each system supports before recommending an approach.
What if there’s already a built-in connector?
That may be the best answer. I first check whether an existing connector or supported import meets the need. Custom work becomes useful when an important matching rule, field, or business step falls outside what the existing connection supports.
Will the integration update in real time?
That depends on what the systems support and how quickly the information needs to arrive. Some connections respond to events; others run on a schedule or retrieve information when someone needs it. We agree on the timing up front and make any meaningful delay clear.
How will access to our systems be handled?
We agree on what the integration needs to read or change and use appropriately limited access where the platform supports it. Privileged credentials are kept on the server, outside customer-facing pages. You can start with system names and a workflow description. Please leave passwords and API keys out of the enquiry form; any required access is arranged separately.
What happens if the external system changes or fails?
We agree on how the integration should handle unavailable services, uncertain results, and records that need attention. Depending on the action, that may mean retrying safely, checking the original result, or pausing for review. Provider changes may require updates; we agree on monitoring and support responsibilities as part of the project scope.
What will I receive from the planning phase?
Planning checks what each system supports, what information or action needs to move, and which system remains responsible for each record. The handoff defines matching and correction rules, duplicate prevention, failure handling, and acceptance checks. An existing connector or supported import may be the right choice. You keep the documented requirements, findings, recommended approach, scope boundaries, and acceptance criteria. When the build is viable and sufficiently defined, the handoff includes a fixed proposal for the first implementation, with timing and operating responsibilities. If the right answer is not to proceed, you receive the reasons and alternatives instead. You can use the handoff with Featherply, another developer, or nobody.
Can I stop after planning?
Yes. The requirements, findings, and recommended approach remain yours. You can use the handoff with Featherply, another developer, or nobody. Each later paid phase requires separate approval.
Who owns the integration, and what ongoing costs might exist?
You own the custom code created specifically for your project once the agreed work is paid for. Third-party software remains subject to its own licences. Hosting, subscriptions, API access or usage, and support may carry ongoing costs. We identify those costs and agree on handover arrangements and operating responsibilities before implementation.
