Komini Case Study

Komini's work is relational. Founders meet in rooms, around a fire, in cohorts and in one-to-one sessions with Kui. A brochure listing those programmes would describe the offer and still miss what makes it work: the experience of sitting with people who understand the weight you are carrying.

So we set one test for every page: does it move a founder one honest step closer to being in the room? The free live session became the front door, the podcast became a way to listen before speaking, and the paid Rowers Journey became the deeper commitment for founders ready to build their team.

That test shaped the language as much as the layout. Komini's own phrases (arrive alive, pull a seat, rowers, the fire) carry the brand, and the pages explain them plainly enough that a founder meeting them for the first time still knows exactly what happens next.

Komini is broader than one programme, so the homepage presents its world as a set of doors, each labelled with how you would walk through it: a weekly podcast, a live session on Zoom, a cohort, and a founder programme that is still coming. The format tag tells a founder the commitment before the title tells them the content.

Below the doors sits an entry point written for a specific feeling rather than a product: are you deep in overwhelm? It speaks to the founder who recognises that too much still depends on them, and sends them to the place where that usually starts to change, with the people already inside the business.

Not every founder is ready to sit in a room with strangers. Komini by the Fire is the quieter way in: a podcast for African founders, by African founders, recorded around a fire with the hosts bantering over a concept, a story and questions sent in by founders. The page opens on that scene, with the line “And we’re back around the fire…”, so it reads as a return to a familiar place rather than a new show to evaluate.

The latest episode plays right on the page, from the first screen, with Spotify and Apple Podcasts offered as alternatives rather than the main route. Keeping the listening inside Komini's site means a founder who enjoys an episode is one scroll away from the live session, instead of somewhere else entirely.

On a phone, the play button sits inside the photograph, with the other platforms set below it. The cadence and the size of the archive (new every two weeks, 51 episodes at the time of capture) are stated plainly, because a regular rhythm is part of what makes a podcast feel like company.

Fifty-one episodes is a lot to walk into. The shelf answers the newcomer's question (where do I start?) in its heading, then gives two ways in: a full player for the latest episode, with its opening line quoted so you know the conversation before you press play, and a list of recent episodes that each play in place.

Below them, listener favourites gather the episodes founders keep coming back to, from years earlier, so the archive's best work does not sink beneath the newest. The page also says the episodes are timed for a car ride, which tells a busy founder exactly when this fits into their week.

The page ends by turning listeners into contributors: got a founder question you want unpacked around the fire? Suggested topics feed future episodes and live sessions, so the podcast keeps learning from the people it is made for. Behind it, listening is measured by episode, with listen-through milestones and actual listening time, so the team can see which conversations hold attention.

The live session page is built around one gesture. The hero arranges founders from different industries in a ring around a fire, and leaves one seat empty, marked as yours. The call to action, pull a seat, is the same words as the illustration, so the page reads as an invitation rather than a form.

Upcoming sessions appear as admit-one tickets with the topic, date, time in East Africa Time and seat count. Choosing one starts a seat pass that fills in as you answer: your fire, your name, your business, and your pulse, which tells the hosts how you are really doing before the session begins. Seven short steps feel lighter than one long form, and the pass shows what you are building as you go.

On a phone, the ring tightens into a half circle above the headline, so the empty seat stays visible in the first screen without crowding the words.

Each upcoming fire is shown as a ticket: a numbered stub in Komini's colours, the topic, the time, and a request link. Treating sessions as tickets gives them weight, and the seat count tells a founder the room is small enough to be heard in.

The request itself is a two-panel pass. On the left, a dark ticket fills in with each answer; on the right, one question at a time, with progress shown as seven dots. Founders see their seat being made rather than a list of fields being emptied, and the last field, the conversation they hope to have, prepares the hosts as much as it registers the founder.

The Rowers Journey asks founders to send their best people on a sixteen-week programme. That is a considered decision, so the page follows a deliberate order: recognition, then diagnosis, then structure, proof, fit, price and finally process. The copy report behind it records why. A founder needs to see the problem clearly before reading about a solution.

