Fieldwork reads your email, chats and meeting notes every 15 minutes and keeps one task list up to date: what’s new, what changed, and who’s waiting on you. We set it up on your own server and tune it to how you work.
ALERT · TELEGRAMTHU 11:30Fieldwork· now Dana at Acme has waited a day for the revised contract.
MORNING BRIEFINGFRI 08:30Send revised contract · due today2 people waiting on a reply1 action item from Monday’s sync
CONSOLE · EVERY CHANGE, WITH WHY09:13 created ACME-14 ← Dana’s email09:40 OPS-12 + evidence ← #opsThu 11:30 alert sent · Dana waiting 1dFri 08:30 briefing sent
Dana · Acme Can you send the revised contract by Friday?
#ops · Sam Invoice approved, ship it
09:12 An email from Dana at Acme: “Can you send the revised contract by Friday?”
09:12 Fieldwork reads it, matches Dana to Acme and checks your rules: a client deadline this week is urgent.
09:13 A task appears in your tracker, due Friday, high priority, with Dana’s email linked as evidence.
09:40 A Slack thread approves the invoice. It’s added to OPS-12 as evidence, not a duplicate task.
Thu 11:30 The contract still isn’t sent, so a Telegram nudge reminds you Dana has waited a day.
Fri 08:30 Your morning briefing: what’s due today and who’s waiting on you.
09:12 Email arrives
09:12 Understood
09:13 Task created
09:40 Slack update
Thu 11:30 Nudge
Fri 08:30 Briefing
01 Collect from every channel
Gmail
Slack
Telegram
GitHub
Notion
Meeting notes
Fieldwork checking every 15 minEACH MESSAGERead the messageMatch person & projectCheck your rulesUpdate the trackerDana · Acme · Contracts → urgent#ops → OPS-12 · add evidenceDana waiting 1 day → nudge08:30 → build briefing
ALERT · TELEGRAMTHU 11:30Fieldwork· now Dana at Acme has waited a day for the revised contract.
MORNING BRIEFINGFRI 08:30Send revised contract · due today2 people waiting on a reply1 action item from Monday’s sync
CONSOLE · EVERY CHANGE, WITH WHY09:13 created ACME-14 ← Dana’s email09:40 OPS-12 + evidence ← #opsThu 11:30 alert sent · Dana waiting 1dFri 08:30 briefing sent
Dana · Acme Can you send the revised contract by Friday?
#ops · Sam Invoice approved, ship it
09:12 An email from Dana at Acme: “Can you send the revised contract by Friday?”
09:12 Fieldwork reads it, matches Dana to Acme and checks your rules: a client deadline this week is urgent.
09:13 A task appears in your tracker, due Friday, high priority, with Dana’s email linked as evidence.
09:40 A Slack thread approves the invoice. It’s added to OPS-12 as evidence, not a duplicate task.
Thu 11:30 The contract still isn’t sent, so a Telegram nudge reminds you Dana has waited a day.
Fri 08:30 Your morning briefing: what’s due today and who’s waiting on you.
What you get
A task list that keeps itself
Tasks in Plane, an open-source tracker on your own server, filed by company and project.
Alerts when someone’s waiting
A Telegram ping when a person has waited on you too long, so you answer before they chase.
A briefing every morning
At 08:30: what changed overnight, what’s due today and who needs a reply.
A console that shows its work
Every change the agent made, the messages behind it, and why.
Your rules
It works the way you do.
What counts as urgent, what closes a task, who gets a reply within three hours, what to ignore: it all lives in a plain rules file you can read and edit. Every correction you make becomes a new rule.
procedure.md
## urgent- a client deadline this week- investors: reply within 3 hours## ignore- newsletters, receipts, calendar noise## the agent may- create tasks and comment- close tasks only with my approval
What it won’t do
Safe by design.
Reply or send anything for you.
It reads. It never speaks on your behalf.
Keep your messages in our database.
They’re stored on a machine you control.
Change a task without evidence.
Every update links to the message behind it.
Act on a guess.
When it’s unsure, it files the task and flags it for your approval.
Who it’s for
For people with too many inboxes.
Founders & execs
Several companies, investors, hires and a team, spread across five apps. Know who’s waiting on you before they have to chase.
Investor and hiring threads tracked to the end
One list across every company you run
A morning briefing instead of inbox archaeology
Consultants & agencies
Every client on a different channel. Each request lands in that client’s project, with the evidence attached.
Client requests filed by client, automatically
Nothing promised in a call goes untracked
A record of what was asked, and when
Done for you
How we set it up.
Four steps from the first call to a system that runs on its own. The last one feeds the first, the same way our logo does.
Step 01
Interview
We learn how you work: your channels, companies, people and what counts as urgent. That becomes your rules file.
Step 02
Install
We set it up on your server, or a small machine we help you choose, and connect one source at a time.
Step 03
Suggest
For the first week it only proposes changes. You approve or correct, and every correction becomes a rule.
Step 04
Hand over
Once it’s right, it runs on its own. You own the system and your data.
What the name means
ad infinitum∞infinitum
in·fi·ni·tum
/ˌɪn.fɪˈniː.təm/in-fi-NEE-tum
noun · Latin
The infinite; that which has no bound and no end.
Infinitum Labs A studio that builds AI agents, automations and video that keep running long after launch day.
ORIGIN Latin, neuter of īnfīnītus ‘unbounded’, from in- ‘not’ + fīnītus ‘limited’, from fīnis ‘boundary, end’.
ad in·fi·ni·tum
/ˌæd ˌɪn.fɪˈnaɪ.təm/ad in-fi-NY-tum
adverb · from Latin
Again and again, without end; forever.‘the workflow triggers, runs and repeats ad infinitum’
How long our automations are built to run.
ORIGIN Latin, literally ‘to infinity’: ad ‘to, towards’ + īnfīnītum.