What happens after the 14-day trial?

You automatically drop to the free plan — no charge, no interruption. You keep all your tasks and data forever. No credit card required to start.

Does Flowly sync with Google Calendar?

Yes. Pro plan includes two-way Google Calendar sync. Events appear as tasks, and Flowly tasks show up in your calendar so your schedule stays in one place.

Can I export my data?

Always. Export all tasks, time logs, and analytics as CSV or JSON from your account settings at any time — your data is yours.

How is Flowly different from using Toggl + Todoist?

Flowly tracks time inside the task — no tab switching, no import/export, no double-entry. One click starts the timer; one click marks done. Everything lives in the same view.

What happens if I cancel Pro?

You drop to the free tier immediately with no data loss. Tasks beyond the free limit are archived (not deleted) and restored automatically if you resubscribe.

What is a sprint retrospective?

A sprint retrospective is a short team meeting at the end of a sprint to reflect on how the work went. The team reviews what went well and what did not, then agrees on concrete changes to try in the next sprint.

How do I keep a retro from turning into a complaint session?

Structure it. Move deliberately from what went well to what did not, then to root causes and a small set of owned actions. The output is the test: if the retro ends without concrete, assigned actions, it was a vent, not a retro.

How many action items should come out of a retro?

Two or three. A retro that produces ten action items produces zero real change because nothing gets the focus to actually happen. A few well-chosen, owned actions are far more likely to stick.

All templates

🔄engineering

Sprint Retrospective

Run a sprint retro that ends in owned action items, not just venting.

We'll add these tasks after you sign up. Free, no credit card.

How it works

A retrospective that only lists complaints changes nothing. A good one ends with a small number of concrete actions, each with an owner. This template structures it: gather notes and metrics, list what went well and what did not, dig into root causes, agree on two or three actions, assign owners, then carry them into the next sprint. Apply it at the end of every sprint so the team actually improves instead of repeating the same problems.

What you get (7 tasks)

Gather notes and metrics from the sprintmedium~30m
Collect what happened during the sprint: completed work, missed items, and any relevant metrics. Facts keep the retro grounded.
#prep
List what went wellmedium~20m
Capture what worked this sprint. Naming successes makes it more likely the team repeats them on purpose.
#retro
List what did not go wellhigh~20m
Name the problems honestly and without blame. The goal is to fix the process, not to find someone at fault.
#retro
Surface blockers and their root causeshigh~30m
For each significant problem, ask why it happened until you reach the real cause rather than the symptom.
#retro
Agree on 2-3 concrete action itemshigh~20m
Pick a small number of specific changes to make next sprint. Two or three real actions beat ten vague intentions.
#actions
Assign an owner to each action itemhigh~10m
Give every action a named owner. An action with no owner is a wish, not a commitment.
#actions
Carry the actions into next sprintmedium~15m
Add the action items to the next sprint so they get done, and review them at the start of the following retro.
#actions

Sprint Retrospective

How it works

What you get (7 tasks)

When to use this

Frequently asked

Ready to use it?