Working together in detail

From your question to a sound decision

Your task sets the direction. Together we clarify options, prerequisites and useful next steps. I combine independent advice with practical experience in AI, automation, product development and integration: through focused orientation, ongoing advice or project guidance.

Question · options · decision

What you bring and what you gain

What you bring

Your question, current workflow and desired outcome. Examples, approved documents and the perspectives of the people involved help us understand difficulties and important exceptions. You do not need a finished project brief.

What I contribute

An independent view of suitable AI support, fixed rules and simpler tools. Practical product and integration experience helps connect the options with your data, processes and responsibilities.

What emerges

A reasoned recommendation, clear priorities and a useful next step. Open points and prerequisites become understandable. We agree what to record and how I will support you according to your question and the engagement format.

This may mean focused orientation, independent support for recurring decisions or project guidance with selected technical tasks. Your IT team or another provider can carry out the implementation.

How we work together

The process provides direction while allowing for your situation. It can be followed once for a focused question or revisited as new questions arise in ongoing advice and project guidance.

  1. Agree the question and scope

    You describe the current process, difficulties and desired outcome. We clarify priorities, constraints and the decision that the work should help you make.

  2. Understand information and options

    I assess approved documents, examples and requirements within the agreed scope. Recurring work, handovers and exceptions reveal potential for automation. We consider where fixed rules, AI or a simpler tool could fit.

  3. Compare options and explain a recommendation

    Potential benefit, effort, assumptions and risks are weighed together. I explain why an approach appears suitable, what remains open and which prerequisite should be addressed first.

  4. Discuss findings and the next step

    We discuss your questions, the recommendation and a useful order of work. Your team can then agree who takes each task and how to prepare the next decision.

What a recommendation rests on

The assessment relates to your task and the available information. Clear examples explain a possible workflow; evaluation for your own use rests on relevant cases and requirements that we agree together. I compare suitable models and applications using the same tasks and clear assessment criteria.

Fictional decision example

Choosing an AI solution for internal document questions

How does a question lead to a reasoned recommendation? This fictional example considers usefulness, data requirements and ongoing operation together.

Recommendation in brief: First improve the existing search and document organisation. If this does not meet the need for answers, consider a managed service for a limited pilot, provided its data handling and access controls fit the requirements.

See assumptions, options and recommendation

Starting question and assumptions

A fictional organisation uses shared document storage. Staff regularly look for work instructions and project knowledge. They want to bring information from several documents together in an answer and check the sources. Multiple versions and unclear ownership make searching difficult.

The decision assumes that:

  • An initial team will use an approved set of documents. Answers support their work and are checked against sources before important decisions.
  • Existing access permissions must be preserved. Personnel files and confidential customer documents are excluded from the first step. External processing of the remaining documents is conceivable, but has not yet been approved.
  • Document owners can keep the material current. IT can manage access, but cannot maintain an additional application. An external operations partner would need a separate arrangement.

Criteria for comparing the options

The essentials are traceable, current sources, appropriate access permissions and visible gaps in knowledge. Setup, ongoing support and everyday review effort also matter. Data handling, deletion, recovery and the ability to move to another solution need to be clarified.

Three suitable options

Improve existing search and document organisation

Assign owners, remove outdated versions and configure the available search appropriately. This uses the existing storage and access arrangements. Staff still read and combine sources themselves. It may be sufficient if unclear or hard-to-find documents are the main problem.

Use an externally managed service

A service could assemble answers with source references and maintain the application. This leaves fewer technical operating tasks with the team. Permission handling, data use and storage, deletion and export need checking. The provider cannot replace ownership of the organisation's documents or review by staff.

Use own or rented infrastructure

Greater control over data handling and integration may make this option worthwhile. Operation on the organisation's premises also involves hardware and physical upkeep. With rented infrastructure, the host provides the hardware; the application, access controls, updates and recovery still need clear ownership. Both options require internal capacity or an operations partner. Location alone does not ensure privacy or security.

Recommendation under these assumptions

I would first organise a defined set of documents and check the existing search against typical questions. Unclear versions affect all three options and should be resolved before adding an application.

