How we work
AI agents do much of the typing. Senior engineers make the decisions, review every change and stay accountable for the result. This is what that looks like on a real project.
Delivery
From first call to ongoing support
Free call
We learn what you need, what worries you and what has already been tried.
Discovery or review
A short, paid first step: a discovery phase for new builds, or a review for existing code.
Plan and price
Milestones with a fixed price or an estimate range, and the assumptions written down.
Build in small steps
Small changes released to staging every week, so you see progress and can change direction.
Launch and support
A planned launch with a rollback plan, then monitoring, patching and improvements.
The guardrails on every change
We use AI coding agents throughout our work: for scaffolding, tests, migrations, refactoring, upgrades, documentation and investigating bugs. Every change, whoever or whatever wrote it, goes through the same steps before it reaches your users.
- Small, clear tasks. Work is broken into pieces a person can review properly in minutes, not days.
- Written project rules. Each repository has an instructions file that tells agents and engineers how the codebase is organised and what they must never do.
- Tests with every change. New behaviour comes with automated tests, and the full suite runs before review.
- Automated checks. Static analysis, code style and dependency audits run in CI on every pull request.
- Senior review. A named engineer reviews each change for correctness, security, performance and fit with the rest of the code.
- Staging first. Changes go to a staging site you can try before they reach production.
Our article on AI-driven development guardrails goes into more detail.
Who does the work
Larasoft is a UK company, and every engagement is led from the UK. Our engineering team includes vetted developers working remotely. You will always know who is working on your project, and you will have a lead engineer who knows your application.
Ownership and security
Your code lives in a Git repository in your name. Servers, domains, payment accounts and third-party services are set up in your name too, with access granted to us, so you can change supplier at any time. We use separate credentials for each environment, never work on production data unless a task requires it, and remove our access when an engagement ends.
Reporting
You get a task board you can see at any time, a short weekly update on what was done and what is next, and tracked hours against every task for hourly work.
FAQ
Frequently asked questions
Will AI tools see our code?
Only tools and providers that are suitable for your project's confidentiality and data protection needs. We never give AI tools access to production data or production secrets, and we can agree specific restrictions with you.
Who is accountable if something goes wrong?
We are. Every change is reviewed and approved by a named engineer, and the lead engineer on your project is responsible for its quality.
How will we communicate?
Usually a shared Slack or Teams channel, a task board you can see, and a short weekly update. We can join your existing tools and rituals.
Talk to a senior Laravel engineer
Book a free 30-minute call. Tell us what you are building or what is worrying you, and we will tell you honestly what we would do, what it costs and how long it takes.