Scope, method, execution, review, report, and findings discussion.
The proposal fixes the fee and identifies assumptions that would require a change.
Pricing and engagement
Loometry does not publish a one-size-fits-all price during the private preview. We confirm fit, define the standard scope, and provide one fixed quote with the work, timing, assumptions, data handling, provider charges, and terms stated together.
Standard engagement
The standard scope is intentionally narrow. A materially different provider path, case set, review need, or delivery schedule is discussed before it enters the proposal.
The model or configuration you use now.
The change you are considering.
Safe examples of the work that matters.
After scope and access are approved.
Change, stay, investigate, or mitigate.
What affects the quote
Five facts are usually enough to decide whether the standard scope fits and what questions remain.
Which model, provider, endpoint, prompt, or configuration change are you considering?
What exact baseline and candidate paths need to be made comparable?
Are up to 10 safe representative examples ready, or do they need structured preparation?
Which provider account, gateway, endpoint, limits, and security review are required?
When is the answer needed, and who must review the method and recommendation?
Cost separation
The customer should be able to see what pays for the assessment work and what pays the selected provider for request usage.
The proposal fixes the fee and identifies assumptions that would require a change.
The proposal states how provider charges are funded or reimbursed. The assessment reports them separately.
Any projection states price dates and excludes unknown discounts, taxes, caching, gateways, and workload changes.
Commercial boundaries
The private preview stays explicit about startup stage, changing workflows, and work that needs separate professional or technical scope.
The first assessment does not require a seat licence, annual contract, or broad platform rollout.
Production monitoring, migration, load testing, security review, and implementation need their own decision and terms.
No payment is requested until the proposal names the current seller, scope, fee, data handling, and applicable terms.
Questions
The fit check is for deciding whether the assessment can answer the question responsibly.
Yes. A prompt, endpoint, gateway, tool, or configuration decision can be the named change when both paths are precise.
No. Public, synthetic, redacted, or specifically approved examples can support the first assessment when they preserve the decision-relevant behaviour.
No. It begins after the scope, cases, criteria, provider access, quote, and terms are approved. The proposal confirms actual dates.
That is a different scope. We first decide whether the extra cases can materially change the recommendation and then quote any additional work.
The proposal states how they are handled. The report always separates provider usage and estimates from the Loometry project fee.
The recommendation says investigate further and identifies the smallest next test or mitigation that could change the answer.
Loometry Model Change Assessment
Share the baseline, candidate, decision, and timing at a high level. We will confirm fit, scope, access needs, delivery timing, and the fixed project quote before work begins.