chronoflowbeta
Invite-only beta · waitlist gets priority access

Your calendar, email, and tasks finally talk to each other.

ChronoFlow connects your inbox, calendar, and tickets for software engineers. AI extracts action items with due dates. You see your whole day in one workspace — not five tabs.

  • Free full beta — no credit card
  • Priority onboarding for waitlist members
  • Locked-in pricing when paid tiers launch
dashboard · chronoflow
Today · Tue Mar 12

  • Standup

    9:00 – 9:15 AM · Meeting

  • Auth refactor — deep work

    9:30 – 11:00 AM · Focus block

  • 1:1 with Sarah

    2:00 – 2:30 PM · Meeting

Focus · running
42:18of 90:00

This week

14h

Streak

6 days

Avg/day

2.1h

Tasks5 todo · 3 in progress · 12 done
  • Review PR #812 — token refreshgithub
  • Reply to client about API delaygmail
  • ENG-1284 — login timeout on Safarijira
Inbox · 24 unread
  • Alex Rivera— Re: Q2 roadmap review
  • GitHub— Pull request review requested: api#812
  • Sarah Chen— Notes from architecture sync

You complete 40% more tasks on days with fewer than 3 meetings.

Why this exists

Every engineer reading this knows the pattern. It's not that you're disorganized. It's that work shows up in one tool and the action needs to happen in a different one.

I kept missing tasks — not because I wasn't trying. A review request would land in Teams, a deadline would hide in email, a ticket would get assigned in Jira. Each lived in a different app, and nothing connected them. I built ChronoFlow to fix that.

Slack

A PR review request lands at 4pm.

You'll do it after lunch tomorrow. You don't.

Gmail

A client deadline is buried mid-thread.

You see it on Friday. The deadline was Thursday.

Jira

A ticket gets assigned to you in standup.

You never open Jira that day. It's still 'To Do' next sprint.

Google Calendar

A meeting drops on top of your focus block.

Your deep-work morning is gone before you notice.

ChronoFlow lives in those gaps.

See the workflow

One Tuesday. Four tools. Zero dropped balls.

This is the loop ChronoFlow is built around — work arrives scattered, action happens in one place.

  1. 9:02am

    Standup assigns you a Jira ticket.

    It lands on your ChronoFlow task board with priority and a link back to the issue.

  2. 11:14am

    A client deadline hides mid-thread in Gmail.

    AI extracts it — due Thursday, P1 — without you re-reading the whole chain.

  3. 1:45pm

    Your manager pings you on Teams about a PR review.

    The action item syncs alongside your email and Jira tasks in one list.

  4. 4:00pm

    You block 90 minutes before tomorrow's deadline.

    A focus block hits your calendar, marked busy so meetings can't overlap it.

How it works

Three steps. No new habits.

Use the tools you already pay for. ChronoFlow is the workspace that ties them together.

Step 01

Connect your accounts

One-click OAuth for Google, Microsoft, and Jira. Your data goes directly from each provider — no admin ticket, no rip-and-replace.

Step 02

AI extracts your tasks

Gemini reads Gmail, Outlook, and Teams in batches and pulls out action items with priority and due dates. Noise stays out of your task board.

Step 03

Plan and ship your day

One view for tasks, calendar, focus blocks, and team scheduling. Ask ChronoFlow to draft replies, create tickets, or find time with your team.

What's shipped

From inbox to ticket to calendar — without leaving the workspace.

The AI that reads your inbox is the centerpiece. Everything else exists because action items alone don't help if your calendar, tasks, and team chat live in different worlds.

AI task extraction · the headline feature

Stop hand-scanning your inbox for action items.

ChronoFlow reads your Gmail, Outlook, and Teams messages in batches and uses Gemini to pull out the things you actually have to do. Newsletters, marketing, and CI notifications get filtered out. Confidence scoring means only real action items make it through to your task board — with priority and due date inferred from the message itself.

  • Batched LLM calls — no rate-limit failures on a 200-email morning
  • Filters out newsletters, promotions, GitHub notification noise
  • Priority and due date inferred from the message itself
  • Source link back to the original thread on every task
ai task extraction

Inbox

Alex Rivera · 9:42 AM

Re: Q2 roadmap review

Can you review the staging deploy doc by Friday? Also need an LGTM on the rollback plan.

Maya Patel · Yesterday

Launch checklist v3

Two open items — file the analytics ticket and confirm the customer announcement copy.

extract

Tasks created

Review staging deploy doc

gmailhigh · due Fri92%

LGTM on rollback plan

gmailmedium · due Fri84%

File analytics ticket

outlookmedium · due Wed78%

Ask ChronoFlow

Type what you need. It happens across your tools.

When clicking through the UI isn't the fastest way, just type. "Draft a reply telling Sarah Thursday at 2 works." "Create a P1 Jira ticket for the login timeout." "What did I miss today?" ChronoFlow runs the action in the right tool with the right context — pulling the email thread, the assignee, or the ticket history so you don't have to. Every write action confirms before it goes out.

  • Drafts email replies using the original thread for context
  • Creates Jira tickets with priority and assignee inferred
  • Summarizes unread mentions, new assignments, pending reviews
  • Confirms before sending or writing — you stay in control
ask chronoflow
Create a P1 Jira ticket for the login timeout on Safari, and reply to Alex saying I'll review the rollback plan by Friday.

On it. Filing the ticket and drafting the reply now — both will ask for confirmation before they go out.

Jira · ticket createddone
ENG-1284Login times out on Safari after 60s idle
P1 · highassigned to yousprint 24
Gmail · draft readyawaiting send

