Question 1

How much does IT outsourcing cost?

Accepted Answer

It's a ladder with a free entry point. Backlog review: free in 3–5 days, with a written plan of who you need and what a month costs. Trial sprint: $3,900 for 2 weeks, one engineer, fixed scope, code in your repository. Dedicated engineer: from $5,900/month for full-time capacity (~160 hours) on your backlog, code review and CI/CD included. Engineer plus a hands-on team lead: from $12,900/month. Team of 3: from $15,900/month; for anything bigger, we assemble a team for the task and name every member before the contract. For comparison, a full-time mid-level developer on staff typically costs $10,000/month or more with taxes, plus 1–3 months to hire. Month-to-month contract, 30 days' notice to exit.

Question 2

How is this different from support at $2,900/month or a CTO at $3,900/month?

Accepted Answer

Three things: what you buy, who sets the tasks, and what you have at the end of the month. Software support (from $2,900/month) keeps a finished product running: SLA on-call, incidents, updates and 10–40 hours of development. CTO as a Service (from $3,900/month) is 20 hours of decisions: architecture, priorities, reviews, hiring, while your team writes the code. A dedicated team (from $5,900/month per engineer) is ~160 hours of hands on your backlog: you set the tasks, and at the end of the month your repository has new releases. The price tags look close, but you buy different things: from a CTO, expensive decision-making time; from an engineer, full-time execution. Many clients combine them: the CTO decides, the team builds, and support keeps the result running.

Question 3

There are only two of you. How can you give us a team?

Accepted Answer

Honestly: we won't give you a team of seven, and we won't promise one. The core of every dedicated team is one of the two co-founders: 13+ years in software, a hands-on team lead who writes code and reviews every PR. Around them are engineers from our pool whom we've worked with on past projects; we name the team members and send CVs before the contract. The realistic format is 1–3 engineers per project and no more than 3–4 projects at a time, otherwise the team lead stops being a team lead. If you need a turnkey team of ten, we'll tell you on the first call and recommend who to go to. Proof of the format: the founders built an ERP/FSM platform for a US field service company as part of the client's product team, shipping a new module to production every 3 weeks. The system has been in production since 2019.

Question 4

Do unused hours expire?

Accepted Answer

You're not buying a bundle of hours but an engineer's dedicated capacity for the month, as if they were on your staff. Every hour is visible in the tracker in real time (we work in MarchTracker, our own product, and you get access), and at the end of the month you get a report: how many tasks were closed and how many hours went into them. If a month falls short through our fault, we carry the hours over or adjust the invoice; that rule is written into the contract. If there aren't enough tasks for a second month in a row, we'll suggest a smaller team or a switch to support at $2,900/month ourselves, instead of quietly sending invoices. Overtime beyond the agreed capacity is approved in advance, so there are no surprises on the invoice.

Question 5

How do we exit the contract, and what do we keep?

Accepted Answer

You can start with a trial sprint for $3,900: two weeks, one real task, fixed scope, so you see the code and the pace before any long-term commitment. After that the contract is month to month: 30 days' notice to exit, no penalties, no non-refundable deposits. There's nothing to collect when we part: the code has lived in your repository under your organization since day one, and exclusive rights transfer to you under the contract. Plus two weeks of overlap at our expense: architecture docs, a walkthrough of open tasks, and a handover to your developer or a new vendor. We don't hold on to clients by being the only ones who understand how things work.

Question 6

What's your SLA?

Accepted Answer

For a dedicated team, the SLA is about pace and communication, not uptime, and it's in the contract: replies within 2 hours during business hours, participation in your standups, a demo every 2 weeks, a written report every week. We agree on the sprint scope before it starts, and if we're falling behind, you hear about it mid-sprint, not at the demo. An SLA for production incidents (response from 15 minutes, on-call duty, credits on the invoice) is a separate service, software support from $2,900/month. You can add it alongside the team, and we'll tell you honestly if you don't need it.

Question 7

Who exactly will write the code, and what if an engineer isn't a fit?

Accepted Answer

Before the contract you get specific CVs and talk to each engineer yourself, not to a manager. In the first two weeks you can ask for a replacement without giving a reason: we don't bill for the switch or for the new engineer's onboarding time. After that, a replacement for any reason takes 1–2 weeks, with an overlap period at our expense. Documentation and code review are set up so that one person leaving doesn't stop the project.

Question 8

We have our own developers and a CTO. How will you fit in?

Accepted Answer

That's our main format: priorities stay with your CTO or product manager, and we deliver. We work in your tools (Jira, Slack, GitHub), join standups and planning sessions, and follow your code style and review process. We don't impose our own processes; if we see your process losing time, we'll say so in the report instead of quietly changing it. If you don't have a technical lead, we'll bring in a hands-on team lead or suggest pairing the team with CTO as a Service.

IT Outsourcing / Dedicated Team

Situations where we help

You need developers in 2 weeks, not in six months

Your team lead quit, and the project stalled for a month

Six months of backlog and an overloaded team

Five freelancers later, the code is spaghetti

Let's estimate the budget for your task

Features and benefits

Your backlog, your priorities, our hands

A hands-on team lead and code review on every PR

Every task and every hour in the tracker

Code in your repository from day one

±1 engineer in 2 weeks

Management and code review aren't billed separately

How we work

Backlog review: 3–5 days, free

Trial sprint: 2 weeks, $3,900

Onboarding: 1–2 weeks

Productive work: month to month

Exit or handover: your call

What it costs

Dedicated engineers for your backlog

Real results

ERP/FSM Platform for Managing Contractors in the US

ERP modernization and a B2B portal for an auto parts distributor

MarchTracker: A Team Task Tracker for iOS, Android and Web

Frequently asked questions about IT Outsourcing

Read next

CTO as a Service

IT Consulting

Support

How to Choose a Software Development Company: 10 Criteria

Software Requirements Specification: A Complete Guide + Template

ERP/FSM Platform for Managing Contractors in the US