Working with us, from the first call to a system in use

Both, depending on the work. Fixed price suits well-specified scope and is worth the premium you pay for certainty; evolving work priced fixed usually produces either a padded estimate or an argument about change requests. We will tell you which we think fits and why.

It depends on current commitments, and we would rather say so than promise a start date we cannot staff properly. Discovery can often begin sooner than build.

Yes. Substituting the team after the pitch is a common industry practice and not one of ours. If someone has to change, you will be told rather than discover it in a standup.

You can. Working in increments means there is something usable at each stage, and code sits in your repositories from the start, so stopping leaves you with what has been built rather than nothing.

Often. Adding capacity, covering a specialism, or taking a self-contained part of the estate are all common. It works best when the split of responsibility is agreed explicitly rather than assumed.

You find out early, which is the point of short increments and honest reporting. Projects fail slowly while the status stays green; the value of frequent working software is that it is very hard to misrepresent.