What we built
Smart contracts and NFT mechanics. The access logic, the distribution rules and the on-chain behaviour that the fan proposition depended on — built against the campaign's requirements rather than retrofitted to them afterwards.
A launch campaign that matched the build. Community, creator activity and press running to the same dates as the engineering milestones, so nothing was announced before it existed. That sounds obvious. It is the single most common failure in Web3 launches.
The advantage of one team
When marketing and engineering sit in the same building, three things stop happening. Announcements stop outrunning the code. The campaign stops describing mechanics in language the contracts do not support. And when something in the product changes, the messaging changes the same day rather than three weeks later.
That is not a philosophical point. It is the difference between a launch where the audience trusts what it reads and one where the first technically literate reader finds the gap.
The outcome
The programme raised $5M, with momentum from the opening of the round rather than a scramble at the end — which is what happens when the community and the coverage exist before the window opens rather than being assembled during it.
