Terms of Service
These terms cover the use of XRA’s website and explain how service requests, payment questions, project scope, and digital materials relate to individual engagements.
Review the sections relevant to your request or engagement. The applicable written agreement and transaction documents govern the specific commitments for your work.
In this document
01 Scope and relationship to project documents
02 Evaluating a service
03 Inquiries, service requests, and confirmation
04 Pricing, payment, and transaction questions
05 Project scope, delivery, and changes
06 Client inputs, confidentiality, and access
07 AI-assisted work, third-party platforms, and review
08 Website materials, project references, and projected results
09 Responsible use and website availability
10 Questions, records, and updates
01. Scope and relationship to project documents
These website terms describe how visitors and prospective clients use the XRA website to explore business consulting, marketing, sales, and AI-powered services. They cover service information, inquiries, request forms, project references, and documents made available on the site. If you are acting on behalf of an organization, distinguish requests made on its behalf from questions you are asking in a personal capacity.
The website gives you a starting point for evaluating an engagement. A quote, proposal, order confirmation, statement of work, or other written agreement may address the terms that apply to a specific purchase, including the scope, delivery schedule, price, or responsibilities of each party. Use the document governing your engagement to resolve questions about that engagement.
When two documents differ on a material point, ask XRA to identify which written document applies before committing funds or authorizing work. The website terms do not establish a priority between documents signed by both parties or amend any rights or obligations already agreed in writing.
02. Evaluating a service
Service pages describe the types of business work XRA can support. Details may vary by service, package, project size, the systems involved, or the information available at the beginning of an engagement. Review the service description together with any current proposal and supporting materials, particularly where your organization needs a specific output, integration, or production deadline.
Before proceeding, establish what the quoted service covers, the format in which you need the work, and the decisions your team expects to make with it. If you anticipate implementation, migration, ongoing support, or training, confirm whether those activities are within the agreed scope.
A public description or sample can illustrate how a service is structured. For procurement, compare it with the actual project documents, which should identify the applicable deliverables, inputs, review stages, and exclusions for your assignment.
03. Inquiries, service requests, and confirmation
XRA provides inquiry and service request forms so you can explain the service you are interested in, describe your project, and give the team contact information. A request should identify the right point of contact and contain enough information for XRA to assess the work. Confirm that you have permission to share any information you provide about colleagues or other people.
If you receive a submission receipt, payment prompt, or follow-up communication, check what that message confirms. A receipt can show that information was transmitted, while the engagement documents determine the commitments, milestones, and any work that XRA has agreed to perform.
If a named service, quoted amount, billing contact, currency, or project description appears incorrect, contact XRA with the request reference before proceeding. For changes after a request has been sent, identify the earlier request and explain what changed so the parties can work from the same version.
04. Pricing, payment, and transaction questions
Review the amount and currency shown for your selected service before paying. Ask for an explanation where taxes, installments, licensing charges, or other items are described separately. Confirm whether the price is fixed for the stated scope and which costs would require additional approval.
Where your engagement uses a payment service, verify the service name, payment amount, and business reference in the materials presented for that transaction. Never send full card numbers, security codes, passwords, or banking credentials through an XRA contact form or ordinary email. Keep the payment confirmation and any engagement reference available for your records.
For payment errors, duplicates, cancellation requests, rescheduling, and refund questions, provide the service and transaction reference. The applicable engagement and transaction terms, together with any rights provided by law, determine how those questions are handled. This page does not introduce a fixed cancellation window or refund schedule.
05. Project scope, delivery, and changes
The written project scope is the reference for how the engagement will proceed. Where applicable, it identifies what the client will provide, the work XRA will perform, milestone dates, review responsibilities, and the format for delivery. Read it together with any agreed technical requirements or dependencies.
Changes in requirements can affect schedule, cost, or availability. For example, adding a market, replacing an integration, or requesting an implementation after a planning-only engagement can change the work substantially. Submit the requested change and clarify its effect on milestones, price, and deliverables before treating it as part of the project.
At review or handover, compare the work with the specific acceptance criteria and review process recorded for the engagement. Raise gaps with a clear reference to the requested output and explain how the observed result differs. Any correction period or ongoing support arrangement should come from the engagement documents.
06. Client inputs, confidentiality, and access
XRA may ask for context required for scoping or delivery, such as business objectives, process descriptions, or details of an existing tool. Provide accurate information and identify material assumptions or gaps. Where authorization is required, obtain it from the owner of the material or system before sharing it or approving access.
Provide only the information needed for the task at hand. Use the channel agreed for confidential documents, credentials, system access, and sensitive records. In particular, keep client lists, account credentials, internal financial files, and personal records out of general public-facing forms.
Confidentiality obligations and access controls for a particular engagement are governed by the applicable written arrangements. If work requires access to a platform or dataset, agree on the accounts, permissions, duration, and handover process before access is granted, and keep a record of who can authorize changes.
07. AI-assisted work, third-party platforms, and review
Some XRA services concern AI-assisted workflows, automation, or platforms provided by other companies. For an engagement that involves those tools, confirm which tools are in scope, who owns the accounts, how outputs will be reviewed, and who can authorize the use of project information with a tool provider.
AI-generated and automated outputs may need practical review for factual accuracy, fit to the business context, and alignment with the client’s own policies. Establish who checks the work before it is deployed, especially when an output influences customer communications, financial reporting, operational controls, or important business decisions.
Platform features, availability, and commercial terms can change. Where a deliverable depends on a subscription, data feed, application interface, or client-side permission, agree how that dependency is handled and who is responsible for maintaining it after handover.
08. Website materials, project references, and projected results
Case studies describe particular engagements and the conditions or measurements relevant to those engagements. A result from one client gives context for evaluating the work, but it should be assessed alongside your own market, inputs, budget, implementation, and measurement period.
Illustrative return calculations, forecasts, and scenarios depend on their stated assumptions. Before using them to set a budget or evaluate a proposal, confirm the investment amount, the time horizon, how returns are calculated, and which external costs or factors could affect the result.
The use of website materials, project deliverables, trademarks, and materials provided by the client may involve different rights. Check the terms applicable to the specific material before republishing, licensing, or distributing it. Ownership and permitted use of deliverables should be addressed in the documents governing the engagement.
09. Responsible use and website availability
Use the website and its forms for legitimate business inquiries and related purposes. Do not impersonate others, submit harmful code, attempt to access restricted parts of the website, interfere with another visitor’s use, or use XRA’s forms to distribute unsolicited or abusive messages.
Check the current service page and confirm material details directly when the information will influence a procurement decision, financial commitment, or operational plan. If a form or link appears to fail, report the affected page and the approximate time without including confidential details in the report.
Questions about liability, remedies, or disputes arising from a specific engagement require reference to the applicable agreement and law. These website terms do not introduce a governing-law clause, dispute venue, monetary liability cap, or contractual waiver.
10. Questions, records, and updates
Use the internal Contact page for questions about these terms, a listed service, or a specific engagement. Include the service name, the relevant section of the document, and your reference number when one exists. For billing or delivery questions, include the issue date or milestone to help distinguish older versions.
Keep a copy of the documents you relied on when requesting a service, approving a change, or making payment. A useful project record includes the applicable scope, quotation, approvals, milestones, and payment confirmations, together with any subsequent written amendments.
When reviewing a website update against an existing agreement, confirm whether it affects only publicly available information or whether the parties have separately agreed to change a commitment. The Privacy Policy on this site separately addresses questions about personal information.
Questions about an engagement?
If you’re reviewing a proposal or preparing to request a service, share the service name and the specific point you’d like to clarify.

