Q: If we enable Copilot for a pilot, does it change our existing license or contract?
A: No. Pilot or beta enablement does not modify the existing MSA, seat license, or ACV. The current commercial arrangement remains unchanged. Any future transition to paid AI credits is handled as a separate commercial conversation, never as an automatic change.
Q: Can we get written confirmation of the pilot terms?
A: Yes. SqlDBM provides written confirmation stating the pilot enablement terms — no pricing change, no contract modification, no seat impact — before enabling AI for any account that requests it.
Q: What does your internal AI governance approval process need from us?
A: SqlDBM provides a full documentation package covering data handling, LLM provider architecture, compliance posture, access control, and audit trail. This is available at trust.sqldbm.com and via written Q&A with security and procurement teams. The goal is to make the internal approval process as fast as possible by providing everything needed upfront.
Q: Will pricing change when Copilot moves out of beta?
A: SqlDBM will introduce a credit-based consumption model for Copilot after beta. Credits are consumed per interaction, with rates varying by task complexity. Customers are invited to run pricing scenarios before rollout. Pilot customers will be notified well in advance of any change, and there will be no automatic conversion from beta to paid usage without an explicit commercial agreement.
Q: What does Copilot cost?
A: Copilot uses a credit-based consumption model. Pricing details, tier structures, and consumption estimates are available under NDA through your SqlDBM account team. There is no charge during pilot or beta enablement. Contact your account executive or visit trust.sqldbm.com for a pricing walkthrough.