Home/Knowledge

OXIAE / KNOWLEDGE & DECISIONS

Understand the choices. Build with confidence.

Detailed guides, worked examples and practical tools for integrations, AI, company knowledge and new or existing software.

APIs & integrations

API integrations: turn separate applications into a manageable data flow ↗

Choose an integration approach and prepare data ownership, costs, testing, recovery and operation around a clear business process.

01 / APIs & integrations

What does an API integration cost? Define the job before the price

Understand integration costs through data flows, business rules, recovery, testing, operating costs and comparable proposals.

Read the guide ↗02 / APIs & integrations

Standard connector or custom integration: test the whole process

Compare connectors, integration platforms and custom development through business rules, exceptions, recovery, operating costs and handover.

Read the guide ↗03 / APIs & integrations

Connect CRM and accounting: agree customers, orders and invoice boundaries

Design a CRM-accounting integration with stable identity, field ownership, clear invoice actions and controlled introduction.

Read the guide ↗04 / APIs & integrations

Synchronise data without uncontrolled overwriting

Assign field ownership, recognise competing changes and design explicit rules for versions, empty values, archiving and recovery.

Read the guide ↗05 / APIs & integrations

Prevent duplicate orders and invoices when API messages repeat

Design processing that recognises repeated operations, investigates uncertain outcomes and preserves source-to-destination identity.

Read the guide ↗06 / APIs & integrations

Webhooks or polling: choose for timeliness and recovery

Compare event notifications, periodic reads and combined integration designs, including missed changes, authenticity and business backlogs.

Read the guide ↗07 / APIs & integrations

An API integration has stopped: investigate and recover without duplicate work

Control an integration incident through business impact, preserved evidence, targeted diagnosis and a verified backlog recovery process.

Read the guide ↗08 / APIs & integrations

API integration maintenance and handover: what must be in place?

Make an integration transferable with account ownership, data contracts, meaningful monitoring, recovery procedures and rehearsed handover.

Read the guide ↗

n8n & process automation

n8n and process automation: from working practice to a controlled workflow ↗

A complete starting guide to process selection, n8n, cost, hosting, failures, approval, pilots and maintenance. Includes practical guides and a fictional process example.

01 / n8n & process automation

Which business process should you automate first?

Choose a first automation using evidence about volume, handovers, exceptions and useful outcomes. Includes a worked selection example.

Read the guide ↗02 / n8n & process automation

n8n, Make or Zapier: which fits your business process?

Compare n8n, Make and Zapier using a real workflow: supported actions, exceptions, maintenance, cost and handover. Includes a practical evaluation plan.

Read the guide ↗03 / n8n & process automation

What does workflow automation cost? Budget beyond the initial build

Budget for workflow automation using discovery, integrations, testing, maintenance and review. Includes a transparent fictional calculation.

Read the guide ↗04 / n8n & process automation

n8n Cloud or self-hosting: what must your business organise?

Compare n8n Cloud and self-hosting through responsibility, access, data flows, recovery and maintenance. Includes a fictional decision example.

Read the guide ↗05 / n8n & process automation

A failed n8n workflow: investigate and recover without duplicate actions

Investigate failed workflows using execution evidence, business references and checks on earlier actions. Includes a detailed fictional recovery case.

Read the guide ↗06 / n8n & process automation

Human approval in workflows: make authorisation meaningful

Design human approval around authority, a specific data version, expiry and controlled execution. Includes a fictional purchasing example.

Read the guide ↗07 / n8n & process automation

Designing an automation pilot: evidence for the next decision

Plan an automation pilot using representative cases, observable acceptance, human review and stopping conditions. Includes a fictional trial design.

Read the guide ↗08 / n8n & process automation

Maintaining n8n workflows: ownership, checks and controlled change

Organise workflow maintenance around ownership, meaningful checks, updates, access and handover. Includes a fictional business-rule change.

Read the guide ↗

AI agents & chatbots

AI agents for business: from first decisions to daily operation ↗

A practical guide to AI agents and chatbots covering task selection, knowledge, connections, costs, evaluation, handover and operation.

01 / AI agents & chatbots

AI agent or chatbot: which approach fits your process?

