What counts as one workflow?
One operational process with a defined trigger, authorized inputs, system actions, review points, outputs, and audit record. Discovery confirms the boundary before a price is committed.
Can we add workflows later?
Yes. Each additional workflow is scoped against the environment already in place, the integrations it needs, and any new control requirements.
Is an operations plan required?
No. The installed system remains with the client. An operations plan covers monitoring, patching, incident support, evaluation review, and agreed improvements after launch.
What changes the installation price?
Legacy integrations, inconsistent data, custom interfaces, complex access models, high availability, and extensive validation can increase the scope. We document those conditions before implementation begins.
Who pays for model or cloud usage?
The client owns the relevant infrastructure and provider accounts. Any external model usage is billed through the client’s account and identified in the approved architecture.
How long does delivery take?
A clean integration can move through discovery, build, reference testing, and launch quickly. Complex environments require a longer discovery and integration schedule. The delivery plan states the expected calendar before work starts.