Product

A teammate, not a tab

Analyst lives where your team already works. There is no dashboard to learn and no builder to maintain: you brief it in Slack, it returns finished work, and you approve what goes out.

The loop

From mention to merged

01

Brief

Mention @analyst in any channel and describe the outcome the way you'd brief a teammate. No prompt engineering, no forms.

02

Plan

Analyst breaks the ask into steps, checks what it already knows about how your team likes this done, and posts the plan if the task is big.

03

Route

Each step goes to the right model: fast models for mechanical work, frontier models for judgment. Nobody picks a model, ever.

04

Execute

Analyst operates your actual tools from its isolated environment: queries the CRM, edits the doc, opens the PR, renders the asset, runs the numbers.

05

Approve

Approval-first is the default, not a setting. Anything irreversible or outward-facing waits for your go in the thread; you can relax gates per workflow as trust builds.

06

Deliver

The artifact lands back in Slack: the report, the PR link, the assets, the updated records. Finished, approved, done.

Model routing

The right model for every step

Most agents run everything through one expensive model, then pass the bill to you. Analyst's router matches each step of a task to the cheapest model that does it perfectly, which is why pricing stays flat.

Mechanical
Extraction, formatting, lookups, data entry
Fast small models
Synthesis
Drafting, summarizing, research, asset generation
Mid-tier models
Judgment
Strategy, code review, anything irreversible
Frontier models + human confirmation
Memory

Memory that compounds

Every brief, correction, and approval teaches your Analyst something durable: your tone, your formats, your definition of done. That memory lives on your environment and nowhere else.

Voice

It writes investor updates like your CEO and release notes like your best PM, because it learned from theirs.

Formats

The board deck template, the weekly report structure, the PR description style. Set once, kept forever.

Judgment

Which deals matter, which bugs are urgent, which posts need a second pair of eyes. Encoded from your feedback.

Onboarding

Show it, don't configure it

You don't write prompts or build flows. You show Analyst the work the way you'd show a new hire: record a Loom, share your screen on a call, or submit a quick video walking through the task. It watches the recording, learns the steps and systems, and takes the work over.

Show it

Record a walkthrough or share your screen. Narrate the task once, the way you actually do it.

It learns

Analyst turns the recording into a repeatable routine: the steps, the tools, your definition of done.

It takes over

The work runs going forward. Add new routines any time by showing it something new.

Now onboarding early teams

Put an analyst on every team.

We connect your Slack, you show it one recurring task, and it runs that work for your team by the end of the first session.

Or write to hello@analystlabs.ai