Engagement
Pick the model that matches the uncertainty you still have.
These are the three commercial shapes SWS publishes, plus maintenance. They can be combined. A technology conversation is the front door: understand the pain before any of them starts.
01
Fixed price
A single system you can describe.
Requirements, milestones, deadlines, and the budget are written down before the team starts. SWS may change who is on the build. A project manager reports progress. You stay closer to this model than to a dedicated team, because the document is yours to defend.
02
Dedicated offshore resources
Capacity you want, without becoming the employer.
You describe the requirement broadly. SWS assembles people who work on your project and report to you. Hiring, attrition, and employment terms stay with SWS. You can change the size of the team. SWS watches quality and steps in. The detail of how people are found sits on the hiring page.
03
Time and material
A brief that is still moving.
Billing follows the time invested. People can start before a finished specification exists, and the mix of skills can change. A project manager keeps the reporting line clear. Use this when freezing the scope would be fiction.
04
Maintain
The months after the first release.
Deployment is its own job: stores, servers, configuration. After that, systems, traffic, and users change. Maintenance is the published way to keep the investment useful. It is not included by silence in a fixed-price build.