Skip to content

Before the brief. After the handover.

Start with the questions that affect a real project decision. Commercial terms, schedules, and rights must be confirmed in the agreement shared by the company and its client.

16questions · 4 parts of working together

Agree on scope, timing and ownership before work begins.

Getting started and defining scope

You can explain the problem before every document is ready. A useful estimate still needs context about the users and the intended outcome.

What should we prepare for an initial discussion?

Describe the goal, users, current workflow, problems, and connected systems. Existing screens or documents can help, along with known budget or date constraints. Remove unnecessary personal data from examples.

You do not need a complete technical specification first. The initial brief should distinguish what you know from the questions that need joint investigation.

Read the project brief guide
Should we start with a website or a mobile app?

Consider how people will access the product, how often they use it, and which device capabilities are required. A web product may suit link-based access across devices; an app may fit a workflow with different device or usage requirements.

Compare distribution, updates, testing, and ongoing operation as well. There is no single answer that applies to every project.

Compare web and mobile
Can you take over an existing system?

Start with a review of the code, environment, tests, and available rights to establish what can be extended and what needs attention first. Acceptance of the work depends on understanding the system’s actual condition.

Prepare documentation, run instructions, external dependencies, and an authorized access contact. Having the source code alone may not expose every risk.

Explore the service scope
Do we need to choose the technology first?

No. Share any constraints from your internal team or existing systems early. Otherwise, begin with the required behavior, data, and the people who will maintain the result.

Technical choices should explain their reasons, limitations, and operating requirements instead of relying on popularity alone.

How we assess technologies

Estimates, schedules, and changes

Clear assumptions make estimates reviewable and reduce mismatched expectations during delivery.

Are there fixed prices or standard development packages?

This site does not publish a fixed software-development price. Workflow scope, integrations, data, and acceptance criteria affect the work involved. A proposal should identify inclusions, exclusions, assumptions, and external costs.

An unclear brief may need a separately agreed discovery or assessment stage, with its own deliverables and commercial terms.

How is the development schedule determined?

It depends on work sequence, complexity, access to external systems, and stakeholder review or approval time. Share the desired launch date and its business reason so scope or delivery stages can be assessed against it.

An agreed schedule should identify dependencies and how delays in information, approvals, or external services will be handled. One duration cannot be promised for every project.

How do we change or add features during the project?

Record the request and its purpose, then assess the impact on timing, cost, and existing work. Agree whether it belongs in the current release, replaces another item, or moves to a later phase.

Distinguish a defect against existing acceptance criteria from a new requirement, and confirm the changed scope before implementation.

Read about change control
Are payments milestone-based, and is a deposit required?

Payment stages, milestones, and any deposit conditions are set out in the proposal and agreement for that project. This site does not establish a standard deposit percentage or a universal non-refundable deposit rule.

Confirm what work or acceptance event each payment relates to, and how disagreements will be handled.

Read the terms of service

Working together and receiving the work

Knowing who reviews what, and what is handed over, helps both teams keep the project moving.

How do we follow progress and provide feedback?

Agree a main contact, a place for recorded decisions, and review checkpoints at the start. Reviews may use demonstrations, a test environment, or a task list according to the project arrangement.

Consolidate decision-maker feedback with reproduction steps, observed behavior, and the desired result. Meeting frequency is determined by the project rather than a universal schedule.

Explore the working process
Who owns the source code and intellectual property?

Ownership or usage rights for project-specific work, transfer conditions, and related obligations belong in the contract. Existing tools, libraries, and third-party software retain their own license terms.

Before starting, identify which repositories, documentation, design files, and access rights form part of handover. Do not assume that ownership of every component transfers automatically.

Prepare a software handover checklist
What is used to accept the work?

Use the agreed scope and acceptance criteria: which actions a user role can complete, which data must be rejected, or what happens when an integration is unavailable.

Reviewers should exercise representative scenarios and record results. Remaining limitations should be identified and accepted together before closure, rather than judging only whether screens exist.

See verification and acceptance
Do you need production credentials or customer data immediately?

Do not include credentials or unnecessary personal data in the initial brief. Start with sample or redacted data. If production access becomes necessary, agree its purpose, permission scope, and an appropriate transfer channel.

Test accounts and task-specific access limit exposure to unrelated systems. Review and remove unnecessary access when the work ends.

Hosting, ongoing support, and refunds

Separate operating expenses and post-delivery responsibilities from the development scope.

Are hosting, domains, and external services included?

The proposal determines what is included. Identify who owns each account, who pays the provider, and which charges recur monthly, annually, or by usage.

Plan account and data transfer from the outset. Using cloud services does not automatically make the company responsible for every operating cost or availability commitment.

Explore Cloud Infrastructure
What support is provided after handover?

Correction periods, maintenance, dependency updates, and new features should be distinguished in the agreement, along with the actual reporting channel and response arrangements.

Infrastructure operations, backups, monitoring, and incident work may be separate services from software development. This website does not establish a 24/7 support commitment or a guaranteed SLA.

How would we move to another operator or hosting provider?

Review code and data rights, account ownership, and dependencies first. Then plan backups, the new environment, validation, and a rollback path.

Migration effort depends on the system and the existing provider’s terms. Assess it explicitly and list what the receiving team will get.

Read the software handover guide
When can a refund be considered, and how long does review take?

The company policy includes cases such as a service not supplied as described, unresolved technical problems that prevent use, duplicate or incorrect billing, and cancellation within an applicable money-back period. The policy also contains exclusions.

Requests are reviewed and processed within 7 business days; this is not a promise that funds arrive in that period in every case. Payment-channel refunds, account credit, and proportional refunds follow the policy and the assessment.

Read the complete refund policy