Some threads run for days.MariMarikeeps every one alive.

Mari waits, nudges and tracks at a human pace. Every promise, yours and theirs, is held and surfaced before it falls due.

Mari stretching a coral thread between two distant days on a weekly calendar wall
An unhurried thread

Eight days later, she picks up exactly where it left off.

A task does not have to fit in one conversation. Mari sends, waits, and remembers. A reply at 11pm on Thursday is exactly the same to her as a reply ten minutes after she sent. She holds the full thread state, what the goal was, what she already said, who is owed what, and resumes the moment the other person responds, even if that is next week. Nothing cools off because she got distracted.

How she plans the work
Mari filing a paper promise card into a tickler-file slot labelled Wednesday
Every promise tracked

'I'll send it Wednesday' is now her job, not your memory.

When someone says 'I'll get back to you Friday' or 'send me the contract tomorrow', Mari hears it as a commitment and files it as its own thing: the owner, the date, the topic, the thread it lives in. Wednesday rolls around at noon, she nudges politely; the contract still has not landed by Tuesday 4pm, she pings the right person in the soft language that suits how well you know them. Your inbox never has to remember.

Mari calmly holding out an approval card with three labelled options
Before anything real moves

When the stakes are real, she checks in first.

Mari knows the difference between sending the deck and sending the offer. Routine acks go without bothering you. But when a contact asks for a price, a signature, a refund, a discount, or anything that touches your money or your name, she pauses and surfaces three choices in a single tap: approve, edit the wording, decline. She never moves until you tap one. No 'oops, I sent that' moments.

How she stays in bounds
Mari holding a single contact card with five channel badges connecting to one name
One human, not five accounts

Her Telegram, her WhatsApp, the work email — one person, one record.

People do not live in one app, and Mari does not pretend they do. She quietly merges the same human across their Telegram handle, their WhatsApp number, their email, their Slack DM, into a single contact with one shared history, one set of known facts, one running tone. You ask 'what did Lena say about the contract', and Mari pulls the answer whether Lena said it on Telegram in March or in an email last week.

How she remembers them
One continuous coral thread flowing through WhatsApp, Telegram and Gmail icon stands on Mari's desk
The conversation does not reset

Someone switches apps mid-thread. Mari does not even pause.

A client writes you on WhatsApp, you reply by email, they answer on Telegram. To them it is three apps. To Mari it is one ongoing conversation. The brief stays intact, the next reply lands with full context: what was said three apps ago, what was promised, where you left off. No 'sorry, can you remind me what we discussed' anywhere in your life again.

Mari at a wall of analog world clocks for San Francisco, New York, London, Dubai and Tokyo
She knows what hour it is for them

No 'are we still on for Tuesday?' at 2:47am their time.

Mari holds the right timezone for every contact. Nudges land in their working hours, not in the middle of someone's sleep. Public holidays in their country are respected. She knows a Friday-evening message reads differently from a Monday-morning one, and lands hers accordingly. The result reads as thoughtful, not robotic.

How it actually unfolds

The shape of a single follow-up, end to end.

Every follow-up Mari runs goes through the same six beats. You only see the ones that need you. The rest she carries quietly.

Mari in front of a follow-up flow board with six numbered steps from Capture through Close
Mission · One follow-up6 beats, two weeks
Day 0

Capture

The promise is heard mid-conversation. Owner, date, topic and the thread it lives in are filed as one record.

Day 0

Wait, with state

The full thread context is held. Mari does not forget what was already said, who was copied in, what the goal was.

Day 3

First nudge, on time

A polite reminder, drafted in the relationship's tone, sent in their working hours and respecting their public holidays.

Day 6

A softer one, if needed

Three days later, gentler, with a small out for them ('totally understand if it slipped'). Never two messages in 24 hours.

Day 10

Escalate to you, if it is stuck

A 1-2-3 card lands in your tray: keep waiting, message them directly, drop the thread cleanly. You tap once.

Day N

Close cleanly when it lands

When the reply finally comes, the thread closes itself, the promise is marked done, and the next step is taken.

She matches the temperature

The way she writes back depends on who she's writing to.

Mari watches the relationship over time. A new prospect gets a warmer, slightly more careful tone. A founder you have worked with for two years gets shorter, sharper sentences. Your sister gets emoji. You never have to brief her: she calibrates from the history.

Mari calibrating a brass tone dial labelled crisp, warm, playful and formal
Relationship age

A first-week contact gets fuller sentences and a touch more formality. A five-year friend gets fewer words.

Reply pace

If they always answer in five lines, she answers in five. If they reply with two words, she stays brief.

Formality match

If they sign off 'best' or 'cheers', she does too. If they use emoji, she will, once she has seen them do it.

The mood of the thread

If the thread has gone tense, the next nudge is gentler. If it is warm, she leans in. She reads the room.

The tricky parts, handled

Every weird shape a real conversation actually takes.

Real human threads do not behave like a happy path. Mari is built for the eight situations that break every other tool.

Three people on one thread

A group chat where two of them owe you different things. Mari tracks each promise to its owner and nudges them separately.

The 'yes-ish' reply

Someone says 'sounds good, will confirm tomorrow'. Mari treats it as a soft yes and re-checks tomorrow, not now.

The angry reply

A response comes in upset. Mari pauses any scheduled nudges on that thread and surfaces it to you instead, with the full context.

Reply in a different language

They write back in Russian when the conversation was in English. Mari reads it, translates, and answers in their language if you set that up.

Forwarded to my assistant

They hand it off to someone else. Mari recognises the new person, opens their contact, and continues the thread there.

The double-send

They answer twice in quick succession. Mari treats it as one combined intent and replies once, not twice.

The auto-reply

Out-of-office or 'on a flight'. Mari recognises it, does not push, and waits until the OOO window closes.

Gone quiet for months

Three months of silence on a thread. Mari archives cleanly, surfaces a one-line summary in your weekly digest.

The receipts

Every nudge, every wait, every approval, written down.

Mari never sends a message without a record. The full log is yours to open: what she said, when she said it, who she said it to, why she said it (the promise it was tied to, the timer that fired), and whether it got a reply. If anything ever looks off, you can rewind the whole thread back to its original signal.

Mari at a tall open ledger book with neat handwritten log entries
  • Every outgoing message linked back to the promise that triggered it
  • Every wait timer visible with its open and close timestamps
  • Every approval gate logged with the option you actually picked
  • Every nudge attempt plus the cooling-off period before the next
  • Filter the whole log by contact, by date, by promise or by channel

Hand her the thread. Get your inbox back.

Connect Mari to your chats in five minutes. Your first $10 in credits are on us, enough to run a real first week of follow-ups.

Mari at her operations console in the evening while the user has closed their laptop for the day