About

Hey, I'm Brady.

I'm a full-stack software engineer based in Brisbane, Australia. I build AI tools, internal systems, and custom software that helps businesses run better.

Brady Stroud

Brady Stroud

Founder / Senior Software Engineer

I started my career at SSW, one of Australia's top software consultancies, where I worked across .NET, React, Azure, and AI-powered tools like TimesheetGPT. That's where I got used to shipping fast and working directly with clients.

Now I run Stroud.dev, where I help businesses integrate AI into their actual workflows — not just demos, but things like manufacturing planners, multi-channel AI assistants, and automations that connect to the systems you already use (Odoo, Google Workspace, Strava, you name it).

My stack is mostly TypeScript and C#, but I'll reach for whatever gets the job done — Python, Swift, Flutter, n8n, Cloudflare Workers. I'm big on building end-to-end: architecture, code, deploy, iterate.

How we work

Small team, hands-on engineering, business-first thinking.

Stroud.dev is founder-led on purpose.

Most software shops bolt clients onto an account manager and a delivery team. That layer adds friction — every requirement, edge case, and trade-off has to be relayed through someone who didn't ship the code. We work the other way around: the engineer who builds your system is the same person who scopes it, talks to your team, and stays on the line when something needs to change.

We start by understanding the business, not the tech.

Before we recommend a stack, an AI tool, or an integration, we want to know what your team actually does day-to-day, where the time goes, and which workflows are quietly costing you the most. That conversation usually narrows a wide brief down to a sharp, scoped first build — something we can ship in weeks, prove value with, and iterate from.

Practical AI, not demoware.

We've built manufacturing planners, multi-channel AI assistants, document automation pipelines, and Odoo-connected workflows for real operations. The bar isn't "does the demo look impressive" — it's "does this earn its place in the business once the novelty wears off." That standard shapes every recommendation we make.

The stack is whatever fits.

Day-to-day we lean on TypeScript, Next.js, .NET, and Python, with Cloudflare Workers, n8n, Odoo, and Anthropic / OpenAI APIs filling in the rest. We pick tools based on the problem, not the playbook — and we're equally comfortable extending an existing system as we are starting clean.