Commercial engagements
FreshContext work is fixed-scope and evidence-led. Every engagement starts with an agreed workflow, permitted evidence route, deliverables, acceptance boundary and commercial terms.
US$25,000
Fixed scope · one defined workflow
US$50,000
Fixed scope · two materially distinct workflows
From US$125,000
Implementation scope · one defined decision point
From US$250,000
Program scope · multiple teams, systems or policy domains
Prices are in US dollars. Scope, customer dependencies, source permissions, acceptance criteria and deployment requirements determine the final proposal.
What the assessment is
FreshContext evaluates whether context entering an AI-assisted workflow remains appropriate to rely on for the exact task being performed.
The assessment can examine identity, product or plan applicability, version, region, time, source role, provenance, conflict and unresolved evidence where those dimensions matter to the agreed workflow.
It does not promise a business outcome, certify compliance, guarantee truth or silently expand into production deployment.
Payment
Standard commencement is 100% before work begins. Credible enterprise procurement terms may be agreed in the signed scope where prepayment is not operationally possible.
Standard schedule is 60% at commencement and 40% before final report release, unless the signed scope states otherwise.
Typically milestone-based, with scope, acceptance and payment events agreed before implementation starts.
Payment is made against an issued invoice. International bank transfer in US dollars is available; approved enterprise procurement routes may be agreed where required.
Customer rights, FreshContext background technology, any buyer-specific deliverables and any permitted reuse are defined in the signed agreement for the engagement.
Questions
No. The initial Context Integrity Assessment is designed to be bounded around an agreed workflow and evidence route. A production integration is a separate engagement.
FreshContext is designed as a reusable context-integrity layer for different AI, retrieval, agent and human-review workflows. Actual fit depends on the workflow, available context, permitted sources and integration boundary; we do not claim universal compatibility.
No. It evaluates supported context under explicit scope and policy. A signed or preserved record can support review and attribution; it does not make the underlying source true.
No. The current commercial assessment is human-reviewed. Autonomous Operator Mode is not presented as a current commercial capability.
No. Certification, full production acceptance, managed multi-tenancy, formal SLA commitments and other enterprise controls must be separately evidenced and contracted where applicable.
If the problem fits a bounded engagement, we will return with a scope, dependencies and commercial terms.