Bring agents to the PHP you already run.
You have a PHP application in production. It does real work for real people. It does not need a rewrite, a new platform, or a demo that falls over in week two. It needs agentic features wired into the code you have, by someone who codes agentically in PHP every day.
Laravel from 5.x to current Symfony and Messenger-based apps WordPress and WooCommerce Legacy PHP that still pays the bills
What an agent inside your app actually looks like.
Not a chat widget bolted to the side. A unit of work that uses your models, your queue, and your permissions, and asks a person before it does anything you would not let a new hire do unsupervised. Scroll through one controller as it picks up an agent.
Start from the code that already works.
A support ticket comes in, gets saved, a confirmation goes out. Nothing here changes. The agent is added around it, not instead of it.
Give the model tools, not your database.
Each tool is a small PHP class that calls code you already trust: look up an order, search the help center, draft a reply. The model can only do what a tool allows.
Run it on the queue you already have.
The agent runs as a job. Retries, timeouts, failure handling, and logging come from the framework you operate today. No new runtime to babysit.
Keep a person at the gate.
Anything with money, access, or a customer’s trust attached waits for approval in your existing admin. Every run is recorded, so you can read what the agent did and why.
class SupportTicketController extends Controller { public function store(StoreTicketRequest $request) { $ticket = Ticket::create($request->validated()); Mail::to($ticket->customer)->queue(new TicketReceived($ticket)); TriageTicket::dispatch($ticket)->onQueue('agents'); return redirect()->route('tickets.show', $ticket); } } // app/Jobs/TriageTicket.php class TriageTicket implements ShouldQueue { public $tries = 2; public $timeout = 90; public function handle(Agent $agent): void { $run = $agent ->withTools([LookupOrder::class, SearchHelpCenter::class, DraftReply::class]) ->requireApproval(fn (Action $a) => $a->refundsMoney() || $a->changesAccess()) ->recordTo(AgentRun::class) ->run(new TriageTicketTask($this->ticket)); TicketTriaged::dispatch($this->ticket, $run); } }
It fits the PHP you have.
Every stack already has the seams an agent needs: a place to run work, a way to call your own code, and a place where people make decisions. The job is to use them well.
-
Laravel 5.x through the current release
Queues, events, policies, and Eloquent are the right primitives. Tools wrap actions you already have, agents run as jobs, approvals land in the admin your team already opens every morning.
Older apps get the same treatment, with upgrade work scoped only where the agent needs it.
-
Symfony and Messenger-based applications
Message handlers run the agent, services become tools through a thin interface, and the Workflow component holds the approval states. Nothing bypasses your firewall or voters.
-
WordPress including WooCommerce
A plugin that uses your real posts, products, and orders through the APIs you already rely on. Hooks are the entry points, WP-Cron or Action Scheduler runs the work, and content stays on your site.
-
Legacy PHP no framework, or one nobody remembers choosing
Observability first, then a narrow boundary around the functions the agent is allowed to call. The code you have is the asset; the agent is added at the edge, and the rewrite nobody has time for stays off the table.
The kinds of features that get added.
Each one is scoped as a product feature with success and failure criteria, not as an experiment that lives in a notebook.
-
Answers over your own data
Chat and search that read from your database and documents with the same permissions as the person asking. Cited, logged, and wrong less often because it only sees what it should.
-
Extraction into your models
Invoices, intake forms, emails, and PDFs turned into validated records in your schema.
FormRequestrules still apply; the model fills the form, it does not skip it. -
Classification and routing
Tickets, leads, and submissions triaged and sent to the right queue or person, with a confidence threshold that decides when a human takes over.
-
Multi-step workflows with approvals
Agents that gather, draft, and prepare, then stop at a gate. The person approves, edits, or declines in one click inside the tools they already use.
-
Agents that run your back office
Reconciling, chasing, scheduling, and reporting handled as background jobs with a readable trail of what was done, so the work is reviewable instead of mysterious.
-
Evaluations and guardrails
A test suite for model behavior that runs with your Pest or PHPUnit suite, so a prompt change is treated like any other change: reviewed, tested, and deployable.
Built the way Agency Intentional builds.
Agentic PHP is the PHP-specific front door to Agency Intentional, a productized Laravel consulting practice. Same engineer, same operating model, pointed at one problem: putting agents into PHP applications that already matter.
-
Fixed outcomes
Each engagement has a defined finish line and a written definition of done before code starts. No hours to count, no mystery scope.
-
Async by default
Work ships through your repository in small, reviewable changes. Decisions are written down where your team can find them later.
-
Verification at every gate
Tests, evaluations, security checks, and senior framework judgment decide what earns its way into production. Agents accelerate the work; they do not own the risk.
-
Leave it better
The tests, documentation, and operating clarity improve along with the feature, so your team can keep running it without us.
The person behind both sites has been building software products and teams for thirty years and has used Laravel since the v4 beta. The agentic part is newer; the judgment about what to let into production is not.
If the work you need is broader than agents, from a painful Laravel application to steady monthly product engineering, that lives at agencyintentional.com. Either way, the conversation starts the same way.
Tell us what your PHP app does. We’ll tell you where an agent fits.
One email with the stack, the problem, and what worries you. You get back a straight read on whether it is worth doing, what it would take, and a fixed shape for the work if it is.