REACH — how it works

REACH is ManjuLAB’s guided digital marketing assistant. The console walks you through company onboarding, channel connect, channel-specific content packs, approval, and calendar scheduling. Under the hood: submit content, AI proposes campaign copy, a human approves, then you export (Phase 1) or publish when a verified publisher is enabled.

Start here in the console: Walkthrough (dummy SaaS / Healthcare / Recruitment / Retail companies — simulated credentials) → Get started → Create & publish → Calendar. Staff tools live under Operator tools. Nothing posts to live social networks in walkthrough mode.

Phase 1 reality check: Production path for ManjuLAB is LinkedIn + export. Automatic LinkedIn network publish is gated (M8). Facebook, Instagram, X, YouTube, TikTok, etc. appear in the Demo gallery so you can see how other publishers would look — they are learning samples, not live publishers yet.

1. Core loop

Intake — paste title + body in Content Inbox
Pipeline — normalize → understand → plan → copy → creative → validate
Approval — different user from submitter must approve
Export / publish — build package; LinkedIn auto-publish stays gated
Analytics — manual metrics + evidence-based recommendations

2. Roles

operator — submit intake, run pipeline, export, enter metrics (op-1)
approver — approve / reject / request changes (ap-1)
admin — all of the above + worker tick, brand config, seed demos (admin-1)

Default staff password: reach. Tenant for real work: manjulab.

3. Create your first real workflow (ManjuLAB → LinkedIn)

Open the console and sign in as op-1 / reach / tenant manjulab.
Go to Content Inbox. Enter a real title and body (product news, blog excerpt, event).
Submit intake. Note the intake id.
Open Campaigns (or use API POST /intake/{id}/run) to start the AI pipeline.
If jobs stall, sign in as admin-1 → Audit / Admin → Worker tick a few times.
Sign out, sign in as ap-1 (approver must not be the submitter).
Approval Center — paste campaign id → Approve.
Back as operator/admin → Export → Build export. Copy the package into LinkedIn manually.
Analytics — enter impressions/likes with a reason → Generate recommendation.

That sequence is your template for every real ManjuLAB campaign until M8 LinkedIn API publish is verified.

4. Dummy companies & rock-flows

Use Demo gallery in the console (or GET /reach/api/v1/demo/catalog). There are ~20 sample workflows across LinkedIn, Facebook, Instagram, X, YouTube, TikTok, Threads, Pinterest, Google Business, Email, Blog, and WhatsApp — each tagged with a publisher name and campaign state.

Open the creative workbook to see how a brief becomes platform-specific flyers (Instagram vs Facebook vs WhatsApp for Northwind Yoga, LinkedIn for ManjuLAB, X / LinkedIn / email for Contoso Coffee) and why each asset is shaped differently before approval and distribution.

Admins can press Seed demo companies to create demo tenants and campaign shells in the database. Then change the login Tenant field to e.g. demo-northwind-yoga to browse that company’s campaigns.

5. Publisher map (what “done” means)

LinkedIn (Phase 1) — Export package; optional NullPublisher path → EXPORT_READY
Other channels (demo) — same workflow states; publisher adapters are placeholders until product enables them
PUBLISH_UNCERTAIN — never auto-retry with heuristics; human confirms remote URL or fails/exports

6. Useful URLs

Console: /reach/
Creative workbook: /reach/workbook.html
API health: https://api.brahmando.com/reach/api/v1/health
Demo catalog: GET /reach/api/v1/demo/catalog (Bearer token)
Seed demos: POST /reach/api/v1/admin/seed-demos (admin)