Who leads the product and who is responsible for delivery?
Team structure and billing are separate decisions. A dedicated team can work iteratively; a fixed-price project needs a clearly defined scope.
Specialists integrated into your team
You set priorities and lead the product. We agree on roles, relevant experience, access and how specialists contribute to development and verification.
Dedicated team
We plan a team around the product’s needs. Product ownership, technical coordination, acceptance and changes in capacity are defined in the proposal.
Project with agreed deliverables
We define the workflows and the outcome to be accepted, then organize implementation. The client’s team validates requirements, provides access to systems and approves deliverables.
How do we set the price and track the budget?
UP2DATE’s development benchmarks are €8,000–€16,000 for a focused MVP and €16,000–€60,000 for a broader product, excluding VAT. Platforms, backend, integrations and testing define the scope. Infrastructure, licenses and support are budgeted separately; projects with additional requirements receive their own estimate.
| Model | What we agree |
|---|---|
| Fixed price | A fixed price suits a clear scope: deliverables, assumptions, exclusions and acceptance criteria. A change to any of these requires an impact assessment and a decision before implementation. |
| Time & Materials | In a time-and-materials engagement, priorities can change. We agree on capacity, rates, effort reporting and the points at which we review the remaining budget. The model is confirmed in the project proposal. |
What do we prepare before development starts?
Objective and decision-maker
We identify the users, main workflow, budget and target date. The client appoints the person who sets priorities and accepts the outcome.
Systems and access
We inventory the code, environments, documentation, APIs and contacts. We establish the access required and the data permitted for testing.
First delivery
We define the first version, exclusions and acceptance criteria. The start date depends on the team, access and clarification of dependencies.
What should a progress review show?
The working version and the client’s decisions form the basis of the review. Demo frequency and reporting format are agreed for the project.
- Features delivered and what has been accepted.
- Work in progress, blockers and dependencies on the client or suppliers.
- Effort spent and the remaining estimate, under the agreed commercial model.
- Proposed changes, their impact and decisions needed before the next stage.
What happens when a new requirement arises?
We describe it and assess its impact on scope, cost and timeline. The designated decision-maker decides whether to include it, defer it or replace another feature. We update the plan and acceptance criteria accordingly.
How do we decide whether a version is ready to launch?
Technical verification
Functional scenarios, permissions, integrations and errors, on the agreed devices and environments. Performance and security checks are defined according to requirements.
Client acceptance
The responsible person checks the complete workflow using approved examples and records acceptance or the issues to resolve.
Operational readiness
We clarify migration, monitoring, access, rollback and support contacts. Publication in app stores also depends on Apple’s or Google’s review.
What does handover and the end of the engagement include?
The contract establishes rights to the code, transfer conditions and notice periods. Third-party and open-source components retain their licenses. The handover inventory reflects what was actually built.
- Repository, delivered version and build and release instructions.
- Accounts, environments, configurations, and transfer or revocation of access.
- Documentation, dependencies, tests and open issues.
- Operational responsibilities, knowledge transfer sessions and handover acceptance.
We start with a conversation about your situation
The first 30-minute discussion is free. Prepare your objective, existing systems, budget constraints and the people involved. Detailed analysis, design and the proposal are agreed separately.