Sistava is an AI workforce platform where solo founders hire AI employees to run their business around the clock. Each AI employee has a specific role like sales, marketing, or customer support, with real tool integrations, persistent memory, and the ability to work inside your existing apps like Slack, Gmail, and HubSpot.

What is an AI employee?

An AI employee is an autonomous AI agent with a defined role, persona, skill set, and tool access. Unlike a chatbot that only answers questions, an AI employee takes on recurring work like writing emails, qualifying leads, answering support tickets, and publishing content, and it works on its own around the clock without being prompted each time.

How is Sistava different from project management software?

Sistava is not project management software. You hire AI employees who do the work, not a tool that tracks work done by humans. Your AI employees run sales outreach, write marketing content, answer support tickets, and handle operations on their own, without constant supervision.

How much does Sistava cost?

Sistava has a free plan you can start without a credit card, plus paid plans that scale with how much work you hand to your AI employees. See the pricing page for current plans.

What can AI employees do on Sistava?

Your AI employees take on the recurring work that runs a business: qualifying and reaching out to leads, writing and publishing marketing content, answering support tickets, and handling day to day operations. Each one comes with a role and skill set, so it can start working the day you hire it.

Sistava is built for solo founders and small teams who need to run sales, marketing, support, and operations without hiring a full human team. It gives you the equivalent of a growth team you can hire in minutes.

Run Sprints and Work Cycles

A sprint puts a goal and a window around your team's work, so a week means something instead of being an endless list of tasks.

TL;DR

A sprint is open, paused, closed, or cancelled. You or your team leader open one, the team works inside it, and one of you ends it when the work is done. Nothing moves on its own. Sprints are optional: a team with no sprint still works its task board perfectly well.

How It Works

A sprint moves through four states, and nothing but you or the leader moves it.

State	What it means	Who changes it
Open	The sprint is running. Tasks land in it, the team works them, progress shows on the board	You or the team leader
Paused	Held in place. Existing tasks stay linked, but new work created while paused stays loose instead of joining it	You or the team leader
Closed	Wrapped and kept as history, with whatever review was written at the end	You or the team leader
Cancelled	Stopped for good without a full review. Unfinished tasks are left untouched and visible, never archived	You or the team leader

Nothing expires on its own. When an open sprint passes its target end date it keeps running and the banner starts saying it is ready to wrap up. It closes when someone decides it is finished, not when a clock runs out.

Planning and review are conversations. Once a week the team leader talks to you about what the sprint should aim at and how the last one went. That conversation is the planning, and it is also the review. There is no separate mode the team sits in while it happens.

Execution is schedule-driven. The leader runs on its own heartbeat schedule. Each cycle, the leader checks the task board, handles failures first, delegates work to team members with capacity, and journals what happened.

Unfinished work moves only if you say so. When you end a sprint you choose whether to open the next one immediately and whether unfinished tasks come with it. Nothing is moved or archived behind your back, whether you close or cancel.

The Review

Closing a sprint is where most of its value is. Your team leader writes the review themselves: what the sprint set out to do, what actually landed, what did not, and what they would change next time. It is written from the task board and the work journal, in their own words, and kept so you can look back at it later. A cancelled sprint keeps a short cancellation note instead of a full review.

There is no separate ceremony to schedule or attend. The review is the close.

Where to Find It

Sprints appear in the Tasks tab when viewing a team:

Go to your Workspace
Click on a team in the sidebar
Open the Tasks tab
The current sprint appears as a banner above the kanban board

The banner shows the sprint number (or title, if you gave it one), its status, its goal, and how far through the window it is. With no sprint running, the same row offers a Create button and a Plan with [leader] button instead.

What You Can Do

