Payment-led progression
Registration creates a payment reference; verified payment becomes part of the participant record before private applicant access and review progression.
Case study
MTPN Naija Iconmtpn-naijaicon.com ↗
From talent registration to controlled auditions, voting and progression.
A competition operating system connecting eligibility, payment, applicant review, judge scoring, auditions, contestant publication, public voting and programme progression.
15application lifecycle states
3default voting rounds
3staff role types
2candidate pipelines
The operating problem
Talent decisions should stay human. Programme operations should not have to be.
The challenge
A competition has different control points: eligibility, payment, review, judging, audition logistics, public participation and stage progression. The platform had to keep those actions aligned while preventing a payment, vote or status change from becoming an informal side process.
The design question
How do you keep one accountable participant lifecycle while preserving staff and judge authority over the actual talent decisions?
The connected operating journey
One record moving through the business.
01RegisterApplicant profile and evidence
→02PayVerified entry payment
→03ReviewAdmin and judge decisions
→04AuditionSchedule and qualification
→05VoteControlled public participation
→06ProgressCamp, final and winner stages
What the system connects
Automation around the rules. Human control around the decisions.
Review, judging and auditions
Admins manage application state and auditions while judges record score, note and qualification outcomes that feed the participant lifecycle.
Voting with abuse controls
Open-round state, contestant eligibility, identity format, signed challenge, rate limits and duplicate rules are checked before a vote is accepted.
Participant portal
Applicants can follow their private status and timeline across payment, review, audition and later programme stages.
Academy application queue
A separate student and instructor intake supports a second talent pipeline with its own review statuses and private résumé handling.
Programme visibility
Applications, payments, judge scores, audition details, contestant publication, vote audit and stage status are available to operations teams from connected records.
What changed
The process became a connected operating flow, not a collection of screens.
A competition has different control points: eligibility, payment, review, judging, audition logistics, public participation and stage progression. The platform had to keep those actions aligned while preventing a payment, vote or status change from becoming an informal side process.
Registration, payment confirmation, judging, auditions, voting and finalist progression now operate from one participant lifecycle with explicit stage rules.
The platform automates programme administration without pretending it can automate talent judgement.
The Nadmaa approach
Business analysis first. Technology second.
This was a programme-governance problem: payment, eligibility, judging, public participation and progression had to stay connected without turning the competition into a black-box algorithm.
Fix the process. Connect the systems. Build what's missing.
Where is your operation still being rebuilt by hand?
Bring us the operating problem.
You do not need to know the technology answer. We can map the workflow with you and identify what is worth fixing first.