Pilot-first pricing
Start with one Palari, one kind of work, and one approved set of sources. The pilot is quoted around scope, not seats or a public tier table, so the team can trust the loop before anything broader gets connected.
The pilot is deliberately small: choose client follow-up, invoice reminders, a weekly owner briefing, support replies, office admin, or another repeatable job your team already does. Palari shows its sources, records what happened, and asks before the scope expands. Pricing is discussed after the work boundary is clear.
What the pilot proves
Pilot sequence
Start narrow
Pick one recurring office job, one human owner, and the exact sources the Palari is allowed to use.
Prove the loop
Run real work through Task Cards, review the Completion Cards, and decide what belongs in memory.
Grow from there
Quote the next step around the scope you approve: domains, Palaris, sources, policies, memory, and tools.
After the pilot
After the pilot, the commercial plan follows the approved work boundary: how many Palaris, how many domains, which sources, and whether Team Memory, Team Policies, or outside tools are part of the rollout.
Keep one Palari close to one person or founder. Best for reminders, drafting, follow-ups, and a small set of approved sources.
Bring a domain into a shared workspace with Team Memory, Team Policies, source standards, and manager-visible task status.
Use Tool Exploration to decide whether Slack, Google Workspace, Canva, QuickBooks, HubSpot, or another tool should enter the domain.
Beta boundary
Personal Palari Memory is private unless shared; Team Memory is separately approved and visible only to authorized team members. Larger tasks, new sources, and outside tools become explicit scope decisions.
Continue exploring Palari