I built Wasala Ops because I kept seeing people do work their systems should have handled.
I came to automation through finance, accounting, and operations — not through software sales. I was already inside the reports, invoices, spreadsheets, approvals, and handoffs that kept repeating every week.
The first automations were built to remove work I was doing myself.
That experience shaped how I approach projects now. I start with the actual process, the people using it, the systems already in place, and the point where the work keeps slowing down or getting repeated.
I’m based in Oakland County, Michigan, and outside Wasala Ops I serve as a volunteer firefighter. It is very different work, but it has sharpened the same instincts I bring to systems: clear procedures, dependable handoffs, known failure points, and reliability when things get busy.
Wasala Ops stays intentionally small and direct. You are not handed from sales to an account manager to a developer. You work with the person mapping the process and building the solution.
Practical first. Maintainable second. Fancy only if it helps.
Start with the process
I care more about what your team is actually doing than which product logo is involved.
Use the simplest tool that works
That might be Power Automate, Excel, an app, a website, AI, an API, or a combination of them.
Build for exceptions
Good systems handle missing data, bad inputs, unusual cases, and the moments where a person still needs to make the call.
Leave something people understand
The goal is not a clever black box. It is a dependable system your business can actually use and maintain.