One client projectFrom brief to handover

Build with AI, review progress with your client and deliver the next version. MainPath keeps code, checks and releases together in the project – so the handover includes more than a working link.

Appropriate access for the people working on the client project

One briefA history you can follow

From the first draft to the latest update, your code stays versioned. The team can see what changed and keep working from the shared project state.

  • Implement changes with your AI agent in the project
  • Connect tests and build results to the relevant version
  • Deliberately release the checked version to production
Follow changes through to release

The foundation is readyYou shape the result

Three building blocks for work your team can develop together and hand over with a clear history.

Start from a prepared foundation

The appropriate template creates a repository, project structure and pipeline. Your AI agents get shared guidelines for working on the code.

Check the next version

Tests and builds accompany your changes. Try the result on Dev and review it with the client before releasing to production.

Share variants where they belong

When several brands use the same product, manage branding and store listings as variants. Independent client products stay in separate projects.

From brief to handoverFour clear stages

  1. Define the brief

    Agree on what you are building, who will work on it and where the application will run. Start with a new project or supported existing code.

  2. Develop with AI

    Work in the shared repository. Your agent helps with implementation; changes, tests and build results stay associated with the project.

  3. Review together

    Show the version in the development environment. Check the agreed features with the client, then decide whether to release to production.

  4. Document the handover

    Hand over code and configuration with the appropriate access. Agree who will own the accounts, credentials, future releases and ongoing operation.

Built for this clientWith a foundation you can reuse

Belongs to the client project

  • Features, content and integrations from the brief
  • The appropriate access, environments and credentials
  • Acceptance, handover and the agreement for ongoing operation

Becomes your way of working

  • Prepared project structure and shared rules for AI agents
  • A traceable process for tests, builds and releases
  • Experience from this brief that helps with the next project

Reuse does not mean sharing credentials or client data. Decide which parts can stay shared for each product.

Your next client briefWith the handover in mind

Start with a manageable client project. Develop, check and deliver together – and agree on ongoing operation before the handover.

Questions about client projects

Can we bring an existing client project?

Yes, if the stack is supported. Your AI agent checks the existing code first and then guides the import. This does not automatically migrate arbitrary CMS or plugin setups.

Bring existing code

What belongs in a client handover?

The technical handover includes code, relevant configuration, required access and a clear release and operating process. Agree the rights to the application code in your client contract. MainPath does not replace that agreement.

Does each client project automatically get a separate server?

No. Assign a suitable server to the project. Projects can deliberately share a machine or run on separate servers. Plan the separation of data and operations to fit the brief.

Assign a server to a project

When is whitelabel a better fit than a separate project?

When several brands use the same product and shared logic. Branding, domains and store listings can then be managed as variants. Separate projects are often a better foundation for different requirements and independent development.

Understand whitelabel variants

Does the client need to use MainPath for acceptance?

Trying a deployed web application does not require a MainPath account. Working on or managing the platform project requires an account with appropriate access. You implement sign-in for the application’s own users in the application code.

Thank you for your request

We have received your request and will get back to you as soon as possible.

Would you like to talk to us directly?

Choose a time here for an introductory call with Robin.

Open the calendar in a new tab