Skip to content
AI Automation · Workflow Systems · Product Operations

AI & workflow automation — built around real business problems.

I design and build AI agents, automations and digital products that turn fragmented business processes into clear, repeatable workflows. I start by understanding how work moves through the business, then choose the right technology.

Built across
SaaSAI AgentsClaude / ChatGPT PluginsNotion WorkersWorkflow AutomationShipped iOS Apps
02 · 60 second demo

See the workflow
in action.

Watch how I turn a fragmented client process into a structured workflow with clearer ownership, outstanding actions and approvals.

Problem → process → workflow → system → outcome Watch the full walkthrough →
03 · Methodology

How I approach
automation.

I start with the process, not the technology.

Technology is selected after the workflow is understood — not the other way around. The goal is a system people can actually use, not automation for its own sake.
01

Understand the existing process

Map how work currently moves between people, clients and tools.

02

Identify friction

Find bottlenecks, duplicated work, missing information, unclear ownership and manual follow-up.

03

Design the workflow

Define stages, owners, required inputs, records, decision points and approval gates.

04

Build the system

Use AI agents, automation, SaaS, Notion or connected systems depending on the problem.

05

Test and improve

Test real scenarios, handoffs and edge cases before refining the workflow.

06

Support adoption

Document how the system works and make it understandable to the people who actually have to use it.

04 · Selected builds

Built to solve real
workflow problems.

A selection of AI agents, workflow systems, SaaS and apps I’ve designed and built around practical business needs.

ChatGPT plugin listing for Client Onboarding & Readiness by ChasePad.
Claude / ChatGPT Plugin

Client Onboarding & Readiness by ChasePad

Reads briefs, proposals and kickoff information, flags what is missing — including assets, access, approvals, owners, deadlines and blockers — and turns it into a clear onboarding plan before work begins.

Capabilities
AI workflow design · Missing-information checks · Structured outputs
Marketplace screenshot for the Client Request Architect AI agent.
Marketplace-Approved Notion AI Agent

Client Request Architect

Turns messy client briefs, emails, meeting notes and proposals into a structured request plan, highlighting missing information, risks and next actions.

Capabilities
AI agent design · Workflow design · Structured outputs · Business process analysis
View AI agent case study
Notion WorkersAutomation queue
Read structured workspace inputReady
Execute AI-assisted taskRun
Return structured outputWrite
Workspace Automation

Notion Workers

Built automated Notion Workers that read workspace information, run AI-assisted tasks and return organised results.

Capabilities
Automation · Workflow design · AI-assisted task execution
Additional builds
UGC Brief-to-Delivery AI agent icon.
AI-assisted workflow

UGC Brief-to-Delivery

Turns a campaign brief into requirements, hooks, scripts, shot lists, deliverables and handoff information.

Vegan Protein Planner iOS product screens.
Mobile apps

iOS apps I’ve designed and shipped

Vegan Protein Planner and GLP-1 Week Coach show my experience across app functionality, integrations, subscriptions, testing and App Store deployment.

05 · Flagship case study

From fragmented client chasing to a structured workflow.

The goal was not simply to digitise a checklist. It was to make the state of the project visible.

Client-facing teams often manage requests, assets, revisions and approvals across email, messages and separate documents. That creates a simple operational problem: people can be waiting on different things while no one can immediately see what is outstanding, who owns the next action or whether the latest version has actually been approved.

ChasePad workflow screens showing dashboard, client request link and approval flow.
The problem

Scattered information creates hidden blockers.

Requests, assets, feedback and approvals sit across different channels. Follow-up depends on memory. Ownership becomes unclear. The team cannot easily tell what must happen before the project can progress.

My approach

Map the work before choosing the tool.

I review how work moves from the initial client request through asset collection, feedback, revisions and final approval, then identify where the workflow breaks down: unclear ownership, missing information, manual follow-up and dependencies held somewhere else.

Workflow design

Define what has to be true before work can move forward.

StageWhat happens at each stage?
OwnerWho owns the next action?
InputsWhat does the client need to provide?
RecordWhat information must be captured?
ApprovalWhat requires sign-off?
GateWhat allows work to progress?

This becomes the plan for the system.

The solution

Turn the workflow into a working system.

I built a structured client workflow with workspaces, request checklists, visible outstanding items, reminders, revision tracking and recorded approvals. The system makes four things clear: what is ready, what is blocked, who owns the next action and what needs to happen next.

Client workspacesStructured requestsOutstanding statusRevision trackingApproval evidenceFollow-up support
Workflow outcomes

What the workflow improves.

Clearer ownership

Teams can identify who owns the next action.

Greater visibility

Outstanding requests and approvals are visible instead of buried in conversations.

Structured interaction

Clients have a defined place to provide information and assets.

Better accountability

Approvals and decisions can be recorded.

Repeatability

The workflow can be reused consistently across client projects.

Business processanalysis
Workflowdesign
Requirementsdefinition
Systemdesign
Implementation& integrations
Testing& refinement
Adoption& documentation
06 · Deep dive

Want to see the full workflow?

The short demo shows the process at a glance. The full walkthrough shows how the system works in more detail — requests, ownership, outstanding items, feedback, revisions and approval evidence.

07 · Business relevance

Where I can apply this.

The same approach applies across departments: understand the process, clarify the steps, ownership and handoffs, then build the right system around them.

01

Operations

Repetitive internal processes, requests, approvals, handoffs and coordination.

02

Customer service

Information retrieval, structured responses, triage and escalation workflows.

03

Marketing

Campaign workflows, content operations and AI-assisted content planning.

04

E-commerce

Product and content processes, customer workflows and operational automation.

05

Recruitment / People

Information collection, candidate workflows, onboarding and internal processes.

I focus on finding places where AI or automation can remove repetitive work without making the workflow harder for the people who actually have to use it.

08 · Next step

Building better workflows
with practical AI.

If you’re looking for someone who can understand the process first and then build the right AI, automation or product solution, I’d be glad to talk.