Market signals, client moves, scheme programmes, payment outages and competitors’ deal wins become target accounts, a named contact, a first message matched to the right PaySky bundle, and a booked solution workshop. Agents research and draft. People send.
Click any lead card to expand it: contact, draft email and LinkedIn note, brief, stage and assignment.
Live from the pipeline. Weighted value applies a win probability by stage: Signal 2%, Qualified 5%, Drafted 5%, Sent 10%, Replied 20%, Booked 35%.
Click any number, bar or table cell to see the leads behind it.
Each cell counts leads per team member and stage. Red means unhandled: unassigned leads, leads still at Signal, Qualified or Drafted more than 3 days after being assigned, and leads with an overdue follow-up step. Leads marked Won, Lost or Opted out are left out of the red count. Click a name to open that person’s leads.
Everyone signs in with their own PaySky Scanner account. Super admins create, change and remove accounts on the Users page, and the database enforces each role:
People appear in this list after they open the page once. You can also assign to anyone in your organization by searching their name on a lead.
Every lead is scored on two separate questions, each out of 100: does the institution fit PaySky, and does the contact own the problem? Both must reach their pass mark. A hard exclusion fails a lead whatever its scores. Missing evidence sends it to Review rather than failing it. A strong news signal never rescues a poor fit. The radars score every new lead with this test, skip leads that fail, and only auto-route leads that pass.
Fail the lead whatever its scores.
If any of this is missing, the lead goes to Review.
The daily scan assigns new leads that match a rule, and you can route the current unassigned leads with the button below. Rules are checked from top to bottom and the first match wins. A rule matches when the field contains the text, ignoring case (for example Language contains “French”, Region contains “Middle East”, Lead type contains “Incident”). People appear in the list once they have opened this page.
Accounts and keywords the daily scan checks first, every day, before its general search.
The Social Radar scans these influencers, LinkedIn pages, newsletters and news sites every 6 hours. LinkedIn blocks automated reading, so for each LinkedIn source add the person’s or company’s own website or newsletter as the “Also read” link: that is where the radar picks up what they publish. Posts that search engines index are picked up too.
A lead is stale when it hasn’t been sent and its signal is older than this many days. Stale leads fade in the pipeline and can be hidden or archived.
Seven rooms, one hand-off chain. Rooms marked Agent run on a daily scheduled task at 6:40am Dubai time; rooms marked Person stay with your team so every message goes out from a real sender.
Reads the pipeline before each run so nothing is added twice and no lead a person owns is changed.
Checks the watchlist first, learns from your lead ratings, applies the auto-routing rules, then scans five streams:
Every 6 hours, offset from the Signal Radar, reads posts and articles from fintech influencers, LinkedIn pages, newsletters and news sites (listed in Settings) and turns relevant ones into leads, marked “News & social”.
Every morning, reads which institutions visited paysky.io (company level, from Apollo), drops internet providers, students and existing open deals, and turns fitting visitors into leads of type “Inbound interest”. The email never mentions the visit.
Scores every new lead on two questions, institution fit and contact fit, against the test in Settings. Leads that fail are not added. Leads with missing evidence arrive as Review and are not auto-routed.
Names the best person to contact from public sources (management pages, press releases, regulator notices). Adds an email only when it is published; otherwise gives the best route in.
Writes a short email and a LinkedIn note. Each one cites the signal, picks one PaySky bundle, and backs it with the closest proof point.
Rep reviews, localises and sends from their own mailbox, then marks the lead Sent. The 14-day sequence starts and shows up under Today.
Rep sends the connect note by hand on day 2. No automation tools: LinkedIn restricts accounts that use them.
Books the 60-minute solution workshop. “Write account brief” on the lead produces the one-page prep: signal, use cases, modules, references, discovery questions.
What the radar looks for, who it points at, and what to lead with. Proof points come from the PaySky company profile.
| Signal | Who to target | Lead with | Proof point | Window |
|---|---|---|---|---|
| Central bank launches or expands an instant payment system | IPS operator, participant banks and wallets | National Infrastructure Stack; Universal QR | Egypt UPG: 31 wallets, merchants 80K → 850K in under 2 years | 3–12 months |
| National QR standard or migration deadline | Banks, e-money issuers, PSPs | Universal QR, merchant management, bulk onboarding | UPG: one national gateway for all wallets and Meeza cards | Until the deadline |
| Digital or virtual bank licence | The new bank’s CEO, CDO, product heads | Super App Stack; Store and Invoice Cube | Yalla: 1M+ accounts in 9 months; ADCB PacePay: 10,000+ merchants | 0–12 months before launch |
| P2M or acquiring approval | Head of Acquiring, CDO | Digital Acceptance Stack: SoftPOS, TMS, merchant management | First SoftPOS in the Middle East (ADCB) | 0–6 months |
| Telco wallet or super-app launch | Head of Mobile Money / Fintech | Merchant super app, B2B marketplace, bill payments | MTN MoMo Market: 1.5M businesses, 16 markets | 3–9 months |
| Cashless government revenue or e-receipt mandate | Revenue authority, ministry of finance, municipalities | Revenue Cube; omni-channel gateway | Sudan E15: 23,000+ services, over USD 1B in year one | Budget cycle |
| Joining PAPSS or a cross-border scheme | Central bank payments directorate, transaction banking | Remittance hub; orchestration | GIM-UEMOA: 8 countries, 156 banks, 50 mobile money operators, 180 fintechs | 6–18 months |
| Existing client expands: new country, new licence, new product, tender or new executive | The client’s sponsor and the new decision-maker | The next bundle on their roadmap | Their own live deployment with PaySky | Act within weeks |
| Visa or Mastercard launches a product or regional programme (tap-to-phone, tokenization, Click to Pay, A2A, agentic commerce, SME acceptance, contactless or 3DS mandates) | Scheme country managers and partnership teams, plus the banks that must enable it | Co-delivery: PaySky as the local processing and enablement partner | Visa strategic partner and investor; first SoftPOS in the Middle East | 3–12 months |
| Outage, regulator penalty or resilience mandate (switch down, app outages, dual-connectivity or failover rules) | CIO, CTO, Head of Payments, Head of Operational Resilience | Switching & orchestration with failover; risk (Shield); TMS | National gateways run for Egypt, Libya and 8 UEMOA countries | Weeks, while the pain is fresh |
| Vendor dispute, contract exit, acquisition or end-of-life of an incumbent platform | The institution’s CIO and procurement; the incumbent’s affected clients | Migration path from the matching PaySky module | Closest live deployment to their use case | Before the renewal or tender |
| Competitor win · Complement: a competitor announces a deal with a bank, wallet, telco or government (press release, LinkedIn post, tender award, partner page) | The client that signed: the sponsor of that programme and the heads of the areas the deal does not cover | The PaySky modules outside the deal’s scope, built to sit alongside it (e.g. they bought switching → offer QR, SoftPOS, super app, Cubes) | Closest live deployment for the missing piece | Right after the announcement, before the roadmap fills |
| Competitor win · Counter: the same deal, seen from the signed client’s rivals in that market and segment | The rivals’ CDO, Head of Payments or Digital, who now face a competitor with new capability | The equivalent or stronger capability from PaySky, positioned as how to match or leapfrog the move | The reference closest to the rival’s segment | 0–3 months, while the rival is still reacting |
| Inbound interest: an institution visits paysky.io (several visits, solution or contact pages) | The visiting institution’s head of payments or digital; the role that matches the pages they read | The bundle that matches the pages visited | The reference closest to their segment | Days: first touch within 24–48 hours |
| Tourism or fuel push, new acquiring market | Acquirers, fuel retailers, fleet operators | FX Cube (DCC); Fuel Cube | FX Cube plugs into POS and e-commerce checkout for multi-currency acceptance | Varies |
Open the lead and use the Reply helper: paste their reply and get three answers (brief, with one proof point, or fuller). Each acknowledges the concern before answering and uses only approved figures. Pick one, edit it in your own words, and send it from your mailbox. The lead moves to Replied. If they ask not to be contacted, set the outcome to Opted out and stop.
Lead with empathy and facts, never blame. Reference the public report only, offer resilience help (failover routing, a second switch path, monitoring), and do not name the incumbent vendor in writing.
When an institution reads paysky.io, someone there is already thinking about the problem. Reach out within a day or two, but never mention the visit (“I saw you on our site” reads as surveillance). Write about the problem the pages they read point to, and offer something concrete: the 60-minute workshop or a short plan for their market.
Every lead carries two scores: does the institution fit PaySky, and does the contact own the problem? “Qualified” means both pass; it is permission to prioritise, not a reason to skip judgement. “Review” means evidence is missing: usually a named contact. Find the person, then press Re-score. If the test keeps disagreeing with your useful/not-useful ratings, change the test in Settings, not the leads.
One competitor deal can open two kinds of lead. The radar files each as lead type “Competitor win” with its play.
Tag each lead with a territory (for example “KSA distributor”) and filter by it. Anyone you share this page with can see every lead, so give partners their own page if they must only see their territory.