People, by evidence
Search the directory the way you'd ask a colleague, plus 1:1 prep built from someone's last few weeks.
Solutions · For your team
Nobody chases status. Answering the brief does the work.
Status-chasing, standup meetings, calendar herding. Avna takes them over, and the brief turns up where the team already is — in Telegram, before anyone opens a dashboard.
Avna
Telegram · team workspace
DAILY BRIEF: TODAY
2 meetings: standup at 10:00. "Ship deck" is overdue; Sara is waiting on it.
✓ Ship deck↦ Tomorrow
push the deck task to friday
Done: "Ship deck" moved to Fri 17:00.
✓ task moved⟳ Jira DEV-214 updated
Connects to
- Telegram
- Jira
- Google Calendar
- Chrome extension
- GitLab (read-only)
- A brief lands when each person starts work
- Standups happen in chat, and you get the digest
- Reply to move a task, nudge someone or book a slot, and Jira follows
- One task board, fed by minutes, Jira and the assistant
A rhythm, not a routine you run
The cadence runs on its own. You see only the parts that need you.
- A standup question 30 minutes into each person's day, answered in chat
- Your digest three hours later, including who has not answered
- Rollups flag what is at risk, overloaded, unassigned or undated
- A weekly review drafted for each person and each team
Your people
Walk into the one-to-one already knowing
Who has what today, in their own words. Open a row and the 1:1 is already written.
- Every 1:1 arrives pre-written from their tasks and meetings
- The check-in is their own sentence, not a status guessed for them
- Flags are rare, and each one says exactly why
- Book the 30 minutes, or have the prep sent to you on Telegram
Who has what todayLoad and check-in, per person, with the six weeks behind today's bar.
“Wallet load tests are running. Blocked on the staging DB until someone re-seeds it.”
Above 85% for five weeks running, and rising.
Last 1:1 was 5 weeks ago
SHIPPED SINCE LAST TIME
- Payment webhook retries: shipped Tuesday
- Wallet top-up load test harness: shipped last Thursday
STUCK ON
- Staging DB re-seed: waiting on infra for 6 days
- Billing v2 QA window: overdue by 2 days
YOU AGREED LAST TIME
- She would hand the on-call rota to Omid after the flag ships
- You would find her a second reviewer for payments work
WORTH ASKING
- The on-call handover has not moved since you agreed it
- Four of her nine open items are other people's blockers
Book 30 minutesSend me this as a note
“Webhook is wired. Writing the migration notes today, nothing blocking.”
Last 1:1 was 2 weeks ago
SHIPPED SINCE LAST TIME
- Payment webhook: shipped Monday
- Crypto checkout block watcher: shipped a fortnight ago
STUCK ON
- Nothing overdue
- One item waiting on Sara's staging re-seed
YOU AGREED LAST TIME
- He would write up the migration for whoever picks it up next
- You would stop adding to his week without moving something out
WORTH ASKING
- He has taken on two of Sara's items this month without being asked
- He has not booked leave since Farvardin
Book 30 minutesSend me this as a note
No check-in today.
There has not been a 1:1 yet
SHIPPED SINCE LAST TIME
- In-app purchase flow: shipped three weeks ago
- Nothing closed in the last two weeks
STUCK ON
- Nothing overdue, and nothing waiting on him
- Two open items, both due next month
YOU AGREED LAST TIME
- Nothing agreed yet: this would be the first one
- He joined six weeks ago
WORTH ASKING
- His load has fallen every week for a month
- He is the person Sara's on-call rota was going to move to
Book 30 minutesSend me this as a note
Ask your workspace. It acts.
Who knows Kubernetes? Who owns billing? Ask. Avna searches profiles and calendars, proposes the slot, and books it.
The rest of running a team
Scheduling on real calendars
Google Calendar free/busy across attendees, the one slot that works, proposed and booked.
A Today screen
Your brief, calendar and waiting-on-you queue, plus a tab per team with load and six weeks of check-ins.
New hires, without the shadowing
The assistant answers week-one questions from your knowledge; whatever it can't answer becomes knowledge.
Where work already lives
Google Calendar, Telegram, two-way Jira sync, and GitLab activity feeding who-knows-what.
One wallet, guardrails on
Credits in one balance with a runway estimate, low-credit warnings and caps per assistant. Customers keep getting answers first.
Less chasing, more shipping
Free to start, no card · Telegram, Jira, Google Calendar · what we keep and throw away →