Keep the client relationship. Hand over the whole project.

For agencies, software companies and consultancies that need a complete project delivered — requirements, build, testing, deployment and handover — under the scope they agree with their client.

  • Agencies

    Design, marketing and digital agencies whose client needs software the agency does not build in-house.

  • Software companies

    Firms with more projects than capacity, or a project outside their stack, that need the whole thing delivered rather than staff added.

  • Consultancies

    Advisers who have specified a process or a system for a client and need it built to that specification.

How an engagement works

  • Your client, your relationship

    You own the client relationship and the commercial agreement with your client. Primanza's agreement is with you.

  • A whole project, not a seat

    Primanza takes the project from discovery to handover under the same six-stage model as any direct project, with the scope, acceptance criteria and timeline written in the proposal to you.

  • Communication lines agreed

    Whether Primanza speaks with your client directly during discovery and demonstrations, or only through you, is decided in the agreement.

  • White-label where agreed

    Delivery under your brand — documentation, demonstrations and handover presented as yours — is available where the written agreement says so.

How it starts

  1. Write to partners@

    The client's problem as you understand it, the systems involved, the scope you have agreed or expect to agree, and how you want to work.

  2. A reply from the founder

    Within two business days, Monday to Friday.

  3. Discovery with or through you

    As agreed: with your client in the room, or from your specification.

  4. Proposal to you

    Deliverables, acceptance criteria, timeline and commercial terms, addressed to your firm.

What the written agreement settles

Partnership terms are agreed individually; there is no standard programme. Every agreement answers these before work begins:

  • Who the parties are, and who the end client is
  • Scope, deliverables and acceptance criteria for the project
  • Whether delivery is under Primanza's name or white-label under yours
  • Who speaks with the client, and when
  • Ownership, licences and access at handover
  • Confidentiality and non-solicitation
  • Commercial terms and payment schedule
  • Support after launch, if any, and who provides it
  • How either side ends the arrangement, and what happens to work in progress

Start the conversation

partners@primanza.com is read by the founder. A reply comes within two business days, Monday to Friday.

Discuss your project.

Describe the problem, the systems involved and what a good outcome looks like. The discovery conversation starts from there, and the proposal puts the scope in writing.

  1. You write

    Through the form or to hello@primanza.com: the problem, the systems involved, what a good outcome looks like, and any constraints you already know.

  2. We talk

    A discovery conversation about the workflow as it runs today and the outcome you need. A reply comes within two business days, Monday to Friday.

  3. The proposal

    Deliverables, assumptions, dependencies, acceptance criteria, timeline and commercial terms, in writing, for you to accept or change.