Delivery
The work is built in steps that are usable on their own. At the end you have a running service, the access credentials, the source code and documentation.
Building happens in steps that are usable on their own, rather than in one large push that is shown to somebody only at the end.
Structure
Every step is cut so that it can do something by itself. There are two reasons: you see along the way what you are paying for, and if a project ends earlier than planned, something usable is still in place.
The basis is open systems, and they run on your infrastructure. What that means in detail is described on the building block pages: content management, maps, collaboration, knowledge systems.
Existing content, data and access are carried over. How much effort that takes was settled by the stocktaking in the first conversation, because surprises at this point are among the most expensive there are.
Result
You get a running service, access to it, the source code and documentation that somebody other than me can read.
On top of that comes an introduction for the people who will work with it, because a system is only finished when it can be used without having to ask.
Limits of this phase
There is no dependency that you have to buy your way out of later. Open source means you do not need me in order to carry on: you can take over running it yourself or commission somebody else.
And a project only closes with the handover. It is over when your organisation can work with the result, not when the last invoice is settled.
Frequent questions
Who owns the result?
You do. Source, data and access are yours, and the systems underneath are open.
What about the old content?
It comes along. The stocktaking in the first conversation has already shown how much effort that takes.