About the practice
Feature Vertex Hub is a small practice in Johor Bahru. We write feature experiment readouts for product teams, then sit with them until a decision exists on paper. We are hired after the experiment has run — sometimes before, when the design would make a later readout impossible.
Aisha Rahman founded Feature Vertex Hub after too many launch reviews in which the experiment appeared as a screenshot and the decision appeared as a feeling. Product managers in Johor and Kuala Lumpur already know how to ship. They asked for someone who would still mention peeking, festive traffic, and the users who never entered the test.
The name is literal. A feature has a vertex: the moment the squad must choose. We stay at that point. We do not stay to write the next roadmap, recruit testers, or run the company’s experiment programme.
Clients are usually squads inside banks, commerce, telco, and ride-hailing products who already collect results. English is the language of the memo. Malay is welcome in the briefing when that is how the disagreement actually happens; the decision slip is still written so a later reader can follow it.
One reader owns the memo. A second reader marks overclaim before you see it. Briefings are seventy-five minutes because that is long enough for guardrails and short enough to prevent a new hypothesis from being born in the room.
We will decline work when the assignment is known to be broken and the request is still “please recommend a ship.” We will also decline to estimate a delayed effect from a holdout that was mixed into a later campaign.
The office address is used as given: Bang Mara,Johor Bahru,Johor,80000,Malaysia. Video briefings follow Malaysian working days. Incomplete experiment packs are returned before a date is held.
People
Aisha started Feature Vertex Hub in Johor Bahru after years of sitting in launch reviews where the experiment table arrived as a screenshot and the decision arrived as a mood. She writes the first reading on most flagship readouts and chairs briefings when the product manager needs a firm close.
Wei Jun spent a decade next to product squads whose experiments crossed app and web assignment. He is the second reader on memos that involve holdouts, peeking, or a results window that collides with a campaign calendar.
Priya runs squad workshops and keeps the seventy-five-minute briefing on the original question. She used to be the person in the room who noticed the feature had already shipped while the experiment was still marked as running.
The original hypothesis stays on the table. Counts sit next to percentages. A mild result is allowed to stay mild. The product manager leaves with a slip that says ship, iterate, or stop, and with the name of the person who owns the next step.
If that sounds like the conversation your squad already meant to have, request a readout or read how a briefing day is run.