I did not start Siaco because the world needed another landing page. I started it because the people I care about — salon owners closing a chaotic Saturday till, parish teams juggling members and ministries — were stuck between notebooks, WhatsApp threads, and software that was either too foreign or too expensive.

Glamora came first: Kenya-first salon operations with live M-Pesa, not a US template with a currency switch. Catolica followed the same instinct for the Church — respect the workflow, host it ourselves, and ship something a real team can run.

Why a studio, not a single app

One product teaches you a market. A studio forces you to build a craft: clean deploys, boring admin tools, honest pricing, and the discipline to keep marketing separate from the product runtime. That is why Siaco sits on the default web ports while each SaaS app keeps its own stack and URL.

Where I see us in five years

• Glamora is the default operating system for ambitious Kenyan salons and spas — bookings, staff, and Lipa na M-Pesa as table stakes.
• Catolica is trusted by dioceses and active parishes for members, teaching, giving, and day-to-day ops.
• Siaco is a known multi-product studio: a few sharp SaaS lines, local ownership of data, and customer success that feels like a partner, not a ticket queue.
• We hire and train builders in East Africa who can ship full products — frontend, backend, payments, and production hygiene — without waiting on someone else’s cloud CMS.

Five years is not a fantasy deck. It is enough time to prove the thesis: useful software, hosted close to the customer, paid for because it removes real pain on Monday morning.

If that resonates — whether you run a salon floor or a parish office — request a demo on a product page and tell us what “success” looks like for your team.