An initial product review
Inspect the code, setup, documentation and known issues before recommending changes.
Technical support that keeps
your product working and improving.
Get help with product issues, software maintenance and focused improvements. We review the existing system before agreeing what to change.
For existing products, including systems built by another team.
A reported problem.
A verified improvement.
An illustrative support flow for a sign-in issue shows why reproducing and checking the problem matter.
Example scenario
Some users cannot finish signing in.
What the numbers show
- 1Collect the contextRecord the affected flow, error message and steps, without asking for passwords.
- 2Reproduce and assessInvestigate the issue in an appropriate environment and agree its priority.
- 3Make the fixChange the relevant behaviour and check nearby flows for regressions.
- 4Verify and releaseConfirm the agreed result, prepare deployment and record the change.
A practical support scope,
agreed with your team.
Support is planned around the product’s needs and available access, not an assumed unlimited service.
Useful when
- Recurring bugsInvestigate reproducible problems and fix the affected behaviour.
- Maintenance falling behindReview dependencies and software updates, including compatibility before release.
- Small improvements piling upPrioritise focused changes that make existing workflows easier to use.
Issue investigation and fixes
Reproduce the problem, identify a cause and make a scoped change.
Dependency maintenance
Review updates and test their impact on the product’s existing behaviour.
Progress and change notes
Keep priorities, verification and handover information visible to your team.
Get the context.
Keep priorities clear.
We establish access and ownership before starting ongoing work.
Review the product
Understand the codebase, setup and known issues; identify missing access or documentation.
You leave withAn initial assessment
Agree the work queue
Prioritise fixes and maintenance, with clear limits for each piece of work.
You leave withA scoped set of tasks
Fix, verify and review
Deliver agreed changes, record the checks and review what should come next.
You leave withChecked changes and an updated work queue
Questions before we start.
Is deployment the main problem?If releases, environments or monitoring are the recurring source of trouble, a DevOps review may be the better starting point.Explore DevOpsCan you support software another team built?
Yes, subject to reviewing the codebase, access, dependencies and documentation. The initial assessment helps us agree what we can take responsibility for.
Is support available around the clock?
Availability and response expectations are agreed for each project. There is no default round-the-clock or emergency-response commitment on this website.
Does support include new features?
Small improvements can be part of the agreed scope. A larger feature or redesign is assessed separately so its impact on priorities and effort is clear.
What access will you need?
That depends on the task. We agree the minimum necessary repository, test environment and diagnostic access, and how credentials are shared securely. Never put passwords in a contact form or an email.
Two ways in.
Both reach a person.
Both reach the studio directly.