NGA ERP

Tuesday, 02 June 2026

Dishant Goel
← backlast updated 25d ago
A3idea

A3. Network management (NGA Connect)

A. Marketingpriority: lowenergy: light

NGA Connect already exists. Extend or repoint at the Drive folder so all systems can read it.

Original ask (Dishant's words)

"A) Marketing: ... 3) Keep in Touch with those in my Network."

What this really is

Not "manage NGA Connect contacts." The real A3 is touch your network 200 times a year, gently and at the right moments, with no manual effort. Birthday wishes, festival greetings, periodic check-ins, small acknowledgements. A warm CA network sustains the funnel. Dishant's framing (2026-05-07):

"how other tasks can automate themselves by sending whatsapp to specific numbers or groups including birthday and holidays wishes."

Already exists

NGA Connect (contact management with AI card scanner) — extend it, don't rebuild. NGA Connect is the source of contacts; A3 adds the touchpoint cadence on top.

Approach

A3 owns who to touch, when, and what to say. The actual sending (WhatsApp, email, etc.) is handled by E9 — Approval-gated outbound dispatch. A3 generates the touchpoints; E9 dispatches them. Touchpoint types to support:

  • Birthday wishes (auto-triggered from contact birthday + WhatsApp number)
  • Festival greetings (Diwali, holidays — sent to whole network or segments)
  • Periodic check-ins (every 3-6 months for warm contacts not seen lately)
  • Personal acknowledgements (their child's wedding, achievements)

Notes

2026-05-07 — Considered for Week 1, deliberately dropped

Selected as part of the Week 1 marketing trio (A1 + A2 + A3) on 2026-05-04 to start the funnel of business. Dropped from Week 1 on 2026-05-07 — capacity reality after HSIPL April report shipped, Dev Plastics replication planned, and other Week 1 work in motion. A1 and A2 moved into motion. A3 carries over. When A3 reactivates, the design is clearer than it was on 2026-05-04: A3 owns who to touch, when, and what to say; actual sending is the E9 pattern. So A3's first build doesn't need to solve dispatch — just needs contact data + cadence + content templates. This is a deliberate deferral, not abandonment. Subtractive thinking applied honestly.

Weekly tasks (0)

No tasks linked to this agenda.