Pluto Marketing logo
Pluto Scout
Prospect lists for Pluto Marketing

Use the username you were given. Caller accounts work the call list; admin accounts also approve spending and change settings. Locked out? Ask the admin to reset your sign-in.

Scout finds and scores the shops. Humans make the calls.
Powered by Pelican OS
Pluto Marketing logo
Pluto Scout
WorthyA shop becomes a Lead only when its score clears the bar and there's enough to build from.
Talked to & interestedA shop enters the Pipeline only after someone has talked to them and they're interested.
Set up — admin only
Powered by Pelican OS

Intake

Every shop Scout is checking, scoring and deciding on — one place, each shop showing its stage and its next step.

Leads

Shops released for calling, best first. Open a lead for its brief, or start the next call.

Said no

Pipeline

Deals in progress — one column per stage. Open a card for the shop's record.

Approvals

Spending, contact reveals and demo builds that need an admin's yes. Nothing here runs until you approve it — each item says what it does and what it costs before you decide.

Suggestions

Ideas from Board loops, each with its reasoning. Adopting an idea spends nothing and changes no gate — it queues the idea to be built, and the result is written back onto the same item here. Money approvals live in Approvals.

Build queue

Demo websites waiting to be built. The builder builds each one from the shop's record — the queue is checked four times a day, so a build is same-day, not instant.

Criteria

A shop is Worthy when its score clears the bar for its kind — the bars and weights are below. These are also the rules Scout hunts by: where to look, which kinds of shops, and how much each kind of problem counts. Saving re-scores every shop from data already held — re-scoring is free and never pulls new data.

Current criteria

The four weights add up to 100 — they set how much each part counts in a shop's score.

Batches & spending so far

Usage counters

Settings

Connections, texting, autopilot, and money & access. Admin only. Keys are stored on the server and never shown again after saving — only the last 4 characters.

Jump to:

Google Places API key

From the Google Cloud project "Pluto Marketing" with Places API (New) enabled. Status:

Apollo API key

Finding a shop owner's own email or mobile (email 1 credit · mobile 8 credits). Reveals need admin approval and only unlock once a shop is ready to call. Status:

Apify API token

Powers the full data pulls — all of a shop's reviews and photos. Each pull needs admin approval first (in Approvals), unless autopilot is on for Apify pulls. Status:

Texting (Twilio) — Pluto's own number

Powers "Text the demo link" sending directly from Scout. Until this is connected, that button opens the caller's own messaging app instead — Scout does not send texts yet. Status: Not connected

US business texting needs A2P 10DLC registration on Pluto's own legal identity — that step is the admin's, in the Twilio console. Never enter Patto's number here.

Autopilot

When the master switch and the Apify switch are both on, Scout approves and runs Apify full data pulls by itself as they are recommended — inside the $25/month ceiling and the $25 single-batch ceiling. A pull whose real cost drifts from its quote stops and asks again; it never overspends quietly.

Autopilot will never, on its own: fire the Google deep backup pull · reveal owner contacts (Apollo) · release a call list · build a demo website · change the scoring rules. Those always need a person.

Master autopilot
Apify full data pulls — auto-approve and run
Releasing call lists🔒 Always needs a person — not a setting
Demo website builds🔒 Always needs a person — not a setting
Revealing owner contacts (Apollo)🔒 Always needs a person — not a setting

Never automatic — the engine itself refuses these, no setting can turn them on:

MCP server — ask Scout from Claude

Scout has its own MCP server, so a signed-in user can connect their own Claude and ask questions about Scout's shops ("which Segment B shops are ready to call?", "show me the brief for this shop"). It is read-only — answers only; outcomes and notes still happen here in Scout. It can only see Scout's Pluto data — nothing else.

Endpoint: https://scout.srv1004667.hstgr.cloud/mcp

How the caller connects (one time, about a minute): 1) Open Claude and go to Settings → Connectors. 2) Choose "Add custom connector". 3) Paste the endpoint address above. 4) When Claude asks for a token, paste the token created here. 5) Ask Claude a question about a shop. Tokens can be revoked here at any time — a revoked token stops working straight away.

About

Pluto Scout — Powered by Pelican OS. Standalone today; folds into Pelican OS at launch, records and timelines unchanged.

Activity log

Sign-ins and actions in Scout, per user. Admin only — this page and its data are refused to caller accounts on the server, not just hidden.

Per user

Latest activity

Request demo build

Built by the builder from this shop's record — the queue is checked several times a day, so it is same-day, not instant.

Must include (optional)

Unsaved work on this record

You talked to them and they're interested.

Moving to the Pipeline needs all three: the Interested outcome (already logged), what they said yes to, and a next step with a date. This moves them to Pipeline so the deal can be worked — "Won", with the package and start date, is set on the Pipeline board when they sign.

What did they say yes to?