MYRT BD Console

Dashboard

Welcome - get started in 3 steps
  1. Add leads. Add one in Pipeline, import a CSV/XLSX, or scan a source.
  2. Set your basics. Sender name and target in Settings (used in outreach + the north-star).
  3. Add scanner keys. PeopleDataLabs/Apollo and a vision key under Scanner › Sources (optional - the app works without them).
BD progress manual · closed
current · auto-summed from the BD volume ledger
— log volume per account in the lead modal’s MYRT volume section.
Projected (weighted):
Σ expected_volume × stage probability across open leads — a weighted pipeline projection, not yet processed.
What BD has closed — MYRT payroll/payout volume processed (manual ledger). Sender name + target edit in Settings.
MYRT network on-chain · live
Reading the chain…
Live on-chain — all MYRT movement, not only payroll · as of (MYT).
Follow-ups
Nothing due. Set follow-up dates on leads.
Monthly MYRT volume
Log MYRT volume on your won / onboarding accounts to see the trend.
Pipeline funnel
No leads yet. Add or import leads to see the funnel.
Segment mix
No leads yet.
Top accounts by MYRT volume

Pipeline

Drag cards between columns to change stage.
Name Company Segment Stage Urgency Tags Owner Vol (RM/mo) Last activity Next follow-up
No leads yet. Add one, import a CSV/XLSX, or scan a source. No leads match these filters.

Volume

Total MYRT volume (all time)
Accounts with volume
Quick-add account

Money flowing in before the lead exists? Add it here (defaults to onboarding) and log volume immediately.

Log monthly volume

Showing won / onboarding accounts (and any with volume). Toggle “show all leads” to log on others.

No accounts to show. Mark leads won/onboarding, or toggle “show all leads”.
Channel ROI · which source converts to real volume
SourceLeadsWonProcessed volume 
No leads yet.

Scanner

Sources configuration
No GITHUB_TOKEN detected — capped low to respect the unauthenticated rate limit.
Find the token in the careers URL: jobs.lever.co/token · boards.greenhouse.io/token · jobs.ashbyhq.com/token · apply.workable.com/token. Then scan the ATS monitor source. Verified live examples: lever/anchorage, greenhouse/gemini, ashby/OpenSea, workable/io-global.
No LinkedIn API / scraping — licensed providers (Apollo/PDL) + public RSS/ATS feeds only (ToS + PDPA).
Scan a source

Multi-signal GitHub search. Runs a set of web3 signals — keywords + language: qualifiers (language:Solidity finds devs by their actual code, not bio text) — across the chosen location (or all MY variants), then merges + dedupes by login and enriches each profile (name, bio, company, followers, public email/website/twitter where set). Edit the signal set in ⚙ Sources. ⚠ No GITHUB_TOKEN in .env — depth + enrichment are limited (10 vs 30 searches/min). Add one for full results.

PeopleDataLabs/Apollo firmographics (with a key in Sources) find Malaysia-based web3 companies; without a key you get a news signal from crypto-funding RSS — ranked reputation-first, each tagged “verify”, you approve with “+ Add”.

Hiring signal from public crypto job boards (web3.career, paginated, plus CryptoJobsList best-effort). Listings are classified by their real job location and collapse to unique companies: “Malaysia + remote/APAC” keeps MY-located + remote/APAC roles and drops listings pinned to a specific other country, ranked MY-first then by open roles. Each row shows its strongest signal (MY-located / Remote-APAC) and is tagged “verify”; “+ Add” sets flow = inbound and saves the listing in notes. Public listings only, never LinkedIn.

ATS monitor. Watches the career pages of companies you add in ⚙ Sources — Greenhouse, Lever, Ashby, Workable (free public endpoints, no key). A company is surfaced only when it has Malaysia or APAC roles, with the matching role + a MY-hiring / APAC-hiring label. This is how you catch OKX / Binance / etc. that don’t list on web3.career. A bad token just skips that one target. Public job feeds only, never LinkedIn.

