Skip to content
jamil-mahmud/riseup-cms-portal
README

CMS Portal

A content management portal at Riseup Labs, one of the three applications I owned end to end, from discovery through launch.

What it is

A web portal for managing content in one place, built at Riseup Labs, a software company in Dhaka. It was one of three applications I owned as product manager and DRI between January 2023 and March 2024, next to Jeeto.Online (gaming) and MOffice (metaverse). I took all three from discovery through launch.

The job of a portal like this is simple to state and hard to get right: give a non-technical team one place to create, edit, approve and publish content, without a developer in the loop for every change. The people who own the words are rarely the people who own the code. A good portal lets the first group move at their own pace while the second group keeps the system safe.

The specific client, content model and feature set are not public, so this page sticks to what I can show: the kind of product it was, the market it sits in, and how I ran it as a product.

Industry

Content management is a crowded, mature market. On 17 October 2026, W3Techs reports that WordPress runs 39.6% of all websites, a 58.4% share of sites that use a CMS it can detect, while 32.1% of sites use none of the systems it tracks. Shopify, Wix and Squarespace follow far behind. Drupal sits under 1%.

That spread tells you how teams choose. Most websites fit a general platform, and an off-the-shelf CMS wins on cost and speed. Teams choose between open-source platforms such as WordPress, Drupal and Wagtail, headless products such as Contentful, and site builders. A custom portal wins when the content model, the approval workflow or the integrations do not fit those tools: when content has to flow into other systems, follow a particular review path, or serve users with different roles and rights.

Riseup Labs builds in exactly that space. Its service pages offer content management system development and web portal development, describing a web portal as a secure web-based platform that gives access to functionality and content through an easy-to-navigate interface. A CMS portal at Riseup was therefore a product that had to justify itself against strong off-the-shelf options, which is why discovery mattered so much.

What happened

  • Discovery first. I ran feature, competitor and user analysis before anything was designed. The question was not “what can a CMS do?” but “what does this team need that an off-the-shelf CMS would not give them?”
  • Roadmap and wireframes. The analysis turned into a roadmap and wireframes, so the flows were agreed with the team before development started.
  • Scope in writing. I authored the PRD, MRD and BRD, so engineering, design and the business worked from one definition of the product.
  • Stage goals. I set data-sequenced KPIs per stage, MVP, then MSP, then MMP, so each release had a clear bar to clear before the next one began.
  • Launch. I owned the portal as DRI from discovery through launch, within my time at Riseup Labs (Jan 2023 to Mar 2024).

All of this ran alongside two very different products. Jeeto.Online was a consumer gaming app chasing growth; MOffice was a 3D virtual office in a new category. The CMS portal was the quiet one: a tool for people inside an organisation, where success looks like fewer handoffs and fewer mistakes rather than headline user numbers.

Impact

No public metrics exist for this product, so I do not quote any. What I can say is sourced from my own record:

  • One of 3 applications I owned end to end, discovery through launch (Jan 2023 to Mar 2024)
  • Shipped with a full set of product documents (PRD, MRD, BRD) and stage-based KPIs from MVP to MMP

I will add outcomes here only when they can be sourced.

How I shaped it

  • Started from the problem, not the feature list. Competitor and user analysis set what the portal had to do better than an off-the-shelf CMS. In a market where WordPress alone runs four in ten websites, “build your own” needs a clear reason, and discovery is where that reason is found or not.
  • Made scope explicit with three documents. Each answers a different question. The PRD says what the product does and how it should behave, for design and engineering. The MRD says who it is for and what market need it meets. The BRD says why the business wants it and what it must return. Writing all three meant fewer arguments later about what “done” meant.
  • Defined what “working” meant at each stage. Stage-based KPIs, from MVP to MSP to MMP, kept the team focused on the next proof point instead of the full wishlist. The MVP has to prove the core job works for real users. Later stages raise the bar towards a product that can be sold and marketed.
  • Wireframed before building. Flows were agreed with the team before development started. For a content tool, the flow is the product: who drafts, who reviews, who publishes, and what each person sees.
  • Measured with events, funnels and retention. My approach to product analytics at Riseup is documented in an article I wrote for Riseup Labs in January 2024: pick the KPIs that match the product’s goals, track key user actions as events, build conversion funnels to find where people drop off, segment users by behaviour, track retention over time, and pair the numbers with direct user feedback. That is the lens I used to judge each stage.

How it moved on

  • Jan 2023 to Mar 2024: discovery, specification and launch under my ownership
  • Jan 2024: I publish my product analytics approach on the Riseup Labs blog
  • Mar 2024: I leave Riseup Labs; later changes to the portal are not public