The first interaction is a question rather than a pitch: if you stepped away for three months, what would your business do? Four honest answers (grow, flat-line, yo-yo, decline) each come with a small chart from the day you step away to month three, and choosing one leads to a sharper follow-up. The line under it names the real question: what still depends on you, and what has already moved into the team?

Further down, a team-pattern tool lets a founder think of one person and walk through twelve everyday situations in about three minutes. Each person becomes a shape across six qualities, such as owning outcomes and holding it without you, so overlaps and gaps across the team become visible. Evaluations stay in the browser, and the page says so, because founders are describing real colleagues.

The programme's language is rowing: Rowers move the business forward, the founder steers as cox. The how many should I bring section turns that metaphor into a working control. Adding a Rower fills a seat in a rowing boat, the boat's speed and stroke rate rise with the crew, and the button below always reads see the investment for however many Rowers you chose.

That button lands on the investment section with the same number already selected, so the price shown is the founder's own: per person, for the full programme or monthly, with the team total beside it. The copy report explains why price comes before how to join: a founder who meets the application before the cost can feel pulled into a commitment. Showing the investment first makes the next step feel like a choice.

Proof follows the same principle of showing rather than claiming. Rowers sent postcards from the boat, each with an old belief crossed out in handwriting and the new one written beneath it, followed by what their manager noticed. Founders can drag the card away to read the next one, or use the arrows.

Testimonials usually ask a reader to trust a sentence. The postcards ask them to watch a belief change. The old belief is written first and struck through, the new one is written out beneath it, and the card closes with something observable: a team that now follows up every customer who has not ordered, or delivery delays that come with a reason and an early warning.

On a phone, the postcard becomes the whole screen and responds to a swipe, so the stack feels like something you hold rather than a carousel you operate.

The Rowers Journey has two audiences with different jobs. Founders enrol their team; team members who discover the page themselves cannot enrol alone. We kept those as two separate flows instead of one form with branching questions, because they answer different questions: can this team join the cohort, and has a high-potential person raised their hand?

The founder application reduces payment anxiety directly. Applying does not charge anything; payment only comes up after review, if the founder chooses to go ahead. Earlier drafts said this three different ways, and repeating it made people wonder why payment was being managed so carefully. One calm statement, placed where the worry appears, does the job better.

The Rower interest path lives inside the section describing who a founder should send, not in the hero or the navigation. A team member is most likely to recognise themselves after reading those qualities, and placing the call there keeps founder enrolment as the main path. The form asks whether the founder already knows, which decides whether Komini follows up warmly or first gives the Rower words to start the conversation.

Komini's thinking pages carry the deeper narrative: how the journey works, what Komini believes, the seven areas of the business everything comes back to. We set them as editorial issues, with a volume number, a reading time, a masthead and a table of contents, because these pages are meant to be read, not skimmed for a price.

The format also gives founders a reason to stay. A clear contents list and a single call to action at the end (start with your team) let someone read the whole argument and then act, instead of being interrupted by offers on the way through.

With every page given one job, the analytics needed to answer one question per page: is it doing that job? We instrumented the site page by page and section by section. The live session form reports its funnel step by step, including where people stop. The Rowers page reports its calls to action, the diagnostic, the team pattern tool, the crew and pricing calculator, the video and the questions. Every event says what kind of page it came from.

Privacy was part of the design, not a later filter. Nothing a founder types reaches the analytics: no names, no emails, no description of their challenge. Team size and revenue are recorded as bands, not exact figures, and a browser test reads the real outgoing requests to confirm that contact details in payment links never leave the site. The team preview site sends nothing at all.

The tracking plan is honest about its limits too. Ad blockers hide some visitors, so rates matter more than raw counts, and numbers before launch are not comparable. That makes the next stage of the work clear: watch which doors founders choose, where the requests stop, and whether the free session leads to the paid programme, then refine the pages that are not yet doing their job.