VulCode

White label software development for agencies

You sell and run the client, we build under your brand: websites, stores, apps and integrations. That is how we work day to day with the Aphrodi branding agency.

Commerce and tech
A build review for the agency: the design laid over the test version, the checked places and the sign-off
The client's test site under the agency's brand, with the client's note, on a phone

Who does what in a white label project

We agree the split before the first project and keep to it in every one after.

Agency client

  • The brief

    The client talks to the agency and knows its brand and account manager.

    Agency: brief
  • Handover

    The invoice comes from the agency.

  • Rights to the code

    In full white label and with a technical contact, the code rights pass to the agency or its client after payment.

Agency

  • Strategy and design

    Brief, identity, mockups and approvals on the agency side.

    VulCode: design
  • Handing over

    The agency hands the finished product to the client.

    Agency client: handover

VulCode

  • Code and launch

    We build under the agency's brand, in its repository or with a code handover.

    Agency: launch
  • Care in the background

    We stay in the background for maintenance.

  • The agency's brand in the repository

    In full white label we do not appear in communication, and the repository and documentation use the agency's brand.

Three ways to work with an agency

Agencies want to work with a technical partner in different ways. Each model goes into the contract.

  1. Joint team

    Who talks to the client: both sides

    In communication and on the invoice

    Whose brand in communication: both, if agreed. Invoice to the client: per contract.

    Code rights

    Per contract

  2. Technical contact

    Who talks to the client: the agency, us on technical matters

    In communication and on the invoice

    Whose brand in communication: the agency's. Invoice to the client: from the agency.

    Code rights

    Go to the agency or its client

  3. Full white label

    Who talks to the client: only the agency

    In communication and on the invoice

    Whose brand in communication: the agency's. Invoice to the client: from the agency.

    Code rights

    Go to the agency or its client

Aphrodi: the agency designs, we build

A design and branding agency we share projects with. Aphrodi creates identities and designs, and we write the code.

The Aphrodi home page
The Aphrodi home page
The Aphrodi client panel with the wallet, project budgets and support
Client panel
Services on the English version of the Aphrodi site
Services, English version
The agency's story on the English version of the Aphrodi site
About, English version

Aphrodi

  1. Aphrodi website: 1 week

    The agency website built from its design, with a portfolio CMS

  2. Client panel: shared core

    Aphrodi's client panel on a shared multi-brand core

  3. UI/UX design: Aphrodi

    Interface design by Aphrodi, bought from us together with the build

  4. Team panel

    An internal team panel for clients of both brands

What goes into a contract with an agency

This is the subcontracting agreement we sign with an agency. The wording is agreed case by case, and the numbers match the notes beside it.

  1. Confidentiality and agency clientsWe do not contact agency clients outside the agreed scope and we do not poach them. It is a contract clause, not a promise.
  2. Copyright in writingWe put the transfer of economic rights in writing, because otherwise it is void. The contract lists the fields of use, so the agency knows exactly what it may do with the code.
  3. Billing modelA fixed price per project or a block of hours for ongoing work, described in billing models.
  4. Care after launchWe run maintenance on the agency's behalf, and the client keeps talking to the agency.
Subcontracting agreement
Agreement on cooperation in delivering projects
File
subcontracting-agreement.pdf
Applies to
all projects, once
  1. ConfidentialityAn NDA covering the client, project and data; no direct contact with or poaching of agency clients
  2. Code rightstransfer to the agency or its client, after payment
  3. Formin writing
  4. Fields of uselisted in the contract
  5. Billing: a fixed priceper project, when the scope is known upfront
  6. Billing: a block of hoursfor ongoing work and changes
  7. MaintenancePost-launch care and response times, on the agency's behalf.

Both parties and their lawyers approve the final wording.

From the first talk to the first quote

  1. A talk about the model

    Which way of working suits the agency and what projects it sells.

  2. A framework agreement

    Confidentiality, code rights and billing once for all projects.

  3. Project quotes

    A separate technical quote per project, usually within an hour of the brief.

What the agency hands us and what it gets

The most common split of work in projects we do for agencies.

The agency hands overThe agency gets
  • A design in FigmaA website or app built pixel-perfect, with animations
  • The client brief and feature listA technical quote for its own offer
  • Access to the client's hostingDeployment, backups and monitoring
  • Change requests from the clientFixes on an agreed timeline, without client contact
  • A project that needs integrationsConnections to payments, ERP or KSeF
  • A client who wants a panel or appA solution the agency cannot build itself
A technical care report in the agency's brand: uptime, backups, updates and the client's requested changes

Questions agencies ask

What agencies ask before the first joint project.

Let us talk about working together

Tell us what projects your agency sells and what is missing on the technical side. We will reply with a proposed way of working.