Context Model
Business data is put into a relevant context.
Information from different sources is assigned to a company, an opportunity or a task. The model is source-independent: if the data sources change, the logic stays.
AI in B2B with human accountability
AI accelerates. People decide. THE Orange Growth connects both.
THE Orange Growth connects business data, AI-supported analysis, human judgement and concrete execution in a process you can retrace. Not as another AI tool, but as a controllable layer between your data and your decisions.
- Available todayDiagnosis and strategic guidance
- In progressProduct Core, the actual product logic
The problem
Information alone does not create growth.
Most companies have enough data. What is missing is the connection between context, decision and action.
Context is scattered.
Emails, documents, CRM and experience sit in different places. Nobody sees the whole picture.
AI adds capacity, not accountability.
AI analyses faster. Who decides and who stands behind the result still stays open.
Decisions leave no record.
Later it is hard to retrace why something was decided or never carried out.
Core product logic
Scattered information becomes growth decisions you can retrace.
THE Orange Growth connects business context, growth logic, AI analysis, human decision and traceable execution into an accountable system for B2B growth.
- Context ModelPut data into one coherent picture
- Growth LogicAssess what matters for growth
- RoutingSend it to the right role
- Human DecisionReview, approve, take ownership
- Audit TrailDocument it so it can be retraced
The difference to an AI tool: the product is not the single answer. The product is the governed path from information to an accountable action.
The building blocks
Four blocks lead from information to decision.
Growth Logic
Domain rules assess what is relevant for growth.
The basis is the BBC model with Brand, Business and Contact. It makes visible where a follow-up is missing, which opportunity takes priority and which level a measure pays into.
Routing
Tasks and recommendations go to the right role or person.
What counts is risk, confidence in the recommendation and ownership. Standard cases can be prepared. Uncertain or sensitive cases go to the responsible person, who receives exactly the context needed for the decision.
Human Decision
People review, adjust, approve or escalate.
A recommendation is a proposal, not a decision. The responsible person adds context, adjusts where needed and carries the responsibility for the result.
An example
From an overlooked follow-up to an approved action.
This is how a single flow is meant to work in THE Orange Growth. Step by step, with a clear role for AI, people and the system.
Conceptual flowPilot logic for illustration. Not a real client case, no results or figures.
Starting point
A contact at an existing client has asked for a proposal. The email sits in the inbox, the proposal as a document on the drive and the contact in the CRM. Nobody has followed up yet.
- Context ModelSystem
Email, proposal and contact are assigned to the same client and the same opportunity.
Result: one shared case instead of three scattered pieces of information.
- Growth LogicSystem
The opportunity is placed along Brand, Business and Contact. It identifies an open request, a missing follow-up and an existing client relationship.
Result: the gap and the priority become visible.
- AI analysisAI
The AI summarises the history, drafts a follow-up message and flags what is unclear, for example whether the proposal is still current.
Result: a recommendation with an assessment of confidence and risk.
- RoutingSystem
Because this is external communication, the case goes to the responsible person. It stays open until they have decided.
Result: nothing is sent automatically.
- Human reviewHuman
The responsible person sees the summary, the sources and the open questions. They adjust the text and add the current status of the proposal.
Result: a reviewed and adjusted recommendation.
- DecisionHuman
They approve the message. The decision goes back into the case with its reasoning.
Result: a documented approval.
- ActionSystem
The message is prepared for sending and a reminder is created.
Result: one concrete next action.
- Audit TrailSystem
Source, context, recommendation, change, approval and timestamp are stored so they can be retraced.
Result: later you can check who decided what, and why.
- LearningSystemTarget architecture
Whether and how the recommendation was changed feeds into future assessments.
Result: better recommendations in the next round.
Audit Trail
Traceable instead of blind trust.
The audit trail is not an add-on, it is a core function of the Product Core. Every relevant recommendation and decision is meant to be documented so it can be retraced.
In progress
Basis
- which source was used
- which context was available
- which analysis was carried out
Recommendation
- which recommendation was produced
- which risk was identified
- how confident the recommendation was
Decision and action
- who reviewed it
- who decided
- whether the recommendation was changed
- which action was triggered
- when the action happened
Governance
Not every action is carried out automatically.
How much may be prepared and when a person has to decide depends on risk and on confidence in the recommendation. Thresholds, roles and rights are defined per use case.
Target architectureAn example of a configurable principle. Productive thresholds do not exist yet.
Low risk, high confidence
Prepare
- Automated preparation
- Standardised action possible
- Documented in the audit trail
Example: an internal reminder about a due follow-up.
Medium risk or uncertain context
Human review
- Review by a responsible person
- The recommendation can be changed
- A documented decision
Example: prioritising a strategic account.
High risk or external communication
Approval
- Mandatory human approval
- Expert approval where subject expertise is needed
- Escalation when required
- Full traceability
Example: a message to a client or partner.
When in doubt: if the context is unclear or the recommendation too uncertain, nothing is carried out automatically. The case waits for a human review.
Decision rights: who may do what
Decision rights define who may review, change, approve and escalate. AI can analyse and recommend. People keep context, decision and responsibility.
| Right | Who | Note |
|---|---|---|
| Analyse and recommend | AI | Proposals only, never a decision |
| Prepare automatically | THE Orange Growth | Standard cases with low risk only |
| Review and change | Responsible person | Can adjust or discard recommendations |
| Approve | Accountable person or expert approval | Mandatory for high risk and external communication |
| Escalate | Any reviewer | In case of doubt, conflict or unclear ownership |
| Carry responsibility | Named people in the company | Never the AI |
Product data governance
Company data only as far as necessary.
Data protection, data minimisation, permissions and traceable processing are considered in the product architecture from the start. Before productive use, the concrete scope is validated per use case.
Website privacy
Operating this website
Cookies, tracking, appointment booking via HubSpot, server logs and external services. Covered by the privacy policy.
Read the privacy information →Product data governance
Company data inside the system
Data sources, connectors, permissions, roles, AI processing, human review, audit trail, retention, deletion and export. Agreed in writing before every pilot.
-
Least privilege
A connector should only access the data and functions required for the specific use case. No blanket full access. Permissions are role-based and revocable.
Target architecture -
Data minimisation
One defined use case, a limited data scope and period. No unrestricted search across inboxes or documents, and no unnecessary permanent storage.
Target architecture -
Tenant isolation
Data from different clients stays separate. Permissions are controlled per client, demo and productive data are kept apart, and access across client boundaries is controlled.
Target architecture -
GDPR and Swiss FADP
Both legal frameworks are considered in product development: the GDPR for the EU and EEA, the Swiss Federal Act on Data Protection for Switzerland. The implementation is reviewed legally and technically before productive use.
To be validated
Ways to start
Three ways to start a workflow.
A workflow can be triggered by a person, by an event or by a schedule. Which one a use case needs is defined in the pilot.
Target architecturePlanned as a product function. Not yet available in production.
On demand
On request
A person starts the workflow with a concrete growth question.
“Prepare me for the conversation with this client.”
Event triggered
Triggered by an event
A defined input or change triggers the workflow.
“A new thread of communication requires a review.”
Scheduled
On a schedule
A defined routine runs regularly.
“Weekly review of open follow-up opportunities.”
Architecture and status
The Product Core sits above the data sources.
Data sources can change, the logic stays. Microsoft is the first connector planned and in progress. THE Orange Growth is the neutral Product Core above it.
- Source systemsThe systems where data sits today, such as email, documents or CRM.To be validated
- Connector layerThe connection to the systems holding relevant business data. Prepared first for environments such as Microsoft 365.In progress
- Neutral context modelA source-independent picture of companies, opportunities and tasks.In progress
- THE Orange Growth Product CoreGrowth logic, routing, decision rights and audit trail.In progress
- AI orchestrationAnalysis, prioritisation and recommendation with an assessment of confidence and risk.In progress
- Human decision layerHuman review, approval and escalation.In progress
- Action layerPrepared or approved actions in the connected systems.Target architecture
- Commercial outcomesMeasurable growth progress, which has to be proven in pilots.To be validated
- Available today
Growth diagnosis, strategic guidance by THE Orange Guy, keynotes and workshops with THE Orange Guy as a speaker, and curated expertise through THE Orange Gate.
- In progress
The Product Core with context model, growth logic, routing, human review and audit trail. Microsoft 365 is the first planned connector.
- To be validated
Pilots, data access per use case, requirements under the GDPR and the Swiss FADP, as well as hosting and data residency.
- Target architecture
Further connectors, configurable thresholds and roles, tenant isolation and extended actions, depending on what pilots require.
We name prices, service levels and pilot clients only once they are contractually agreed.
AI and human intelligence
AI processes more in less time. People keep context, decision and responsibility.
People are not a fallback for the moments when the AI is unsure. They are a fixed part of the architecture.
AI handles
- Analysis
- Classification
- Prioritisation
- Pattern recognition
- Preparation
- Recommendation
Human intelligence handles
- Context
- Judgement
- Weighing options
- Approval
- Responsibility
- Escalation
- The final decision
THE Orange Growth handles
- Context Model: create the connection
- Confidence Management: assess certainty
- Risk Management: assess risk
- Routing: send it to the right place
- Decision Rights: define the rights
- Handoff: hand over cleanly
- Audit Trail: document it traceably
- Prepare the next action
- Learning: learn from decisions
A transparent next step
Start small. Review it properly.
We do not sell a finished platform. We check together whether one concrete use case fits your company.
Thought together
There are people behind the system.
THE Orange Guy
The personal perspective, strategic leadership and ownership. Experience, clarity and trust for decisions that get executed.
Learn more →
THE Orange Gate
The curated network of vetted specialists and fitting partners. The right expertise, exactly when it is needed.
Learn more →First conversation
30 minutes. No obligation. No pitch.
We clarify which growth decisions keep coming back in your company, and whether an approach like THE Orange Growth makes sense for them.
Pick a slot directly in the calendar. Booking runs through HubSpot.
- Sort the starting pointWhere is your growth today, and where does it stall?
- Clarify the goalWhat exactly should change?
- Agree the next stepYou leave with one concrete, sensible next step.