Some work has no end.
Marikeeps it running.
Hand Mari a brief that lives weeks. She picks her own moments, runs it untended, and surfaces only what truly needs you.
Not a task that closes. A brief that stays alive until you say done.
Some work doesn't fit in one task. 'Keep my Upwork pipeline full' or 'sell my apartment on eBay' isn't a single ask, it's a standing brief: a goal, a policy, a budget, the accounts she runs it through, and the durable memory of every thread inside it. You hand it over once. She lives with it for as long as it takes, picking her own moments to act and her own moments to ask you.
Mission holds the brief. Thread holds the relationship. Task does the work.
A mission lives for months. Inside it, every active conversation with one customer is a thread, lasting days, holding the negotiation state (what was offered, what was wanted, where things stand). Inside each thread, an ephemeral task runs the immediate job (read the message, draft the reply, hit submit). Threads survive task restarts. Missions survive thread closures. Each layer remembers what the one below it can't.
She ticks on her own. She also reacts the moment something happens.
A discovery tick fires every couple of hours: cheap HTTP fetch of a marketplace feed, a deterministic dedup against what she's already seen, then a fast classifier on whatever is genuinely new. Nothing else. A reactive listener wakes the moment a customer writes — Mari's Gmail subscription pushes the message in, the right thread resumes with full context, the agent reads and answers. Idle ticks are quiet and cheap. Real events get attention the second they happen.
If one thread needs you, the other twelve keep moving.
When Mari needs your call on a single thread (a non-standard price, a question only you can answer), only that thread enters 'awaiting owner'. The mission as a whole keeps working: discovery still ticks, new threads still open, other negotiations still progress. Your one decision unfreezes one thread, never the whole brief. So you can be away for days without missing what actually moved.
Inside the policy she acts. Outside it she asks. The line is yours to set.
Every mission carries a policy: minimum price, working categories, response tone, working hours, escalation rules. Everything inside the policy Mari handles autonomously, in your voice, at the pace the conversation needs. Anything that lands outside (a low-ball offer, an unfamiliar question, an unusual request) gets a clean Telegram card with three options and waits for your tap. The boundary is a setting, not a guess.
Cost scales with events, not with calendar time.
A standing mission that's quiet today costs you roughly zero: the discovery tick is HTTP plus a cheap classifier, the reactive listener is free until a message arrives. Cost only shows up when she actually drafts a reply, books a slot, or submits an action. An active mission on Upwork is usually around two dollars a day. A quiet one is around thirty cents. One winning lead repays the month many times over.
The same six beats, ticking quietly until something real happens.
Every mission Mari runs cycles through the same six beats. Most beats are pennies-cheap; the meaningful spend only fires when there's actually meaningful work to do.
Tick
The discovery loop pulls the marketplace feed (HTTP, no browser, no model). Nothing else. Pennies-cheap by design.
Dedup + classify
Already-seen items are dropped against an internal seen-list. Only the genuinely new go through a fast classifier scoring relevance to your policy.
Spawn task
When a real match shows up, Mari opens a thread for that lead and spawns one task: draft an outreach in your voice with the right angle.
Decide together
If the policy is 'agent assisted', you see the draft and tap to send. If it's 'agent autonomous' inside policy, she sends it on her own and tells you after.
Wait, with state
Once sent, the task installs a watch on the thread and goes quiet. No polling, no spend. The customer's reply will wake the right thread by itself.
Resume on the moment it happens
An incoming message via Gmail push or platform webhook resumes the thread within seconds, with full negotiation state and full task history intact.
Six standing missions, all running quietly today.
The shape is always the same: a clear brief, a policy you set, accounts she runs it through, a budget cap. The work inside it changes every day, the brief doesn't.
Upwork lead pipeline
Find suitable orders, draft outreach, negotiate to a close, hand over the win.
eBay sale
List the item, talk to interested buyers, handle the price negotiation, get to a closed sale.
Rental portfolio
Watch tenant chats, route maintenance vendors, chase rent on time, renew Ejaris.
Weekly investor digest
Pull this week's portfolio progress, draft the one-pager, send for your sign-off Friday morning.
Always-on inbound lead
Watch the contact form on your website, qualify each lead instantly, book the discovery call.
Hiring funnel
Source senior backend candidates, draft personal outreach, book screens, keep the funnel sheet alive.
Six everyday moments inside a standing mission.
Real missions are not happy-path slideshows. These are the real shapes Mari handles, from the cheapest day to the one where she stops and asks you.
Happy path · found and won
New order matches the policy. Mari drafts in your voice, you tap send, customer replies, negotiation settles inside policy, you approve the final price, thread closes 'won'.
Empty tick · the cheap day
Tick pulls 40 listings, 39 already seen, 1 new but scored below the relevance threshold for your policy. Skipped, marked seen, no model call, no browser, less than a penny.
Mari doesn't know the answer
Customer asks for portfolio samples. Mari has none in mission state. She doesn't invent; the thread enters 'awaiting owner' with one clean question to you. The rest of the mission keeps moving.
Below the price floor
Buyer counters at well below your floor. Mari pauses the thread, sends you a card with three options: hold, accept, counter at your number. One tap, she sends.
Session expired mid-action
On submit, the platform redirects to login. Mari detects it, freezes the action, sends you a one-tap relogin link to her cloud browser. You sign in once, the cookies persist, the action resumes.
Budget cap reached
Mission hits its daily spend cap. Discovery keeps ticking (it's pennies), but new replies queue until tomorrow. You get a Telegram heads-up with a one-tap 'raise the cap' option.
A standing mission still has a fence. Six lines she never crosses.
The mission gives her autonomy. The policy gives her a boundary. The boundary is short, fixed, and enforced in the planner prompt itself.
- She never accepts an order, signs a contract, or commits you to a deal outside your policy without your tap
- She never sends a price below your floor, even if the buyer pushes — she escalates instead
- She never shares your phone, address or contact details to a customer without your explicit approval
- She never lets one thread's escalation freeze the whole mission — only that thread pauses
- She never drains your budget silently — the per-mission cap throttles outbound work and pings you
- She never invents an answer she doesn't know — she asks you, in clear words, and waits
A mission threads through every other feature.
Missions are the long shape that holds everything else together. Follow any thread.
Hand her your first standing mission.
Connect Mari in five minutes and give her one brief that lives for as long as you do. Your first $10 in credits are on us, enough to run a real first week of a mission.
