Scope, Requirements and Delivery

Yes. That is the purpose of our paid specification stage. We interview the people involved, map the current process and produce a written specification of what will be built, with its scope, acceptance criteria and a fixed price.

It depends on the size of the work, and we confirm the timeline in the specification before you commit. Most projects take 8 to 16 weeks. Simple applications may take 6 to 8 weeks, while complex systems can take 16 to 24 weeks. Legacy system replacements typically take three to six months.

Working software that meets the agreed acceptance criteria, deployed and ready to use, with your existing data migrated. You also receive user training and documentation, and an agreed arrangement for support and hosting.

By keeping each Work Item tightly scoped, with what is in and out written down. We solve the core problem first and leave nice-to-haves for later stages, once real use shows whether they are needed.

Yes, and we recommend it. Start with the problem that costs you the most, prove the value, then add further Work Items as the business needs them.

That is normal. Changes are assessed, scoped and priced as a change or a new Work Item. You approve them before work starts, so nothing changes your budget without your agreement.

Most involvement is at the start, when we learn how the work is done, and near the end, when your team tests the software on real work. In between, we ask for regular feedback at progress demonstrations. We keep the time we need from your team as focused as we can.

Each Work Item has written acceptance criteria agreed before work starts. It is finished when it meets those criteria and your team has accepted it.

Yes. Because the work is split into Work Items, you commit to one stage at a time and see working software at the end of each. During development we also demonstrate progress regularly, so you see the system take shape.