AI Workflow Engineering

Automate & Accelerate your Growth.

Designing seamless AI pipelines for every step - So your business scales at lightning speed.

Get in touch

Let me supercharge your growth.

I turn chaos and ambiguity into reliable systems that scale - blending my deep technical expertise in AI with my many years of building and automating operations.

The result?

⚡️ turbocharged sales cycles, and more ⏳time to focus on what really moves the needle:
landing deals 💵 and scaling the business 📈.

Get in touch

My Tools:

Zapier

What I Like: With Agents, Interfaces, Tables, and MCP servers, Zapier remains a favorite for building versatile workflows.

What It’s Good For: Automating tasks across apps, from simple integrations to complex workflows, enhancing productivity.

Make

What I Like: Streamlines workflows with a no-code, visual interface, ideal for automating tasks across departments.

What It’s Good For: Automating marketing campaigns, managing customer support tickets, and integrating AI agents for efficiency.

Power Automate

What I Like: Microsoft’s low-code tool seamlessly connects apps, reducing manual work without coding.

What It’s Good For: Automating data entry, email notifications, approval workflows, and data synchronization across apps.

Lindy AI

What I Like: Enables custom AI agents for tasks like email and customer support, user-friendly with no coding required.

What It’s Good For: Automating repetitive tasks such as email management, scheduling, and customer support workflows.

Anthropic

Claude Opus 4: Excels in complex tasks and coding, perfect for large-scale projects requiring deep reasoning and precision in frontend/backend development.

Claude Sonnet 4: Efficient for everyday use, great for general tasks and consistent coding assistance for smaller projects.

Relevance AI

What I Like: Builds AI workforces for complex tasks with low/no-code agents, offering precision and scalability.

What It’s Good For: Automating sales, marketing, customer support, research, and operations with multi-agent teams.

Cursor

What I Like: Enhances coding with AI-driven suggestions and natural language, boosting developer productivity.

What It’s Good For: Writing, refactoring, and debugging code, with deep understanding of entire codebases for efficient development. Also excellent for large context.

Vercel

What I Like: Simplifies frontend deployment with fast, secure, scalable hosting; v0 adds AI-powered UI generation from natural language.

What It’s Good For: Building and deploying static sites, SPAs, and JAMstack architectures, especially with Next.js.

Replit

What I Like: Browser-based IDE for coding and collaboration, supporting multiple languages with AI assistance via Replit Agent.

What It’s Good For: Building full-stack apps, teaching coding, and collaborating on projects with instant deployment.

Loveable.dev

What I Like: AI-powered platform for building full-stack apps using only a chat interface, making development accessible.

What It’s Good For: Quickly creating MVPs, prototypes, or full applications without coding expertise, ideal for startups and solo developers.

OpenAI

GPT-4o: Good for day-to-day queries and basic writing.

GPT-4.1: Handles extensive data with a 1 million token context limit, ideal for coding long-form content and research tasks.

GPT-4.5: Advanced chat capabilities for writing, programming, and problem-solving, good writing style too.

xAI

Grok 3: Blends superior reasoning with extensive knowledge, ideal for scientific research and complex coding queries.

Grok 4: Most intelligent model globally, with native tool use and real-time search for advanced coding and scientific tasks.

Grok 4 Heavy: Enhanced for demanding tasks, perfect for high-stakes coding applications requiring maximum power (math super genius)

Google

Gemini 2.5 Pro: Advanced reasoning and accuracy, ideal for deep research and complex coding queries across domains. Insane context sizes.

Veo 3: Video generation model for cinematic content, very realistic video and audio good.

What I Build.

I’m a generalist architect. I can take a problem from a blank page to a running, deployed system on my own, and I’m comfortable anywhere on the path between them. Design, frontend, backend, data, infrastructure, AI. I’m not attached to any one stack. I pick the right approach for the problem in front of me and learn whatever it needs. The breadth is the point: it means I can hold an entire system in my head and make the pieces fit, rather than owning one slice and handing off the rest.

Range.

Most engineers go deep in one lane. I go deep in several and stay fluent across all of them. That lets me design a system end to end and keep it coherent, where a problem that crosses from interface to data to infrastructure stays one decision instead of three handoffs. I move between roles as the work demands and I learn new territory quickly, because the underlying way of thinking carries over.

Interfaces and design.

I care how things look and feel before I care how they’re built, and I can build them too. I design interfaces and the systems that keep them consistent across many products at once, so a whole family of applications shares one coherent language instead of drifting apart. Good taste up front, structure underneath to protect it.

Building software end to end.

I build complete products, not pieces of them. Front to back, from the screen a person touches to the logic and storage behind it, deployed and working. Owning the whole thing means I can make tradeoffs across the stack instead of optimizing one layer at the expense of another.

Systems architecture.

I design how the parts of a system fit together: how services talk to each other, how identity and access work, how something stays secure and dependable as it grows from one user to many. I think in terms of correctness and failure modes first, and I build so the boundaries are clean enough that change stays cheap.

Data.

I structure data so it’s reliable to work with, move it between systems without losing or duplicating it, and build search and analysis on top, at whatever scale the problem demands. I model information carefully, because a clean model is what makes everything above it simple. I care as much about how a system remembers and reasons over its data as about how it stores it.

Infrastructure and operations.

I run systems in production and keep them running. Deployment, scheduling, monitoring, and the discipline of building things that recover on their own and tell you when something’s wrong. I’d rather a system be small and dependable than large and impressive, and I optimize for getting more out of less.

AI and intelligent systems.

I build with AI as a core material rather than a feature bolted on the side. That means connecting models to real tools and real data, designing how a system reasons, remembers, and stays efficient, and keeping people in control of the parts that matter. I also build privacy-first, with systems that keep sensitive data on a person’s own device and treat that as a constraint to design around, not an afterthought.

Let's connect

Let's connect