Nothing gets lost between conversations, or when someone leaves

You run your day, your team conversations and shared procedures in one place.

Sound familiar?

Four sentences, one cause.

It's a place problem, not a discipline one.

Flaber holds what gets lost between tools: lists, notes, what you agreed in your conversations, and a pointer to where the rest lives. It helps you put your work in order and run 1:1s so the next one starts from what you agreed last time.

Google Drive, SharePoint, Excel, OneNote, Outlook — that stays where it is. Flaber replaces none of it — it stands alongside.

One simple place

01People

Each conversation starts where the last one ended.

You run 1:1s — instead of digging through files you scroll your day and see who you are meeting and what it is about: what was agreed and what you owe the person.

Flaber has a place of its own for it, and a conversation outline that helps you agree on a plan of action.

02Team

People leave, the documents stay.

You take over the shared documents — procedures, task lists — of someone who has left the company.

Documents left behind by someone who has gone do not disappear — they wait to be taken over. You click "Take over" and the team's procedures keep working, only with a new owner.

The team loses nothing; the documents stay shared and keep working, only the owner changes — it becomes you.

03Resources

One place instead of another email.

You share the note so it is always at hand. You and the team save the time spent writing emails and resending files — everyone has the same thing in one place, with no mess in other folders and under the same label.

04Day

Today you start with what is left.

You start the day with the tasks you did not get done yesterday — finished ones move into history on their own.

A task is not just text — you can attach a document from Flaber, or a link to a file that lives somewhere else.

app.flaber.io/people/chris-wagner/talks

My day

Today · 19 August
B•1.@H3H2I↗
Useful links<-- move faster
Today
Close the access thread with Robert
Reply to accounting about the invoices
Settle how the areas are splitHow the team's areas are split
write down who decides on performance
Reply to Anna about the production keys
Prepare for the 1:1 with Chris
This week
Go through the backlog of July tickets
three are still unanswered
Onboarding procedure (dev-share)
This month
Routine: closing the month
Collect the data for the quarterly review
DONE
Close the access thread with Robert
Reply to accounting about the invoices
Send the sprint summary to the team
DoneSaved
Useful links
✕
Folders
•SharePoint — 2026 yearly folder
◦contracts and annexes, current version
•SharePoint — quarterly reviews
◦notes and conclusions from the last four
Files
•Company procedures (PDF)
◦document flow, version 4.2
•Scope of duties — template
◦for conversations about a change of role
Other
•Team holiday calendar
•Contacts — suppliers and support
How the team's areas are split
✕

Anna — payments and integrations. Chris — architecture and reviews. I stay with recruitment and the budget.

Open thread: who owns performance. Right now nobody, so it comes back to me.

By 1 September every area has one person who decides — the rest consult, they don't approve.

July tickets stay with Anna until the end of the month, then they go back to the shared queue.

What we are not changing: code reviews still go through Chris, including the ones about payments.

Open document

Chris Wagner

Analyst
…
JournalTalksGoalsReport
To discuss
0 open
PLANPoint to two decisions from this sprint that someone else makes.…
PLANAgree what "a decision handed over" means — when you may come back to it.…
TopicWorking with Anna on closing the month…
Add a topic to discuss…
+ Add
Talks
+ New talk
10/08/2026He handed the testing library decision over. Came back to it two days la…⌄
What's going on at work
He handed the testing library decision over. Came back to it two days later and changed it — the team noticed.
What you agreed
Point to two decisions from this sprint that someone else makes.From the last one
Agree what "a decision handed over" means — when you may come back to it.
How you'll know
The sprint closes with no "waiting on Chris" thread.From the last one
31/07/2026draft⌄
24/07/2026★ achievement⌄
‹ NotesSaved…

How the team's areas are split

Important✕Checking
B•1.@H3H2I↗

Anna — payments and integrations. Chris — architecture and reviews. I stay with recruitment and the budget.

Open thread: who owns performance. Right now nobody, so it comes back to me.

By 1 September every area has one person who decides — the rest consult, they don't approve.

July tickets stay with Anna until the end of the month, then they go back to the shared queue.

What we are not changing: code reviews still go through Chris, including the ones about payments.

