lucasterryAI tools
systems · built with claude
Infrastructure built at Cascade: brand, comms, ops and community, all systematised. Systems that let the team operate without me in the room.
how it works
A Claude Project preloaded with Cascade's brand voice, tone guidelines, and example marketing copy. Anyone on the team opens the project, describes what they need in plain language, and gets on-brand output, no briefing required.
how it works
A three-part Notion doc covering visual identity standards, copy tone and voice guidelines, and a content examples bank. Built as a resource for scanning all outgoing content to ensure branding accuracy, so any team member could QA their own work without a review cycle.
how it works
A Notion database with one row per major depositor. Fields: deposit history, preferred comms channel, conversation log, last-touch date, next action. Treated less like a CRM and more like a relationship journal.
how it works
A Claude skill that pulls from three sources: Granola meeting transcripts, Slack thread summaries, and the day's calendar. One command generates a structured Notion daily page with meeting prep, outstanding threads, and a task list. Turns context-gathering from a 20-minute morning ritual into a 30-second command.
how it works
Built using direct user stats pulled from the platform. A dashboard that maps each KOL's referral network, showing referred trading volume, invite code usage, and campaign performance over time. Used to monitor influencer campaigns and allocate budget more effectively. Vibe-coded with Claude against our internal data exports.
how it works
A permission system connecting Discord roles to on-chain and platform data. Users were automatically sorted into tiers based on trading enablement status, volume stats for VIP channel access, and PnL-based rankings. Built to make the community feel earned and exclusive without manual management overhead. Designed the logic, drafted the PRD, and worked directly with engineering to ship it.