---
title: "Software Architect | Outsourced Development | Azendo"
description: "Assign a Software Architect to your roadmap under one monthly agreement, working from Thailand with an Azendo service delivery manager accountable for delivery."
url: "https://azendo.co/services/software-development/software-architect/"
---

[← Software development](https://azendo.co/services/software-development/) 

# Software Architect assigned to your roadmap.

A Software Architect makes the structural decisions that are expensive to reverse later. Service boundaries, data ownership, and how the system behaves under ten times the load.

Assigned under one service agreement with a minimum monthly capacity in hours, run by a service delivery manager in Chiang Mai, Thailand — five hours ahead of Northern Europe.

[Contact us](https://azendo.co/get-in-touch/) [See pricing](https://azendo.co/pricing/) 

Part of our service line

[Software development](https://azendo.co/services/software-development/) 

This role is delivered as part of our software development services. Take the role on its own, or the whole discipline as one delivery team.

## What a Software Architect does on an outsourced software development team.

Skills and scope are agreed before delivery starts, so the first sprint is productive rather than a ramp-up month. The work runs to the same backlog, the same repositories and the same definition of done as your own team's.

### Software Architect skills and technology we assign for

* [Domain-driven design](https://azendo.co/skills/domain-driven-design/)
* [event-driven architecture](https://azendo.co/skills/event-driven-architecture/)
* [microservices and modular monoliths](https://azendo.co/skills/microservices-and-modular-monoliths/)
* [CQRS](https://azendo.co/skills/cqrs/)
* [API design](https://azendo.co/skills/api-design/)
* [AWS and Azure reference architectures](https://azendo.co/skills/aws-and-azure-reference-architectures/)
* [Kubernetes](https://azendo.co/skills/kubernetes/)

* System design and service boundaries, documented as decision records rather than diagrams nobody updates.
* Scaling and resilience planning before the traffic arrives, not during the incident.
* Technical review of work in progress, so the architecture on paper matches the one in the repository.
* Reviewing third-party vendor architecture before you commit to an integration you cannot reverse.
* Writing the migration plan when a service needs splitting, including what runs in parallel and for how long.

## Seniority levels we assign.

Senior and principal only. Architecture decisions made by someone without production scars are expensive. Seniority is one of the inputs behind the [committed monthly capacity](https://azendo.co/pricing/) written into your agreement.

## When a Software Architect is the right assignment.

Usually assigned part-time alongside a delivery team rather than as a standalone role. On an ongoing roadmap this role is most often assigned alongside a Backend Developer or a Frontend Developer. All 4 roles in this service line can sit on the same agreement, and capacity moves between them at the monthly cycle rather than requiring a new contract. It is one of the assignments that make up [software development outsourcing](https://azendo.co/services/software-development/) at Azendo.

160 h

Typical monthly capacity for this role

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

## Other roles in software development.

[Backend Developer Software development role](https://azendo.co/services/software-development/backend-developer/)[Frontend Developer Software development role](https://azendo.co/services/software-development/frontend-developer/)[Full Stack Developer Software development role](https://azendo.co/services/software-development/full-stack-developer/) 

The same delivery team, on your product, month after month.

Chiang Mai and Bangkok, Thailand — five hours ahead of Northern Europe

## Questions about assigning a Software Architect.

Do we need a full-time architect? 

Rarely. Most engagements use part-time architecture capacity alongside a delivery team, which is how we usually scope it.

Will the architect write code? 

Yes, some. An architect who never touches the codebase produces designs that do not survive contact with it.

## Add software architect capacity to your roadmap.

Tell us the scope and the stack. We come back with the profile, the capacity and what the first month looks like, or you can [talk to a service delivery manager](https://azendo.co/get-in-touch/) first.

[Contact us](https://azendo.co/get-in-touch/) [How it works](https://azendo.co/how-it-works/) 

## Assign a Software Architect to your roadmap.