›Linksused in 4 documents
Shared — David's team
Who sees this
✕
EveryoneDavid's team
David's team
Checking✕
Done

Shared

Documents with no owner are circulating in the team
2 documents · David's team
Take over
EveryoneChecking
EveryoneAnna KraftChris Wagner
Notes
Payment integration — …
Sandbox works. Production is waiting on keys I have been asking for the second …
Things I don't want t…
Retros. Reviews. Everything I find easier to do myself than to …
Architecture decision…
Three things agreed out loud and written down nowhere. If …
The debt that starts to h…
An event queue with no retry. Works until something goes down.
Checking
You open the person's card — the Talks tab.
9:41••• •• 100%
Flaber
01
01People

Each conversation starts where the last one ended.

You run 1:1s — instead of digging through files you scroll your day and see who you are meeting and what it is about: what was agreed and what you owe the person.

Flaber has a place of its own for it, and a conversation outline that helps you agree on a plan of action.

My day
Today · 19 August
Useful links
Today
Close the access thread with Robert
Reply to accounting about the invoices
Settle how the areas are split
How the team's areas are split
Reply to Anna about the production keys
Prepare for the 1:1 with Chris
DONE
Close the access thread with Robert
Reply to accounting about the invoices
Send the sprint summary to the team
DoneSaved
How the team's areas are split
✕

Anna — payments and integrations. Chris — architecture and reviews. I stay with recruitment and the budget.

Open thread: who owns performance. Right now nobody, so it comes back to me.

Open document
Chris Wagner
Analyst
JournalTalksGoalsReport
To discuss
0 open
PLANPoint to two decisions from this sprint that someone else makes.
PLANAgree what "a decision handed over" means — when you may come back to it.
TopicWorking with Anna on closing the month
Talks
+ New talk
10/08/2026He handed the testing library decision over. Came back to it two days la…⌄
What's going on at work
He handed the testing library decision over. Came back to it two days later and changed it — the team noticed.
What you agreed
Point to two decisions from this sprint that someone else makes.From the last one
Agree what "a decision handed over" means — when you may come back to it.
How you'll know
The sprint closes with no "waiting on Chris" thread.From the last one
31/07/2026draft
24/07/2026★ achievement
‹ NotesSaved
How the team's areas are split
ImportantChecking

Anna — payments and integrations. Chris — architecture and reviews. I stay with recruitment and the budget.

Open thread: who owns performance. Right now nobody, so it comes back to me.

By 1 September every area has one person who decides — the rest consult, they don't approve.

›Linksused in 4 documents
Shared — David's team
Who sees this
EveryoneDavid's team
David's team
Checking
Done
Shared
Documents with no owner are circulating in the team
2 documents · David's team
Take over
Notes
Payment integration — …
Sandbox works. Production is waiting on keys I have been asking for the second …
Things I don't want t…
Retros. Reviews. Everything I find easier to do myself than to …
Shared
Lists
My day
Notes
Team

That place is Flaber.

Get started

One-on-one

Status, plan, result.

Every conversation follows the same rhythm. Your team member knows they were heard. You get something you can act on. You both know what the next one is about.

Status

What your team member wants to raise and what you want to discuss.

Plan

What exactly you are doing and who takes responsibility for it.

Result

What the plan is expected to deliver and how you will know it worked.

Open points come back to the next conversation.

Who Flaber is for

Leading a small team? Time to stop hunting for information.

Documents and team work

Your team's knowledge base

Procedures, lists and agreements in one place — together with links to external company documents.

A shared space

Your team works in the same workspace as you. You share documents both ways, and you see at once what came in and from whom — without digging through your inbox.

Onboarding a new person

Bringing someone in stops being a recall exercise. You launch the template with one click, and the full set of files and references is already in place.

One-on-ones

A steady rhythm

You run meetings with your people on one pattern: Status — Plan — Result.

Agreements carry over

Open threads move to the next meeting, so you start from what you agreed on earlier, not from a blank page.

Achievements

A separate place to flag what deserves to stand out in the report.

What you won't find

Start running your team
from one place.

An account for you and your whole team.

Get startedLog in