Pilots and engagement
One question. Four weeks. A clear next step.
Test FORGE against a real estate-intelligence question in one non-production environment. Agree the scope and fixed fee first, then use the findings to decide what comes next.
Pilot and subscription scope
Agree the right scope for your estate.
For Customer AI / AJAEX Tooling, using your approved AI client. Contact AJAEX for pricing. The proposal confirms the included scope and commercial terms before access.
Start with one outcome
Setup and four-week pilot
Contact us for pricing
Scope and commercial terms agreed in your proposal
- One outcome in one non-production environment
- Agreed read-oriented tools and access scope
- Up to three working sessions over four calendar weeks
- Evidence pack, limitations, and a next-step recommendation
- Onboarding included, with no separate pilot setup fee
Agree the pilot outcome, access, and commercial terms before connecting your environment.
Discuss a pilotContinue after the pilot
Estate Intelligence
Contact us for pricing
Subscription scope and terms agreed separately
- One named customer estate and one non-production environment
- Agreed Estate Intelligence capability scope
- Your approved internal delivery team, with no per-seat charge
- Transition from the completed pilot and compatible updates
- Reasonable-efforts email support during UK business hours
Use the pilot findings to agree the subscription scope, operating requirements, and commercial terms. A subscription does not start automatically.
Discuss your estateYour AI client and model costs are separate. Production intelligence, additional environments, and governed change require separately agreed scope and pricing.
AJAEX Managed remains private preview and Customer Private remains design-partner scope. Both are individually quoted to reflect the deployment and operating responsibilities.
Engagement ladder
Start focused, then expand when the evidence supports it.
- 01
Find the right starting point
Review your TRIRIGA versions, environments, use case, security requirements, AI environment, and success criteria.
Outcome: A clear recommendation on whether and how to proceed with a pilot.
- 02
Setup and four-week pilot
Four calendar weeks, one outcome, one non-production environment, up to three working sessions, and an evidence pack. Tools and success criteria are agreed before access.
Outcome: Findings, limitations, and a recommendation to continue, adjust, or stop.
- 03
Subscription or private licence
Available after the relevant security, support, operating, assurance, and commercial requirements are agreed.
Outcome: An agreed operating model and supported scope.
Build the business case
Agree what would make the pilot worthwhile.
Choose a recurring investigation your team already understands. Agree the current baseline and success criteria, then compare the pilot evidence with how you work today.
Time to a usable answer
Compare investigation and review time, manual lookups, and the specialist input needed to reach a defensible conclusion.
Evidence you can check
Check known dependencies, inspect the sources, and record missed or uncertain relationships. Speed matters only if the evidence holds up.
Value across the team
Assess how often the same kind of investigation recurs and whether developers, testers, and new team members can use the result.
Use the findings to decide whether the recurring value supports an annual subscription. A subscription is a separate agreement; the pilot can recommend continuing, adjusting the scope, or stopping.
Available engagement paths
Compare the pilot, preview, and design-partner routes available today.
Bring your AI
Customer AI / AJAEX Tooling
Organisations that already have an approved AI client or model account.
Managed workspace
AJAEX Managed
Teams that want one managed workspace and a single service boundary.
Private edition
Customer Private
Regulated, sovereign, isolated, or customer-operated environments.
Scoped pilot
See what a pilot includes, excludes, and is designed to prove.
A scoped pilot can include
- Named business and technical outcome
- One agreed non-production TRIRIGA environment
- Selected delivery model and mapped data flow
- Explicit release-controlled tool allow-list
- Customer-approved integration identity and access scope
- Up to three working sessions across four calendar weeks
- Results, limitations, and success-criteria review
- Recommendation to continue, adjust the scope, or stop
Outside the agreed pilot scope
- Tools outside the agreed pilot scope
- Automatic production write access
- Production service levels, certifications, or compatibility commitments beyond the agreed scope
- An untested migration or workflow-behaviour guarantee
Contact AJAEX for a pilot proposal. It confirms the outcome, environment, included work, support, and fixed fee before access begins.
Commercial questions
What happens before a quote.
How is FORGE priced?
Contact AJAEX for a proposal based on your outcome, estate, environments, delivery model, and support requirements. Pilot and subscription scope and commercial terms are agreed before access. Managed and private deployments are individually quoted.
Does a pilot automatically start a subscription?
No. The pilot ends with findings, limitations, and a recommendation to continue, adjust the scope, or stop. A subscription requires a separate agreement on scope and commercial terms.
Is the fit conversation paid?
The initial qualification conversation is used to determine whether a bounded engagement is sensible. Any discovery work, architecture output, demonstration preparation, or environment access beyond that is scoped explicitly.
Why does the base subscription cover non-production?
The base scope supports recurring investigation, development, and change preparation before promotion. Its value depends on an environment that represents the work you need to investigate. Findings from non-production do not establish the current production state. Production Estate Intelligence and additional environments are scoped and priced separately.
Do we need to buy an AI model from AJAEX?
Not for the Customer AI route. The customer provides its approved AI client or model account while AJAEX operates the specialist TRIRIGA intelligence and tooling. Managed and private models have different responsibilities.
Can governed change be included in a pilot?
Yes, where the use case justifies it and the named non-production environment has an agreed tool policy, confirmation path, identity, approval, rollback, and verification plan. Read-oriented intelligence remains the safer default entry.
Start with one outcome, one environment, and a clear scope.
Share the decision or delivery problem you need to solve. The fit review establishes whether a bounded paid pilot is the right next step.