--- title: "Outsource Software Development Services | Azendo" description: "Outsource software development services to an assigned team in Thailand. One agreement, one delivery manager, capacity that moves with your roadmap." url: "https://azendo.co/services/software-development/" --- [← All services](https://azendo.co/services/) # Outsource software development services to a team that stays on your roadmap. Most companies that outsource software development services get a project delivered and a team dissolved. We work the other way. Specialists are assigned to your codebase and stay there, working your backlog under one agreement, with an Azendo service delivery manager answering for what ships. Chiang Mai is five hours ahead of Copenhagen, so the overlap is most of a working day. [Contact us](https://azendo.co/services/software-development/#team-builder) [Talk to a service delivery manager](https://azendo.co/get-in-touch/) How the role joins your team Added to delivery \+ capacity Software Engineer Assigned capacity * [React](https://azendo.co/skills/react/) * [Node.js](https://azendo.co/skills/nodejs/) * [PostgreSQL](https://azendo.co/skills/postgresql/) Capacity 160 h committed monthly ## What is software development outsourcing? Software development outsourcing means contracting engineering capacity from an external provider rather than employing it directly. Arrangements differ mainly in who directs the work: some supply engineers a client manages, others take responsibility for delivery itself. The distinction decides who carries the coordination load, and it matters more than the hourly rate. ## What our software development outsourcing services actually cover. Scope and stack are agreed before anyone starts, so the first sprint produces work rather than questions. Your backlog, your repositories, your definition of done. What that means in practice is that nothing on this list is a separate line item. A partner who outsources software development services to us gets the whole set under one agreement, and the balance between them shifts as the roadmap does. A quarter heavy on integrations looks different from one spent paying down platform debt. The part most partners underestimate is documentation. It is the least visible item here and the one that decides whether the fourth engineer to touch a service can work on it without a meeting. We treat it as delivery work rather than something done afterwards if there is time. * Feature development Work taken from your backlog and carried to production, in your codebase. * Code review and quality gates Static analysis, tests and a coverage floor set at scoping, not invented later. * Integrations and APIs Connecting your product to the systems it already depends on. * Sprint planning and stand-ups Your rhythm, your tools, alongside your product owner. * Documentation and handover So the codebase stays readable as the team and roadmap grow. ## Assigned to fit the stack you already run. We match the specialist to the stack you already run, at scoping, before anything is signed. What follows is what we see most often, not a limit. We do not arrive with a preferred framework and propose a rewrite. If your platform is a .NET monolith that works, the right answer is usually an engineer who knows .NET rather than a migration nobody asked for. Where the stack genuinely is the constraint we will say so, with a reason. If something you depend on is missing from these lists, it is worth asking. The lists cover the common cases across our current engagements, and a stack we have not named is a sourcing question rather than a no. Frontend * [React](https://azendo.co/skills/react/) * [Vue](https://azendo.co/skills/vue/) * [TypeScript](https://azendo.co/skills/typescript/) * [Next.js](https://azendo.co/skills/nextjs/) * [Angular](https://azendo.co/skills/angular/) * [Tailwind CSS](https://azendo.co/skills/tailwind-css/) * \+ more on request Backend * [Node.js](https://azendo.co/skills/nodejs/) * [Python](https://azendo.co/skills/python/) * [Java](https://azendo.co/skills/java/) * [.NET](https://azendo.co/skills/dotnet/) * [Ruby on Rails](https://azendo.co/skills/ruby-on-rails/) * [Go](https://azendo.co/skills/go/) * \+ more on request Data and infrastructure * [PostgreSQL](https://azendo.co/skills/postgresql/) * [MySQL](https://azendo.co/skills/mysql/) * [Redis](https://azendo.co/skills/redis/) * [Docker](https://azendo.co/skills/docker/) * [AWS](https://azendo.co/skills/aws/) * [GraphQL](https://azendo.co/skills/graphql/) * [Elasticsearch](https://azendo.co/skills/elasticsearch/) * \+ more on request ## One fixed fee for a monthly average. We take the engineer's working hours across a full year, subtract annual leave and public holidays, then divide by twelve. That average becomes the capacity in your agreement and the price stays flat. April has fewer working days than May. Your invoice does not notice. 160 h Typical monthly capacity for one engineer Fixed Monthly price, unaffected by leave or holidays 4–6 weeks From signed scope to delivery starting Monthly Cycle to raise or lower committed hours Your assigned engineers work from our own floor, on our equipment, on your codebase. Bangkok, Thailand — five hours ahead of Northern Europe ## The software development roles we assign. Take one role, or several as one delivery team. Each role below has its own page describing what it delivers under a service agreement. [Backend Developer Services, APIs and integrations Read about the role →](https://azendo.co/services/software-development/backend-developer/)[Frontend Developer Interfaces in your existing codebase Read about the role →](https://azendo.co/services/software-development/frontend-developer/)[Full Stack Developer Features end to end Read about the role →](https://azendo.co/services/software-development/full-stack-developer/)[Software Architect Structure, boundaries and scaling Read about the role →](https://azendo.co/services/software-development/software-architect/) ## Outsource software development services, build in-house, or bring in a local agency. There are three sensible ways to add development capacity and outsourcing software development services is only one of them. An in-house hire suits permanent local work. A local agency suits a project with an end date. We suit the roadmap that keeps producing work. | Comparison | Building it in-house | Local agency | Azendo | | ------------------------------- | ---------------------------------- | ----------------------------------------- | ----------------------------------------- | | Time to productive output | Months — recruit, onboard, ramp up | Fast to start, slow to learn your product | 4–6 weeks | | Continuity of context | Resets when someone leaves | Rebuilt with each new project | Held by the same delivery team, for years | | Continuity of product knowledge | Lost when the hire leaves | Ends with the project | Held by the assigned team | | Who answers for delivery | You do | Account manager, between projects | A service delivery manager, continuously | | Cost profile | Fixed, whatever the workload | Priced per project | One monthly fee, adjustable each cycle | | Scaling a discipline | A new hire each time | Re-scoped each engagement | Capacity up or down at the monthly cycle | ## Questions about outsourcing software development. How is this different from a typical software development outsourcing company? Most rotate people between clients and price against delivered scope. We assign specialists to one roadmap for the life of the engagement, and the same service delivery manager stays accountable throughout. You are not handed to a new account manager every quarter. Is this outsourcing or staff augmentation? Outsourcing, in the sense that we own delivery. Staff augmentation puts people under your management. Here the management stays with us and you review the output. Can I choose the seniority level? Yes, junior through principal, priced by level. We will tell you which level the scope actually needs, including when that is lower than you asked for. What if our stack is not on the list? Tell us what you run. The lists above are the common cases, not the boundary. Can we add people or disciplines later? At the next monthly cycle. Adding QA or DevOps to an existing agreement does not mean renegotiating it. Who owns the code? You do, from the first commit. Work happens in your repositories under your licence. ## Often assigned alongside a software engineer. A specialist rarely works alone on a roadmap. These disciplines cover the ground around the role and can be added to the same service agreement. [Mobile development Native and cross-platform apps](https://azendo.co/services/mobile-development/)[QA and test automation Test strategy and automated coverage](https://azendo.co/services/qa-engineering-and-test-automation/)[Cloud and DevOps Infrastructure as code, CI/CD, observability](https://azendo.co/services/cloud-and-devops/)[UX/UI design Research, flows and interface design](https://azendo.co/services/ux-ui-design/) ## What changes when you outsource software development to an assigned team The difference between outsourcing a project and outsourcing capacity shows up around month four. A project team hands over and leaves; the knowledge of why a service was built the way it was leaves with them. An assigned team is still there, and the second year costs less to run than the first because nobody has to be told twice. That is also why we scope by discipline rather than by ticket. A [backend developer](https://azendo.co/services/software-development/backend-developer/) who has carried your integrations for eighteen months makes decisions a newcomer would have to escalate. Where the question is structural rather than incremental, a [software architect](https://azendo.co/services/software-development/software-architect/) is assigned alongside rather than instead. Most roadmaps that outgrow their team hit a release problem before they hit a build problem. Features arrive faster than they can be verified, and the bottleneck moves without anyone announcing it. Where that is what is happening, [outsource qa testing](https://azendo.co/services/qa-engineering-and-test-automation/) capacity is the more useful first addition, not more engineers. Capacity is agreed in hours per month and written into the agreement, so adding a discipline is a change to the [committed monthly capacity](https://azendo.co/pricing/) rather than a new contract. That is deliberate: the model only works if growing the team is easier than justifying it. ## Tell us what software development capacity your roadmap needs. Tell us about your project and the capacity you have in mind. A service delivery manager will get back to you.