Fixed-scope delivery · US · UK · Canada
PHP Development Company
A PHP development company in India that quotes fixed scope, names the delivery date, and puts a penalty against missing it. Discovery, build, QA and handover: one price agreed before we start rather than a range, one team, and your IP assigned from the first commit.
A written spec, architecture, risk list and one fixed build price, not a range. Yours to take elsewhere.
Below that figure a smaller engagement is the better buy, and we will say so.
Two build slots open for October starts
How we contract
Six terms we put in writing
The things every buyer of offshore development has been burned on. Each of these is a clause in our MSA, not a promise on a website.
Fixed price, agreed before we start
After discovery you get one number, not a range. It does not move unless you change the scope in writing, and then you see the revised number before anyone writes code.
A delivery date with a penalty behind it
We name the date in the contract. Miss it through our fault and the final invoice drops 10% per week late, capped at 30%. It has been invoked once in four years.
Weekly demo, not a monthly update
Every Friday there is something running you can click. If a week produces nothing demonstrable, you find out that Friday rather than at the end.
Thirty days of warranty after handover
Anything we built that does not do what the spec says is fixed free for thirty days after sign-off. Not "support hours": a defect warranty.
Your repository, from the first commit
Work happens in your GitHub organisation and your cloud accounts. There is no handover event because you already have everything.
One invoice schedule, no surprises
40% on signature, 40% at the midpoint demo, 20% on sign-off. Net 15, USD or GBP. No hourly overages on a fixed-scope build.
The team you get
Who is actually on your project
A pod of four, named in the contract, on your project for its duration. Not a resource pool that changes between sprints, and not a salesperson who disappears after signature.
You meet the delivery lead and the senior engineer during discovery, before you commit to the build. If either is not right, we change them then.
Straight answer
Buy a team, or buy a developer? The honest split
Two different products get sold under the same heading, and buying the wrong one is expensive. Project delivery, which is what this page sells, means we own the outcome: scope, estimate, schedule, QA, the lot. You approve a spec and a date, and management is our problem. That is worth paying for when you have no engineering leadership to spare, or when the thing being built has a hard external deadline.
It is the wrong purchase if your scope is genuinely still moving. Fixed price needs a fixed spec, and getting one costs two weeks of discovery, worth it for a defined build, wasted if you are still deciding what the product is. In that case hire a dedicated developer and direct the work yourself week by week. It is cheaper, faster to start, and you keep every decision.
The uncomfortable truth about fixed price is that both sides price the risk. Our number includes a buffer for the unknowns in your codebase, and you pay that buffer whether or not they materialise. Time and materials is cheaper on average and more expensive in the worst case. If you can carry variance, T&M is the rational choice; if you need one number to take to a board, fixed price is what that certainty costs.
One thing we will not do is quote a fixed price without discovery. Any agency that gives you a firm number for a substantial build from a two-page brief and a call is either padding it heavily or planning to make the difference back on change requests. The two weeks of discovery are how the number becomes real, and you own the spec afterwards whether or not you hire us to build it.
We have sent four enquiries to our staff-augmentation page this year because a fixed-scope build was the wrong purchase for them. Two came back eighteen months later with a defined project.
The three routes
Fixed scope, dedicated developer, or hire
In-house figures are a typical US mid-to-senior PHP salary plus employer costs. The dedicated-developer column is our own published monthly rate.
Capabilities
What we build
Eight kinds of project we quote most often. If yours is not on this list, describe it in a paragraph and we will tell you honestly whether it is us.
Custom PHP web application development
Greenfield builds on PHP 8.4 with a test suite, CI pipeline and written documentation from the first week, not bolted on before handover.
PHP 8.4Pest
GitHub Actions
Docker Legacy PHP 5.x to 8.4 upgrades
Static analysis first, then a branch-by-branch upgrade with the site staying live throughout.
Laravel application development
Multi-tenant SaaS, billing, queues and Filament panels on Laravel 12.
Laravel 12HorizonFilament 4 REST APIs and third-party integrations
Stripe, HubSpot, NetSuite, shipping and tax APIs, with retries, idempotency and a replay log.
StripeWebhooksOpenAPI CodeIgniter maintenance and migration
Keep CI3 patched and secure, or move it to Laravel one module at a time.
CodeIgniter 4 WordPress and WooCommerce engineering
Block themes built properly, headless front ends on a Laravel API, and stores that stay fast well past forty thousand products.
WordPress 6.8HPOSWP-CLIACF Pro Performance and database optimisation
Query profiling, indexing, caching layers and queue offloading, measured before and after, in writing.
RedisOctane Code audits and clean handover
A written report on an inherited codebase: risks, effort, and what to fix first. Yours to take elsewhere.
Something else?
Describe the problem in a paragraph. We will tell you honestly whether it is us, and who else to ask if it is not.
Tech stack
Current versions, not a wish list
What is in production for our clients this quarter. We will work in older versions too, most rescue jobs start there.
Language & frameworks
PHP 8.3 / 8.4 Laravel 11 / 12 
Livewire 3 Filament 4 CodeIgniter 4 
Symfony components Data & infrastructure
MySQL 8 
PostgreSQL 16 Redis Docker AWS · Hetzner · Forge GitHub Actions Quality & front end
Laravel Pint 
Vue 3 
Tailwind 4 
Alpine The engineers
The engineers who would build it
Salaried staff, named in your contract for the duration of the build. You meet the lead and the senior during discovery, before you commit to anything.
Subscription billing, multi-tenant schemas and the money paths. Reviews every pull request on his team himself.
Laravel 12 Vue 3 PostgreSQL Strangler migrations off CodeIgniter: one router, both frameworks live, no big-bang rewrite.
CodeIgniter PHP 8.4 MySQL 8 Integrations specialist, Stripe, NetSuite and three shipping carriers, all idempotent.
Stripe Sanctum Queues Writes the tests nobody else wants to write, starting with the paths where a wrong number costs real money.
Two build slots open for October starts. The full pod is named in your contract before you sign it. Meet the whole team →
How we work
What every fixed-scope build includes
On fixed scope we own the outcome, so these are contractual rather than aspirational. Each one is in the agreement before any code is written.
Not a range. It does not move unless you change the scope in writing, and then you see the revised number before anyone writes code.
Miss it through our own fault and the final invoice drops 10% per week late, capped at 30%.
If a week produces nothing demonstrable you find out that Friday, rather than at the end of the month.
Anything we built that does not do what the spec says is fixed free. A defect warranty, not support hours.
No separate project-management fee, no QA line item, and no charge for the handover.
Signature, midpoint demo, sign-off. No hourly overages on a fixed-scope build.
You do not have to take any of this on trust. The first ten working days are risk-free, every rate is published in full, and the work happens in your repository from the first commit.
How it works
From first email to a signed-off build
Discovery is two weeks and produces a spec you own. Nothing is committed until you have both the spec and the price.
- Day 0
Send us the brief
A document, a Figma file or three paragraphs. An engineer replies inside one business day, never a form response.
- Week 1-2
Discovery, fixed fee
Requirements, architecture, risk list and a written spec. You own it whether or not we build it.
- Week 2
One price, one date
A fixed number and a delivery date, both in the contract, with the late penalty attached.
- Build
Weekly demos
Something clickable every Friday, sprint reports, and staged releases into your environment.
- Handover
Sign-off + 30 days
Documentation, runbook and a defect warranty. Your repo already has everything.
Why India
Why choose a PHP development company in India
A four-person pod here costs roughly what one senior contractor costs in the US, which is what makes fixed-price delivery viable at all: the buffer that protects a fixed quote would price a domestic team out of the deal. PHP has also been the backbone of Indian software services for twenty years, so the depth is in the unglamorous work: inherited codebases, migrations and integrations.
YOUR WORKING DAY, AND OURS
- IP assignment on day one
- Everything written for you is yours on commit, not on final payment. Assignment clause, not a licence.
- NDA before repository access
- Yours or ours, signed before anyone is added to your GitHub organisation.
- Your jurisdiction, your paper
- We sign MSAs governed by Delaware, England and Wales, or Ontario law without argument.
- Milestone billing, not monthly hours
- 40% on signature, 40% at the midpoint demo, 20% on sign-off. Net 15, USD or GBP, and no hourly overages on an agreed scope.
- Scope changes priced before they happen
- Any change gets a written price and schedule impact for you to approve or decline. Nothing is absorbed silently and argued about at handover.
FAQ
Questions buyers ask before the first call
If yours is not here, email it. We publish the answer rather than saving it for a sales call.
How much does a PHP development company in India charge?
Discovery is a fixed fee over two weeks, and it ends with one fixed build price rather than a range. Our discovery fee is $2,400 and builds start at $9,500, both published on the rates page; what your own project costs comes out of discovery, because that is the only honest way to name it.
Why do you insist on paid discovery?
Because a fixed price without it is a guess, and the cost of a wrong guess ends up on your invoice as change requests. Two weeks produces a spec, an architecture and a risk list, and you keep all three whether or not we build it.
What happens if you deliver late?
The final invoice drops 10% for every week we are late through our own fault, capped at 30%. It is a clause in the contract, not a goodwill gesture, and it has been invoked once in four years.
How do you handle change requests?
You get a written price and schedule impact before anyone writes code, and you approve or decline. We do not absorb scope silently and then argue about it at handover, which is how most fixed-price relationships fail.
Who owns the code and the IP?
You do, assigned from the first commit rather than on final payment. The work happens in your GitHub organisation and your cloud accounts, so there is no handover event to negotiate.
What if we are not happy with the team?
You meet the delivery lead and the senior engineer during discovery, before the build is committed. If either is wrong for you, we change them then, that is one of the things discovery is for.
Do you offer fixed price or time and materials?
Both, and we will tell you which fits. Fixed price needs a settled scope and costs a risk buffer; time and materials is cheaper on average if you can carry variance. If your scope is still moving, a dedicated developer is usually the better buy.
What is included in the price?
Project management, QA, code review, documentation, deployment and thirty days of defect warranty after sign-off. No separate PM fee, no QA line item, no charge for the handover.
How much of our time will this take?
Roughly two hours a week: one demo call and asynchronous answers on Slack. Discovery is heavier. Expect four to six hours across the two weeks, because that is where your knowledge becomes the spec.
Can you take over a project another agency started?
Yes, and it starts with a paid audit rather than a quote. We need to know what is actually there before we will put a date against finishing it, and you own that report regardless.
Talk to an engineer
Tell us what needs building
You get a reply within one business day from an engineer, not a form autoresponder, with an indicative range, the discovery scope and the next available build slot.
A fixed price and a date, before any build work
NDA signed before we see your codebase
Or book a 30-minute scoping call at a time you pick
We never share your details, and we do not run a mailing list.