02. Shared acquisition process
Communication channel: A matrix channel is available.
The collectives are encouraged to operate their project acquisition with inter-collective projects in mind.
Communication of new acquisitions
Collective A is in an early stage of any acquisition process with a potential new customer i.e. at the latest when a definite collaboration is discussed. Mere networking (e.g. the exchange of business cards) doesn't need to be communicated. *In any case, acquisition is communicated. This is necessary to avoid competition between collectives.
In the course of this, the following information should be shared:
- type of the project
- a short description
- as appropriate: Name of the customer incl. references (respecting any privacy needs)
Collective A concludes: The project is not feasible alone or not at all.
In both cases, collective A communicates requirements publicly in the channel, providing the following information:
- What type of support is required?
- Staff reinforcement (people from other collectives supplement the collective's team)
- Project release (the project is to be handed over entirely to another collective)
- Multiple collectives can perform the task in parallel (e.g. a larger project with several subprojects)
- Requirements (e.g. tech stack)
- Required language skills (as in spoken language)
- Budget (if known)
- Required qualifications
The other collectives are to respond likewise transparently for all in the public channel. If there's no response after three workdays, the project can be declined by collectiva A. Principally, no projects are to be refused before that period. This also applies to projects collective A is not interested in.
Specification of a shared acquisition process
Collective A always has priority for the project they have announced. This is to avoid creating a disadvantage of open communication (of projects) for collectives.
If no collectives are interested in the project (e.g. the three workdays have passed or all collectives in the channel have declined), collective A informs the customer about this.
If there is too much interest in the project (more collectives than possible wish to participate), the collectives (or team members) take on a friendly and constructive discussion based on the following criteria:
- Which collective needs the project more?
- Are the collective's members currently getting paid?
- For how many months has the collective not received any or not enough (paid) projects?
How many more months is the collective able to last without any projects?
Which collectives is better suited for the task?
- Experience with the tech stack
- Experience with similar projects (in terms of scale, schedule and budget)
- Number of people/profiles available for the project
- Language skills
- Trust (based on previous collaboration experience)
- Hourly rates
If a team has been formed based on these criteria, the communication with the customer goes as follows:
- If collective A is part of the team, collective A is responsible for explaining the modus operandi to the customer (legal considerations, project coordination, etc.). Collective A is mainly responsible for communication with the customer.
- If collective A is not part of the team, they forward the contact to the formed team (or the now-in-charge collective), which is from then on responsible for the communication.