Automations
Work that runs itself, in the tools your team already has open.
Every team has a few jobs that only get done when someone remembers: the weekly report, the notice that goes out late, the list that goes out of date when someone new joins. They are easy to build. They just need to run on a schedule.
How they work
What these jobs do.
Demos
See each job run.
Birthday and anniversary notices
A scheduled job reads the company directory every morning and posts to the Teams channel your team already reads.
Company directory
The job reads every account in Microsoft 365, groups people by how the business is organized, and publishes a branded PDF. When someone joins, the next edition includes them.
Key-date report
A scheduled job queries the ERP, finds the key dates that are overdue or coming due, and emails each owner a branded summary of what needs updating. Nobody has to log in or pull an export.
Pipeline and closed deals
The same approach reads the pipeline. Every Friday morning it posts the open pipeline ranked by expected launch value, and the next morning it announces any deal that closed.
Common questions
Before you book a walkthrough.
What runs these jobs?
Scheduled scripts that call APIs you already have: Microsoft Graph for the directory and email, a Teams Workflows webhook for chat posts, and your ERP’s own API for business data. They run on a timer in your tenant. Nothing calls a third-party service and no data leaves your environment.
Is this AI?
No. The jobs are ordinary scripts, so the same inputs give the same output every time. We use AI to help write them, but no model runs when a notice goes out.
What happens when someone joins or leaves?
Nothing. The job reads the directory on every run, so a new starter appears in the next edition and a leaver drops off without anyone editing a list.
Can these run against our systems?
Yes. The examples here use Microsoft 365, Teams and an ERP, but the same approach works with any system that has an API. Tell us the job and we will tell you whether it is worth automating.
What keeps slipping?
Tell us the job, which system it reads from, and who needs to see the result.