ResilAgent: Durable UI Scraping & Automation Monitor for Small Teams

If we were building this for a 20-person SMB, we’d avoid trying to pick the “perfect stack” first. Start with one ugly, high-value workflow and make it boringly reliable before expanding. Since you’re already in Teams/Microsoft 365, Power Automate is worth testing first for anything touching Teams, SharePoint, Outlook, approvals, etc. If you need more flexibility, n8n is a good next place to look. The no-API reporting system is probably the workflow I’d test hardest because browser automation is usually where reliability gets interesting. For the internal knowledge bot, the bigger question may be less about the AI model and more about whether your files, permissions, naming, and source data are organized well enough to trust the answers. And yes, under $300/month can be very realistic for an initial deployment with moderate usage. At your size, I’d be more concerned about maintenance time than token cost.

The thing that decides whether this feels stable a year from now is where you draw the line between the model and the plumbing. For the weekly report out of software with no API, script that with Playwright on a schedule rather than handing it to an agent, because an agent clicking through someone else's UI is the part that breaks quietly and eats your Monday. For the Teams bot over project notes, invoices and client history, almost all the work is ingestion and retrieval rather than the model, so chunk with metadata like client, date and document type, carry the source permissions through, and make it cite the document it answered from so people can check it. Then keep a fixed set of about thirty real questions you rerun every time you change a model, otherwise an upgrade will quietly make it worse and nobody will notice for a month. (disclosure, I run a dev shop, so pinch of salt.)