imbahub
Menu +
US
Talk to us
IMBAHUB / Websites

A website your team can take forward.

A successful delivery includes more than a working homepage. We plan website projects around clear handover points, so you know what is delivered, which accounts you need and how future changes will be handled. Rights and ongoing services belong in your actual agreement.

From commissioning to responsibility

  1. Define

    Agree files, rights and responsibilities before development.

  2. Rehearse

    Let the receiving team complete an everyday task.

  3. Hand over

    Confirm access, documentation and ongoing operations.

Commission the handover alongside the website

The gap often appears after launch: someone needs to update a service, but nobody knows who controls the project or whether that change is included. A useful delivery specification describes both the finished website and the conditions for maintaining it. An editor login does not replace documentation about hosting, dependencies and responsibility.

We begin with the tasks your team will perform. Will you update contact details, publish articles or commission further development? These choices affect the content model, introduction and handover exercises. A small consultancy with one editor needs a different arrangement from an organization coordinating several regional teams.

Separate project files from usage rights

A project may combine custom code, reusable components, photography, fonts and external services. Receiving files does not automatically give you unrestricted rights to every part. Ask for an inventory stating what you may use, modify and transfer. We do not replace specific license conditions with a promise that everything is yours.

For a consultancy, a sensible scope might include the website project, content, an editing introduction and named operational contacts. A larger team might also need a responsibility matrix and a rehearsed publishing process. Both could have ten public pages; the work required for a reliable handover would still differ.

PartWhat to clarify
Project and contentDelivered material and usable formats
Images and licensesPermitted use and restrictions
Accounts and hostingAccount holder, access and billing contact
SupportIncluded work, contact route and separate costs

Rehearse the first working day

An editor should complete an ordinary task before the handover is accepted. For example, change a telephone number in the preview version, check the relevant page on mobile and demonstrate the agreed way to correct a mistake. The exercise must use the permissions and tools that the delivered project actually provides.

Record outstanding issues separately from new requests. Fixing a broken link is different from replacing an approved site structure. An agreed issue list gives both parties a clearer basis for further work and prevents a vague approval from hiding unresolved dependencies.

  • Name the person who receives the delivery.
  • Keep an access inventory without placing passwords in email threads.
  • Confirm who runs hosting, domain renewals and support afterwards.

Define the project and its ongoing dependencies

Development can be scoped as a project, while domains, hosting, licenses and future changes remain separate cost decisions. Those costs still need explaining when the build is purchased as a one-off service. Share your current website and the tasks your team needs to handle. We can then specify the build, documentation and operational responsibilities without promising independence from services the site still relies on.

Questions, answered

Does delivery automatically include ownership of all code?

No. Delivered files and rights must be specified in the agreement. Third-party code, images and licenses may have their own conditions.

Could another developer take over later?

Prepare for that with documented dependencies, appropriate project access and clear rights. Whether the solution can be transferred must be assessed for the actual project.

IMBAHUB

Let’s plan your website

Tell us what your team needs to take over.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.