Updates live in threads
Slack and Teams keep every message. None of them tell you what changed since yesterday, in one glance.
Early launch · Every feature free · No credit card
One 60-second check-in becomes a calm morning brief: what changed, what is stuck, who needs you, and what needs a decision. For teams of people and their AI agents. No AI summaries. No scores.
Good morning
Here's what matters today.
Changed
5
Blocked
2
Needs you
3
Needs you
Sarah
Needs your input on the checkout redesign
Which database for app data?
Claude Code · recommends PostgreSQL
What changed
Launch moved · Monday → Friday
Compared with yesterday's check-in
PostgreSQL ratified. SQLite ruled out.
Reason recorded
Your morning brief. One calm screen instead of five apps.
The gap
It is Monday, 9:04. Messages, meetings, tickets and now agents all hold a piece of the truth. Nobody holds the whole thing. So you ask around, and the answer is old by the time it arrives.
And still no single answer to what matters today?
Slack and Teams keep every message. None of them tell you what changed since yesterday, in one glance.
The call ends and the picture is already old. You stitch blockers together from memory.
A board knows the ticket. It does not show who needs you, who is stuck, or how the team feels today.
An @mention scrolls away with the thread. Nothing keeps it open until a person handles it.
Your agents do real work. Teammates often have no idea what was done, or whether anyone checked it.
Weeks later nobody remembers why. People and agents decide the same thing again.
The answer
Tynbo turns small daily signals into one brief. Open Today. If nothing needs the team, you do not need the meeting.
Decisions, focus shifts and finished work since yesterday.
Blockers, with how long they have been open.
Explicit requests that are still waiting on someone.
Proposals and questions waiting on you, with the reason attached.
Every brief also says how many people checked in, so a quiet team is never mistaken for a healthy one.
How it works
Four steps. No AI, no task boards, no extra meetings.
Share what happened: yesterday, today, blocked, what is new. Agents can report too.
Weekly focus, explicit requests and team context stay alive over time.
See what moved: focus shifts, new blockers, decisions made.
Open Today. Needs you, blockers, decisions and changes in one calm brief.
What a check-in looks like
Four fields. Optional mood.
Optional, any time
A decision I made, and why.
Work my agent did.
A day with Tynbo
This is the whole product, in the order it actually happens.
Yesterday, today, blocked, what is new. Optionally a mood. That is the only thing Tynbo ever asks of her.
Alex has been blocked for 3 days. Sara asked you for a review. The launch date moved from Monday to Friday. Nothing is lost between standups.
What changed, what we are worried about, where we need help, what needs a decision. Two minutes later you know whether you need the meeting at all.
“Which database?” arrives with options and a recommendation. You tap Ratify on your phone. SQLite is recorded as ruled out, with your reason.
A digest for managers lands by web, email or Slack: counts and changes, with every number traced to something recorded.
Everything in Tynbo
Each part exists to answer one thing: what matters today? Here is all of it.
The only daily input. Once a week you can also record a decision and its reason, or work your agent did.
Mood is optional. Nothing else is required.
One calm screen, in the order that matters, instead of five apps.
An explicit @mention or follow-up stays on Today until it is resolved, with the reason it needs you.
Because Sarah mentioned you
What is stuck, who is stuck, and for how many days, from real check-in history.
3 days blocked
Focus shifts, new blockers and moved dates, compared from real check-ins.
Launch Monday → Friday
Who checked in, every blocker with the person behind it, and an optional shared mood that only shows when people choose to share. Never a score.
Today’s three priorities, scratchpad, habits and bookmarks. Private until you decide to share something in a check-in.
Scope, reason, ruled-out options, history and review dates. Export to DECISIONS.md any time.
Agents post short updates, or you enter their work by hand. Always labelled, never shown as verified.
Decisions, why they were made, and what changed, in one view. Team-level counts only, no rankings.
Managers pin an announcement to the top of everyone’s brief, instead of broadcasting into a channel that scrolls away.
One weekly focus gives everyone enough context to see where the team is heading, without turning Tynbo into project management.
No summary model and no invented urgency. Every line traces back to something a person or an agent actually recorded.
And everything around it
Agents & decisions
Your agents check in too. When one needs a project decision, you answer once and confirm it. Every later session starts from your answer.
“Which database?” arrives with options and its recommendation.
One tap on your phone or computer. The other option is recorded as ruled out, with your reason.
A later session gets your confirmed answer, with its scope and review date.
Labels you can trust
An agent’s suggestion stays “Proposed” until a person confirms it. Agent work is never shown as verified. Tynbo makes your answer available to agents; it cannot control what they do.
// Claude Code, Cursor or any MCP client
create_question("Which database?")
→ waits for a person
get_decisions("database")
Ratified: PostgreSQL. SQLite ruled out.
report_work("Billing screen ready for review")
Why Tynbo
What changed, who is stuck, what was decided. No boards, no sprints, no productivity scores, no rankings, no status meeting unless the brief says you need one.
Not another task manager
Tynbo is not here to manage your team’s work. It is here to help everyone understand it.
Explainability
Tynbo does not guess what is important. Every line on your brief comes from an actual team signal, and says so.
Sarah needs your review
Because Sarah explicitly mentioned you.
API integration · Blocked 3 days
From real check-in history, not a guess.
Launch moved · Monday → Friday
Compared with yesterday’s check-in.
Use PostgreSQL · Ratified by Maria
Reason recorded. SQLite recorded as ruled out.
Who it is for
Team members
A 60-second check-in replaces repeating yourself in threads, calls and DMs.
Managers
One brief and a weekly digest. Skip the meeting when nothing needs the team.
Founders
Decisions, with why and what was ruled out, survive the next reorg, hire or tool change.
Agents
Check what is already decided, raise a question, report work. Always labelled.
Pricing
Everything is free during early launch. Paid plans will stay per person and predictable.
When paid plans launch
Full product. No feature gates.
Teams with 6 or more people. Agents are not paid seats.
No credit card · Paid plans come later, still per person
Trust
Built for small teams who want awareness, not surveillance.
The team only sees what people choose to check in.
A roll-up appears only when people share. Never a score.
No email scraping. No training on your data. Tynbo does not read your code.
Export or delete your data any time. Decisions export to DECISIONS.md.
FAQ
Under a minute, once a day. You write four short fields: yesterday, today, blocked, and what is new. Mood is optional. That is the only input Tynbo asks for.
Neither. There are no boards, sprints, scores or rankings. Tynbo turns small daily signals into one brief so everyone understands what matters today.
No. Tynbo uses real records and plain rules. Every line you see maps to something a person or an agent actually recorded. There is no AI-written summary, no fuzzy matching and no score for any person.
A decision an owner or admin has confirmed. Members can record a decision, and it waits as proposed until someone with authority ratifies it. Ratified decisions can later be superseded or retired, and they are flagged for review after a date you choose.
Yes, through a project token and an MCP connection. Agents can ask whether something is already decided, ask a new question, read ratified decisions and report their work. They have no login, never see check-ins, moods or personal notes, and anything they propose waits for a person.
No, and Tynbo says so. Agent work is always labelled Agent-reported, or Agent work entered by a named teammate. It is never shown as verified.
Everyone on the team can read them. A share link lets you show decisions only, from a period you choose, to someone outside the team. You can turn a link off at any time, and it expires on its own.
No. Decisions and agent connections are part of the same plan. Agents are not paid seats.
Create a team, invite a few people, check in once. Five minutes, and tomorrow starts clearer.
Free during early launch · No credit card