GizoMarket
Shaping a Nigerian Classifieds Marketplace
Contributed to shaping a Nigerian classifieds marketplace through product direction, seller monetisation, onboarding workflows, marketplace operations and development requirements.
- Company
- GrandGale Technologies
- Product
- Nigerian classifieds marketplace
Case Study Contents (15)
Project introduction
GizoMarket is a Nigerian classifieds marketplace designed to connect buyers and sellers across products, services and properties.
My work involved contributing to the product direction, defining business and operational requirements, refining user workflows, and translating product decisions into actionable development specifications.
The work covered the marketplace experience across buyers, sellers and administrators, with particular attention to how the product would support listing discovery, seller onboarding, monetisation and day-to-day marketplace operations.
The challenge
The product needed a clear and coherent marketplace model that could serve buyers, sellers and administrators without introducing unnecessary transactional complexity.
Beyond the core listing experience, several interconnected product questions needed to be addressed:
- —How should sellers join the marketplace and become eligible to publish listings?
- —How should the platform generate revenue from seller activity and additional visibility?
- —How should categories, locations and listing information remain consistent?
- —How should administrators manage approvals, promotions and public content?
- —How could changing stakeholder requirements be translated into clear, testable development work?
These were not isolated interface decisions. They affected the underlying business rules, user journeys and operational workflows of the marketplace.
My contribution
I contributed to product planning and execution across several areas:
- —Product direction and scope definition.
- —Seller onboarding and verification requirements.
- —Subscription and paid promotion models.
- —Marketplace categories and location requirements.
- —Admin workflows and content management.
- —Notification requirements.
- —UX improvements and functional quality.
- —Development tickets, specifications and acceptance criteria.
I worked with stakeholder feedback and product observations, translating them into decisions and structured requirements for the development team.
Clarifying the marketplace model
One important part of the product work was shaping the experience around a focused classifieds model.
The product direction centred on helping buyers discover listings and contact sellers directly, while giving sellers the tools to publish and manage listings.
This meant prioritising:
- —Product, service and property listings.
- —Buyer discovery and search.
- —Seller profiles and listing management.
- —Direct buyer and seller communication.
- —Seller subscriptions and paid listing visibility.
- —Administrative oversight of marketplace activity.
The earlier concept included more complex transactional functionality, such as escrow and order management. The direction moved towards a simpler listing and enquiry experience, with in-app messaging supporting communication between buyers and sellers.
The product decision was about focus: making listing discovery, seller participation and visibility central to the marketplace experience.
Defining the seller subscription model
The marketplace required a structured commercial model for sellers.
I worked on defining a unified subscription framework for Individual and Business Sellers, including its pricing controls, listing entitlements and lifecycle rules.
The proposed subscription durations were:
| Plan | Duration |
|---|---|
| Weekly | 7 days |
| Monthly | 30 days |
| Quarterly | 3 months |
| Bi-Annual | 6 months |
| Annual | 12 months |
The business rules covered more than payment. They defined how subscriptions would affect seller activity:
- —Administrators control subscription pricing and listing limits.
- —Only active listings count towards a seller's listing allowance.
- —Sold, deleted, archived and expired listings free up capacity.
- —Unused listing capacity does not roll over.
- —Automatic renewal was excluded from the first version.
- —Existing listings remain visible after subscription expiry.
- —Sellers with expired subscriptions cannot create new listings.
- —Paystack was identified for online payments, with manual confirmation available for bank transfers and exceptions.
This work translated a commercial idea into a set of operational rules that could guide implementation.
Designing paid listing visibility
I also contributed to defining the marketplace's paid promotion structure.
The model separated banner advertising from Featured Listings.
Banner promotions
- —Platinum
- —Gold
- —Silver
- —Bronze
These placements required promotional banner assets and an administrative review and publishing workflow.
Featured Listings
This was a separate promotion type. Rather than creating a new banner, it used the existing listing and placed it in a designated Featured Listings section after approval.
An important operational requirement was that listing photographs should not automatically be stretched into advertising banners. Administrators needed to upload appropriately designed promotional assets.
The advertising requirements were later extended to account for separate desktop and mobile banner designs.
The work connected seller visibility, commercial opportunities, homepage merchandising and the administrative processes needed to manage paid placements.
Refining seller onboarding and verification
Seller onboarding needed to support both Individual and Business Sellers, with administrative review before seller activation.
I worked on refining the registration and documentation requirements as stakeholder needs changed.
One example involved business documentation.
The requirements retained CAC certificate collection for Business Sellers while removing the NIN Slip, Proof of Address and TIN Certificate collection requirements.
This required distinguishing between documentation that still served a business requirement and documentation that was no longer needed.
The resulting requirements addressed:
- —Individual and Business Seller registration paths.
- —Seller application submission.
- —Administrative review and approval.
- —Rejection and activation workflows.
- —CAC certificate collection for Business Sellers.
The objective was to keep the necessary verification requirement while reducing unnecessary steps in the registration process.
Making marketplace categories more flexible
A fixed category structure can prevent sellers from accurately describing what they offer.
I proposed a category and subcategory submission workflow that allowed users to request options that were not already available.
The proposed flow was:
- 01Users select an existing approved category or subcategory.
- 02If the option is unavailable, they select Others.
- 03They enter the category or subcategory they need.
- 04The submission goes to administrators for review.
- 05Administrators approve or reject the request.
- 06Approved options become available for future use.
Subcategory submissions also needed to retain their relationship with the appropriate parent category.
The requirement was intended to balance user flexibility with administrative control and consistent marketplace data.
Addressing location data reliability
The client reported that some Nigerian Local Government Areas were missing from the application's dropdowns.
Rather than treating this as a problem with one form, I considered the wider dependency on location data across the application.
The proposed requirements covered:
- —All 36 Nigerian states and the Federal Capital Territory.
- —All 774 LGAs and Area Councils.
- —Correct state-to-LGA mapping.
- —Searchable LGA selection.
- —Automatic LGA updates when a state changes.
- —Consistent location data across registration, seller profiles and listing forms.
- —Preservation of existing users' saved location information.
Two possible approaches were considered: replacing the existing location API or developing a centrally maintained dataset and API.
The work focused on defining the required coverage and behaviour. It should not be interpreted as evidence that a replacement location system was fully implemented.
Defining marketplace operations and notifications
A marketplace involves many events that require communication with buyers, sellers and administrators.
I worked on requirements for a notification system covering 34 approved notification events across account activity, listings, payments, subscriptions, promotions, messaging and administrative workflows.
The specification addressed:
- —In-app and email delivery, depending on the event.
- —Read and unread states.
- —Unread notification indicators.
- —Notification history.
- —Links to relevant application destinations.
- —Duplicate prevention.
- —Maintaining in-app notifications even when email delivery fails.
The focus was on defining notification behaviour around actual product events rather than treating notifications as an isolated interface feature.
I also contributed to requirements for an Admin-managed public content system covering pages such as About Us, Privacy Policy, Terms of Service, Contact Us and FAQs.
The intention was to allow administrators to manage public-facing content without requiring developers to edit hardcoded pages for every content change.
Improving product quality and user experience
Alongside larger product requirements, I worked on identifying and documenting issues affecting important marketplace journeys.
Examples included:
- —Draft creation failing for Service and Property listings while working for Products.
- —Authentication behaviour when users navigated backwards after logging in.
- —Notification links directing users to incorrect destinations.
- —Admin page links pointing to localhost rather than the deployed website.
- —Incomplete Nigerian LGA options.
I also defined specific homepage and responsive improvements.
These included displaying the three main category cards in one row on mobile while preserving the desktop layout, and moving the Latest Listings navigation action below the listing cards.
When application performance concerns were raised, I defined an investigation covering frontend rendering, image loading, API response times, database queries, pagination and measurement of performance before and after optimisation.
The emphasis was on identifying the underlying issue before prescribing a technical solution.
How I approached the work
A recurring part of my contribution was turning loosely expressed requests and observed problems into development-ready requirements.
The approach generally involved:
- 01Understanding the business or user problem.
- 02Identifying the affected user groups and workflows.
- 03Clarifying the expected product behaviour.
- 04Considering dependencies and operational implications.
- 05Defining acceptance criteria.
- 06Translating the requirements into structured development tickets.
- 07Following up on observed implementation issues.
This helped make requirements more actionable for developers and reduced ambiguity around what a feature or fix was expected to achieve.
What this work demonstrates
GizoMarket provided practical experience across several dimensions of product management:
- —Product thinking: Connecting individual features to the wider marketplace model.
- —Commercial thinking: Defining subscription entitlements and paid visibility.
- —Systems thinking: Considering how seller, buyer and administrator workflows interact.
- —Requirements engineering: Turning business needs into clear product behaviour and acceptance criteria.
- —Stakeholder management: Refining requirements in response to changing client feedback.
- —Technical collaboration: Considering frontend, backend, API, data and deployment implications.
- —Product quality: Identifying functional problems and defining testable improvements.
Reflection
One of the most important lessons from this work was that product decisions rarely exist in isolation.
A subscription model affects listing capacity, seller permissions and expiry behaviour. A category submission feature affects data consistency and administrative responsibilities. A notification system depends on the events and workflows happening across the entire product.
Good product management requires understanding those relationships before translating an idea into a feature.
GizoMarket strengthened my ability to approach product work as a connected system of business objectives, user needs, operational rules and technical requirements.
Evidence and delivery note
This case study describes my documented product management contributions, decisions and requirements. Some items were defined as development requirements, while the available records confirm implementation evidence for selected work, including the Admin Pages Management interface. I do not have verified delivery or business outcome metrics for every workstream, so I have not presented proposed features as completed releases or claimed unverified improvements.