Gen8

Build workflows and agents with guidance

Builders · workflows and agents

Build your own workflows and agents

Building an agent is design work: you define the assignment, tools, knowledge and where a person approves. You know the process, we know the platform. Together we get the first version working.

  • Starts with a conversation
  • Review before production
  • A log of every step
gen8 · build sessiondone

Build a first workflow

Plan01Assignment defined: register and enrich new requests
Action02Tools selected: read the CRM and propose a lead
Action03Tested on last month's real requests, including messy ones
Reflect04Two exceptions found: approval added
Ready for review · you decide on launch

Components

What an agent consists of

An agent is not a standalone model. It is a combination configured for each process, determining what it can do and what it will never do.

Changing the tools changes what it may do. Changing the knowledge changes what it relies on. That makes what you build verifiable. More explanation is available under AI agents.

An assignment

The goal, what a good result looks like and what it must explicitly avoid assuming.

Tools

The actions it may perform in your systems: read, search, create, update. If an action is not included, it cannot perform it.

Knowledge

The documents, agreements and examples it relies on, with the corresponding permissions.

Control

For each action: read only, propose with approval, or execute automatically with a log.

Working method

Start small, test on real work

  1. Choose one process

    Start with work you know yourself and where an exception causes little harm.

  2. Smallest working version

    Build one step well first, instead of an entire process halfway.

  3. Test on real examples

    Run the workflow on last month's examples, including messy ones.

  4. Review and launch

    We review permissions, control and logging. You decide what goes live.

Signals and cadence

When an agent starts working

An agent can respond to a signal, such as an incoming email or completed conversation, or run on request. Which form fits depends on the process; we decide together during kickoff.

Want to use a workflow across several teams or organisations? Read templates and reusable workflows.

Which workflow do you want to build?

Tell us in an introductory meeting. We look together at where to start and how we guide you.

  • Response within one business day
  • Starts with a conversation