Compare chatbots, fixed workflows and AI agents by task, permissions, reliability and operating effort, with a practical decision example.

Read the guide ↗02 / AI agents & chatbots

What does an AI agent cost? Budget for delivery and operation

Build a realistic AI-agent budget covering scope, integrations, evaluation, usage, human review and maintenance, without invented price promises.

Read the guide ↗03 / AI agents & chatbots

Which permissions should an AI agent receive?

Design bounded AI-agent permissions for reading, proposing and executing, with approval boundaries, practical access checks and recovery examples.

Read the guide ↗04 / AI agents & chatbots

Connecting an AI agent to your CRM: design the data flow

Define an AI-to-CRM integration with dependable customer matching, limited actions, duplicate handling and evidence of actual processing.

Read the guide ↗05 / AI agents & chatbots

Testing an AI agent: turn fluent answers into useful evidence

Build a practical AI-agent test set covering sources, actions, exceptions, handover and repeatable acceptance criteria.

Read the guide ↗06 / AI agents & chatbots

From AI agent to employee: design a useful handover

Make AI-agent handover work by recognising boundaries, preserving context, assigning ownership and preventing duplicate follow-up.

Read the guide ↗07 / AI agents & chatbots

Business knowledge for AI agents: sources, access and freshness

Prepare AI-agent knowledge sources by defining valid versions, permissions, usable citations, deletion and testable answers.

Read the guide ↗08 / AI agents & chatbots

Operating an AI agent: monitoring, changes and recovery

Plan AI-agent operation with useful alerts, usage limits, source ownership, regression checks, pausing and a workable recovery route.

Read the guide ↗

RAG & business knowledge

RAG and business knowledge: make information findable, reviewable and manageable ↗

A practical guide collection covering sources, retrieval, permissions, citations, evaluation, costs and maintenance for RAG applications.

01 / RAG & business knowledge

RAG, search or a knowledge base: what does your team need?

Compare document search, a managed knowledge base and RAG against tasks, source quality, review effort and everyday use.

Read the guide ↗02 / RAG & business knowledge

Prepare company documents for RAG: build a managed source collection

Make documents useful for a RAG trial through ownership, validity, structure, removal rules and representative checks.

Read the guide ↗03 / RAG & business knowledge

RAG access control: who may retrieve which company information?

Define users, organisations, source permissions, caches and revocation before making internal knowledge available through AI.

Read the guide ↗04 / RAG & business knowledge

RAG retrieves the wrong passage: investigate retrieval before rewriting the answer

Diagnose retrieval quality with expected passages, product versions, document structure, filters and controlled comparisons.

Read the guide ↗05 / RAG & business knowledge

Citations in RAG: does the passage actually support the claim?

Design reviewable AI answers using appropriate passages, versions, conditions and useful next steps when evidence is missing.

Read the guide ↗06 / RAG & business knowledge

Test a RAG system: assess sources, answers and refusals separately

Build a useful RAG evaluation with representative questions, expected passages, permission cases, clear criteria and repeatable comparisons.

Read the guide ↗07 / RAG & business knowledge

What does a RAG system cost? Budget for sources, retrieval, evaluation and updates

Examine RAG costs through source preparation, processing, search infrastructure, evaluation, permissions and everyday content maintenance.

Read the guide ↗08 / RAG & business knowledge

Keep RAG current: source changes, withdrawal and everyday knowledge maintenance

Organise source freshness through change detection, processing checks, ownership, withdrawal and targeted reassessment.

Read the guide ↗

Custom software & portals

Custom software and customer portals: turn a business process into a usable first release ↗

Prepare custom software or a customer portal through solution choice, clear scope, data agreements, roles, acceptance and handover.

01 / Custom software & portals

Standard software or a custom application: compare the work that needs doing

Decide when an existing product fits and when custom software is useful, using a common trial process, exceptions, maintenance and a comparable cost model.

Read the guide ↗02 / Custom software & portals

Define custom software scope: turn a wish list into a usable first release

Prepare a bounded software assignment with users, information, states, exceptions, acceptance evidence and explicit extension boundaries.

Read the guide ↗03 / Custom software & portals

