Private beta

Give each kind of work its own Palari.

A Palari is a named coworker with clear scope for one repeatable job. It uses approved sources, drafts the next step, and waits for your review before anything moves.

Start with one Palari See an example

Approved sources

Coworker with clear scope

Permissions

PREPARED FOR REVIEW

SSofia

Sofia prepared a client follow-up

For the client you review

Ready for your review

Sofia prepared this for you to review before replying to the client. Nothing is sent or updated until you approve it.

Sources used

4 sources

Team Policies checked

2 rules

Waiting for approval

2 held

THE TENSION

Teams need shared standards. People need their own space.

Work AI is splitting in two directions. Companies want one official place with shared standards. People keep using private AI chats because they feel faster, more personal, and closer to the work.

ONE OFFICIAL PLACE

One official place

Easy rollout

Generic replies

Sources live somewhere else

Good for control. Weak for ownership.

THE MIDDLE PATH

Palari

A named Palari works from approved sources, keeps the right memory, and waits for permission before anything important changes.

Sources

Task

Memory

Permission

Personal enough to use. Structured enough to trust.

PRIVATE SPEED

Private AI chats

Fast prompt

Private context

Shared state disappears

Good for speed. Risky for shared work.

Standardize the work, not the person.

WHAT A PALARI IS

A Palari is a coworker with clear scope.

Sofia is the Palari for client follow-up. You are the human reviewer. The Client Follow-up Palari Domain tells Sofia what to draft, which sources to use, what to check, and what needs your approval.

A Palari is a coworker with clear scope.

Sofia's scope

Client Follow-up Palari

Client Follow-up Palari Domain you review

Can use

Last email

Client notes

Current pricing sheet

CRM note

Can prepare

Reply draft

Next-step note

Follow-up reminder

Task Card

Approval required

Send reply

Update CRM

Save Team Memory

Connect tools

Cannot access

Finance folder

HR folder

Your private notes

Unapproved drafts

Prepared for review

Sofia prepared the reply draft and next-step note from approved sources, then held both for your review. Nothing moved before review.

PALARI TODAY

Start the day with work already prepared.

Your Palaris prepare the next steps from approved context. Review the decisions, approve what is ready, and keep everything else held.

Your tools keep the records. Your Palaris prepare the work.

5prepared

2need approval

1open decision

0actions sent

Prepared today

SSofia prepared a client follow-up

AAlfred found 3 open decisions

MMara prepared invoice reminders

TTheo found 2 support replies waiting

LLeo suggests cleaning the lead sheet

5prepared

2need approval

1open decision

0actions sent

Sofia prepared a client follow-up

For the client you review

held for approval

What Sofia prepared

Reviewed last email thread and notes

Summarized key points and next steps

Drafted a clear follow-up email

Prepared CRM next-step note

Reply draft

Hi Alex,
Thanks again for the update yesterday. Based on our conversation, I wanted to follow up on the next steps we discussed...

View full draft

Approved context and Team Policies checked.

Reply draft and CRM note stay held until you approve.

Approved context

Team Policies checked

Waiting for approval

CRM note and full revision choices stay inside the review flow.

PALARI DOMAINS

A Palari Domain is one repeated workflow.

Each Palari Domain can contribute prepared items to Palari Today. The Client Follow-up Palari Domain is the operating template behind Sofia's client follow-up item.

Browse Palari Domains

Selected Palari Domain

Client Follow-up Palari Domain

GmailShared sheetHubSpot

This Palari Domain produced Sofia's active item: proposal reply for the client, sources attached, your review required, send reply and CRM update still held.

Common tasks

Reply drafts
Next steps
Follow-up reminders

Typical sources

Client notes
Pricing sheet
Prior emails
CRM note

Useful checks

Promises matched
Tone reviewed
Open question flagged

Suggested tools

Gmail
Shared sheet
HubSpot

Default permissions

Sending needs review
CRM updates need review

Browse Palari Domains

TASK CARDS

A Task Card is the review screen before anything happens.

The Task Card shows the goal, sources used, off-limits places, reviewer, Team Policies checked, and what needs approval before the reply can move.

Summary: sources, off-limits places, and approvals stay attached to the review card.

Permission state

The card makes the task visible before Sofia sends, changes, shares, or connects anything.

Sources used

The sources and off-limits places stay attached to the task, so a person can review the scope before work moves forward.

TASK CARDYou reviewStatus: DraftingPrepared by SofiaS

Client follow-up: a client proposal

This is the Task Card before any external action happens.

Goal

Draft the proposal reply and a next-step note for your review.

Using

Last email, client notes, pricing sheet, CRM note.

Off limits

Finance folder, HR folder, private notes, unapproved drafts.

Approval required

Send reply; update CRM next-step note.

Sources used

Last emailClient notesPricing sheetCRM note

