winston-sales-intelligence

Automating CRM prospect lookups and outreach logging in Supabase involves querying the nv_accounts and nv_account_contacts tables to find prospects, then recording interactions in the cro_outreach_log table. This skill automates that workflow to reduce manual data entry and track the full prospect lifecycle.

To log prospect pain points and trigger signals for sales follow-up, you insert the captured context into the nv_pain_points and cro_trigger_signal database tables. This skill automates the insertion process, ensuring context is saved accurately for future outreach coordination.

Yes, you can update prospect engagement stages directly in your Supabase database. This skill modifies the engagement_stage field within the nv_accounts table, allowing you to coordinate and track the progression of a prospect through your sales lifecycle automatically.

The best way to enrich prospect data and insert new contacts into a Supabase CRM is to automate the insertion into the nv_accounts and nv_account_contacts tables. This skill handles the data entry, applies enrichment, and ensures correct session context to resolve env_id and business_id.

Yes, this CRM prospecting automation requires correct session context to function properly. It needs to resolve your env_id and business_id to interact with the Winston Supabase database tables successfully and avoid writing data to demo CRM tables.

Your prospect records might not insert into the correct Supabase CRM tables if the session context is missing or if the system is targeting demo CRM tables. This skill requires correct env_id and business_id resolution to write successfully to your live nv_accounts and cro_outreach_log tables.