Time reserved for existing product
- Analysis and estimation
- Implementation, review and QA
- Deployment and documentation
Docodex - websites, applications and digital systems for business.
Monthly roadmap capacity
We turn the product roadmap into a monthly stream of prioritized features and improvements.
Pricing depends on reserved capacity, product complexity, backlog, QA, deployment and collaboration pace. Does not include unlimited features.

The service model
for whom
Startups, SaaS, internal applications, online stores and mobile applications with users, feedback and roadmap.
What we develop
Capacity is used for prioritized activities, not an unlimited list of deliverables.
Backlog and roadmap
Priorities may change, but we analyze the impact on started tasks and dependencies.
Transparent pattern
Analysis, estimation, implementation, review, QA, deployment, meetings and documentation.
The capacity is reserved for the agreed period; carryover exists only if the offer provides for it.
Overtime is estimated and approved in advance, and large tasks become milestones.
We replace ad hoc tasks with a monthly flow of decision, development, validation and reporting.
Ideas and issues that are not rated or ordered.
Changes started without estimate, dependencies or acceptance criteria.
Releases without review, QA, controlled deployment or rollback.
Code and infrastructure that slows down every new change.
Tasks and milestones
It has clear requirements, controllable dependencies, and can be analyzed, deployed, and tested responsibly.
Big modules, migrations and architectural changes are not hidden in a small subscription.
External projects
Repository, documentation, environments, build and deployment.
Architecture, dependencies, tests, security and technical debt.
Pickup, initial fix, refactoring, migration or separate project.
The evaluation does not guarantee project acceptance or delivery pace before the technical status is understood.
Evidence and reporting
Completed activities, time spent, blockages and recommendations.
Commits, reviews, deployments and important decisions in the agreed tools.
The risks and priorities for the next period remain visible.
The package reserves capacity, not unlimited functionality. Analysis, QA and deployment activities take time.
For a small backlog and recurring improvements to an existing digital product.
For products that need a constant pace of functionality and optimizations.
For products with active roadmap and need for higher recurring technical capacity.
Hours do not carry over automatically. Large tasks, overtime and complete new projects are estimated separately.
The choice depends on the product, risk, objectives and actual capacity required.
| Appearance | PackageDevelopment 10From €749 + VAT / month | RecommendedDevelopment 20From €1,390 + VAT / month | PackageDevelopment 40From €2,590 + VAT / month |
|---|---|---|---|
| Positioning | Development 10 | Recommended | Development 40 |
| Price | From €749 + VAT / month | From €1,390 + VAT / month | From €2,590 + VAT / month |
| What does it include? | 10 hours reserved monthly, prioritized Backlog, Analysis and estimation, Implementation and review | 20 hours booked per month, Monthly Planning, Features and Integrations, UI/UX and Refactoring | 40 hours booked per month, Backlog and milestones, Web, mobile and API development, QA and documentation |
| Suitable for | For a small backlog and recurring improvements to an existing digital product. | For products that need a constant pace of functionality and optimizations. | For products with active roadmap and need for higher recurring technical capacity. |
Process
Technology


Projects in other technologies are evaluated individually before collaboration is confirmed.
Do not submit passwords, keys, code archives or sensitive data through the form.
It is the reservation of monthly technical capacity for functionality, enhancements, integrations, UI/UX, testing and evolution of an existing product.
Indicative packages include 10, 20 or 40 hours per month. The exact capacity and activity types are defined in the offer.
Tasks are described, estimated and ordered by impact, risk, dependencies and period objectives.
We can develop pages, forms, modules, dashboards, roles, reports, automations, APIs and mobile features.
Not automatically. The capacity is reserved for the agreed period, and the carryover must be explicitly provided for in the offer.
Functionalities that exceed the capacity of a month are divided into stages or treated as separate milestones or projects.
Yes, analysis, review and testing are part of the time consumed. The level of QA depends on the project and the risk of the change.
Deployment can be involved and time consuming. Access, suitable infrastructure and a rollback procedure are required.
Planning, clarification and review meetings may consume the reserved time, according to the established work pattern.
Yes. The backlog can be reprioritized, with attention to started tasks, dependencies, and risk of direction change.
We request approval for overtime, move tasks to the next period or propose a separate milestone.
The minimum period and termination conditions are set out in the offer and contract, depending on the reserved capacity.
Yes, subject to the notice period and contractual terms. Closing includes handing over backlog status and completed work.
Yes. The report can include tasks, time used, deployments, bottlenecks and recommendations for the next period.
Ownership of the custom code, access to the repository and rights to the components are set out in the offer and contract.
Continuous development
We evaluate the product, backlog and required capacity before building the monthly plan.