After Delivery
Delivery isn't the end of the relationship. It's the point where your infrastructure starts doing its job.
Once a project is launched, we want you to know what happens next — what is covered, what support is available, how maintenance works, and what happens if you decide to manage the infrastructure yourself or move to another provider.
Our goal is simple:
Build useful infrastructure without creating unnecessary dependency.
1. Launch & Handover
When your project is ready for delivery, we'll make sure you have the information and access you need to use it.
Depending on the project, handover may include:
Final configuration
Access and account information
Documentation
Training or onboarding
Relevant technical information
Outstanding items or known limitations
Support and maintenance arrangements
The exact handover process depends on the scope of your project.
You should understand what you've received and how it works.
2. Warranty
Where a warranty is included in your agreement, it covers defects or issues where the delivered infrastructure does not operate substantially as agreed.
A warranty generally addresses:
“It doesn't work as specified.”
It does not normally cover:
“We'd like it to work differently now.”
A new requirement, additional functionality, change in scope, or different business need is normally treated as a change request and can be assessed separately.
Your specific warranty period, coverage, exclusions, and conditions are defined by the applicable agreement.
3. Maintenance
Digital infrastructure needs care after launch.
Depending on the solution, ongoing maintenance may include:
Monitoring
Software and security updates
Configuration changes
Backups and recovery processes
Performance improvements
Infrastructure management
Technical support
Periodic reviews
Maintenance requirements vary significantly between projects.
Some solutions require ongoing management.
Others can operate with minimal intervention.
We don't recommend maintenance simply because we can sell it. We recommend it when the infrastructure actually benefits from it.
4. Ongoing Support
After delivery, you may still need help.
Depending on your agreement, support can include assistance with:
Using the infrastructure
Troubleshooting
Configuration
Technical questions
Changes to existing functionality
Integrations
Account or access issues
The available support channels, response expectations, and pricing depend on your service arrangement.
If you have an ongoing support or maintenance agreement, your requests are handled according to the terms of that agreement.
If you don't, additional support may still be available on an ad-hoc or project basis.
5. Service Level Agreements
Some managed services may include a Service Level Agreement (SLA).
An SLA defines the service expectations agreed between you and fortheworld.
Depending on the service, this may include:
Response times
Severity levels
Escalation procedures
Availability or uptime targets
Maintenance expectations
Support responsibilities
Not every project requires an SLA.
If one applies to your service, its specific terms will be included in your agreement.
Your agreement is the source of truth for your actual service commitments.
6. Changes After Launch
Launching a project doesn't mean the system can never change.
Businesses evolve.
Requirements change.
New opportunities appear.
Third-party services develop.
You may discover something that could work better once people are actually using the system.
That's normal.
Depending on the change, we may:
Adjust the existing configuration
Add new functionality
Connect another service
Improve an existing workflow
Create a separate project
Recommend a different solution
We'll explain the implications before making changes that affect scope, cost, timeline, or infrastructure.
Good infrastructure should be able to evolve.
7. You Are Not Locked In
We believe in building useful ecosystems, not creating artificial dependency.
Where appropriate and subject to the terms of your agreement, you should be able to take your infrastructure elsewhere if your needs change.
Depending on the project and arrangement, handover may include:
Documentation
Configuration information
Relevant credentials or access arrangements
Data export where applicable
Knowledge transfer
A transition period
Some third-party services may have their own contractual, technical, or portability limitations. We'll make those clear where relevant.
Your infrastructure should work for you — not hold you hostage.
8. What If You Take It In-House?
That's completely fine.
Your organisation may eventually decide that it makes sense to manage the infrastructure internally.
If so, we can work with you on the transition where this is technically and commercially possible.
The transition may involve:
Documentation → Access → Knowledge transfer → Handover → Transition support
The exact process depends on the infrastructure involved.
Our objective is to make the transition orderly rather than create unnecessary friction.
9. What If You Want Us to Keep Managing It?
That's fine too.
For organisations that don't want to manage the technical infrastructure themselves, we can provide ongoing managed services where appropriate.
This can allow you to focus on your organisation while we take care of agreed aspects of the underlying digital infrastructure.
The exact services, responsibilities, support levels, and pricing are defined per engagement.
You focus on your mission. We help keep the machinery running.
10. The Long-Term Principle
We don't think of delivery as:
Build → Invoice → Goodbye.
We think of it as:
Understand → Build → Launch → Learn → Improve.
Some projects are completed and handed over.
Some become long-term managed environments.
Some evolve into completely new projects.
There isn't one correct model.
What matters is that the relationship remains useful for both sides.
The Short Version
After delivery, you have choices.
Manage it yourself.
Let us maintain it.
Ask us for additional support.
Expand it as your needs grow.
Or eventually move it elsewhere.
The infrastructure should serve your organisation, not trap it.
We build ecosystems, not lock-in.
Build better. Connect smarter. Scale sustainably.
#ForPeopleForPlanet