Skip to content

BRTHLS / Businesses and institutions / Enterprise AI

Business. Brand. Product.
Connected through AI.

I combine business leadership, brand judgement and product design to put AI into your processes. Together, we decide what is worth building. I connect it to your systems and prepare your team to run it.

For CEOs, CIOs, COOs, CAIOs and transformation leaders in businesses and institutions.

The next step involves more than one team.

  • A pilot ready for everyday use

    It works in a trial. Now it needs ERP or CRM integration, agreed permissions and someone accountable when something fails.

  • Several teams, different priorities

    Leadership needs an investment decision. IT needs a viable architecture. Teams need a solution that fits their work.

  • Adoption with shared standards

    The tools are already arriving. What is missing is a set of usage rules, evaluation, training and a way to assess whether the process improves.

The first engagement

An investment decision you can stand behind.

After an initial conversation about fit, we can agree an assessment. I review a priority process with you and identify what it would take to bring it into production.

  • The process, objective and accountable business owner.
  • A map of data, systems, permissions and dependencies.
  • Risks, acceptance criteria and an implementation proposal.

Scope and terms are agreed before work starts. The assessment may also recommend preparing the data or postponing implementation.

See a decision brief

From decision to everyday use

Every phase leaves a deliverable and an owner.

  1. Decide

    With leadership and the process owner: priorities, a baseline and success criteria.

    What your organisation retains

    A decision brief and agreed scope.

  2. Connect

    With IT and security: architecture, access and integration. ChatGPT Enterprise where appropriate, APIs, agents and ERP or CRM connections.

    What your organisation retains

    An integrated pilot and representative tests.

  3. Validate

    With the people using it: quality, exceptions, approvals and release conditions.

    What your organisation retains

    Verified acceptance criteria and a deployment plan.

  4. Transfer

    With the operating team: training, documentation, ownership and agreed follow-up.

    What your organisation retains

    The ability to use, supervise and maintain the solution.

Worked example / Synthetic data

From a brief to a proposal ready for review.

A process where business, brand and technology meet. This illustrative walkthrough does not query systems, run a model or represent a client engagement.

BRTHLS / Sample deliverable Awaiting validation

Decision brief

Sales proposal assistant

Objective
Prepare a draft consistent with the catalogue and brand voice.
Scope
CRM brief → approved sources → draft with references.
Owners
Sales validates the proposal. IT validates access and integration.
Before proceeding
Test source traceability, permissions and handling of missing data.

Proposed decision

Pilot draft preparation. Keep sending subject to human approval.

Synthetic example of format and content. It does not describe a client or a delivered project.
  1. Authorised input

    Sales records a brief and its owner in the CRM.

    Example request: prepare a training proposal for a team.

  2. Sources and context

    The solution retrieves the approved catalogue and brand guidelines the user is permitted to access.

    Each recommendation retains its reference. Undocumented terms remain unresolved.

  3. Human review

    The owner checks scope, language, price and terms before approving.

    Sending stays blocked until approval is recorded.

  4. Delivery and follow-up

    After approval, the workflow can record the accepted version and next action in the CRM.

    The record shows what was approved, who approved it and what remains to be done.

Intended output

A sourced proposal, a human decision and traceable follow-up.

What if a source or permission is missing?

The process stops at that point and requests review. It does not invent terms or extend the user’s access. This exception is also part of acceptance testing.

Control is designed in from the start.

  • Data, access and compliance

    Data protection, security, AI Act obligations and, where relevant, public procurement are assessed. Residency, ENS and contractual requirements are checked for each solution and jurisdiction.

  • Delivery accountability

    I work with your business and technology owners. Time commitment, specialist collaborators, approvals and support are agreed for each project.

  • Continuity and independence

    Accounts, licences, documentation and operations are defined during design. The proposal separates services, licences, usage and infrastructure; ongoing support has its own scope.

BRTHLS scopes and delivers the project; OpenAI sells its products. Any OpenAI involvement is agreed for the individual opportunity.

One connected practice. Different ways to work together.

Implementation belongs within BRTHLS: business judgement, process design, technology and people. AI in production remains the service for building and handing over; advisory, fractional leadership and training support it when the project calls for them.

Explore all services

Start with the process that matters.

Tell me what you want to improve, which teams are involved and where work gets stuck today. We can then decide on the next step.