Bug investigation and fixes
Report what happened, what you expected, and who is affected. We investigate the issue, implement a fix, and test the affected behavior before release.
Keep your software
in good shape.
When your project no longer needs active development, keep it cared for. Submit bugs for us to fix while we keep dependencies current and regularly scan the codebase for defects.
Discuss maintenanceA fixed monthly maintenance fee, lower than the active development engagement. We agree the software covered, care priorities, and engagement details with you before the transition.
Who it suits.
For products that are in use and need ongoing care after feature development settles down. Maintenance suits a stable roadmap with bugs to resolve and a codebase to keep current. If you need substantial new features or larger changes, active development is the better fit.
What the monthly fee covers.
Dependency updates
Review and update the libraries and packages the software depends on, checking compatibility and the effect of those changes on the application.
Regular defect scans
Regularly scan the codebase for defects and investigate the findings. Confirmed issues join the maintenance work alongside bugs reported by your team.
Who does what.
Banana Pancakes
Handles technical investigation, fixes, dependency updates, defect scans, and verification. We agree the engineering and communication contacts when setting up maintenance.
Your team
Reports problems and explains their effect on users and the business. Reproduction steps and examples help us investigate; you also help confirm whether a proposed change meets the original need.
How priorities work.
Reported bugs and findings from updates or scans go into the maintenance backlog. We assess their effect on users, risk to the software, and any dependencies before agreeing the order of work.
A report is the starting point for investigation. We establish what is wrong, make the change, and verify the result. If a request calls for substantial new functionality, we discuss it as development work and agree the next step with you.
Pancake Studio is the shared workspace we are developing for scope, decisions, progress, and review. The portal is in development.
As your project changes.
Moving from active development to maintenance is an agreed change in the engagement. We identify the software to care for, review known issues, and confirm the monthly fee and maintenance priorities.
Maintenance keeps attention on the product as it is used. When new goals call for sustained feature work, we can discuss moving back to active development and agreeing a new set of priorities.
Explore developmentA few practical questions.
What does the monthly fee cover?
Active development covers the agreed feature work and improvements, engineering direction, project coordination, implementation, review, testing, and releases. Maintenance covers bug fixes, dependency updates, and regular codebase scans for defects. We agree the scope and fixed monthly fee with you before starting.
What happens when active development ends?
When your project no longer needs ongoing feature work, it can move to maintenance at a lower fixed monthly fee. We agree the transition and care priorities with you. If substantial new work comes up later, we can discuss a return to active development.
How are bugs handled in maintenance?
You submit a report describing what happened, what you expected, and who is affected. We investigate, prioritize the issue by its impact and risk, implement a fix, and test it before release. Dependency updates and regular defect scans also help identify work beyond reported bugs.
Tell us what your project needs.
Share a short outline. We’ll discuss the work, the monthly fee, and how to get started.
Discuss your project