A supporting service for existing products
Maintenance and ongoing development for apps and web systems
A steady technical partner for fixing issues, improving the product, and continuing development after launch. We help existing products stay stable and align their capabilities with changing business needs.Need steady support for an existing product?
Tell us what the system does, which technologies it uses, and what kind of work you need to move forward. We will come back with fit-check questions and a suggested working frame.
A working frame for a product that keeps moving
After launch, a product still needs fixes, improvements, dependency updates, new features, and release preparation. You can start with a one-off task or work within a steady monthly frame, with priorities set by task complexity and the agreed hour cap.Who it fits
Clients after launch, or product owners with an existing app or system who need a regular developer.What the hours cover
One-off task handling or monthly development time for fixes, improvements, testing, and continued development by agreed priority.How it starts
We review the system, understand the code and needs, then choose a suitable working frame.
Two situations this service is built for
A product after launch
The app or system is already in use and needs maintenance, improvements, and continued development based on what happens in practice.A system built elsewhere
There is an existing product, and you need a regular developer to enter the codebase carefully, understand the current state, and take on ongoing tasks.
Systems and technologies
The service is not limited to one technology stack. Existing products can be maintained, extended, or gradually migrated to newer technologies when that is the right move for the product:- Frontend: React, Angular, Vue, Next.js, and existing JavaScript sites
- Mobile: React Native, Flutter, and existing hybrid apps
- Backend: Node.js, .NET, Java, PHP, Python, and existing API services
- CMS platforms, WordPress sites, admin systems, and older legacy websites
- Maintenance, fixes, and upgrades for existing systems, alongside migration to newer technologies when it makes sense
What can be done within the hours
The monthly hours are used for actual development and maintenance work. The monthly scope depends on task complexity and the hour cap, not on a fixed number of tasks:- Bug fixes and issue investigation
- Performance and stability improvements
- New features and improvements to existing flows
- Integrations and external services
- Dependency updates and development-environment adjustments
- Testing and release preparation
Supporting existing AI capabilities
If the product already includes an AI capability, it can be handled within the agreed hour frame and scope. Continuous monitoring and around-the-clock availability are not included unless explicitly agreed, and AI provider costs remain separate.- Improving model instructions and checking answer quality
- Updating the data sources the capability depends on
- Handling integrations and API changes
- Reviewing fit when models or AI services change
- Tracking usage cost and response times within the agreed work
How the work starts
The service starts with a fit check and a conversation. There is no automatic subscription, and support is not promised for every system before the technical state is understood.System review
We understand what the product does, who uses it, what hurts today, and what already exists in the code and infrastructure.Technical fit check
We check repository access, local setup, documentation, dependencies, and technologies to see whether we can take responsibility professionally.Task priority
Tasks are ordered by urgency, product value, and complexity, with a clear view of what can enter the first month.Working frame selection
We choose between a one-off task, a basic monthly frame, or broader support according to the product state and desired pace.
A working frame that fits your system
You can start with a one-off task or choose a monthly frame according to the system state, task scope, and desired pace.- For fixing an issue, improving an existing system, or building a defined feature. We start by understanding the need and checking fit, then agree the scope and price before the work begins.
One-off task
Quote based on work scope
- For fixes, updates, and continued development, by agreed priorities and within the monthly hour cap.
Ongoing maintenance and development
From ₪3,000 per month
Basic frame of 10 monthly hours
- For products that need more hours, work across several systems, or ongoing development. The working frame is adapted to the needs and desired pace.
Broader support frame
Custom pricing
You can start with a one-off task. There is no requirement to join a monthly frame.
The work scope and terms are agreed after understanding the need and checking fit. Hosting, licenses, and external provider costs are not included unless agreed otherwise.
How the monthly task scope is decided
The work is not based on a fixed number of tasks. The same hour cap may cover several small fixes, one complex task, or a mix of both. Before each month or work period, the highest-value tasks are prioritized by complexity, risk, and user impact.
Service terms set in the proposal
Numerical terms such as response times, resolution times, rollover rules, and extra-hour pricing are set in the proposal according to the system, urgency, and service scope.- Response time and resolution time are defined separately in the proposal, according to task urgency and service scope.
- Unused-hour rollover, if offered, is defined in the proposal and is not set here in advance.
- Extra-hour pricing, commitment, and cancellation terms are defined in the work agreement.
- Reporting for used hours is agreed according to the work style and tools that fit the client.
- The cost and scope of the initial onboarding review are set after the system is understood.
- Hosting, licenses, and payments to external providers are priced separately from development hours unless agreed otherwise.
Related services
If you are still building a new product, start with the main development services. Ongoing maintenance is a supporting service for a launched or existing product.Maintenance and ongoing development questions
Can we join with a system built by another developer?
Yes, subject to review. Before ongoing work starts, we need to understand the codebase, development environment, documentation, dependencies, and system access. If the system is not a fit, that will be said before any commitment.
Can the hours be used for new feature development?
Yes. The hours can be used for new features as well as fixes, improvements, integrations, and release preparation. Priorities are agreed together by value, urgency, and complexity.
Is a review required before starting?
Yes. A technical fit check is required so we can understand whether the system can be handled professionally and what needs to be arranged before ongoing work starts.
What happens if a task is larger than the hour frame?
The task can be split into stages, the first part can be prioritized, or additional scope can be agreed. A large task is not promised inside one month if the hour cap is not enough for it.
Does the service include hosting and external services?
Not by default. Hosting, licenses, developer accounts, and payments to external providers are priced separately unless the proposal says otherwise.
How are response times decided?
Response times are set in the proposal according to the system type, task urgency, and support frame. They are separate from resolution time, which depends on the complexity of the issue or task.
How much does the service cost?
Monthly support starts at ₪3,000 per month for a basic frame of 10 hours. One-off tasks and broader support are priced according to the system and work scope. You can also ask about a single task without joining a monthly frame.