Action	How
Start a sprint	Click Create on the empty-state banner, fill in a title, goal, duration, and optional linked Company Objective
Ask the leader to plan	Click Plan with [leader name] to have the conversation instead of filling the form yourself
Set or change the goal	Open the sprint banner to the detail drawer; the Goals field saves as soon as you click away
Change the title, duration, or recurrence	Same detail drawer; every field there saves itself, there is no separate edit form
Pause a sprint	Open the three-dot menu on the Tasks tab and choose Pause [sprint]. Tasks stay linked, new tasks stay loose until you resume
Resume a paused sprint	Same menu, Resume [sprint]
End a sprint	Open the three-dot menu and choose End [sprint], or use End Sprint in the detail drawer. Write an optional summary, then choose whether the next sprint starts now and whether unfinished tasks carry over
Cancel a sprint	Same menu, Cancel [sprint]. It becomes history immediately; unfinished tasks are left exactly where they are
Work without a sprint	Close or cancel the current one and do not start another. Tasks keep working
View sprint tasks	Open the team Tasks tab. Tasks are grouped by sprint
Intervene mid-sprint	Message the leader anytime to adjust goals or priorities
View sprint history	Open View all sprints from the three-dot menu to see every past sprint with its goals, tasks, and review
Export a sprint	Open a past sprint from history, or the current one's detail drawer, and export it as Markdown, CSV, or JSON

How to Set It Up

Hire a pre-built team. Pre-built teams come ready to work in sprints
Chat with the leader, or fill the form yourself. Either click Plan with [leader] and describe what you need this week, or click Create and set the goal, duration, and optional linked objective directly
Let it run. The leader assigns tasks and members execute
End it when it is done. Write what happened, decide whether the next one starts now and whether unfinished work carries over

Tips and Tricks

Be specific in your first sprint. The leader has no history to work from. Tell them exactly what you want delivered
Give the sprint a goal. A sprint without one is just a date range. One sentence is enough
Turn on Keep sprinting. When creating a sprint, this offers a follow-up sprint the moment you close the current one, so the rhythm does not lapse by accident. It is off by default so the cadence is a deliberate choice, not something you inherit
Check the task board. The team Tasks tab shows all sprint tasks. You can see what is in progress, what is done, and what is blocked
Pause instead of cancelling when work is just on hold. Pausing keeps the sprint and its tasks intact for a later resume; cancelling ends it for good
Let the leader handle failures. If a member gets stuck, the leader reassigns or adjusts during its next heartbeat. You do not need to intervene
Say what to change at the end. Your review shapes the next sprint. Even a short "focus more on X" helps

Good to Know

Sprints are team-level only. Individual employees do not have sprints. Sprints coordinate work across a team through the leader
Sprints are optional. A team with no sprint is a normal setup, not a broken one. Tasks, schedules, and chat all work the same
Tasks can live outside a sprint. A task with no sprint is fine and shows on the board like any other
Past the end date is not a failure. The sprint keeps running and simply asks to be wrapped up
Cancelling never touches your tasks. Every unfinished task on a cancelled sprint stays exactly where it was, still visible on the board
A team can only have one active sprint at a time. Open or paused, never both at once; closed and cancelled sprints are unlimited history
Sprint history is permanent. Closed and cancelled sprints, their goals, tasks, and reviews are all preserved. Nothing is deleted

Frequently Asked Questions

Q: Do I have to plan every sprint myself? A: No. Ask the leader to plan and it proposes a goal based on the last sprint's results. You approve, adjust, or ignore it.

Q: Can I change goals mid-sprint? A: Yes. Edit the goal from the sprint detail drawer, or message the leader to shift priorities.

Q: How long is a sprint? A: Default is 7 days (1 week). You can pick 1, 2, 3, or 4 weeks, or set an exact day count when creating or editing it.

Q: What happens when a sprint runs past its end date? A: Nothing breaks. It stays open and starts showing as ready to wrap up until you or the leader end it.

Q: What is the difference between pausing and cancelling? A: Pausing holds the sprint so you can resume it later with the same tasks and goal. Cancelling ends it for good; it becomes history immediately, and unfinished tasks are left untouched on the board.

Q: Do I have to run sprints at all? A: No. Close or cancel the current sprint and do not open another. The board, tasks, and schedules keep working exactly as before.

Q: Can individual employees have sprints? A: No. Sprints are team-level only. For individual work, use tasks and schedules directly.