What does custom software cost? Compare scope, uncertainty and operation

Examine software costs through concrete workflows, dependencies, implementation, usage and maintenance rather than an isolated starting price.

Read the guide ↗04 / Custom software & portals

Customer portal roles and permissions: who may use which record?

Define portal access by organisation, record, operation and field, including invitations, downloads, role changes and meaningful denial tests.

Read the guide ↗05 / Custom software & portals

Customer portal statuses: explain what happened and what still needs doing

Design understandable portal states with clear meaning, ownership, next steps, source freshness and a route for uncertain outcomes.

Read the guide ↗06 / Custom software & portals

Import data into new software: turn an export into reviewed records

Prepare a bounded data import with selection rules, field mapping, stable references, trial loading, reconciliation and business sign-off.

Read the guide ↗07 / Custom software & portals

Accept custom software: assess complete tasks and agreed boundaries

Prepare software acceptance with representative users, input, exceptions, access, recovery evidence and an explicit decision about unresolved findings.

Read the guide ↗08 / Custom software & portals

Deliver new software: arrange code, accounts, data and future development

Make a new software delivery transferable through practical arrangements for access, building, operation, data, documentation and future changes.

Read the guide ↗

Existing software & audits

Understand the choices. Build with confidence.

API integrations: turn separate applications into a manageable data flow ↗

What does an API integration cost? Define the job before the price

Standard connector or custom integration: test the whole process

Connect CRM and accounting: agree customers, orders and invoice boundaries

Synchronise data without uncontrolled overwriting

Prevent duplicate orders and invoices when API messages repeat

Webhooks or polling: choose for timeliness and recovery

An API integration has stopped: investigate and recover without duplicate work

API integration maintenance and handover: what must be in place?

n8n and process automation: from working practice to a controlled workflow ↗

Which business process should you automate first?

n8n, Make or Zapier: which fits your business process?

What does workflow automation cost? Budget beyond the initial build

n8n Cloud or self-hosting: what must your business organise?

A failed n8n workflow: investigate and recover without duplicate actions

Human approval in workflows: make authorisation meaningful

Designing an automation pilot: evidence for the next decision

Maintaining n8n workflows: ownership, checks and controlled change

AI agents for business: from first decisions to daily operation ↗

AI agent or chatbot: which approach fits your process?

What does an AI agent cost? Budget for delivery and operation

Which permissions should an AI agent receive?

Connecting an AI agent to your CRM: design the data flow

Testing an AI agent: turn fluent answers into useful evidence

From AI agent to employee: design a useful handover

Business knowledge for AI agents: sources, access and freshness

Operating an AI agent: monitoring, changes and recovery

RAG and business knowledge: make information findable, reviewable and manageable ↗

RAG, search or a knowledge base: what does your team need?

Prepare company documents for RAG: build a managed source collection

RAG access control: who may retrieve which company information?

RAG retrieves the wrong passage: investigate retrieval before rewriting the answer

Citations in RAG: does the passage actually support the claim?

Test a RAG system: assess sources, answers and refusals separately

What does a RAG system cost? Budget for sources, retrieval, evaluation and updates

Keep RAG current: source changes, withdrawal and everyday knowledge maintenance

Custom software and customer portals: turn a business process into a usable first release ↗

Standard software or a custom application: compare the work that needs doing

Define custom software scope: turn a wish list into a usable first release

What does custom software cost? Compare scope, uncertainty and operation

Customer portal roles and permissions: who may use which record?

Customer portal statuses: explain what happened and what still needs doing

Import data into new software: turn an export into reviewed records

Accept custom software: assess complete tasks and agreed boundaries

Deliver new software: arrange code, accounts, data and future development

Existing software and audits: understand the situation and choose a manageable next step ↗

Taking over an existing codebase: establish what must keep working

Scoping a software audit: which decision should the evidence support?

Prioritising technical debt: which improvement actually helps the business?

Modernise or rebuild existing software: compare the whole transition

Migrating a running legacy system: ownership, cutover and fallback

From audit finding to improvement: evidence, priority and retesting

Testing software recovery: a backup is not yet a working business journey

Handing over existing software operations: let a second person perform the work