Created on 16th May 2025
•
For Brands:
Operational hassles:
Excessive operational overhead managing influencer campaigns manually.
Scaling nano influencer engagement
Non feasibility of running campaigns with 100,500,1000 nano influencers manually.
Costs
High agency costs that make influencer marketing inaccessible to smaller brands.
Data Opacity
Lack of transparency in metrics and ROI measurement.
Payment Friction
Payment friction requiring multiple platforms and manual verification.
Micropayment Limitation
Unfeasibility of paying extremely small amounts with a few hundred or thousand views for 100s,1000s of creators.
Lack of global access
Limited or no access to global creator networks, especially for payout considerations.
Authentication
Difficulty identifying authentic creators with engaged audiences efficiently.
For Creators:
Monetisation early on.
0 monetisation ability till you reach a mega scale of 10ks or 100ks of views despite having engaged niche audiences.
Payment delays:
30-90 day payment delays causing financial instability.
Fee / value leakage
Middleman agencies eating into the original brand budget and the creator sees a fraction of the original value assigned to their work.
Contract enforcement:
Enforcement of contracts with brands - legal and operational challenge doesnt make it worth pursuing despite making the deliverables.
Reputation / credibility
No standardized way to prove work history(Proof of work) and engagement metrics - especially being a nano influencer.
Geo limitations
Geographic limitations restricting access to international opportunities - both due to discovery and payment rails reasons.
Administrative overhead
BD, outreach to brands , Complex contracts and negotiations taking away from time used for creation
Task scheduling and monitoring complexity
One of our most significant challenges was implementing reliable task scheduling to ensure comprehensive system monitoring. We needed a robust mechanism to track and execute scheduled tasks without omissions, which was critical for maintaining consistent monitoring across all handled platforms. We addressed this by implementing a centralized task management system with redundancy checks to verify successful execution.
Deployment environment dependencies
We faced considerable difficulty getting FFmpeg pre-installed on our deployment service, which was essential for our media processing requirements. This required creating a custom Nixpacks configuration to ensure FFmpeg was properly integrated into our deployment pipeline. The solution demanded deep understanding of both our deployment environment and FFmpeg's dependencies.
Platform isolation and system resilience rarly in development
we identified a critical vulnerability: if one platform's integration failed, it could potentially crash our entire backend system. To resolve this, we redesigned our architecture to use a microservices approach, where each platform's backend operated as a separate, isolated service. This architectural decision significantly improved our system's fault tolerance and stability, allowing individual platform issues to be contained without affecting the broader system.
External api rate limits, built redundancies by using multiple sources.
Tracks Applied (1)
Technologies used
Cheering for a project means supporting a project you like with as little as 0.0025 ETH. Right now, you can Cheer using ETH on Arbitrum, Optimism and Base.