Try us, at zero risk.

  • No deposit
  • No upfront fee
  • No commitment
Get in touch

What you get and what you pay.

With offshore staffing or staff augmentation, the provider finds a developer and the managing is left to you. We do it as a full service. The QA engineers are ours: we employ them, assign them to you full time, give them an office and equipment, train and coach them, and run delivery with you every week.

Price examples

Mid-level, full time, everything below included. Junior and senior levels are priced in your proposal. All 27 things included ››

  • Service

    We manage and develop the team

    • A service delivery manager who runs the team and answers for delivery
    • A 1:1 with our Head of Delivery every two weeks
    • Weekly delivery scoring and monthly capacity reports
    • A Talent Success Manager for every specialist
  • HR

    We are the employer

    • Recruitment and technical assessment
    • Employment contracts
    • Salary and payroll
    • Tax and social security
  • Facilitation

    We provide the workplace

    • A desk in our own office in Chiang Mai or Bangkok
    • A Workplace Experience Manager on site
    • Team events through the year
    • IT support
  • Equipment

    We supply the tools

    • Laptop and hardware
    • Software licences
    • LinkedIn Learning access
    • Device security and management
Your QA engineer Salary and benefits ONE MONTHLY FEE Delivery management Talent Success Events and wellbeing Equipment Workplace HR

One monthly fee. Everything around the QA engineer is in it.

You agree a monthly capacity in hours with us. The fee covers the QA engineer's salary and every layer around it: the service delivery manager who runs the team, training and development, the workplace, the equipment and the HR behind the employment. It is the same amount every month.

  • One agreement and one invoice, with no setup fee or management surcharge
  • Holidays are already priced in, so April and May cost the same
  • Capacity moves up or down at the next monthly cycle
How the monthly fee is built →

Tailored teams down to every detail.

We make sure your team is 100% tailored to your needs and expectations. We headhunt QA engineers when needed, so we deliver high-performing teams.

Before we start Alignment on your needs
  • Roles and seniority
  • Stack and domain
  • Way of working
  • Capacity and start date
Talk to our teamBook a scoping call
WEEK 1 Sourcing WEEK 2 AI processingand screening WEEK 3 Technical testing WEEK 4 Mindset, cultureand logic 25 headhunted for your brief 12 matched to your stack 5 pass technical testing 1 proposed to you
  1. 25 Week 1 Sourcing Headhunted for your brief
  2. 12 Week 2 AI processing and screening Matched to your stack
  3. 5 Week 3 Technical testing Pass technical testing
  4. 1 Week 4 Mindset, culture and logic Proposed to you

Any role your roadmap needs.

These four are the QA and test automation roles with their own pages. Beyond them we assign specialists across ten disciplines, on the same agreement and with the same service delivery manager.

"We don't hand you a QA engineer and step back. We build the team around your product, and we stay in it every week."

Mikkel Schmidt, CEO and founder

Mikkel Schmidt, CEO and founder of Azendo

Questions about a dedicated QA and testing team.

Is this a one-off test or an ongoing team?

An ongoing team. Our testers stay with your release calendar, so coverage improves with every release.

Do we have to manage the testers?

No. It's staff augmentation delivered as a managed service. Our QA engineers are assigned to your releases full time, and we employ, train and manage them. You set the priorities and decide what ships.

Can we outsource test automation only?

Yes. Strategy, automation and manual testing can be scoped separately, and many teams start with automation.

Can we choose the seniority level?

Yes, from junior to principal, priced by level. Mid-level engineers suit most regression work.

What if our tooling isn't listed?

Tell us what you use and we'll confirm the fit at scoping.

Can we add a second QA engineer later?

Yes, at the next monthly cycle.

Who owns the tests?

You do. They live in your repositories from the first commit.

How does QA keep its place when a release date moves?

Testing often becomes the last step before a release and the first thing cut when the date moves. When QA reports to the same service delivery manager as the developers, testing keeps its place, because one person is accountable for the whole release.

Who builds and maintains the test suite?

That means a suite that runs on every merge. A test automation engineer builds and maintains it, and when load or speed is the risk, a performance test engineer covers what functional tests can't.

Where do your testers start?

Our testers start by reading your incident history, because the most valuable tests cover what has already broken.

Can QA join a development team we already have with you?

QA often joins a team set up through software development outsourcing. One committed monthly capacity covers both, and developers and testers work as one managed team.

Build the whole team around your QA engineers.

Most partners add a second discipline within the first year. It joins the same agreement, the same sprints and the same service delivery manager.

Book a discovery call