TechOneDigital Talk to David

AI architecture & engineering

What should the AI do for you?

For enterprise workflows where AI decisions and actions need clear boundaries.

Defined permissions. Risk-based controls. Traceable outcomes.

Or start from one of these.

Ways to work together

Bring the unresolved decisions.

From AI ambition to work that gets done

One outcome. Two ways to deploy.

Explore the operational applications, then discuss which scope and controls your situation needs.

  1. 01 / Outcome

    AI Efficiency

    Remove repetitive work, shorten cycle time and reduce errors, with a result you can measure.

  2. 02 / Foundation

    AI Enablement

    Prepare the data, integrations, permissions and approval controls one AI use case needs.

  3. 03A / Ready-made

    AI Workforce

    Start from defined AI workflow patterns for sales, finance, marketing and IT operations.

    See the AI roles
  4. 03B / Your process

    AI Agents

    Design an agent around your process, with agreed acceptance tests, handover and operating responsibilities.

    Explore custom agents

AI Workforce + AI Agents

Choose a ready-made AI role or build one around your process.

Explore defined workflows across four operational areas. Select one to see an illustrative workflow and discuss the scope.

Sales & Marketing

Research, outreach and reporting with a rep or marketer approving what goes out.

  • View details
  • View details
  • View details
  • View details

Finance & Documents

Documents in, approved data out. Twenty document types, five languages and four ways in.

  • View details
  • View details
  • View details
  • View details

IT Operations

Monitoring, reviews and change planning through defined operations, with agreed access and action controls.

  • View details
  • View details
  • View details
  • View details

Custom Agents

An agent around your process, with agreed acceptance tests, handover and operating responsibilities.

  • View details
  • View details
  • View details
  • View details

Controls follow the consequence.

Define what AI can access, which actions it may propose or execute, and where approval is required. Higher-impact actions need stronger checks, explicit responsibility and a recovery or escalation path.

Direct answers

What companies ask before AI touches real work.

What is an AI workforce?

An AI workforce is a set of defined AI roles for recurring operational work. On this site those roles cover sales, marketing, finance, documents and IT operations. The scope and controls are agreed for the workflow.

What is the difference between an AI workforce and a custom AI agent?

AI workforce roles start from a defined workflow pattern. A custom AI agent is designed around a process, system and acceptance criteria unique to your company. Both need defined permissions, appropriate controls and action and outcome records.

What does AI enablement include?

AI enablement maps the process, connects the required systems, limits the operations available to AI, defines approval points and sets acceptance tests before deployment.

How are AI actions controlled?

Permitted actions, validation and approval rules are defined for each workflow. The required controls depend on impact, reversibility and your organisation's policies. Where human approval is required, it covers the exact action and target.

What needs to be defined before AI can access our systems?

The scope needs to define which data and actions are available, who can authorise access and which controls apply.

How does an engagement start?

Describe your situation and the decision or work you need to support. The objective, access, responsibilities, scope and expected output are agreed before work starts. A pilot is one possible starting point, not a requirement for every project.

Technical perspective

David Máj

Founder & Technology Consultant

David Máj

Putting AI into production raises decisions about system access, ownership, verification and failure handling.

My background combines enterprise application development, system integration and production operations. I use that experience to work through the decisions that arise when AI connects to business systems.

Why AI projects stall before the model matters

The process comes from the people in it. I walk through the work with the people who do it today, before anyone touches a model. What they approve is what the AI learns to prepare.

  • Access is a design decision. Read access also needs limits. Writes require controls appropriate to the action, its impact and reversibility.
  • Approval covers the exact action. Where approval is required, it covers the target and proposed change, not only a summary of the intention.
  • Refusal needs a next step. Define when a capability must refuse, what evidence it records and who handles the exception.
  • Scope before commitment. Agree the question, access, responsibilities and expected output before work starts. A pilot is one possible starting point, not a requirement for every project.

The engagement defines the objective, responsibilities, scope and acceptance criteria around the systems and people involved. Technical decisions, handover and ongoing support are agreed for the specific project.

Start a conversation

Tell us about your project.

Discuss technical project involvement: . Context: Technical Leadership. Reply to about the scope, responsibilities and next step.

One reply from a person. No newsletter, no sequence. Spam check by Google reCAPTCHA runs only when you click.
  1. No project request sent.