Contact

Talk to Class1 about one real AI cost decision

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.

Email pilot@1snob.com Review pilot scope

Before you email

Keep private material out of ordinary email.

Useful contextGitHub organisation, language and framework, model providers, approximate call volume, current cost visibility, and the budget owner’s goal.

Do not attachPrivate source code, API keys, production credentials, customer records, regulated data, or complete cloud invoices.

Technical evaluationUse the browser estimator for a local demonstration, then discuss a suitable private installation path.

Method questionsReview the evidence and limitations, Blue Book basis, and LLM cost-control guide.

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.

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.