To: alex@acme.dev · Re: Q2 roadmap review

Hey Alex — taking a look now, I'll have feedback on the rollback plan by Friday EOD. Flagging anything blocking before then.

SendEdit
Ask anything — schedule, draft, summarize, file a ticket…

Team scheduling

Find time without the back-and-forth.

Pull up your teammates' availability across Microsoft Teams, find a common open slot in seconds, and create the meeting in place. No more "what time works for everyone" email chains. Free/busy only — nobody's actual events get exposed.

  • Multi-person availability across the week
  • Common-slot detection across selected teammates
  • Create the meeting from the same UI
team scheduling · Thursday
4 teammates · find a 30 min slot
9 AM — 6 PM
911135
You
Alex Rivera
Sarah Chen
Maya Patel
Everyone free · 11:00 AM – 12:00 PM
Schedule

Smart calendar

A calendar that knows what's movable.

Google Calendar and Outlook synced via incremental sync — changes show up in seconds. Events are classified as meetings, focus blocks, tasks, or personal, so the system knows what it can move and what it can't. When conflicts appear, your protected time stays protected.

  • Google + Outlook calendars merged into one view
  • Event types tell the scheduler what's movable
  • Focus blocks survive the daily reshuffle
calendar · week of Mar 11
MeetingsFocus blocksTasks
Mon
Tue
Wed
Thu
Fri
9
10
11
12
1
2

Standup

Auth refactor

1:1 Sarah

Code review

Deep work

Standup + planning

API review

Migrations

Customer call

Standup

Ship checklist

Unified inbox

Gmail and Outlook, side by side.

Read, star, and triage your email without bouncing between apps. The AI extraction layer runs on top of this view — when a message has an action item, the task lands on your board with a link back to the original thread.

  • Gmail + Outlook in a single inbox view
  • Star, flag, and track without switching apps
  • Source labels keep every task traceable
mail · gmail + outlook
  • Alex RiveraRe: Q2 roadmap reviewPulled together my notes from the sync — let me know what you…9:42 AM
  • GitHubPR review requested · acme/api#812Jake asked for a review on token refresh logic. 3 files changed.9:30 AM
  • Sarah ChenNotes from architecture syncWrote up what we landed on for the auth boundary. Thoughts?Yesterday
  • StripeInvoice paid · INV-04923Your invoice for $1,200 has been processed.Yesterday
  • Maya PatelLaunch checklist v3Final pass on the checklist. Two open items I'd flag.Mon

Focus time

Deep work, on the clock.

Preset durations from 25 minutes to 4 hours, or custom. Creates a calendar block marked busy so meetings can't sneak in. Live timer, do-not-disturb signaling, and a session history so you can see your focus patterns over time.

  • Calendar-backed blocks visible to your team
  • Live timer with running session and history
  • Streaks and weekly totals to track the habit
focus · running

42:18

of 90:00

Current session

Auth refactor — deep work

Calendar block · do-not-disturb on · 47 min remaining

This week

14h 12m

Streak

6 days

Presets25m50m90m120mCustom

Analytics

See where your time actually goes.

Weekly trends, focus vs. meeting hours, task completion rates, peak productivity windows. AI-generated insights surface patterns you'd never spot yourself — like which days of the week you actually ship.

  • Focus hours vs. meeting hours, week over week
  • Task completion rates by source and priority
  • AI insights with actionable recommendations
analytics · this week

Focus vs meeting hours

15.8h focus·17.2h meetings

+12% vs last week

Mon

Tue

Wed

Thu

Fri

Tuesday and Thursday are your peak focus days. Consider blocking deep work earlier on those mornings — your completion rate is 38% higher.

Integrations

Connect what you already use.

Personal OAuth, scoped to what ChronoFlow needs. Your data goes directly from each provider — no middleman, no broker, no syncing through us.

Google

Live

Calendar · Gmail · Drive

Microsoft

Live

Outlook · Teams · Calendar

Jira

Live

Issues · sprints · sync

GitHub

Live

PRs · issues · reminders

Slack

Coming soon

Channels · DMs · mentions

Self-hosted

On roadmap

Run it on your own infra

Your data, your stack. Tokens are stored encrypted, scoped to the read/write actions ChronoFlow needs. A self-hosted deployment is on the roadmap for teams that need data to stay on their own infrastructure.

FAQ

Quick answers

Straight talk — no buzzwords.

What is ChronoFlow?

A unified workspace for software engineers. It connects Gmail, Outlook, Microsoft Teams, Google Calendar, Outlook Calendar, and Jira — then uses AI to extract action items so tasks don't get lost between apps.

Who is it for?

Individual engineers and small teams who live across email, chat, tickets, and calendar. If you've missed a task because it landed in the wrong tool, this is for you.

Is it free?

Yes during the private beta. Waitlist members get full access at no cost and locked-in pricing when paid tiers launch later.

What integrations are supported?

Google (Gmail, Calendar), Microsoft (Outlook, Teams, Calendar), Jira, and GitHub are live today. Slack is coming soon.

Do you train AI on my data?

No. AI processing runs through AWS Bedrock. Your data is not used to train models. You connect via OAuth and can disconnect at any time.

When will I get access?

We're inviting waitlist members in weekly batches. Join with your work email — we'll reach out from team@chronoflow.app when your invite is ready.

Get early access. Join the waitlist.

Invites roll out weekly. Waitlist members get priority onboarding and free beta access.

Be one of the first on the list.

  • Free full beta — no credit card
  • Priority onboarding for waitlist members
  • Locked-in pricing when paid tiers launch
No credit cardNo Claude subscriptionNo vendor lock-in