How we work with you
There are three ways to work with XSIS: a dedicated team, staff augmentation or project-based delivery. Each one sets out who directs the work, who manages the people and how cost is set.

In-house and outsourced teams
Behind all three is the same delivery model. Our own engineers lead the work, vetted outsourced teams add capacity where it is needed, and one standard applies to everyone. XSIS is a full-service software engineering company with in-house and outsourced teams. Our own engineers lead every engagement and are accountable for it. When the work needs more people or a skill we do not hold in-house, we add engineers from outsourced teams we have vetted. They join a team our people lead, under our contract, our standards, our security rules and our reviews.
XSIS leads
A named XSIS delivery lead and technical lead on every engagement.
Vetted teams
Outsourced teams are assessed by our senior engineers before they work on any client project.
One standard
The same terms, engineering standards and code reviews for every engineer.
No hidden people
A team map names every person, their role and who employs them.
Compare the models
Choose the model that matches how clear your outcome is and how much day-to-day management you want to carry.
| Criterion | In-house and outsourced teams | Dedicated team | Staff augmentation | Project-based delivery |
|---|---|---|---|---|
| Best for | Any engagement that needs more people or skills than one in-house team | Long-running products with changing priorities | Filling skill or capacity gaps in a team you already run | Defined outcomes with a clear end |
| Scope | Applies to every model | Your roadmap, planned again every cycle | Tasks set by your managers | Fixed in writing, changed only through change control |
| Who directs the work | Set by the model you choose | Your product owner sets the priorities | Your managers direct the work | You agree the scope and accept each milestone |
| Who manages the people | XSIS leads, and outsourced engineers work inside XSIS-led teams | An XSIS team lead runs the team day to day | You manage the work, and XSIS manages employment | An XSIS delivery lead runs the project |
| How cost is set | Follows the model you choose | Usually a monthly cost for the agreed roles | Usually time and materials, per engineer | A fixed price for a defined scope, or time and materials against a budget |
| How it scales | Capacity added from vetted outsourced teams, with your approval | Roles added or released with agreed notice | Engineers added or released with agreed notice | XSIS sizes the team to meet the plan |
In-house and outsourced teams
- Best for
- Any engagement that needs more people or skills than one in-house team
- Scope
- Applies to every model
- Who directs the work
- Set by the model you choose
- Who manages the people
- XSIS leads, and outsourced engineers work inside XSIS-led teams
- How cost is set
- Follows the model you choose
- How it scales
- Capacity added from vetted outsourced teams, with your approval
Dedicated team
- Best for
- Long-running products with changing priorities
- Scope
- Your roadmap, planned again every cycle
- Who directs the work
- Your product owner sets the priorities
- Who manages the people
- An XSIS team lead runs the team day to day
- How cost is set
- Usually a monthly cost for the agreed roles
- How it scales
- Roles added or released with agreed notice
Staff augmentation
- Best for
- Filling skill or capacity gaps in a team you already run
- Scope
- Tasks set by your managers
- Who directs the work
- Your managers direct the work
- Who manages the people
- You manage the work, and XSIS manages employment
- How cost is set
- Usually time and materials, per engineer
- How it scales
- Engineers added or released with agreed notice
Project-based delivery
- Best for
- Defined outcomes with a clear end
- Scope
- Fixed in writing, changed only through change control
- Who directs the work
- You agree the scope and accept each milestone
- Who manages the people
- An XSIS delivery lead runs the project
- How cost is set
- A fixed price for a defined scope, or time and materials against a budget
- How it scales
- XSIS sizes the team to meet the plan
Engagement models
In-house and outsourced teams
XSIS engineers lead and own the work; vetted outsourced teams add capacity and skills under the same standards.
See the service
In-house and outsourced teamsHow it works
XSIS engineers lead every engagement: a delivery lead and a technical lead who own the plan, the architecture and the quality.
When the work needs more people or a specialist skill, we add engineers from outsourced teams we have vetted, and you approve each person.
Everyone works under one contract, one set of standards and one review process, and reports through the same delivery lead.
When to choose it
You want one company accountable for a mixed team.
The work needs more skills or capacity than one in-house team, without a lower standard.
You want to see exactly who is on the team and who employs them.
How it is governed
A team map names every person, their role and their employer.
XSIS engineers review changes from outsourced engineers before they are merged.
Confidentiality and security terms are passed down in writing to every outsourced team.
Questions
What does “in-house and outsourced teams” mean at XSIS?
It means our own engineers lead every engagement and carry the responsibility for it, and we add engineers from vetted outsourced teams when the work needs more people or a skill we do not hold in-house. The outsourced engineers work under our contract and our standards, inside a team that our people lead.
Link to this questionWho is accountable if an outsourced engineer makes a mistake?
XSIS is. Your contract is with us, and our delivery lead answers for the work of the whole team, whoever employs each engineer. That is why our engineers review outsourced engineers’ changes before they are merged, and why one set of standards applies to everyone.
Link to this questionHow do you control security when outsourced engineers are involved?
Each outsourced engineer is bound by the same confidentiality and security terms as our own staff, passed down in writing. Access to your systems is given per person, limited to what the role needs, reviewed regularly and removed when they leave. If you need some work done only by XSIS engineers, or only from certain locations, we plan the team that way.
Link to this questionCan we combine engagement models?
Yes. A dedicated team can run your product while a separate project delivers a bank integration, or we can place a specialist in your own team beside a team we run. Each part has its own terms, and one XSIS contact coordinates them.
Link to this questionDedicated team
A complete team that works only on your product, run day to day by XSIS and directed by you.
See the service
Dedicated teamsHow it works
We assemble a team for your roadmap: engineers, designers and testers, with a team lead.
Your product owner sets the priorities and accepts the work. Our team lead runs the team day to day.
The team stays with your product, so knowledge builds up, and its shape changes with the roadmap.
When to choose it
You have a product or platform with a long roadmap.
Priorities will change as you learn, so a fixed scope would not hold.
You want a stable team without hiring and managing every person yourself.
How it is governed
Planning and review with your product owner at the start and end of every cycle.
Progress, risks and decisions reported at a rhythm you choose.
Regular reviews of delivery, quality and the shape of the team.
Questions
Who manages a dedicated team?
You decide what the team works on: your product owner sets the priorities and accepts the work. We run the team day to day through a team lead who plans the work, removes blockers, looks after quality and reports to you. Line management, performance and replacement of people stay with XSIS.
Link to this questionCan the team grow or shrink over time?
Yes. The team follows your roadmap. You can add roles when a new stream of work starts and release them when it ends. We agree each change with you in advance, with enough notice to bring people in properly or hand their work over cleanly. The notice terms are set out in the contract.
Link to this questionHow is the cost of a dedicated team set?
A dedicated team is usually charged as a monthly cost for the agreed roles, so you can plan your budget. The cost depends on the number of people, their seniority and skills, and any cover outside normal hours. If you prefer to pay for actual time, we can work on time and materials. You see the price and the timeline before we start.
Link to this questionCan we change the engagement model later?
Yes. Work often starts as a project and continues as a dedicated team, or a dedicated team is gradually replaced by your own hires. We plan the change with you, including handover and notice, and keep the same people where that helps.
Link to this questionStaff augmentation
Engineers and specialists who join your team, work in your tools and report to your managers.
See the service
Staff augmentationHow it works
We find engineers who match a role brief we agree with you, and you interview and choose them.
They join your team, use your tools and processes, and report to your managers.
We remain their employer or contracting party and look after pay, equipment, performance and replacement.
When to choose it
You have the management and the process, and need specific skills or more capacity.
You want direct control of the work, day to day.
The need is for a known stretch of work, such as a release or a migration.
How it is governed
Your managers direct and review the work.
Our account contact checks in with you and with each engineer regularly.
Access is limited to what each role needs, recorded, and removed when the placement ends.
Questions
What is the difference between staff augmentation and a dedicated team?
With staff augmentation, our engineers join your team and your managers direct their work day to day. With a dedicated team, we provide a whole team with its own lead, and we run it day to day while you set the priorities. Staff augmentation fits when you already have the management and the process. A dedicated team fits when you want us to carry more of that.
Link to this questionWho manages an augmented engineer?
Your managers direct the work: what to build, in what order, and how it is reviewed. XSIS stays the employer or the contracting party. We handle pay, leave, equipment, performance support and replacement, and our account contact keeps in touch with you and with the engineer.
Link to this questionHow is staff augmentation charged?
Usually on time and materials: a rate per engineer for the time they work, or a monthly rate for a full-time placement. The rate depends on the skills and seniority of the role and on any work outside normal hours. You see the price and the timeline before we start.
Link to this questionIs there a minimum commitment?
The commitment depends on the model and is agreed with you. A project runs to its agreed scope. Teams and placements have notice periods, so that people can join and leave properly and work is handed over. We set these terms out in writing before anything starts.
Link to this questionProject-based delivery
XSIS delivers an agreed scope against written acceptance criteria, with a named delivery lead.
See the service
Project-based deliveryHow it works
We agree a written scope and acceptance criteria with you before the build starts.
A named delivery lead plans, staffs and runs the project, and reports progress, risks and decisions.
You accept each milestone against the criteria. Changes go through change control.
When to choose it
The outcome can be described clearly: an application, an integration, a migration.
You want one company responsible for delivering it.
You need a known basis for the budget and the plan before you commit.
How it is governed
Milestones with demonstrations, accepted against written criteria.
Written change control for scope, cost and dates.
Steering meetings with your sponsor at agreed points.
Questions
How is the work accepted?
Against acceptance criteria we write and agree with you before the build starts. At each milestone we demonstrate the work and you test it against those criteria. If something does not meet them, we fix it. When everything in scope meets its criteria, you sign off the milestone or the project.
Link to this questionWhat happens if our requirements change during the project?
Requirements often change, and that is fine. Each change goes through change control: we describe the change, its effect on cost and on the plan, and you decide. Nothing changes the scope, the price or the dates without your written approval.
Link to this questionHow is a project priced?
A well-defined scope can be priced as a fixed price for that scope, with changes handled through change control. Where the scope is less certain, we price discovery separately and then the build, or work on time and materials with a budget we report against. You see the price and the timeline before we start.
Link to this questionWho is accountable for delivery?
It depends on the model, and we say so in writing. In project-based delivery, XSIS is accountable for delivering the agreed scope. In a dedicated team, XSIS is accountable for running the team well and you are accountable for its priorities. In staff augmentation, your managers direct the work and XSIS is accountable for the people it provides.
Link to this questionGovernance
However you work with us, the same controls apply.
Steering
Your sponsor and our delivery lead meet at agreed points to review progress, risks, budget and direction.
Reporting
Written reports at a rhythm you choose: progress, risks, decisions needed and quality measures.
Change control
Changes to scope, team or cost are written down, priced and approved before they take effect.
Quality gates
Code review, automated tests and a definition of done that every change meets before release.
Security
Named, least-privilege access, confidentiality terms for everyone on the team, and access removed when people leave.
From first conversation to running software
Every engagement follows the same path, whichever model you choose.
- 01
First conversation
You tell us what you need. We ask about the goal, the systems, the constraints and the people you already have.
- 02
Written proposal
We propose a model, the team or the scope, how cost is set and how the work will be governed.
- 03
Agreement
We agree the contract terms, including confidentiality, ownership and security, before any work starts.
- 04
People and access
You meet the people. We set up access to your systems and agree the working rules.
- 05
Delivery
We deliver in short cycles, demonstrate working software, and report progress and risks.
- 06
Run and review
We support what we built, review the engagement with you, and adjust the team or the model as needs change.
Questions about working with us
How do we choose an engagement model?
Start from two questions: how clear is the outcome, and how much of the day-to-day management do you want to carry? A clear outcome with an end points to project-based delivery. A product with a changing roadmap points to a dedicated team. If you already run a team and need skills or capacity, staff augmentation fits. We recommend a model in our proposal and explain why.
Link to this questionHow does an engagement start?
With a conversation about what you need. We follow up with a written proposal: the model, the team or the scope, how cost is set and how the work will be governed. Once you agree, we introduce the people, set up access and start. How quickly that happens depends on the roles and on the access your systems need.
Link to this questionWho is accountable for delivery?
It depends on the model, and we say so in writing. In project-based delivery, XSIS is accountable for delivering the agreed scope. In a dedicated team, XSIS is accountable for running the team well and you are accountable for its priorities. In staff augmentation, your managers direct the work and XSIS is accountable for the people it provides.
Link to this questionCan we change the engagement model later?
Yes. Work often starts as a project and continues as a dedicated team, or a dedicated team is gradually replaced by your own hires. We plan the change with you, including handover and notice, and keep the same people where that helps.
Link to this questionCan we combine engagement models?
Yes. A dedicated team can run your product while a separate project delivers a bank integration, or we can place a specialist in your own team beside a team we run. Each part has its own terms, and one XSIS contact coordinates them.
Link to this questionIs there a minimum commitment?
The commitment depends on the model and is agreed with you. A project runs to its agreed scope. Teams and placements have notice periods, so that people can join and leave properly and work is handed over. We set these terms out in writing before anything starts.
Link to this questionHow will we see progress?
Through written reports at a rhythm you choose: what was planned, what was delivered, what is at risk and what needs your decision. You also see the work itself, in demonstrations, in the backlog and in the code in your own tools. For projects, reports track milestones and change requests.
Link to this questionNot sure which model fits?
Tell us about the work. We will propose a model and explain why.
- Our team will call you within 24 hours during your preferred time slot
- Our team is available 24/7