Working terms

Clear expectations make better products.

Q: What should be agreed before a GeeDook project begins?

The project scope, expected deliverables, responsibilities, timeline, payment milestones, third-party costs and support expectations should be defined before execution begins.

Q: What can be included in project handover?

Depending on the agreement, handover may include source code, project assets, documentation, configuration and the access required for continued operation and development.

Q: Who is responsible for third-party services?

Domains, hosting, cloud resources, external APIs, licenses and third-party subscriptions should have clearly defined ownership, payment and access responsibilities.

A successful project needs more than good engineering. Scope, responsibilities, decisions, payments, changes and delivery should be clear from the beginning so both sides can focus on building the right product.

Scope Defined before execution

Ownership Clear delivery terms

Responsibility Clear on both sides

Project scope

The agreed scope defines what the project is expected to solve and deliver. Features, important workflows, integrations, deliverables, timeline and acceptance expectations should be documented before execution.

Changes and new requests

Products evolve and new ideas may appear during development. Requests outside the agreed scope may require a revised estimate, additional time or a separate delivery phase before implementation.

Payments and milestones

Project payments can be connected to agreed milestones or delivery phases. The amount, timing and conditions of each payment should be defined in the proposal, agreement or contract before work begins.

Client responsibilities

The client should provide required information, content, decisions, approvals and access within a reasonable time. Delays in these inputs may affect the project schedule and delivery dates.

Delivery and ownership

The assets included in handover are defined by the project agreement. Depending on the scope, this may include source code, documentation, configuration, project files and the access required for continued operation and future development.

Third-party services

Domains, hosting, cloud services, external APIs, licenses, payment gateways and other third-party services may have separate costs and terms. Ownership, payment and access responsibilities should be agreed clearly.

Timeline and dependencies

Project timelines are based on the agreed scope and known dependencies. Changes in requirements, delayed approvals, unavailable third-party services or new integrations may require the timeline to be adjusted.

Support and future development

Bug-fix periods, maintenance, monitoring, improvements and future feature development are defined according to the project agreement or a separate support arrangement. Ongoing development is not automatically included unless agreed.

Project handover

The goal is not only to deliver a working product, but a system that can be understood and continued.

Handover should reflect the agreed project scope and give the client a clear understanding of what has been delivered, what they own, how the product is operated and what responsibilities remain after delivery.

Product assets Delivered assets should match the agreed scope.

Source and structure When included, source code should have a clear and maintainable structure.

Documentation Important operational and technical knowledge should not remain only in people's memory.

Access and security Sensitive credentials and production access should be transferred and stored securely.

Important boundaries

A clear project also defines what is not automatically included.

Unless explicitly included in the project agreement, ongoing content production, third-party fees, infrastructure charges, new features, major scope changes and indefinite support should not be assumed to be part of the original delivery.

New features New requirements may require a new estimate or phase.

External costs Third-party subscriptions and infrastructure costs are separate unless explicitly included.

Client content Text, media and business data should be provided by the responsible party defined in the agreement.

Ongoing support Long-term maintenance requires a defined support arrangement.

Planning a project?

Let’s define the problem, scope and responsibilities before we build.

Start a conversation View services