Getting to know the application
For existing software, we review its condition, available documentation, access, and dependencies before agreeing the support scope.
Maintenance & support
Keep the software working as your business changes.
A release is the beginning of the software’s working life. We look after the agreed maintenance, address problems, and help you plan the improvements your team needs next.
Discuss your projectWhen someone needs to own what happens after launch
People discover new requirements once they use a product. Connected services change, updates become necessary, and an occasional problem needs investigation. Without clear ownership, each of these can become a separate scramble.
We agree what the application needs, what your existing providers cover, and what SweatMtn will take care of. That can include an application we build or an existing product that we first review and take over.
What we take care of
Routine care and fixes
We handle the maintenance and issue resolution included in the engagement, and explain when a request is a larger change to the product.
Planning improvements
We help prioritize new requirements and turn them into an agreed sequence of work, with review points before releases.
Keeping responsibilities clear
We define how to report an issue, who responds, the agreed coverage, and which hosting or third-party services are handled elsewhere.
What we need from you
Give us a business contact who can explain the impact of problems and help set priorities. We’ll handle investigation and the agreed software work, and keep you informed about the next steps.
An ongoing arrangement your business understands
Support needs a defined scope. We agree coverage, response expectations, maintenance responsibilities, commercial terms, and how additional development will be approved.
- An application review or handoff into support
- Agreed issue reporting and support arrangements
- A plan for maintenance and future releases
Questions about maintenance & support
Can you support software built by another provider?
We can review it first. Access, documentation, condition, and dependencies determine what we can take responsibility for and whether any initial remedial work is needed.
Are new features included in support?
The engagement defines what is included. Larger features or changes can be scoped separately, with the cost and timing agreed before work begins.
Can hosting be part of the arrangement?
Yes. Hosting, monitoring, backups, and application maintenance can be planned together. We state which responsibilities are included so there is no gap between providers.
Tell us what you want to change.
Bring the problem, the idea, or the system that needs attention. We’ll help work out the next step and what we can take off your plate.