Split into two categories: things that exist but need improvement, and things that don't exist yet. Prioritized by impact on the three channels and the systems-over-hustle mandate.
Contract gen tool works but output lacks polish. Needs: executive summary in plain language, table of contents, DaisyChain logo, Manrope font, customer-friendly cover sheet. Goal: customer signs without extensive legal back-and-forth.
McGowan's work has been organic and intuitive. Needs a playbook: qualification checklist, required deal data, proposal request workflow, escalation paths. Best fit is converting existing pipeline using standardized feasibility scope.
Large backlog of leads is unqualified, unpruned. Each must be run through the decision tree, classified IC/SC/SDP/PFC, and either activated or archived. This is Channel 2's foundation.
Relationships with Solar One, Rise, Elizabeth Kelly exist but aren't engineered. Need: partner qualification criteria, onboarding process, referral tracking, revenue share model, co-branded materials, conversion metrics.
Scope is mostly defined (PSC, LL97, DR, submetering cost, incentives, solar). Pricing ($5K) is hypothesized but unvalidated. 414 Albemarle Road is the test. Alex needs to do price discovery with trusted clients.
Notion holds the data; BD-Hub should own the workflows. The integration between these two systems needs to be defined: what stays in Notion (input, display), what moves to BD-Hub (automation, routing, scoring).
No documented playbook for any of the three channels. Each needs: target profile, outreach cadence, talk track, objection handling, required deal data, stage gates, escalation paths, success metrics. This is the #1 gap — without playbooks, the system depends on people, not process.
The three channels are defined but resource allocation (% of time, budget, unit targets per channel) is not. Alex to propose at next check-in. Must include calendarized deal cycles by channel.
No automated lead routing or nurture. Vision: lead enters via any source → auto-classified by decision tree → routed to correct channel owner → proposal triggered or self-service flow initiated → stage progression tracked → alerts on stale deals. This is the BD-Hub's job.
Described in customer framework (SC customers furnish info via self-service form) but not built. Need: web form → auto-proposal → contract flow. Minimal human touch. AI-powered Q&A for common questions (J51, LL97, etc.).
Channel partners need materials they can use: co-branded one-pagers, proposal templates, presentation decks, explainer content. Clear visual and messaging standards. Currently zero partner-facing collateral exists.
Plan to participate in NYC coop events, industry tradeshows. No calendar, no budget, no booth/materials, no follow-up workflow. Need: event selection criteria, pre-event outreach, day-of capture, post-event nurture sequence.
No unified view of: leads by source, conversion rates by channel, deal stage velocity, pipeline value, revenue per unit, cost of acquisition. Need this to validate channel mix hypotheses and inform hiring.
Per the "Business Know How" analysis: DaisyChain is a distribution and monetization layer for building-level energy infrastructure — not a submetering company. Need to define and own the category: "Electrification OS for buildings." Visibility, messaging, and authority-building plan.
No centralized library of: case studies, one-pagers, ROI calculators, comparison sheets, FAQ docs, onboarding guides. Each deal currently requires bespoke explanation. The library is what makes scale possible.
No systematic outbound for Channel 1. Need: ICP target list (institutional MF owners ≥1K units in NY/CT/NJ), enrichment, sequenced outreach, meeting booking flow. Currently reactive/relationship-based.