Technical fit comes first
Review the technologies, condition, ownership and available access before committing to maintain the application.
CULVION / SOFTWARE & AUTOMATIONDESIGN · BUILD · IMPROVE
Take care of the software you already have
Keep useful software useful.
A slow screen, a broken integration or an update nobody wants to touch can hold a team back. Review the application, agree the priority fixes and release changes with a recovery plan.
No minimum engagement size. Scope and cost are agreed before work starts.UNDERSTAND BEFORE CHANGINGThe next release,
with fewer unknowns.
with fewer unknowns.
01
Source & ownershipAccess and licence terms to confirm
02
Reported issueReproduce the user's experience
03
Change & testAgree the fix and acceptance check
04
Release & recoveryName the owner and rollback route
A review plan, rather than a claim that a system is already verified.
Shaped around your work
A small fix should not depend on one person's memory.
Choose the part you want to make easier.
One part of your brief
Application assessment
Review available source code, documentation, hosting, dependencies and the release process to establish technical fit and important unknowns.
Supplier handoversApplication reviewsRecurring bugsPlanned upgradesSmall feature releases
What we agree before the buildAccounts, knowledge, permissions and the route to a person.+
The decisions behind a useful service
Understand the application before changing it.
A defined support arrangement
Separate incidents, defects, maintenance and new development. Agree service hours, priorities and escalation expectations in writing.
A safe route to release
Establish an appropriate test environment, deployment permissions and a recovery plan before a change reaches real users.
How we begin
Reproduce the problem. Make the change. Release with a way back.
Choose a step for the detail.
01
Understand the application
+Gather available documentation and walk through the product, its users and current issues.
What you reviewA fit assessment and list of missing access
02
Agree the priorities
+Review the issue list, risks, responsibilities and the work that should happen first.
What you reviewA scoped backlog and support proposal
03
Make and verify changes
+Reproduce the issue, implement the agreed fix and check it in the context of the application.
What you reviewA reviewed change and test findings
04
Release and keep records
+Follow the agreed release process and document the work, remaining limitations and next priorities.
What you reviewRelease notes and an updated backlog
What shapes the costSetup, third-party tools and ongoing care.+
A clearer commercial conversation
Start with the problem we can actually inspect.
Access, code condition and the ability to reproduce an issue affect the estimate. We separate investigation from fixes and agree the scope before taking on ongoing support.
Initial assessment
Time needed to understand the application, establish access and identify the work required before support can begin.
The agreed work
Defined fixes, upgrades and improvements, with the assumptions and change process visible.
Ongoing coverage
Service hours, monitoring responsibilities and continuing maintenance, scoped around the application.
Before the first conversation
Questions about software assessment & maintenance.
Can you support software built by another developer?
We can assess it. Acceptance depends on the technologies, code ownership, documentation, access and application condition. We explain the scope we can take on and the limits before starting.
Is 24/7 incident support included?
No coverage or response time should be assumed. Service hours, incident definitions, priorities and escalation are agreed in the support arrangement.
Can you fix a single issue?
Yes, subject to a technical review and a clear scope. There is no minimum engagement size, but an issue still needs enough investigation to make a responsible change.
Should we repair or rebuild the application?
That is a decision to investigate, not a default sales recommendation. We consider the business need, application condition, constraints and the cost of the available paths.
TELL US WHAT YOU HAVE IN MIND
What needs fixing before your next release?
Describe the issue or improvement. You can share technical details later.
A SMALL START. A CLEAR NEXT STEP.
- 01Your side of the story
The work, the problem or the idea.
- 02A scope that makes sense
Responsibilities, timing and cost.
- 03You decide what comes next
No commitment just by enquiring.
START HEREJust the essentials. The rest can wait.