If a need for combined answers remains, I would assess a managed service for a limited pilot. This fits the limited operating capacity, provided it meets the data requirements, preserves permissions and gives verifiable sources. Running an application under the organisation's control becomes viable once its operating arrangements are clear.

What would change the recommendation?

  • Improved search is sufficient: No additional answer application is needed for now.
  • Stricter data requirements: If a managed service is prohibited, operation on the organisation's premises becomes a stronger option. Rented infrastructure remains an alternative only if explicitly approved. Capacity and responsibility need to be secured.
  • Usage or integration needs grow substantially: Compare setup, ongoing effort and switching options again across all three approaches.
  • Reliable internal support or an operations partner becomes available: Own or rented infrastructure becomes a serious alternative even if external processing is allowed.

Open points and next checks

Actual data approvals, document quality, the capabilities of existing search, and the terms and support scope of possible solutions are still unknown.

The next step would be for the business team and IT to agree an approved document set, typical questions and permissions. They check existing search, then an answer solution if needed: Are sources and permissions correct? Do questions without sufficient evidence remain unanswered? These results, clarified data handling and named owners provide the basis for deciding on a pilot.

Data and sources
Is the information accessible, readable, current and reliable enough? Missing information and unsuitable sources need to remain visible.
Benefit and corrections
Which work could usefully be supported, and what corrections would be needed? The result and review effort need to fit everyday work.
Effort and time
Which prerequisites, access arrangements and changes require effort? Assumptions about processing time or reduced workload are made explicit and checked against suitable cases when agreed.
Review and decisions
Who reviews results, resolves exceptions and decides how they are used? Clear ownership is part of a useful workflow.
Data paths and operation
Where is the data, who can access it and who operates and supports the workflow? Local, cloud and hybrid options are considered alongside integration, security and recovery.

Agree responsibilities together

A recommendation becomes a useful next step when roles and expectations fit. You decide the goals, boundaries and information that may be used.

Advice and coordination

I explain the basis for decisions, identify open questions and support discussion between business teams, IT and providers. Review and clarification paths are planned to suit the workflow.

Review and implementation

Your team agrees who reviews results and exceptions. IT or implementation partners coordinate access, integration, operation and support. I can guide or undertake selected technical tasks by agreement.

For technical work, I use accounts owned by your organisation and document the agreed steps for a clear handover. We explicitly agree which access rights I need and for how long.

A technical test or pilot is scoped separately if needed. A focused entry addresses a bounded decision; ongoing advice supports new decisions, while project guidance supports agreed tasks and handovers.

The focused entry includes two workshops and one written decision report. The engagement formats explain its scope and details. Ways to work together

Common questions

Before we talk

A few answers to help you frame your first question and prepare to work together.

Do I need to know which tool or provider I want?

No. We start with your task, the current workflow and the circumstances. We then compare suitable options, such as fixed rules, existing tools, cloud services or local and hybrid solutions. This can also include choosing suitable hardware and clarifying how you will operate the solution. Sometimes the simpler solution is the better one.

Can we start with one small question?

Yes. A clearly defined question, a single workflow or a limited set of documents is a good starting point. For one decision question, the focused starting format offers two workshops and a written decision report. You use that basis to decide whether and how to continue.

Can this work with our existing applications?

That depends on the applications. I check which access options and interfaces are available, which data may be exchanged and where a provider sets limits. A technically possible connection is not always a useful one.

Who implements and runs it afterwards?

We agree this before implementation begins. Your IT team or a provider can implement and operate the solution; I support decisions and coordination. I can also take on selected technical tasks by agreement. We explicitly record who will be responsible for operation, access and support afterwards. Clarify responsibilities together.

How are scope and cost agreed?

The individual offer sets out scope, terms and invoicing to suit your question and the chosen format. Assessing whether a solution is worthwhile includes weighing benefits, corrections, setup and ongoing effort together. The practical question on local, cloud or hybrid AI explains how these options differ in effort.

What would you like to clarify?

Briefly describe your task, the current workflow and what you want to find out. An early idea is welcome too. Please do not send confidential documents in the first message.

What we discuss in our first conversation

We work remotely across the DACH region. Scope, terms and invoicing are set out in the individual offer.

See engagement formats and the focused entry
Open email