Services for teams shipping AI in PHP.
We maintain Deck and Intercept. The same people take on a small number of client engagements each quarter — which is how we learn what the packages need next.
Four ways we're usually brought in.
Every engagement starts with a conversation and a written scope. No open-ended retainers unless that's genuinely what you want.
Architecture review
We read your codebase and tell you the truth about it — where prompts live, how agents are wired, what happens when a model misbehaves, and what will break first at scale.
- Written findings with severity and effort
- Prioritised remediation plan
- Walkthrough session with your engineers
Guardrail build
We implement the layer between your agents and your providers — injection screening, approval gates for destructive tools, structured logging and token accounting.
- Middleware wired into your existing stack
- Prompts migrated into version control
- Tests and runbooks your team owns
Product delivery
End-to-end delivery of an AI product or feature — from prompt design and agent architecture through to the Laravel application around it and production monitoring.
- Discovery, scoping and technical design
- Build, review and deployment
- Handover with documentation
Retained partner
A standing AI capability for teams not ready to hire one. Reserved hours each month for review, pairing, and the work that keeps surfacing.
- Reserved capacity, monthly
- Architecture review as you grow
- Direct line for the hard questions
How an engagement actually runs.
Deliberately boring. You should always know what's happening and what it costs.
A conversation
Half an hour, no charge. You describe what you're building and what's going wrong. We tell you honestly whether we're the right people — sometimes the answer is that you need a package we already give away for free, and that's a fine outcome.
A written scope
Before any money changes hands you get a document: what we'll do, what we won't, what it costs, and how long it takes. Fixed fee wherever the work can be fixed.
The work, in the open
We work in your repository on branches you review. Weekly written updates. Nothing lands as a surprise, and you can see progress without asking for it.
Handover that sticks
Documentation, tests, and a walkthrough with the engineers who'll own it. The goal is that you don't need us afterwards — if you want us anyway, that's a retainer.
Whether this is for you.
A good fit
- ✓You're on PHP or Laravel and putting AI into a product people actually use.
- ✓You have engineers who'll own the system after we go.
- ✓Something is already live or close to it, and the risks have become real.
- ✓You want to understand the decisions, not just receive a black box.
Probably not
- ✕You need a different stack. We're deep in PHP and Laravel, not generalists.
- ✕You want staff augmentation — bodies on a backlog rather than a scoped problem.
- ✕The goal is an AI announcement rather than something that works.
- ✕It has to start tomorrow. We book a quarter ahead and keep the list short on purpose.
Tell us what you're building.
A few sentences is plenty. We reply within two business days, and if we're not the right fit we'll say so and point you somewhere better.