How it works

One job first, run for you. More only when it has earned its place.

Constara sets up and runs agents for one recurring job in your business. You choose the job, set the limits, and approve what goes out. You add another job only after you have reviewed the first.

01 / A free conversation

A free, no-commitment 30-minute conversation about where agents could help your business. We ask what kind of business you run and how many locations, which recurring work takes the most attention, where customers and inquiries reach you, the tools you use today, what you have already tried with AI and agents, what must always stay with a team member, and what you would like to see improved within three months. Then we tell you plainly whether that work is a good place to start. A paid audit, agreed separately in writing, can follow. You decide whether to go further.

From audit to expansion

Five stages from left to right on paper: two chat bubbles, one blue and one white; a written report with a small red ring; a proposal sheet with a short brass rail and a red cord drawn on it; a brass carrier with a blue message bubble on a short rail, with a red cord and a stamp beside it and a calendar card with a gold square past the cord; and three small calendar cards with gold squares, each on its own short rail, beside a closed green ledger.
The path in one picture: a conversation, a written audit, a proposal with its limits, one job behind a checkpoint, then more of the same.

02 / Audit

A written report on one representative recurring job: its sources, its risks, the limits it would need, and whether it is worth delegating. Priced from EUR 900. If nothing is worth delegating, the report says so, and you keep it. The entry audit page sets out what it covers.

03 / Your plan

Nothing starts until you have a written proposal. It sets out:

  • the job and the scope band
  • the evidence and the measurement method
  • the owner and the limits
  • the cap for your case

You can stop here. The proposal is where you decide whether to start, and on what terms.

04 / A narrow pilot

Start with one unit (a site, a brand, or a channel) or one workflow, for three months. Every outgoing message waits for a named approver. At the end, you check the result against the baseline agreed in the proposal. The fee rule is the same as in the ongoing service: the lower of the agreed cap and one third of verified incremental profit, and nothing below the agreed threshold. Pricing explains the rule.

05 / Expand deliberately

Review what worked before adding another job or unit. Each addition goes through the same steps: a written scope, the same checkpoints, and the same fee rule.

  • Keep one named approver and a monthly review.
  • After the pilot, the proposed service rolls monthly, with 30 days’ notice.
  • The cap is reviewed once a year, with at least 60 days’ notice.

Who does what

The audit and proposal say exactly which sources and actions are included.

  • You choose the goal and approve consequential exceptions.
  • We design, connect and operate the scoped system, and maintain its agreed boundaries.
  • Agents prepare routine work within those limits.

What a running job looks like

Envelope, message and form lead to a prepared reply on a brass carrier, a rust checkpoint, a booked calendar and a closed green ledger. Dots under the stages count the five steps.
One job from the inquiry to the record: the agent prepares, the checkpoint waits for a person, and the result is kept.

Once a job is agreed, each piece of work becomes a task in one shared record. Take an inquiry from the web form of a dental clinic. An agent prepares a reply from the clinic’s approved prices, availability, and answers. The reply waits at a checkpoint, where a named person approves, edits, or stops it. After that, the decision and its context stay in the record, and the weekly numbers come from the same place. On the Constara side, Ateles sets the workflow, the limits, and the checkpoints, and Neotoma keeps the sourced record.

The example is synthetic, and the steps are the intended design for a job we set up with you before anything runs.

One organization, not a pile of tools

Separate tools each hold their own copy of the facts. The design puts newly delegated work in one shared record, under shared rules, so that one job can inform another. In a synthetic example, a follow-up waits because an invoice is disputed, and the next report uses a correction recorded elsewhere. This is the intended design, not department-wide coverage available today.

You keep the authority

Models can get better at doing a job. Three things stay with you:

  • What matters this week. You set the goal, and you change it when the business changes.
  • What may proceed. Anything sent outside the business waits for approval by default, and consequential exceptions come to you.
  • Who answers for the result. One named approver, a monthly review, and a record of what was done and why.

That is why the record and the limits are kept apart from any one model.

What this is not

Some limits are part of the offer:

  • It does not replace the AI tools you already use. It works alongside them, and you can ask your own assistant about the same record.
  • It is not software you configure. It is a service we operate, within the limits you approve.
  • It is not a promise to operate every department. The work starts narrow, with one job.
  • Nothing goes out beyond the approval you set.

See what you could delegate.

A free, no-commitment 30-minute conversation. You leave with a clearer picture, whether or not you work with us.

A calendar card with one gold square filled in, beside a small blue notebook with a pencil lying across it.