RemoteOK (public, no key): recent crypto / web3 / blockchain roles collapsed to companies, ranked MY/APAC-mentioned first. These are mostly worldwide-remote, so precision is lower — every row is tagged “verify”. “+ Add” sets flow = inbound and links the listing in notes. Source credited: RemoteOK (remoteok.com).

MM2H agents = manual import. MOTAC's licensed-agent list can't be auto-read (JS-rendered, bot-protected). Open mm2h.gov.my/agencies, copy the table, and upload it via CSV/XLSX here. Refresh ~quarterly.
Firmographic:
RSS:
Signals:
No candidates found.
Upload an image — AI detects the details

A business card or a screenshot of contact details. The AI reads name, company, title, email, phone and website, then prefills a new lead for you to confirm.

Image detection needs an AI model. Preferred (production): set AI_INTEGRATIONS_OPENAI_API_KEY on the server (same model as claimbase). Or add a vision key in Settings. Manual + Add lead always works.

Import leads — upload CSV / XLSX
Map columns
Preview (first 5 mapped rows)
Rows without a mapped name are skipped.
Duplicate review
IncomingStatusMatchesAction

Merge-fill only fills blank fields on the existing lead (never overwrites) and unions tags/notes. In-file duplicates default to skip (the first row carries).

…or paste CSV instead

First line = headers. Recognised: name, company, segment, email, linkedin, telegram, twitter, website, source, owner, urgency, expected_volume, notes.

Lead sources cheat-sheet

Full list is in the Playbook tab. Quick hits: MOTAC licensed MM2H-agent list, crypto job boards (hiring-signal feed), Apollo/PDL for MY-based web3 companies, MY crypto Telegram/Discord, SSM/MIA directories for corp-sec & accountants. Never scrape LinkedIn — use licensed providers.

Outreach

Tip: personalise each message and keep it plain text - vary the opening line and avoid links in the first email to stay out of spam. Copy and send from your own inbox or DMs (this tool doesn't send).

No templates for this filter.
Personalise
No leads yet - the copy keeps {{placeholders}}. Add a lead to personalise it.

Tip: set sender_name in settings to auto-fill {{senderName}}. Paste into LinkedIn / your email tool / Telegram.

Select a template to personalise and copy.

Signals

Log a trigger signal

Frozen-account mentions, new MY crypto job posts, new web3 entity registrations, MM2H approvals — capture them, then convert hot ones to leads.

Feed
No signals yet.

Playbook

Two funnels → MYRT volume
Urgency tiers · work top-down
90-day sequence

One milestone per line (matches Wk 1–2 / 3–6 / 7–10 / 11–13).

Conversion flow
Growth loop

Settings

Everything configurable, in one place. These are the same controls used inline elsewhere - editing here updates them everywhere.

Team & north-star
Forecast - stage probabilities

Used for the dashboard's weighted projection.

Scanner sources & API keys
No LinkedIn API / scraping - licensed providers + public RSS only (ToS + PDPA).
On-chain (MYRT network)

Powers the dashboard's live MYRT network (on-chain) panel. Circulating supply works with no key (public JSON-RPC). Add a free Etherscan API key (v2) — one key covers Ethereum + Polygon — to also show minted / redeemed / network volume. This is live protocol context, separate from the manual payroll ledger + north-star.

Free key at etherscan.io/apis. Verified on-chain: ETH MYRT (6dp); Polygon is a real MYRT contract but currently 0 supply.
Saved views
No saved views yet. Apply filters in Pipeline, then "Save view".
Find duplicate leads

Scans existing leads for exact + likely-duplicate companies. Pick the primary in each cluster; merging re-parents activities, MYRT volume and tags onto it, fills blank fields, and deletes the others. Nothing happens until you confirm.

No duplicate clusters found.
Danger zone

Wipe all leads, activities, MYRT volume, and signals. Templates, playbook, and settings are kept. Use this to clear test data before real use. Type RESET to confirm.