Skip to content
Let’s talk

Your product.
Your next chapter.

A practical guide to the conversations and deliverables behind a thoughtful handover. Exact terms and scope belong in your project agreement.

Before the build

Agree the outcome, written scope, project accounts, deliverables, payment schedule and ownership terms.

Name the people who can approve changes and the systems the project may access.

During the work

Review working demonstrations and keep a record of decisions.

Raise scope changes explicitly, including the cost, timing, and effect on the agreed deliverables.

At the handover

Confirm which repositories, editable design files, configuration notes and operating instructions are included.

Transfer access through the agreed channels. Keep passwords, private keys and customer data out of public repositories.

The next chapter

Record who hosts and operates the product, which third-party services it depends on, and who owns each account.

Agree maintenance, update and support responsibilities. The exact handover is defined in your signed project agreement.

Let’s see what
your idea can become.

A rough sketch. A stubborn problem. An ambitious next chapter. You don’t need to have it all figured out.

Bring us your idea
01 / THE CONVERSATION02 / A CLEAR SCOPE03 / SOMETHING REAL