Every income project in Kairo's database comes with a list of channels where its clients tend to be found. Adding the lists together shows where people actually start. LinkedIn is named in 5 of the 14 projects, while Fiverr and WhatsApp appear 4 times each. Guru, another freelance marketplace, and local referrals come up 3 times. Upwork, word of mouth and cold calls are listed twice each, and a few channels such as direct outreach appear once. The channels fall into two groups. Marketplaces make up the first one: Fiverr, Guru and Upwork. They bring buyers who are already looking, and they take a cut, set the rules and decide who is visible. Kairo rates the dependence on third-party platforms as high for several of the projects that rely on them. People make up the second group: LinkedIn messages, WhatsApp, referrals, word of mouth and calls. Nobody stands between you and the client there, and the work of finding one is yours. Both groups can be quick. Fixing Google Business Profiles, a project reached through calls, WhatsApp and visits to shops, carries an estimate of about ten days to a first client, and general virtual assistant work, reached through marketplaces, about fourteen. Teaching AI tools, which needs some reputation first, carries about three weeks. Those are Kairo's working estimates, and your own results will differ. A single channel is a single point of failure, and that follows from the counts. A freelancer who gets all the work from one marketplace has one rulebook to follow and one algorithm to depend on. A freelancer with a handful of past clients who recommend them holds something that no platform change can remove. The channels based on people cost nothing but time. They ask for a few honest conversations a week, with owners of local shops or with people who already know your work. These counts describe the 14 entries Kairo holds, so read them as a starting point and not as a market survey. To see how the projects rank for your own profile, you can run it through Kairo: https://kairo.builtbyailab.com/en/?utm_source=blog


