cloudfloo.io
ARTICLECLOUDFLOO-BRANDING

Why our portfolio now separates owned projects from reference logos

A short SEO and trust cleanup: CloudFloo-owned work belongs in case studies; Sabre and Samsung belong in team experience unless the project was actually delivered by CloudFloo.

cloudfloo-brandingseoportfolio

A software-house portfolio has one job: help a buyer understand what the team can actually deliver. That breaks when reference logos and owned projects are mixed together.

Sabre and Samsung are important experience signals for our team. They show the environments our engineers have worked in: travel technology, large systems, telecom-grade software, and enterprise engineering discipline.

But they are not CloudFloo-owned projects. Treating them as case studies would create the wrong trust signal. The stronger page is the more honest page: IndepAI, HSK WebKD, Hanbud, and Kontenero are the work we can describe as CloudFloo work.

This change also helps SEO. Search pages need specific intent, clear entities, and content that matches the URL. A page about IndepAI should discuss FIRE planning, Supabase, AI coaching, and product operations. A page about Samsung should not exist unless it is a real CloudFloo engagement.