Daily Journal: I stopped building "Websites" and started building "Workforces".

For years, I was a Full-Stack Developer. I loved code, but I hated seeing businesses hire huge teams for repetitive tasks.

Then I realized: The code I write shouldn't just display information; it should do the work along with humans.

I’m excited to introduce myself as an AI Automation Engineer.

My core focus now is combining System Design with Agentic AI. Instead of just shipping a React/NextJS frontend, I’m shipping:

1) Voice Agents that handle intake calls 24/7.

2) Self-Healing Workflows that automatically fix data errors.

3) Microservices that act as infinite interns.

4) Autonomous Sales & Marketing Engines

Now, I don’t just build chatbots; I build Digital Workforces that handle complex, stateful logic (not just if/then), run on containerized infrastructure (Docker) for reliability, and integrate deep into legacy systems via custom APIs and Robotic Process Automation (RPAs).

I’ve spent the last few weeks documenting my exact engineering process, from Voice AI Architectures to Event-Driven Sales Engines, on my new portfolio.

It’s live now: https://saadk.co

(Check the video below for a 60-second tour of the systems I’m building).

I need your honest feedback: Does the site clearly communicate the "Engineer" side of automation? Or does it still feel like a standard portfolio?

Roast my UI (or my stack) in the comments. I’m iterating live.

8 comments