QuikInfluence — The CRM
What it is: Custom-built CRM for Quik Nation (originally for QuikSession’s booking/customer management)
Why it exists: Salesforce, HubSpot priced them out. Built in-house with $2M in COVID-era telework contracts and 12 developers.
Tech: First GraphQL project. PostgreSQL + TypeScript. Next.js frontend. AWS Amplify.
The problem: Developers (not architects) put ALL apps on one database through QuikInfluence:
- 73 models total, serving QuikCarry, FMO, QuikBarber, iDemand Beauty, everything
- One GraphQL schema for all apps
- Amen Ra wanted GraphQL federation, devs resisted (sunk cost)
- Currently being decoupled — each product gets its own DB/schema
The future: QuikInfluence remains the CRM layer, but properly integrated via federation — not a monolithic DB for everything. Each Heru product gets its own data, QuikInfluence connects to all of them as the CRM overlay.
How to apply:
- QuikInfluence = CRM. Not a dumping ground for all app data.
- The decoupling work is THE most important architectural task
- GraphQL federation is the answer Amen Ra always knew was right
- n8n workflows for QuikInfluence should focus on CRM ops: lead tracking, customer lifecycle, contact sync across products