Skip to content

The pilot

A pilot on real work.

One team, its real work, a short evaluation agreement, and the people who build Constraint.

If your first work isn't running on your real tickets by the end of week two, you can stop and you won't pay for the pilot.

30 minutes with the founding team.

Your first two weeks.

Day one we agree the first work; week one we set up; week two it runs.

  1. Day one

  2. Week one

  3. Week two

How cost works

We agree the price with you on a short call, and it follows the work as your needs change. Every pilot includes the setup and an hour with us every week.

FAQ

Plain answers about accounts, connectors, records and other common questions.

What happens after the pilot?

We review it together. If it isn't the right fit, you can stop there. If you continue, ongoing work runs under a services agreement, and more teams can join.

Where does our data go?

Each session runs on the computer of the person who started it, using your own AI account. Its record is saved to Constraint's cloud service with its ticket, with screenshots removed and keys, tokens and passwords blanked out. Session conversations are stored as traces on your computer and in Constraint's cloud service. Session records in Constraint's cloud are deleted 30 days after the account is deleted. Today, Constraint uses them only to run the service. Your AI service and connected tools receive what each session sends them.

Do agents keep working when my computer is off?

No. Each person's agents work on their own computer while the desktop app is running. A teammate can join a session only while both computers are on. Work can be handed over for good by exporting a session's trace, which a teammate imports and carries on.

Does it work with our tools?

Constraint connects to over 400 tools today, through an integration provider. An administrator approves each connector, and each person connects their own accounts.

Do I need to know about AI to use it?

No. You brief the VP in plain words, the way you'd brief a colleague, and it asks you only the questions that are yours to answer.

Whose AI account does it use?

Your own. You connect your own AI account and choose from its models.

Who approves what gets connected?

An administrator approves each connector, and each person connects their own accounts.

Can a teammate approve a tool on my computer?

No. A teammate can answer a session's questions from their own computer, but approving a tool is never done from another computer.

Who sees the records?

People see session records only for the teams they can read.

Can my teammates see what my AI is doing?

Yes. Teammates see each other's AI sessions live, with whose computer runs each. They can message a session, answer its questions, stop it, or step in while both computers are on. You choose who can step in, per session and per person; each request to join is checked first.

What's a department?

One part of your company, like Marketing, with its own roles and agent teams, directed by the people on that team.

What's a role?

An AI worker with its own job, skills and model. A ticket goes to one role, or to an agent team that runs roles in sequence.

What's a skill?

Written instructions a role follows. Skills are saved in versions, and each role uses the version you choose.

What's a sentry?

A check that spots recurring work and proposes or files a ticket for it. It runs on a schedule, or when something happens in a connected app.

Who can change a shared role, sentry or department?

Only the owner. Everyone else makes a copy. An admin can choose to share a department's setup and its sentries with other teams.

Book a short call

We set up every pilot ourselves, so we start a few teams a month.

Book a short callCheck your tools first

30 minutes with the founding team.

A pilot on real work.

Ready to try it on one team's real work. Every engagement starts with a pilot: one team, under a short evaluation agreement, working directly with the people who build Constraint. When the pilot ends, we review it together; ongoing work runs under a services agreement, or you stop there.

On your side, that's the team and the person who owns its work.

The pilot's length is agreed with you on the short call, and it starts with the first two weeks.

Full details

Your first two weeks.

Day one: we agree the first two pieces of work, and how we'll both know they're done. Week one: we connect your ticketing service, turn your docs into roles and skills, and set up each computer. Week two: the first work runs on your real tickets, with hands-on training.

Day one. We agree with you on the first two pieces of work to hand over, and how we'll both know they're done.

Week one. We connect your team's ticketing service, turn your docs into your department's roles and skills, and set up each person's computer.

Week two. The first work runs on your real tickets, and we train the team hands-on, leaving it resources to work from.

Four questions for a useful hand-off help choose the first two pieces of work.

Goal: what should be different when the work is done?

Information: what does the worker need to begin, and which results must arrive first?

Review: what result will you inspect, and which choice needs a person?

Hand-off: who continues, and where can they find the decision and the session?

Full details

How cost works

Every pilot includes the setup and an hour-long meeting with us every week, during the pilot and after it. The price is agreed on a short call.

We agree the price with you on a short call, and it follows the work as your needs change.

The pilot's length is agreed with you on the short call, and it starts with the first two weeks.

Each session runs on your own AI account.

When the pilot ends, we review it together.

If it isn't the right fit, you can stop there.

If you continue, ongoing work runs under a services agreement, and more teams can join.

An hour-long meeting with us every week, during the pilot and after it.

Full details

Book a short call

Book a short call and tell us about your team and the first work you'd hand over. On the call we agree the price. You work directly with the people who build Constraint.

Tell us about your team, the first work you'd hand over and the tools it works in.

A short description is enough to start a conversation about fit and onboarding.

Please leave out confidential business information, company documents and AI sessions.

Full details

Check your tool compatibility

Constraint connects to over 400 tools today. Type a tool's name to see whether it's one of them.

The finder only searches the list: your typing stays in your browser, and nothing is connected from here.

List updated 29 October 2026.

Not on the list? Book a short call and tell us about your team and the tools it works in.