Pavan Ninja — mockup, Development Ninja coming soon
NINJA-360
← Ninja-360 Dojo
Technical Roadmap · GoHighLevel Build-Out · Working Doc V06

The Ninja-360 Tech Build,
Staged & Sequenced

Tim Petet × Pavan Gantha (AZ Team). Seven milestones, all pointed at one target: the September push — fresh customers at scale. Each stage is scoped, has a "done means done" test, and gets paid as it lands — structure chosen per milestone: trade-out · milestone payment on completion · per-close fee.

Prepared 2026-07-13 · V06 (M6 belt test + ninja360.co locked in as the dedicated outreach domain: web 301 → ninja360.net, mail-only cold sends, August warm-up) · Source: Ninja-360 Master Hub open loops (2026-07-12 pass) + Audit Engine SOP v1.0 · Every item below is existing documented scope, not new invention

01 · How This Works

02 · The Seven Milestones

M0 · Week-1 Task + First ShipThis week · Jul 13–19

Scope

  • Tracking snippet wired to the GHL webhook, tested on a live audit page: cid reader, dwell heartbeat, video-progress events → GHL logs view_count + watch_time and notifies Tim.
  • First ship: publish the AI-Search NAP standard funnel page at /standards/ai-search-nap — files already built (GHL paste version in Drive → "Ninja-360 Audits"); swap the schema placeholders with the real profile URLs (or strip the JSON-LD block) before going live.
Done when: a test contact fires every event type and the notification lands · the standard page is live at its slug and verified on mobile.
Unblocks: engagement tracking for the entire Audit Engine — every milestone after this depends on it.
Structure: part of existing onboarding (assigned 6/29) — completes the first commitment.
M1 · Unblock OutboundBy Jul 31

Scope

  • Toll-free SMS verification (Error 30032): sweep the 5 published workflows — every SMS step reads "Reply STOP to opt out"; add the required (not pre-checked) consent checkbox to the Free Visibility Audit Intake form; capture the public form URL as the opt-in proof URL; confirm ToS + Privacy links; enter honest volume; submit verification in GHL.
  • Email deliverability: SPF / DKIM / DMARC on ninja360.net.
  • Outreach domain: configure ninja360.co (fresh on Cloudflare) as the dedicated cold-send domain — web 301-redirects to ninja360.net (entity stays consolidated, per the AI-Search NAP standard) · its own SPF/DKIM/DMARC for mail · warm-up schedule runs through August so it's ready for the September push. Cold campaigns NEVER send from ninja360.net.
Done when: verification approved · test SMS delivers to US number · email authentication passes.
Unblocks: ALL US/Canada SMS — the standing hold on restaurant prospecting lifts — plus trustworthy email sends. The single biggest sales unblock on the board.
Structure: milestone payment on completion — $ — or equivalent trade-out hours. Set before start.
M2 · Audit Engine Live End-to-EndThrough August

Scope

  • Audit pitch-page publish flow: /audits/{slug}/ custom-HTML, NO-INDEX verified.
  • Custom fields (industry, city, score, belt, audit_url) + Sales pipeline stages with automations: Audit Built → Audit Sent → Pitch Viewed → Call Booked → Won/Lost.
  • Send workflows carrying ?cid tracking; follow-up rules wired: viewed-no-call-in-24h alert · not-opened-48h resend · repeat-view hot flag.
  • Entity Confidence layer: wire the AI-Search NAP standard's checks into the audit flow as a scored dimension + belt upsell prompt.
Done when: one real audit runs all 11 SOP stages with zero manual patching.
Unblocks: the sales funnel as a machine — every audit invitation becomes tracked pipeline. This is what fills September.
Structure: milestone payment on completion — $ — funded by August collected receivables.
M3 · Client Delivery Pipeline V01September

Scope

Belt delivery task templates (from the execution-playbook spec) + onboarding workflows, so a White or Brown Belt delivery runs to checklist without live decisions from Tim.

Done when: one belt delivery executes to checklist, no improvisation.
Unblocks: delivery capacity — the infrastructure that makes Ninja-360's first hire workable.
Structure: per-close fee — $ per NEW Brown/Black Belt closed on this infrastructure. Upside scales with wins.
M4 · Content + Network RailsPre-flight this week · build Sept

