Skip to main content

Services / CraftDuka

AI agent development with controlled business actions

Scope an AI agent around one task, explicit tool permissions and human approval. Start with a read-only assistant before allowing record changes.

Who this suits

Operations managers who need an assistant to use business tools, rather than only answer questions.

When a simpler option is a better fit

A fixed form and deterministic routing rule are simpler when the task has no ambiguity or need to interpret language.

Implementation approach

  1. Select a narrow task such as preparing a sales handoff

  2. Connect approved product information and a read-only CRM lookup

  3. Let a salesperson approve the drafted next action before any update

Illustrative operating rules

Capability boundary and a scoped agent example showing tools, permissions, and human decisions

Illustrative design example. Adapt these rules with the responsible team before implementation.

AI agent development with controlled business actions: decisions and ownership
Record or decisionIllustrative ruleAccountable owner
Customer questionRetrieve approved product facts and cite the sourceProduct owner
CRM lookupRead only the assigned contact and open opportunitySales operations
Discount requestDraft a recommendation without changing priceSales manager

Dependencies and access

  • A task owner and representative questions
  • Approved source documents and access boundaries
  • Test accounts for each permitted tool

Limits and exceptions

An unavailable tool must produce an explicit failure and a human task. An instruction inside retrieved text must never expand the agent's permissions. Keep tool calls and approval decisions in a reviewable log.

Scope and cost drivers

Budget for retrieval, tool development, evaluation, model usage and operational review. More write permissions increase the testing scope even when the conversation looks simple.

Acceptance and measurement

Measure correct task completion, unsupported actions prevented, human corrections and tool failures separately. A fluent answer alone is not an accepted result.

Questions before starting

What must be ready before implementation?

A task owner and representative questions; Approved source documents and access boundaries; Test accounts for each permitted tool.

Discuss the scope and availability

Tell CraftDuka about the task, your current systems and the people who will use it. Our team is based in Nairobi and serves Kenya and East Africa. We will assess the fit and availability before agreeing a project.

Privacy policy