New project. Fieldnote: voice notes from the field that turn into data a lab can search the same day. Deck attached.
fieldnote-deck.pdfFirst email (cold outreach)
Rewritten as you asked, and remembered for next time. It still waits for your yes.
I remember every project, do the research, outreach, posts and inbox, hand the making to your other agents, and ask before anything goes out.
Home is where you talk to me, with whatever needs you beside the chat. Review holds everything waiting for your yes. Activity shows what I'm doing, what I did and what's next. Every project gets a page of its own.
No forms. Say "new project", paste links, drop the deck. I build a memory of it, ask the one question that matters, research, and come back with a plan you approve.
New project. Fieldnote: voice notes from the field that turn into data a lab can search the same day. Deck attached.
fieldnote-deck.pdfGot it, and saved. One question before I plan: who pays, the researcher or the lab?
The lab. Researchers are the users.
Then labs are the market. I saved that as a decision, with why. Here's a plan with three ways in:
Pilot first
Five labs on a free spring pilot, then grants with their letters behind us.
Grants first
Three research-tool grants close before June. Apply, then recruit labs.
Content first
A weekly field-methods post to build a list before asking anyone.
This is what usually eats the week. Once you approve a plan I work through it on a schedule, and each thing ends up in one of four places. Only one of them needs you.
My logo isn't decoration. Each petal is one thing I do, and you'll see them all over the app, so you always know what kind of thing you're looking at.
Facts, decisions with their reasons, how you like things written. Everything I do starts from it.

Approve a plan and it runs on a schedule: checking deadlines, watching the market, finding leads, investors and grants, drafting posts and emails, reading replies, booking calls.

I write. For images, video, audio and code I file a task instead, and Claude Code, Codex or any MCP client you sign in picks it up, makes it, and hands it back for your review.
$ claude mcp add --transport http \ --scope user metsys https://your-metsys/mcp $ claude mcp login metsys
You sign each one in yourself, on a page that says what it can and can't do. It can claim tasks and hand in work. It can't approve, send, publish or read your inbox.

Every email, reply, booking and post waits as a card that shows exactly what will be sent. Say yes, say no, or tell me what to change. Go on, press it.
First email (cold outreach)
Rewritten as you asked, and remembered for next time. It still waits for your yes.
Everything that reaches a person asks first, until you say otherwise. One action at a time, and per project if you like.
When the last ten of an action all went out exactly as I wrote them, with no edits and no undos, I'll offer to do that one on my own.
Offer. Nothing changes a policy by itself.
Writing to someone new
Answering in a thread you already have
A Meet invite in one of your free slots
Through the publish webhook you set up
Or just tell me what I got wrong. I fix what I can, and I send nothing while I do.
Found 6 pre-seed investors who back research tools, and 2 firms behind them. Drafted first emails to the two best fits.
Undo this run?
All of it or none of it. It reaches nobody.
You said: “”. Fixing what it can.
Fixed. Marked 2 people as not a fit and discarded the email to one of them. Nothing was sent.
Undone. Removed 6 contacts and 2 organisations, and rejected 2 emails that were waiting. The conversation still says what it did. Only the data went back.
Not unless you tell it to, one action at a time. By default every first email, reply, booking and post waits for your yes, and after yes you still have ten seconds to undo.
No. It keeps mail from people it already knows and from threads it is part of. The rest of your mailbox is never read into metsys.
It drafts posts for X, LinkedIn, Instagram, Reddit and your blog. You copy them, or connect a publish webhook (Zapier, Make, Buffer or n8n) and approved posts go out through it, under your policy.
Not itself. It writes the brief and files a task, an agent you connected does the making, and you approve the result before anything uses it.
A task's brief and the project notes it needs. They can claim tasks and hand in work. They can't approve, send, publish or read your inbox, and you can disconnect them at any time.
If you want it to ping you, give it one address you own (Slack, Discord, ntfy and the like). It sends counts and project names, never an email body or a recipient, and bunches a burst into one message.
metsys is in closed beta while we get it right with a few builders. Tell me about your project and we'll let you in as places open.
Thank you. We read every request and will write to the address you gave us when a place opens.