Working with XSIS

We estimate from the scope, not from a rate card. After a first conversation we break the work into parts, size each one and write down the assumptions behind the estimate. The main drivers are the number of systems and integrations, the state of your data, security and regulatory requirements, the testing needed and the seniority of the team. You receive a written estimate with options, so you can choose what to do first. You see the price and the timeline before we start.

Link to this question

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.

Read more: Dedicated teamsLink to this question

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.

Read more: Staff augmentationLink to this question

It can. Cost depends on the roles, seniority and skills the work needs, and on who can provide them. You see the price and the timeline before we start. Any change to the mix is agreed with you first.

Read more: In-house and outsourced teamsLink to this question

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.

Read more: Project-based deliveryLink to this question

Usually as a fixed scope with a fixed fee, agreed after a short scoping conversation, or as a number of consultant days for open-ended advisory work. The price depends on the size of the estate to review, the number of options to compare and the depth of analysis the decision needs. You see the price and the timeline before we start.

Read more: Technology and architecture consultingLink to this question

It is usually a fixed fee for a fixed scope, agreed after a short scoping call. The price depends on the number of business areas involved, how many use cases are assessed in depth and how much hands-on review of your data and systems is needed. You see the price and the timeline before we start.

Read more: AI readiness assessmentLink to this question

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.

Read more: How we workLink to this question