Skip to content

PHP development beyond a single framework

PHP work that is not only Laravel: existing apps, custom backends, and careful changes to code you already run.

PHP 8.2+LaravelMySQL / PostgreSQLComposerPHPUnit / Pest

Starting at

[PLACEHOLDER: starting price for PHP Development]

Existing PHP codebases are quoted after a short read of the repo, not from a generic day rate pasted on a website.

  • Features or fixes in the PHP version and style the project already uses
  • A short note on what changed and how to deploy it
  • Tests where the change touches payments, auth, or data writes
  • An honest list of what we will not rewrite in this phase

What we build

How this typically works

  1. 01

    Read the code

    We look at the repo before quoting. A guess from a call alone is not a quote.

  2. 02

    Separate fix from rewrite

    You get a price for the change you asked for, and a separate note if a rewrite would be cheaper later.

  3. 03

    Ship the change

    Small releases you can verify, not a silent month of refactoring.

  4. 04

    Hand back the repo

    You keep ownership. We do not hold the code hostage.

PHP is still the language under a large share of business software: booking systems, member portals, internal tools, and shops that were never “a Laravel app” in the marketing sense. This page is for that work. The Laravel-specific offering is separate, on purpose, so you are not sold a framework migration when you needed a bug fixed.

Who this is for

You already have PHP in production, or you want a new backend in PHP and you care more about a maintainable result than about a particular framework logo.

Common requests:

If the project is a new product and Laravel is the right tool, use the Laravel development page. We will point you there rather than stretch this one.

What we build

Changes you can review in the repository you already have, or a new PHP service with a clear boundary. That includes:

We do not replace your stack with ours as a default. A rewrite is a separate decision, with a separate price, after we have read the code.

Process and timeline

The first step is reading the repository. A quote that skips that step is a guess. After the read, you get either a fixed price for a defined change or an hourly arrangement if the work is a backlog of small fixes.

Old codebases vary more than new ones. A one-file bug can be a day. A PHP upgrade with abandoned dependencies can be weeks. Both get a timeline only after the read, not from this page.

What changes the price

How tangled the existing code is, whether tests exist, whether production data must be migrated, and whether deployment is included. See pricing for how fixed, hourly, and retainer engagements are structured. Starting amounts are not published until you confirm the figures you want on the site.

Laravel development for new Laravel apps and Laravel upgrades. APIs and backends when the deliverable is an HTTP API. Maintenance when you want a monthly block of hours instead of a one-off fix.

[PLACEHOLDER: case study for PHP Development] — ask about similar projects on a scoping call.

faq

PHP Development FAQ

Do you only work in Laravel?

Laravel is the default for new PHP apps. Existing Symfony, CodeIgniter, or plain PHP projects stay in that stack unless you explicitly want a migration, which is quoted separately.

Can you upgrade old PHP?

Yes, when the goal is a supported PHP version and the app still running. We list breaking changes first, then quote the upgrade. We do not bundle a redesign into an upgrade unless you ask.

Will you rewrite everything?

Only if you ask, and only after we show why a rewrite costs less than another year of patches. Most engagements are targeted changes.

Related services

Ready to talk about php development?

Get a fixed quote or book a free scoping call — reply within 24 hours.

No obligation. We reply within 24 hours with either a fixed quote or a short list of scoping questions.

WhatsAppGet a quote