Team Policies checked

Client emails and new commitments need approval before sending. Waiting for approval. Draft only. Nothing sent.

Nothing moves forward until this Task Card is reviewed and approved.

COMPLETION CARDReady for reviewDraft only. Nothing sent.SSofia

Completion Card: client follow-up

Drafted reply

Hi, thanks for sharing the proposal.

It looks aligned with the goals we discussed. A few quick clarifications will help us move faster.

Can you share the timeline for rollout?
Are there any limits on user seats?
Will training be included?

Once I have these, I'll confirm next steps. Thanks!

CRM next-step note

Follow up to confirm timeline, seats, and training. Confirm next steps once info received.

Still held

Approve before action.

Used

4 sources

Prepared / changed

2 drafts

Needs review

2 approvals

Source details

Last email, Client notes, Pricing sheet, CRM note

Team Memory proposal

The client prefers short follow-ups with bullets and one clear next step.

COMPLETION CARDS

A Completion Card is the record after work is prepared.

You can review what Sofia prepared, what sources she used, what still needs approval, and why the status is still Draft only. Nothing sent.

Summary: the card keeps sources, draft changes, and approval state visible after preparation.

Review handoff

Completion Cards are work records for review and handoff. They are not private notes.

Manageable

The manager sees the task, evidence, changes, and review state without reading every private conversation.

TRUST CHAPTER

Manage the work, not the worker.

Managers review scope, sources, drafts, decisions, and approval state. The work lives in Task Cards and Completion Cards, not in private conversations with a Palari.

People keep their own working space. Teams still get coordination, standards, and management clarity.

Learn how trust works in Palari

Sofia's client proposal waits for you.

Sofia

Client Follow-up Palari DomainYou reviewDraft only

Review needed

This draft is ready for your review before anything is sent.

Visible record, team policies, memory proposal, and sharing scope all stay behind review.

Visible work record

You see sources, drafts, and actions relevant to this work.

Team policies

Checks confirm this draft follows your team's policies.

Team memory proposal

Sofia proposes memory to capture for the team.

Palari memory scope

Only what's approved becomes team memory.

Shared only through review

Nothing is sent or remembered without your approval.

TOOL EXPLORATION

Explore the Palari Domain before adding anything.

For messy follow-up tracking, Palari can suggest a tool, a cleanup path, or no new tool. Nothing connects, shares, imports, or exports before you approve the setup Task Card.

Sofia's tool exploration suggestion

Keep the shared sheet for now; create a cleanup Task Card.

Sofia found a tool question while preparing a client follow-up.

Connection not started

Sofia's tool exploration suggestion

Connection not started

Keep the shared sheet for now. Create a cleanup Task Card before connecting tools.

Context under review

Last email

Client notes

Current pricing sheet

Inbox

Current setup

Client Follow-up Palari Domain

Sofia preparing a client follow-up

Current setup

Follow-up tracking is messy.

Palari Domain:

Client Follow-up Palari Domain

Work item:

Sofia preparing a client follow-up

Current setup:

Shared sheet, inbox, client notes

Context under review

Last email

Client notes

Current pricing sheet

Inbox

Shared sheet

4 more context points reviewed

Keep the shared sheet for now.

Create a cleanup Task Card before trying a CRM.

Clean follow-up tracking before any CRM trial.

Clean follow-up sheet columns

Name owner

Decide CRM trial later

Permission before connection

You review

Setup Task Card required

No connection, sharing, import, or export starts from exploration.

No-new-tool cleanup

Best fit

Keep the sheet, clean the work trail, decide later.

CRM trial and billing paths stay as later choices after cleanup clarifies fields, ownership, and need.

Palari compares options before anything connects, shares, imports, or exports.

FAQ

The trust questions stay on the page.

The preview keeps the important answers visible: scope, memory, permissions, management visibility, tools, and regulated-data boundaries.

What is a Palari?

A named coworker for one kind of work, with approved sources, visible records, and permission moments.

Why not just use general chat?

General chat starts broad. Palari starts with a domain, Task Cards, Completion Cards, and team-reviewable rules.

Can managers see everything?

No. Depending on setup, managers review work records and team policies; private worker chats stay separate.

What does permission cover?

Outside tools, vendor sharing, sends, record changes, access expansion, and Team Policy changes wait for approval.

What happens to memory?

Palari Memory, Team Memory, and Team Policies stay separate. Proposed memory is reviewed before reuse.

What about regulated work?

Beta is for low-risk administrative work unless the right agreements, controls, and legal review are already in place.

START HERE

Start with one Palari.

Pick one recurring job, confirm the sources and actions, then review the first draft.

No tools connect until you say yes. Start narrow, review the first draft, then grow from there.

One recurring job

Confirmed sources

First draft

Draft for review

Tools wait for review