Working expectations in plain language
These terms explain the public website, inquiry, and proposal boundaries. A mutually accepted project agreement or proposal governs each specific engagement.
Purpose
They explain what website information, inquiries, proposals, and project agreements mean—and what they do not mean.
Using the website or contacting BES does not automatically create a project engagement, approved recommendation, price commitment, or agreement. Specific work is governed by the mutually accepted document for that engagement.
Website content is general information. A recommendation becomes specific only after BES understands enough context and it is documented through the appropriate working process.
Working Relationship
Each stage has a different purpose and does not automatically create the next stage.
Goals, challenges, questions, and early context are shared without an automatic project commitment.
BES explains an approach it believes fits the information understood at that time.
The proposed scope, outcomes, assumptions, schedule, responsibilities, and commercial context are documented for review.
Both sides accept the applicable terms and confirm the conditions needed to proceed.
Work begins according to the accepted agreement, confirmed responsibilities, and agreed starting conditions.
Responsibilities
Proposals
A proposal records a recommended approach for review. Receiving, requesting, preparing, or discussing a proposal does not by itself require either side to proceed.
Work begins only after mutual acceptance and after any agreed starting conditions are satisfied.
If a proposal and a later signed or otherwise mutually accepted agreement address the same subject differently, the approved project documents should state which provision controls. The mutually accepted project documents define which provision controls.
Changes
When new information, dependencies, risks, or priorities affect the work, both sides should discuss the impact before proceeding on a changed basis.
Material changes should be described clearly, including the reason, expected impact, responsibility, and decision needed. A change becomes part of the engagement only through the approved change process in the applicable agreement.
The applicable agreement defines the change-control process for that engagement.
Confidentiality
Customers should identify sensitive context and avoid sending secrets, credentials, regulated data, or unnecessary production records through public forms.
BES should limit access and use to the working purpose, people, and systems that reasonably need the information. BES will not publish customer names, logos, quotations, or project details without appropriate permission.
Any binding confidentiality duties, exclusions, duration, disclosure rules, or return and deletion requirements must be defined in the applicable approved agreement. Those duties are defined in the applicable mutually accepted agreement.
Read the Privacy PolicyIntellectual Property
Ownership and usage rights will be defined within the applicable agreement or proposal where relevant.
This may include customer materials, BES pre-existing materials, project deliverables, third-party materials, licenses, documentation, and permitted ongoing use. This page does not assign ownership or create a license by itself.
The applicable mutually accepted agreement defines ownership, license, transfer, portfolio-use, and reuse rules.
Questions
Tell us which page, proposal, clause, responsibility, or project document your question relates to. RISA can help route the question, but legal or commercial approval must come from the authorized BES representative. You may also contact BES through WhatsApp at 085707114992; a public email address is not currently available.