Published rangesEach range reflects the expected boundary for the named system. Final architecture, interfaces, schedule, acceptance tests, and fee are fixed in a written proposal.
Build/no-build disciplineThe assessment may recommend process redesign, a commercial platform, internal configuration, a smaller engagement, another provider, or no automation.
Third-party costsCloud, software, model usage, licenses, devices, security testing, travel, and external specialists are excluded unless the proposal explicitly includes them.
Production accessNo credentials or protected datasets belong in public intake. Environment and secret access begins only under a signed scope and least-authority plan.
Change controlNew interfaces, materially different data, additional workflows, changed service levels, or expanded user populations require an accepted change decision.
Support boundaryWarranty, maintenance, response coverage, service objectives, and managed operations are stated per engagement. A build does not silently include unlimited support.