This is an old revision of the document!
Hiring in-house gives you the most control. The people internalise your domain over time, and that knowledge sits with you. The catch is a long ramp-up and fixed costs: recruiting a strong engineer routinely takes several months, hire php developer long term onboarding adds more time, and the payroll continues regardless of workload.
Project outsourcing means someone else is accountable for shipping: they staff the roles, they manage the day-to-day work, and they absorb the risk of missing the date. This works well when the outcome can be described and you have a decision maker with time for it. It fails when the requirements change weekly, as a vendor is not able to invent your business rules.
Staff augmentation sits between the two: you rent capacity while keeping responsibility for delivery yourself. The main advantage is speed — the right specialist can join almost immediately — and it scales down as easily as it scales up. The trade-off is that your engineering managers need time for code review and planning. Without strong internal leadership, you end up paying for effort with no owner.
Most of the time, these models are combined. A common pattern puts the architecture and the core domain inside the software development company in usa, while an external team covers discrete features, migrations or mobile clients. The principle is simple enough: retain the parts that are hard to re-learn, and contract out the well-trodden work.
Three simple questions resolve most of these debates. Start here: is what you are building central to how you make money, or a supporting tool? Next: how long will you need this capacity — months or years? Finally: who answers the phone at two in the morning when it breaks? Work through them with real answers and the right arrangement usually chooses itself.