Decide the model and where it runs
Choose a model that fits the task, data sensitivity, volume, and budget. Decide whether it runs in cloud, private cloud, hybrid, or on-premise.
Plan data access and retrieval
Decide what data the model can reach and how it is grounded. Retrieval over your own documents needs rules about what is in scope and what is not.
Build in security and governance
Access control, an audit trail, and human review are part of the design, not additions. Decide who can ask, see, and act, and how use is recorded.
Plan hosting, inference, and monitoring
Decide where inference runs, how it scales, and how you monitor cost, latency, and quality after launch.
When this matters
- You need a model inside your data boundary.
- Retrieval over private data is in scope.
- Governance and access control are requirements, not nice to have.
What to avoid
- Standing up a model before deciding data access rules.
- Treating a proof of concept as a production plan.
- Leaving monitoring and review for later.
- Connecting data to a model without controls.