Building Coalition Rewards Programs From Zero

Most Rock 'n Roll CEO commercial engagements begin with something. A sales process that needs refinement. A CRM with bad data. A partner program generating activity but not pipeline. The work involves diagnosis, optimisation, improvement.

Then there are the engagements that start with a blank page.

No team. No systems. No existing customers to interview. No historical data to analyse. No playbook to improve. Just a strategic mandate and a deadline.

The instinct is to move fast. Hire people. Build systems. Show progress.

The reality: speed without architecture creates expensive problems that compound over time. Roles get hired before responsibilities are defined. Systems get built before workflows are mapped. Decisions get made before governance exists to enforce them.

Building from zero requires a different discipline. The sequence matters as much as the components.

Impact Africa was a multinational project led by the investment group Lancea Partners of London, assembling a major infrastructure project for central Nigeria. The venture would span multiple business units: an airline, airport, duty-free retail, ground transportation, and various other business units, including a private helicopter service.

Leadership identified early that customer experience across these units needed commercial cohesion. A coalition rewards program would unify the ecosystem, drive cross-business engagement, and create a data asset spanning the entire customer journey.

The challenge: this business unit didn't exist. No team. No technology. No commercial model. No governance structure. Fractional executive leadership was engaged to build it from inception.

Blockchain architecture and technology selection

The engagement began with solution architecture, not hiring. What would the coalition program actually do? How would value accrue and redeem across radically different business units? What technology infrastructure would support transactions at airport retail and helicopter bookings with equal reliability?

Traditional loyalty platforms couldn't deliver the required fungibility. Points earned with one business unit needed genuine portability across all coalition partners without conversion friction or technical limitations.

The decision: build on blockchain from day one rather than migrate years later with millions of members and transactions at risk.

Technology evaluation focused on transaction speed and cost. Bitcoin's network couldn't support the transaction volume required for daily retail operations. Ethereum's gas fees would make small-value transactions economically unviable. The Stellar blockchain platform offered the technical requirements: sub-second settlement, negligible transaction costs, and smart contract functionality for automated rule execution.

A dual-currency model was designed. Tokens for immediate earn-and-spend functionality, pegged 1:1 to USD for consumer comprehension. And crypto-coin as the underlying cryptocurrency asset for longer-term value capture and exchange functionality in Phase 2 of the project.

The technical architecture preceded team structure discussions. The solution had to be viable before resources were committed.

Commercial validation before capital commitment

Market research established TAM, SAM, and SOM across multiple scenarios. A seven-year business case was constructed with granular cost modelling that extended beyond typical three-year projections.

The financial model included hosting costs scaled to projected member growth trajectories, personnel costs phased against revenue milestones, marketing spend mapped to customer acquisition targets by channel and geography. Line items existed for equipment replacement cycles four years forward.

An independent senior financial advisor validated the business case before significant capital deployment. The economics had to withstand external scrutiny, not just internal optimism.

Governance infrastructure while the team remained small

Corporate governance structures were established before the organisation existed to require them. Decision rights, reporting lines, board interaction protocols, financial authority levels, vendor approval processes.

The scaffolding was built to support a larger organisation before that organisation was hired.

Executive hiring against validated requirements

Recruitment followed solution design and commercial validation. Four C-suite roles: CMO, CLO, CTO, COO. Each position defined against the solution architecture already validated and the commercial model already stress-tested.

Candidates were evaluated against specific requirements derived from the business case and technical roadmap, not generic job descriptions copied from competitor organisations.

The hiring sequence was deliberate. Legal and technology leadership secured before marketing and operations. Foundation before amplification. The CLO and CTO roles required immediate functional capability. Marketing and operations could scale after launch infrastructure was established.

Product and operational infrastructure

Technical specifications for the consumer mobile application defined the member experience: wallet functionality with QR code-based transactions, "earn", "spend, and "share" token flows, real-time balance visibility with local currency conversion, tutorial overlays for feature adoption.

A dynamic ranking system was designed to drive engagement frequency:

• Four spend rank thresholds were defined
• Member tiers reset monthly based on cumulative spend across all coalition partners.
• Progress indicators showed proximity to next tier.
• Each rank achievement unlocked partner offer request functionality.

The partner mobile application mirrored consumer wallet capabilities with additional business intelligence access. Partners could issue tokens for cash purchases, receive tokens as payment, and access member analytics dashboards filtered by rank, demographics, location, and transaction behaviour.

Reporting infrastructure provided partners with member acquisition metrics, revenue attribution by customer segment, comparative performance against market benchmarks, and customer acquisition cost calculations. Drill-down capability enabled store-level analysis for multi-location operators.

A partner rules engine was specified to define operational parameters: maximum tokens issuable per member per day, transaction frequency limits, automated fraud detection triggers, POS integration requirements, geo-location verification protocols.

Operational controls for the company included program-wide rule definition, member lifecycle management, partner onboarding workflows, compliance monitoring, and financial reconciliation processes.

The technical specifications weren't aspirational feature lists. They were deployment-ready requirements documentation for vendor RFP processes.

The coalition rewards business unit achieved operational readiness within seven months. Solution design validated. Executive team recruited. Financial models stress-tested. Governance frameworks documented. Technical specifications completed. Everything deployment-ready except launch funding.

The broader infrastructure project stalled. Regulatory delays. Funding negotiations extending beyond projected timelines. Stakeholder coordination challenges across multiple countries and business units. Not unusual for complex multinational initiatives.

The rewards business unit couldn't proceed independently.

However, business unit infrastructure built properly doesn't immediately become obsolete when timing shifts. The solution design remained sound. The Stellar blockchain platform continued maturing, validating the technology selection. The financial modelling methodology held. The governance frameworks required no revision. Executive recruitment had identified capable leadership against validated requirements rather than instinct.

The solution demonstrated sufficient commercial viability that it could support an independent venture. Market opportunity confirmed through structured research. Economics proven through rigorous modelling and independent validation.

The technical specifications were subsequently used to evaluate vendors for similar coalition program implementations. The governance frameworks informed other startup organisational design. The financial modelling approach became template methodology.