You've been invited to the AI Operator Private Beta · April 2026

Welcome to the beta.

Here's an honest look at what Operator does today, what it doesn't do yet, what's rough around the edges, and what we're asking of you in return.

01 The product

What Operator is today.

Operator is an AI assistant you can chat with about your Amazon business. It has live access to your Seller 365 data (Tactical Arbitrage, Inventory Lab, FeedbackWhiz, SmartRepricer) and Margin Pro, and it can answer questions, run analysis across those apps, and help you think through decisions.

You ask it things in plain English. It pulls the right data, does the work, and responds in chat.

It can also take action — update prices, adjust reorder points, create review requests, and trigger anything your connected Threecolts apps can do. If the app can do it, Operator can do it for you.

Operator runs on Colts 1.0, our production agent harness.

02 Scope

In scope. Out of scope.

In scope for this beta

Chat is the whole interface. You ask, it answers — and when you ask it to do something, it does it. Read and write, across every connected app.

Not in scope yet:

  • Automated daily briefings
  • Scheduled playbooks or workflows
  • Automated alerts or triggers
  • Downloadable reports

These are on the roadmap. We wanted to get the core chat experience right first. If the beta goes well, they unlock in Q3.

03 Works well

What works.

  • Answering across apps
    Inventory status, review trends, pricing changes, sourcing questions — pulled from one or several apps at once.
  • Taking actions on your behalf
    Update prices, adjust reorder points, create review requests — anything your connected Threecolts apps can do, Operator can trigger.
  • Exploratory "why is this happening" questions
    Where you'd normally pull several reports.
04 Rough edges

What's rough.

  • !
    Occasionally a query fails and you'll need to retry
    Tell us when it happens.
05 Your role

What we're asking of you.

We picked you because we trust your judgment and we want honest feedback. Here's the deal:

i.

Use it at least 3× per week during the beta.

If it's not part of your workflow, we can't learn what works.

ii.

Tell us honestly what works and what doesn't.

We'd rather hear "this is frustrating" than nothing at all.

iii.

Join the private Slack channel & post when things come up.

Channel invite lands in your onboarding call. Expect us to respond fast.

iv.

A 20-minute exit interview at the end.

Final conversation to capture what we should build next.

06 Reach us

How to reach us.

Four ways. Pick whichever is fastest in the moment — we're monitoring all of them.

Primary — Slack
#aio-beta
Invited on onboarding call
Direct email
For anything sensitive
In-product
👍 / 👎 on any response
We read every single one
Exit interview
20 minutes, end of beta
We'll reach out to schedule
07 After beta

What happens next.

If the beta validates the product

Operator moves to general availability with paid tiers priced around actual query cost and usage patterns — we want to understand how you use it before we set prices. Beta participants get a discount on their first 3 months as a thank-you. Details at the end of beta.

Pro
TBD
Pro 5×
TBD
Enterprise
Negotiated

If it doesn't validate

We'll be honest about that too. We'll work with you on wind-down and share what we learned.

— Let's get started —

Open Operator.
Ask it something.

The first query is the hardest. Try "what should I focus on this week?" and go from there.