Operator workflow thinking
I start with the real workflow: who does what, what information moves where, what repeats, what breaks, and where decisions slow down. The goal is removing operational drag, not simply “adding AI”.
I design, build, and ship AI workflows, automations, dashboards, and internal tools that turn repeated manual work into operating systems people actually use.
I’m a full-stack developer with 10 years of experience building business systems. I sit comfortably between founders, operators, and engineers: mapping the workflow, simplifying the problem, building the system, and helping people adopt it.
I’m interested in this role because it sits exactly where I do and enjoy my best work: between business operations, AI systems, and software execution.
I’m not looking for a role where AI means making impressive demos that never enter daily use. I’m interested in building the internal tools, agent workflows, dashboards, prompts, exception paths, and feedback loops that make teams faster and more effective.
My background is full-stack (front and back end) web development, but the more relevant part is that I’ve spent years working directly with business operators from many different industries understanding how their businesses actually operate. I’m comfortable speaking with founders about outcomes, operators about bottlenecks, and engineers about implementation.
The Beard Capital role is explicitly practical: find the bottleneck, design the workflow, ship the system, make sure the team uses it, and measure whether it worked. That is exactly the work I want to do.
I start with the real workflow: who does what, what information moves where, what repeats, what breaks, and where decisions slow down. The goal is removing operational drag, not simply “adding AI”.
I can move from workflow map to working software. Laravel, Vue, APIs, databases, webhooks, AI APIs and production deployment — enough range to build the first useful version when speed matters.
A workflow only matters if the team uses it. I think about rollout, trust, training, exception handling and feedback loops from the beginning, not as an afterthought.
I can move between the commercial outcome, the technical implementation, and the explanation an operator actually needs — without losing the thread between them.
Service businesses waste time going back and forth to collect missing booking information. The work repeats, but still requires judgement: knowing what is missing, asking the right question, validating replies, and escalating when needed.
GuideFlow receives customer enquiries, extracts structured booking information, identifies missing details, communicates with customers to gather additional information, and evaluates responses against predefined booking requirements before progressing the workflow. Validation checks, confidence thresholds, and exception paths ensure incomplete or uncertain enquiries are escalated appropriately, allowing business owners to focus only on fully qualified booking requests that require human judgement.
Incomplete data, follow-up loops and escalation paths — not a generic chatbot.
Turns a messy operator workflow into an agent system with clear exception handling and full auditability.
Small service businesses run across disconnected forms, inboxes, notes, spreadsheets, quotes and invoices. The result is missed leads, slow responses, inconsistent admin and no clear operating system.
MoreWorx is a production Laravel platform spanning lead generation, customer records, quotes, invoices, payments, job information and AI-assisted growth workflows.
Subscription billing, preview-to-activation, domains, admin tooling and AI content systems.
Find repeated manual work, build the tooling, then turn workflows into reusable internal products.
People, triggers, required information, repeated decisions, existing tools and where the work stalls.
↘Frequency, value, adoption pull, automation risk and the decisions that should remain human-owned.
↘Inputs, outputs, agent brief, data flow, tools, prompts, exception paths, review points and success metrics.
↘A small daily use case with a clear owner, fallback path, logging and a tight feedback loop.
↘Adoption, time saved, failure rate, escalation rate, ROI and direct operator feedback.
↘I’m not limited to strategy documents or agent briefs.
I can build.
Full-stack developer focused on websites, business systems, internal tools and production web applications.
Building AI-assisted operating systems and workflow automation tools for service businesses.
Laravel applications, WordPress platforms, CRMs, internal tools, hosting, deployments and client support.
Requirements gathering, mentoring developers, and teaching business owners how to use new digital systems.
Agent workflows, AI-assisted products, automation tooling and practical operating layers.
GuideFlow and MoreWorx began with messy service-business workflows and turned them into structured systems.
✓GuideFlow uses extraction, missing-data detection, follow-up loops, validation and human escalation.
✓I communicate with operators and engineers clearly — and can build the first version myself.
✓My full-stack background lets me use scripts, APIs, webhooks, dashboards and AI tools at lightspeed without any handholding or babysitting.
✓Rollout, feedback loops, failure tracking and workflow measurement are part of the system design from day one.
✓Experience that adds useful context beyond the core role requirements.
Hands-on experience designing and building my own agentic application, not just working from theory.
Spent time inside Tasmania’s startup hub, working alongside founders and early-stage businesses.
Experience guiding developers, coordinating delivery, and keeping technical work aligned with the outcome.
Postgraduate qualification from QUT covering the security and network foundations behind reliable systems.
Mentored business owners through a government program, finding practical ways technology could make their work easier.
Delivered multiple video presentations for Digital Ready, published on the program website for business owners across Tasmania.
I’m applying because this role matches the work I’m already doing and enjoying: taking messy business workflows, simplifying them, building AI-assisted systems around them, and making those systems useful in the real world.
I can think like an operator, write like a strategist, build like an engineer, and teach like someone who has had to get real people using real systems.