Scope

  • Quick win now: GHL Social Planner pre-flight — confirm channels/config on the Ninja-360 sub-account (the content campaign needs this in week 1; it's small — bundle it with M0 this week).
  • September: Networking pipeline for partners and referrals — tracked referrals in AND out.
Done when: autopost publishes on schedule · partners tracked as pipeline records.
Unblocks: Content Engine cadence + the Partnership pillar of the 90-day campaign.
Structure: trade-out or folded into the per-close arrangement.
M5 · The War Chest — Prospect DatabaseBuild starts now · sends only after M1

Scope

  • Source waterfall (per the Ninja-360 prospecting plan): ACA roster → Gladstone Chamber → Liberty Chamber → Northland business clubs → Google (compliant tooling only). Beachhead verticals: restaurants → chiro → dental/ortho → Airbnb.
  • Every record: business name, vertical, city/zip, contact name, email, phone, website, GBP URL, source, consent status. Deduped + email-verified before it touches the CRM.
  • Loaded into GHL with tags + smart lists by location × vertical, segment-pull tested — campaign-ready.
  • Compliance, non-negotiable: NO SMS to scraped contacts (consent-only channel — standing hold applies) · cold email is CAN-SPAM clean (real address, working opt-out, honest subject lines) · sending architecture protects ninja360.net's domain reputation — Pavan proposes the setup before the first send.
Done when: each batch of 250 verified records lands deduped, tagged, <3% bounce on verification, and a test segment (e.g., "restaurants · Gladstone") pulls correctly in GHL. First target: 500 records.
Unblocks: the email + guerrilla + social campaign — the fresh-customer machine gets its ammunition. (Message/creative comes from the content lane; this milestone is data + rails.)
Structure: milestone payment per verified 250-record batch — $ per batch. Volume scales only as batches stay clean.
M6 · Tech Ninja Belt Test — Agency-Grade GHL + AI AgentsComplete by Aug 31 — before the September push

Scope

  • Complete Nuno Tavares' course on setting up GHL as an agency (Nuno is a HighLevel Certified Expert; courses on Udemy).
  • Complete at least one of Nuno's AI Agents sub-courses.
  • Apply it, don't just watch it: configure the Ninja-360 account to agency-grade spec per the course, and build one working AI agent in the Ninja-360 sub-account (e.g., audit follow-up conversation agent or booking agent) as the proof piece.
Done when: course completions shown + the AI agent demo runs live on a test contact in the Ninja-360 sub-account — before September 1, so the big push runs on agency-grade rails with AI in the toolkit.
Unblocks: the September big push — war chest (M5) + audit engine (M2) + AI agents working the follow-ups. This is the difference between a mailing list and a machine.
Structure: course seat — who pays: (Pavan's professional development / Tim as trade component / split — decide in the room). The knowledge is Pavan's forever; the build stays Ninja-360's.

03 · The Calendar at a Glance

WindowMilestonesFunded by
Jul 13–19M0 complete (snippet + NAP standard page LIVE) · M4 Social Planner pre-flight · sizing agreed in writing for M1/M2Onboarding commitment / trade
Jul 20–31M1 — outbound unblocked (SMS verification + email auth) · M5 war-chest build starts in parallelMilestone $ or trade — set first
AugustM2 — Audit Engine end-to-end · M5 first verified batches load · first campaign fires (M1 green) · M6 courses done + AI agent demo by Aug 31August collected receivables · per-batch $
SeptemberTHE BIG PUSH: campaigns at full clip on agency-grade rails · M3 — Delivery Pipeline · M4 — Networking pipelinePer-close fees begin on NEW belts closed
Ground rules: scope in writing before any stage starts · a stage is paid when its "done when" test passes, not before · no stage jumps the queue · changes to scope are a new written line, not a verbal add-on · no SMS to scraped contacts, consent only · no cold sends until M1 deliverability passes.

Pick the Structure, Put It in Writing

Every milestone above is already documented Ninja-360 scope — this roadmap turns it into a staged build with clean tests and payments that track real revenue. Choose the structure per stage — trade-out, milestone-on-completion, or per-close — itemize the hours, and the first stage starts this week.

Prepared for the Tim Petet × Pavan Gantha working session · 2026-07-13 · V06
Built from: Ninja-360 Master Hub open loops (2026-07-12) · Audit Engine SOP v1.0 · Content Engine pipeline V01
© 2026 Ninja-360 Digital Media LLC | Kansas City, MO