Open to new roles Power Platform architect · AI developer · Phoenix or remote
I automate the boring parts,
and ship real products.
By day I build on the Microsoft Power Platform: I replaced entire HR onboarding and offboarding systems with Power Apps and Power Automate, and I look after more than 20 solutions. After hours I ship my own products, with AI agents doing the legwork and me approving what goes live.
Open to roles
Why in public
Building used to be the hard part. Now I can describe a product at night and have it running by morning, and soon enough everyone will be able to. So the scarce thing isn't the building. It's getting anyone to look.
Which means the moat isn't the code anymore. It's the trust and the audience you earn while you build in front of people. That's the real game now, and most builders haven't caught up to it yet.
So I ship in the open. Every tool, every write-up, and the parts that broke in between. Some of it's small and free. Some of it pays the bills. All of it is me, figuring this out in real time, out loud.
Shipped
in public · live demos + source where it's openHow I work
I'm Sameer. I take a product from a sentence to something people can actually use: the design, the code, the billing, the deploy, and the unglamorous weeks after launch when you find out what you got wrong. Mostly solo, by running AI like a small team I can call up on demand.
The edge isn't the stack anymore. It's taste, and the speed to ship something before the idea goes cold. I also help teams get Claude, Claude Code and MCP working, and I automate the slow enterprise stuff with Power Apps and Power Automate, turning processes that took days into one click.
Dev Diary
building in public, one post at a timeLet's build something.
Open to roles in Power Platform and Microsoft solutions architecture, AI development and automation. Based in Phoenix, happy to work remote.