early access, android

your inbox is a to-do list you never agreed to.

SayDo pulls the action and the date out of the message, asks you once, then puts it where it belongs. On your phone. No account. No cloud.

one email when the first build is ready. no spam. reply to that email to be removed.

on-device by default no account required you confirm every action
message from mihai example

“hey, can you call the dentist about tuesday and send the invoice by friday? also i should book the train.”

3 actions found
  • call the dentisttue
  • send the invoicefri
  • book the trainno date
confirm all

nothing is saved until you say yes.

the actual loop: capture, extract, confirm.

the six-second version

capture first. decide later.

The thought is already in a message. SayDo starts there, instead of asking you to open another app and type it again.

01

paste it, say it, share it

An email, a voice note, a message to yourself. No new inbox, no new habit to build.

02

it finds the commitment

An on-device model pulls out the action and the date. Ambiguous bits go to you, not into your calendar.

03

you approve the result

One confirm screen. The action lands in your list or your calendar. No chat, no feed, no assistant voice.

the honest comparison

better than another place to put the thing.

SayDo is not a better task manager. It is the step before one. Here is the difference that matters.

notes app

stores the sentence.

You still have to reread it, find the action and retype it somewhere useful.

reminders

great once the task exists.

But it cannot hear the commitment in a message. You have to do the extraction in your head first.

ai chat

summarizes in the cloud.

You paste, read, copy and paste again. The result is a conversation, not an action in your day.

saydo

turns the message into a decision.

Extracts the action and date, shows its work, and waits for your yes. On-device, with no account.

No cloud round trip. No second inbox. No “assistant” to talk to.

the parts that are not magic

what SayDo does not do.

it is android first.

iPhone is next, but not today. The first build is Android.

the model is small.

It runs on your phone, which is the point. It will miss an ambiguous sentence. That is why nothing saves without your confirmation.

it does not read your inbox.

You choose what to paste, share or say. SayDo does not get background access to your mail.

it is not a team tool.

No shared workspaces, no cloud sync, no integrations in the first version. It is a personal capture layer.

no account means no cloud restore.

Your data stays on the device. Backup is a file you control, not a server you hope is safe.

the fair question

“can’t I just ask chatgpt?”

You can. It will happily summarise the message. And then it will be trained on that. Then you will copy the summary into a task app, or forget it.

Consumer ChatGPT, default settings. SayDo does not train on your messages.

SayDo is not trying to be a better conversation. It removes the copy and paste between the message and the calendar.

The output is not a paragraph. It is an action with a date, waiting for a yes.

fair questions

the things you would ask before signing up.

where does my data go?

Capture and extraction happen on the device. There is no account and no cloud upload in the first build. You can export a backup file you control.

what happens when it gets something wrong?

It shows you the action and the date before saving. You can edit, confirm or dismiss it. An uncertain parse is a prompt, not a silent calendar entry.

does it work offline?

Yes. The model and the queue are on the phone. Network access is not part of the core capture loop.

is this another chat app?

No. There is no conversation to maintain. You share a message, approve the result and go back to what you were doing.

when is the iphone version coming?

After the Android foundation is stable. The waitlist will get the Android build first, and I will say plainly when iOS is ready rather than promise a date now.

why this exists

SayDo started as a small experiment: can a phone pull the commitment out of a message without sending the message to a server? The answer is yes, if the model stays small and the human stays in charge.

built by one person. no growth team, no data business.

the list

get the thing out of your head.

The first build goes to this list. I will ask what you want it to catch, because the product should fit the way you already write things down.

join the early access list