Book a first callLogin
Documentation

Working with capabilities

Working with capabilities ​

A capability is the unit in which Beyondles HorAIzon accepts work: a goal, a team of agents and a trigger. This page describes the path from the idea to a running result.

Three ways to a capability ​

  • Marketplace: Ready-made templates for common goals. Pick one, connect the systems, start. Menu "Capabilities › Marketplace".
  • Build your own: You describe the goal in your own words. Beyondles HorAIzon proposes the team, the trigger and the required connections. You confirm or change. Menu "Capabilities › Build your own".
  • Send a request: When you are not sure whether your idea is a capability, or when a tool is missing. Beyondles gets back to you. Menu "Capabilities › Send a request".

What a capability needs ​

  1. A goal in one sentence. "Every Monday the weekly report is in the inbox." Not: "Automate reporting."
  2. A trigger. A point in time, an event (new mail, new CRM record) or a human pressing start.
  3. Connections. The systems it reads from and writes to. If a connection is missing, the capability is "limited" and only runs once it is set up.
  4. A budget. Every capability has a cost ceiling. Under "Costs & Budget" you see what it consumes.

What happens after the start ​

  • The agents get to work and log every step. Read it under "Mission Control › Activity".
  • Anything that goes outside or costs money can require an approval. Open approvals are under "Mission Control › Approvals". You define what needs approval in the capability's settings.
  • Results and progress are under "Technical (Admin) › Goals & Progress".

When a capability is not the right thing ​

If you cannot form a sentence starting with "Every Monday …" or "As soon as … arrives …", it is probably not a capability. The decision helper leads you to the right building block in three questions.

Good practice ​

  • One goal per capability. Two goals are two capabilities, even if the same agents work on them.
  • Move the procedure out. The "how" belongs in a skill, not in the capability's description. That way several capabilities can use the same procedure.
  • Start small. One trigger, one outcome, let it run for a week. Then extend.