Ongoing support
Develop an existing backend
We extend an existing backend within a limited work package, with prioritised tasks and documented changes.
Ongoing support / Backend development & data architecture
VAT-exempt under section 19 of the German VAT Act
Develop an existing application
Continue developing your existing application across frontend and backend within a prioritised development block.
US$3,349.00
Total price · one-offVAT-exempt under section 19 of the German VAT Act
- A four-week development period with twenty hours total
- Prioritise up to three related tasks across frontend and backend
- Address agreed changes with relevant integration and regression tests
Your enquiry is non-binding. An order is created only when you accept our quotation .
Image 1 of 4
Service scope
Your result
- Traceable development progress within the agreed allowance
- Documented interface and backend changes with open remaining scope
Included
- A four-week development period with twenty hours total
- Prioritise up to three related tasks across frontend and backend
- Address agreed changes with relevant integration and regression tests
- Hand over documented progress, allowance used and open tasks
Excluded
- Automatic renewal or unlimited feature development
- Complete rebuild, on-call availability or guaranteed immediate response
- New provider fees and extensive data or infrastructure migration
Which projects does this service suit?
Suitable if …
- Several small tasks affect both sides of an application
- An existing product needs further development over a limited period
Not suitable if …
- A fixed extensive result is expected regardless of necessary effort
- A production emergency service or permanent team is needed
Possible overlaps with: Develop an existing backend. If you enquire about these services for the same project, we check for duplicated work before commissioning. Your selection also shows a notice.
What this covers
How do we extend an application when changes affect frontend and backend?
Many product changes do not end at the interface. A new field may also need storage, validation and an adjusted API. This package groups related tasks across both application sides. Twenty hours total are agreed over four weeks.
Up to three tasks are prioritised and assigned criteria. Familiarisation, coordination, development and tests count towards the allowance. A small task should ideally finish as a connected flow rather than starting many functions. The closing report makes progress and open work visible.
One complete small change often helps more than many half-finished ones
Frontend and backend must understand the same data and states. A change finished on only one side often remains unusable. We plan prioritised tasks around a testable result.
The existing stack and its quality determine familiarisation effort. The package is a work allowance, not a blanket promise for every wish list. Major dependencies are identified early. Further work after the allowance requires a new agreement.
Does this sound familiar?
A change affects several layers
New fields or states must fit across the application. One block connects interface, API and backend rule.
Improvements follow the first launch
Specific usage experience can produce a small task list. We prioritise testable changes rather than an open-ended ongoing commission.
You need a manageable next step
Four weeks and twenty hours provide a clear frame. Progress is documented before deciding on further development.
How we approach it.
Group tasks into complete flows
We examine dependencies and define up to three related tasks. Order follows agreed usefulness and feasibility.
Coordinate frontend and backend work
Changes are implemented across affected layers within the allowance. Relevant tests check that the whole flow works.
Hand over results and open work
Handover describes code changes, checks and scope used. Started or unresolved tasks remain expressly identified as such.
After handover
Review the finished flow and open tasks in the closing report. Further work is prioritised again: familiarisation, coordination, development and tests jointly count towards twenty hours.
An additional backend allowance is normally unnecessary for the same task block. Boundaries follow actual functions and avoid duplicate familiarisation.
Describe the intended function and an example of a successful process. Name existing systems and the roles involved without sharing real customer data or credentials.
After your enquiry, we clarify which data the function processes, which rules it must follow and which systems it must contact. Required documents and test access are agreed separately.
Terms used in this service
What does that mean?
- Full-stack change
- A connected interface and backend change. It may affect input, data contract, storage and feedback together.
- Prioritisation
- Deliberately ordering tasks within limited time. It considers usefulness and dependencies and prevents an unlimited parallel wish list.
- Integration check
- Testing how several parts cooperate, such as whether interface and backend use the same new rule and completion status.
Before your enquiry
Questions about the offer.
What is included, what do you need and what happens after your enquiry?
The process in detail →Is this an ongoing development contract?
No. The package covers one defined period and scope. Continuation is agreed separately, not automatic.
Are twenty hours per week included?
No. Twenty hours is the total across four weeks, including familiarisation, coordination, implementation and tests.
Can a new task be added during the period?
A priority change can be agreed. Work already done still counts; new tasks do not automatically increase the total allowance.
Are all tasks published?
Initially, a tested version is created in the agreed environment. Production publication and required approvals are expressly agreed.
When does the backend-only package fit better?
When all tasks clearly lie in the backend. This block fits changes requiring interface and server together; identical work is not planned twice.
When does work begin?
We confirm the start and delivery deadline in writing after reviewing your documents. The agreed scope and complete source data determine the schedule.
Which access is needed?
A working project, repository and suitable test environment Responsible prioritisation and specific criteria for intended tasks Credentials must not be included in the enquiry. Details are agreed only after written commissioning.
What happens after handover?
One written follow-up round is included. The service scope lists the analyses, designs or technical changes covered by the package. We agree additional work with you before it begins.
Read more on this topic
Website maintenance: which tasks are included?
Updates, errors and backups need named owners. Distinguish maintenance, further development and operational support.
Read the guide ↗Related services
These may fit too.
Implementation
Build an MVP
We turn a clearly scoped product idea into a first usable web application, with one core journey, an interface and a backend.