Lead operations as product objects
Lead Central is ROIkeep's lead operations application: Upwork bids, Fiverr gigs and orders, and LinkedIn connection outreach tracked as product objects in one dashboard, next to cold-call campaigns worked through 15 stages.
[ 01 ]
Outreach campaigns
Cold-call lists as campaigns, one metro plus one vertical, imported once and re-run without duplicates.
A cold-call list arrives clean, stays clean on re-import, and is visible only to the reps assigned to it.
- A campaign holds one metro plus one vertical and shows its own lead count, and assigning an SDR to it is what makes it visible to them.
- Members see only the campaigns and profiles assigned to them. Owners and admins bypass the gate.
- Leads import from a flat CSV with column mapping and a per-row skip report.
- The same file re-runs without creating duplicates: leads dedupe on campaign plus place ID, generated from name and address when the source has none.
- An audit log records every meaningful action, filterable by action and entity type, with system-generated events marked.
The same file, no duplicates
A CSV import with column mapping and its per-row skip report.
Not a dialer
Lead Central places no calls and sends no texts. It runs the list, the 15-stage lifecycle, and the record of every call's outcome, whichever phone the rep uses.
[ 02 ]
Lead workspace
The SDR's daily screen, a filterable call list worked through a 15-stage lifecycle.
A rep opens the list and works it, and nothing about a lead lives outside its record.
- Leads are worked in a table or a drag-and-drop board, and filters save in the URL so a view is shareable.
- Every lead carries its address, phone, website, rating, review counts, and contacts.
- Every lead carries a quality grade, A to D, plus a numeric quality score.
- A lead moves through 15 stages from New to Won, Lost, Not Interested, or Do Not Call, and each stage's definition is readable inside the picker.
- One merged timeline per lead holds status changes, field edits, and notes in order, and every change traces back to a user.
- Leads marked lost, not interested, or do-not-call are pushed to the end of the list, not hidden.
The call list
A campaign's lead table with stages and saved filters.
[ 03 ]
Marketplace pipelines
Marketplace bids, conversations, gigs, and orders tracked as product objects.
Bids, gigs, and orders are worked from one dashboard instead of each platform's inbox.
- Platform leads from inbound messages, bid responses, and invites move through 8 stages to a won or lost outcome.
- Upwork bids log as standard or invite with 8 outcomes, and a bid converts into a lead in one action.
- Connect spend is logged daily and monthly against a monthly connect budget, with a low-balance threshold and alerts on both.
- Each profile sets how many bids a day it should send, and progress shows against it with an alert when it goes unmet.
Connect spend under a budget
Daily spend against the monthly connect budget and its alerts.
The connect balance is typed in by hand
Lead Central does not connect to an Upwork account. Bids, outcomes, and connect spend are logged in the product as the work happens, and the balance is a number a person types in.
[ 04 ]
Fiverr operations
Gig history, order delivery, and analytics read from uploaded screenshots.
Gig numbers keep their history, so every change to a gig can be read against what followed.
- Every gig edit is logged by change type, from title and description to pricing, images, tags, and FAQ.
- Uploaded analytics screenshots are read by a vision model, one at a time, in bulk, or for a whole profile.
- Every extracted value is shown for review, and stays editable, before anything saves.
- Gigs compare against each other, over time, and against the previous entry's numbers.
- The order pipeline runs from in progress to completed or cancelled, with a revenue tally and a deadline watchlist.
- Net revenue applies a fixed 0.8 multiplier for Fiverr's cut.
A screenshot becomes numbers
Extracted Fiverr analytics values held for review before saving.
[ 05 ]
LinkedIn outreach
Connection request to closed-won tracking, with a follow-up queue driven by day thresholds.
Follow-ups surface themselves instead of depending on memory.
- Leads add one at a time, in bulk, or by pasting a LinkedIn profile for field extraction.
- A lead moves through 12 stages from Requested to Closed Won, Dead Lead, Declined, or Ghosted.
- The follow-up queue surfaces what is overdue by day thresholds, a DM overdue after 2 days, a demo follow-up after 2.
- Leads tag by industry, with lead counts per industry.
- Connection requests and messages are sent on LinkedIn, by the person; Lead Central keeps the record and the queue.
- The content calendar tracks posts through pending, scheduled, and posted. Posts are published by hand.
The follow-up queue
Overdue follow-ups surfaced by day thresholds.
[ 06 ]
Dashboard and alerts
The single revenue and pipeline view, and the scheduled checks that push work to people.
The numbers and the warnings arrive on their own instead of waiting to be opened.
- One dashboard reads revenue and pipeline across the whole application, filterable by platform, profile, and date range.
- Revenue shows against the monthly revenue goal, and it counts completed orders only.
- Alerts come from 11 scheduled checks, including order deadlines, stale leads, low connect balance, and budget usage.
- Staleness hours, balance thresholds, and budget percentages are set per profile.
- Alerts arrive in-app, by email, and as browser push, and repeats are deduplicated through an alert log.
- A weekly summary email lands every Monday morning.
Revenue against the goal
The dashboard filtered by platform, profile, and date range.
Members, sign-on, and access for Lead Central come from the hub, and removing a person there ends their access and sessions here.
Lead Central is not a separately sold module: every plan ships all four applications.