Contact
Contact Class1 about an AI cost governance pilot
A focused pilot starts with one repository, one workflow, and one budget owner rather than a broad platform rollout.
Business Pilot
Start with one repository and one budget decision.
Class1 is best evaluated on a workflow where model choice, retries, fallbacks, context, tools, or adoption can create meaningful recurring AI spend.
Send a short description of the repository type, the workflow you want to estimate, the approximate monthly AI-spend range, and whether the initial gate should be advisory or blocking.
Before you email
Keep private material out of ordinary email.
Expected reply
A useful first conversation is narrow.
The first step is not a portfolio-wide rollout. It is identifying one change or workflow whose recurring cost can be described, estimated, reviewed, and later reconciled against actuals. That creates evidence for whether the method is valuable in your environment. Our standard SLA for pilot enquiries is 1 business day.
Class1 does not need private code in the initial enquiry. A high-level description is enough to determine whether the pilot fits and which security or data-handling questions must be answered before installation. Our team includes engineers who have built large-scale LLM applications and understand the complexity of cost attribution.
Frequently Asked Questions
- What should I include in my first email?
Include your GitHub organization name, the primary languages/frameworks you use for AI integration, your model providers (e.g., OpenAI, Anthropic), and a rough estimate of your monthly AI spend. - How long does the pilot evaluation take?
Once the pilot is initiated, the technical evaluation usually takes 1-2 weeks depending on the complexity of your workflow and your team's availability. - Do I need to share my source code?
No. During the initial consultation and the pilot, you do not need to share your proprietary source code with us. The browser estimator and our secure local integration ensure your IP remains entirely within your environment. - Can we use an NDA?
Yes. If your internal policies require an NDA before discussing architecture or volume, please mention this in your email and we will provide our standard mutual NDA.