Audit · Keep control
Vendor Exit Audit
Map your AI vendor dependencies and review lock-in by component. Receive a portability report explaining what you own, what you rent and the available exit paths.
Published timing: 5 days
Final scope and timing are confirmed before work begins.
The shape of the scoped work, not a client result or a finished-product screenshot.
The work today
An AI stack that depends on vendor services and contracts.
Dependencies and migration constraints are not mapped.
The progress to work toward
A dependency inventory, component-level lock-in assessment and portability report.
The engagement is scoped around your inputs and acceptance criteria. The outcome is a goal, not a guarantee.
A concrete engagement
Vendor pricing changes and model deprecations are not hypothetical. This audit maps your AI vendor dependencies, scores lock-in risk by component, and delivers a portability report: what you own, what you rent, and the exit path for each.
current stack docs + vendor contracts
Discuss access requirements first. Do not send passwords or private customer data in a public enquiry.
A component-by-component example with the evidence behind each exit constraint.
An example to agree during scoping, not a claim that this evidence has already been produced for your project.
A useful fit
Renewal, repricing or a vendor change has made portability a real decision.
A different starting point
You need an actual migration included in the audit price.
An existing native feature or a smaller change may be sufficient. The call should establish that before a build is proposed.
Evidence, with its limits
The process diagram explains the mechanism. It is illustrative, and it does not establish results for your workload.
The published offer establishes the advertised scope. It does not establish results for your workload.
Ask to review a relevant example and agree the evidence your engagement will produce before committing.
Before you commit
Price basis. $10,000 USD · published project price. Scope, timing and fees are confirmed in the proposal.
Operating costs. Model usage, hosting and any agreed ongoing support are separate where applicable.
Payment schedule. Confirm the payment and billing-start terms for this engagement in the proposal.
Support and cancellation. Confirm support coverage, cancellation and rescheduling terms before committing. A refund policy is not specified here.
Read the existing service terms ↗
sinc-LLM