Dashboard
What the machine did while you were not watching, whether every piston is firing, and where each section stands today.
Daily digest
the morning email, read live: open it to see every lineMarketing engine
every piston that brings in marketing clients, and whether it is firing right nowThe five sections
where each part of the business stands, and a door into eachToday
both channels, last 24 hoursNeeds you
what is standing in the way right nowDetail
where the sending stands, and what the system has been doingMailbox load, last 24 hours
Recent activity
Schedule
Every email lined up to send, in the order it will go, with the time in your own time zone (). The times follow the same rules the sender does: working hours, each mailbox's daily limit and spacing, each campaign's daily limit on first emails, and the wait between steps. Anything held back is listed at the bottom with the reason. Press Change on any time to set it yourself: the email then goes at exactly that time.
Send a campaign
Answer three questions to set one up. Every campaign below carries a checklist that says, in plain words, what still stands between it and the first email going out, and one button that takes care of the rest.
New campaign
three questions, nothing sends yetMore options
Sequences
The emails themselves, and how many days sit between them. Reply steps land in the same thread as the first.
Start one
Your sequences
edit the copy, then save each oneContacts
Import a CSV and every column beyond the six known ones becomes a merge field of the same name.
Import
unknown columns become merge fields of the same nameAny column that is not email, first name, last name, company, title or domain
becomes a custom merge field, so a trigger column arrives as
{{trigger}}.
Browse
Lists
A list is who a campaign writes to. Contacts can sit on as many as you like.
Create one
Your lists
Review
Every company you pick from the Lead finder lands here with its cold email written and its place in the Hiring signals queue campaign held. Read it, fix what you want, approve it. Approval releases it into the queue, and the campaign sends on its own cadence for as long as sending is armed. Rejected ones are stopped.
Write a message once with holes in it, then fill or generate it for the drafts you tick.
Holes: {{company}} {{first_name}} {{role}} {{job_title}}
{{industry}} {{icp}} {{summary}} {{headline}}
{{angle}} {{why_now}} {{proof_page}} {{website}} {{my_name}}
Stats
How each outreach template performs, email and LinkedIn side by side, counted from what actually went out. A template's numbers come from the emails and requests sent to people whose draft was written from it. Verdicts are advice, never action: nothing is dropped by the console, and no verdict is given until a template has been sent enough times to mean anything.
Mailboxes
Each mailbox sends on its own schedule and within its own daily cap. Add as many as you need capacity for.
Add one
any SMTP host works; passwords are encrypted before storageYour mailboxes
each sends on its own schedule and capReplies
Anything that comes back, and everyone you have promised never to write to again.
What came back
a reply stops that contact automaticallySuppression
nobody here is ever written to againSettings
The compliance footer, the safety switch, and who else can use this.
Compliance footer
appended to every sendCAN-SPAM requires a real postal address and a working opt-out in every commercial message. The postal address is set per mailbox, on the Mailboxes tab, because the sender differs. This opt-out line is used by all of them, and the address below is only a fallback for a mailbox that has none of its own.
Unsubscribe links are built from this, so it has to be the address a recipient can actually reach.
Used only where a mailbox has no address of its own. Same fields as the per-mailbox one, so a sparse address still reads correctly.
The writer
the key that lets the console write briefs, summaries and cold emailsThe console writes prospect briefs, the one-line summaries on hiring cards, and the cold-email drafts with Claude. That needs an Anthropic API key, made at console.anthropic.com under API keys. Paste it here once. It is stored on the server, never shown again, and used for nothing else. Without it, everything is filled from the raw facts and reads plainer.
An organization-level key needs the Workspace ID too (console.anthropic.com,
Settings, Workspaces, it starts with wrkspc_). A key made inside a workspace does not.
Ask Claude
give the console a command in plain wordsClaude drives the console through its own API, as you. Every call it makes is shown underneath the answer. It will not arm sending, start a campaign, approve a draft, delete or archive anything unless you tell it to. Needs the writer key above.
Browser extension
the hands: LinkedIn, Upwork, hiring signals, follow-upsRun that line in PowerShell. First time: it puts the extension in
%LOCALAPPDATA%\Sibilla Strupule\CCC Network and tells you the three clicks to load
it unpacked. Every time after: it refreshes that same folder in place, and the extension
reloads itself.
On a Mac, the same in the Terminal app:
The updater on your PC runs that same command every six hours (a scheduled task named
CCC extension updater). The extension checks its own files every five minutes and
reloads itself when they change, and asks this console once an hour whether a newer
version exists (it wears a red NEW badge when it does). If you ever install the
extension from the packaged .crx under a managed browser policy, the browser updates it
from /ext/updates.xml instead.
Reply forwarding
send every reply straight to whoever is handling themWhen someone replies, the whole message is forwarded on, with the original attached and Reply-To set to the person who wrote. Whoever receives it can simply hit reply and answer them directly. Bounces are not forwarded.
Safety
Three switches stand between an import and an email going out, and all three must be on. The global switch in the header, the mailbox's own arm switch on the Mailboxes tab, and the campaign being started rather than drafted. Any one of them off means nothing sends. Only an administrator can arm either switch.
API access
for connecting to this platform directlyA single key that stands in for your administrator account, sent as an
x-ops-key header. Anything the console can do can be done over HTTPS with it,
which is how Claude connects to this platform without a browser session. Treat it like a
password. Rotating it takes effect immediately and breaks anything still using the old one.
Team
you are the only administratorYou are the only administrator. Everyone else can run campaigns, import contacts and handle replies, but cannot arm sending or manage accounts.
Add someone
Account requests
Somebody asked for access from the sign-in page. Nothing has been created. Approving sends them a link to set their own password, so you never handle one.
System mail
Password resets and account requests are sent on their own transport, never through campaign sending, so the arm switch can never stop somebody getting back into their own console.
Schedule
Every LinkedIn connect request and message lined up to go, with the time in your own time zone (). Only LinkedIn is here; email has its own schedule under Outbound. The times follow the rules LinkedIn sending runs on: each campaign's working hours and daily limit, the console filling the queue every twenty minutes, and your browser extension sending one at a time every few minutes while it is running. Press Change to set a time yourself, or Send now.
Review
Every decision-maker found for a company you picked from the Lead finder lands here with a connect note written and a place held in the Hiring signals connects campaign. Read it, fix it, approve it. Approval releases it and the browser extension sends the connection request with the note on the campaign's own cadence. Nobody without a LinkedIn profile URL can be queued; paste one in and the same path follows.
Write a message once with holes in it, then fill or generate it for the drafts you tick.
Holes: {{company}} {{first_name}} {{role}} {{job_title}}
{{industry}} {{icp}} {{summary}} {{headline}}
{{angle}} {{why_now}} {{proof_page}} {{website}} {{my_name}}
Worklist
Everything waiting to be done on LinkedIn. Open the profile, do the one thing, mark it off. The extension does the same work automatically for campaigns set to run themselves.
Your account
Waiting
oldest firstCampaigns
A sequence pointed at a list of profiles, run by one teammate's account. Daily ceilings are capped below what LinkedIn tolerates, whatever you type in.
Start one
Sequences
The steps: view a profile, send a connection request, message once connected. Shared across the team, so a good sequence is written once.
Start one
Prospects
People, keyed by their profile URL. Any column beyond the known ones becomes a merge field, exactly as on the email side.
Import
a Profile URL column is requiredBrowse
Lists
Who a LinkedIn campaign works through.
Create one
Your lists
Inbox
Your own conversations, read and answered from here. The extension mirrors them across from your browser, and a reply you write is queued and sent from that same browser, as you. Nothing is sent from this server, and nobody else on the team can see this.
Nothing has been mirrored across yet. Once the extension is installed and switched on it keeps this in step with your LinkedIn by itself, every few minutes, with no asking. This button is only for right now.
Choose a conversation on the left.
Accounts
Each teammate connects their own LinkedIn from their own browser. Nobody shares a login, and work is only ever handed to the browser it belongs to.
The team
This browser
Looking for the extension...
checkingIf it is already installed in this browser it will answer in a moment, and pick up your key on its own.
Download it, put the folder somewhere permanent, and load it from your browser's extensions page. It takes about a minute, and there is still nothing to type into the extension afterwards.
- Unzip it somewhere it can stay. The browser reads the extension from that folder every time it starts, so it cannot go in Downloads and then be tidied away. Your user folder is a good home.
- Open
edge://extensionsorchrome://extensions. - Turn on Developer mode, at the bottom left in Edge and the top right in Chrome.
- Choose Load unpacked and pick the unzipped
ccc-network-extensionfolder.
Then come back to this page. The extension says hello, this console hands it your own key, and it connects itself.
Developer mode is the ordinary way to run an extension that did not come from a shop, and your browser will remind you it is on each time it starts. That reminder is expected. Leave developer mode switched on, because turning it off switches the extension off with it.
Other ways to install it
On Windows, this one line downloads the extension and puts the folder in its permanent home for you, so all that is left is the three clicks on the extensions page. It needs no administrator rights and it writes nothing but that folder. Run it again whenever you want the newest version.
It puts the folder at
%LOCALAPPDATA%\Sibilla Strupule\CCC Network and prints the path to load.
On a Mac, paste this one line into the Terminal app instead. Same result, no administrator password, and it copies the folder address for the Load unpacked step (press Command + Shift + G in the folder picker, then paste).
Your personal key
The extension holds this key. It identifies you to this console, claims only your work, and reports back what it did. It never sees anyone else's. You should not need to touch it; it is here in case you ever do.
Inbox
Everything anybody has said back, on whichever channel they said it. A reply on LinkedIn and a reply by email are the same event, so they are the same row here, and answering one goes back out the way it came in.
Choose a conversation.
Pipeline
Where each conversation has got to. A reply stops the sequence automatically; this is the part where somebody actually does something about it.
Deliverability
What each sending domain publishes, checked from outside the way a receiving server checks it, and how each mailbox is actually performing. A check that cannot be made is reported as unknown, never as a pass.
Sending domains
SPF, DKIM, DMARC and MXMailboxes
the last 200 sends from eachGuard and warmup
Growth
Read a company's own site, turn it into one specific opening line, take a website form straight into a list, and hand somebody a report they cannot send from.
Read a company
Opening lines
stored on the contact as {{opener}}Website forms
Brand reports
read-only, no account neededBrands
Multiple businesses share this machine and must never share a send. A brand owns its mailboxes, its lists, its campaigns, its social accounts and its posts.
The brands
Add one
The voice is handed to the writing help, so an opener sounds like the brand rather than like a machine.
Queue
You do not pick a time for every post. You set the times you are willing to post on each weekday, once, and posts fall into the next empty slot. The gaps below are the point: they are what is missing from the plan.
Posting times
this account's own clockQueue actions
Calendar
The same queue laid out by month. This is the view that answers "is next week thin?", which a list never can. Click a day to write something for it.
Composer
Write once and send it everywhere, or change the words for one network. The counter shows the tightest limit of whatever is selected, because one number that is right beats four nobody reads.
A new post
How it will look
Bulk upload
text, image_url, tags, posting_timeOne row per post. Leave the time blank to put a post in the queue. A tag has to exist already, so a typo cannot invent one.
Ideas
Somewhere to put a half-thought that is not the queue. Drag one along as it firms up, and turn it into a draft when it is ready.
Feeds
the cheapest way to keep this board fullAnalytics
What happened after the post went out, this period against the one before it. Publishing without measurement is just typing.
Day by day
Post by post
most seen firstGoals
Engagement
Comments and mentions on our own posts, in one list. A reply is queued for the browser, the same as everything else: the server cannot post as the account and should not pretend it can.
Accounts
Each account belongs to one brand and is driven from a browser signed in as it. Connecting means the extension has said who it is, not that we hold a password.
Connected
Add one
Tags
Overview
What paid advertising cost this month and what it bought. Spend comes from LinkedIn and Meta; leads are counted from people who actually reached Brevo, not from what the platforms claim. When those two numbers disagree, the platforms are optimistic and this page is not.
Campaigns
Every campaign on both platforms, with what it spent and what it produced. A campaign only counts toward the dashboard piston once you mark what it is for, the same rule the LinkedIn outreach campaigns follow, so the lamp can never go green on an unrelated campaign.
LinkedIn targeting is expressed in facet URNs. Copy them from Campaign Manager's audience builder. The console asks rather than guesses, because a guessed audience spends real money on the wrong people and still looks like it worked.
Leads
Every person who filled in one of our lead forms, with the campaign that bought them, what they answered, whether they reached Brevo and whether they are in the pipeline. Nothing is ever deleted here: a lead that could not reach Brevo is parked, not lost.
Stats
Every campaign, audience and ad judged on the only thing that matters: what a qualified lead costs. Verdicts are advice, never action. Nothing here pauses a campaign or changes a budget; it tells you which one to, and waits. No verdict is given until enough leads have arrived to mean something.
Creative
Ad copy kept in the console rather than lost inside two ad managers, so it can be written, compared and reused. These are the same outreach templates the Review pages use, filtered to the ads side.
Spend
What has gone out, against the ceiling you set. The guard is the second pair of hands: when a ceiling is reached it pauses every live campaign through the platforms themselves, rather than trusting a plan. It only acts once armed.
Settings
Credentials for both ad platforms and for Brevo, the rule that decides a qualified lead, and the naming rule that lets spend be joined to people. Secrets are stored encrypted and never shown again.
Pipeline
Every company currently being nurtured, and how far along it is. Drag a card to move it. This is the hand-kept one: most of the work that turns into money arrives through Upwork or a referral and never touches a sequence.
Companies
Everything the board holds, as a table you can search and sort by what is due. Open one to see every step taken and to log the next.
Money
What has actually been paid, what the active clients are worth over the next six and twelve months, and what the pipeline would add. Earned covers the past twelve months of payments and cannot be argued with. Every projection says what it is based on.
Tracking
Which motion brings people who become money. Money says what was earned; this says who found them. Grouped by motion first, because that is the decision being made, then by campaign inside it. Nothing here is adjusted or smoothed: machine clicks are shown as their own figure and links that went out untagged are counted rather than left out.
Upwork jobs
Paste the link to any Upwork job. It goes straight into the Clients pipeline, the browser extension reads the job page from your own Upwork session, and a dossier is written into its profile: who the client is, their track record, red flags, the angle, and how to open the proposal.
Extension not running? Paste the job text too
Recommended jobs
Your Best Matches, read every three hours, and the daily round's own searches (the Digital Secretary playbook's terms), each with the playbook's verdict and reasons. Add the good ones to the pipeline and each becomes a pending proposal. Hearting a job on Upwork does the same. Dismiss the rest.
Proposals
Every job you add to the pipeline lands here as a pending proposal, with the client's own questions read from Upwork. The assistant writes each one and submits it for review. You read it, then approve it or send it back. On approval the browser extension fills in Upwork's form and sends it, as long as it costs no more Connects than you approved.
Lead finder
Founders and CEOs who could hire you, found four ways: funding news (who just raised or is about to), your own LinkedIn (who reacts, comments or views your profile), events you were at, and people you add by hand. Every one is graded A, B or C with the reasons and where each was read, and matched to the offer that fits them. Peers (coaches, consultants, mentors) are sorted out as Not a fit. Nothing here sends anything: picking someone puts them in Clients, and any message still waits for your approval.
Add someone by hand, or import a list from an event
Podcasts
Podcasts and YouTube channels that interview founders, found every working hour, each rated on one question: is there an honest pitch from your story for their listeners? Every strong fit gets a first email in Pitch emails. Nothing here sends anything.
Journalists and guest blogs
Writers who cover founders, pitching and European startups, and sites that publish guest articles. Rated the same way as podcasts. Nothing here sends anything.
Pitch emails
A first email for every podcast, writer or site rated 60 or more, in your words. Read each one, change anything, then approve or skip it. Approved emails wait: nothing is sent from this console yet.
Commitments
Every yes from a host, writer or editor, with what they asked for, what you sent and what you still owe, so nothing you promised is forgotten.
Grading rules
Every lead is scored out of 100 from the facts on its card. Each fact adds or takes away the points below. Change a number and press Save: every lead is graded again at once. Tier A, B and C are the bars; anything under C, and every peer, is Not a fit.
Funding news sources
public news feeds, read by the console every six hoursSocial listening searches
what the extension searches for on LinkedIn and XSequences
This page is for people already in the pipeline: the Upwork leads and the LinkedIn leads you have spoken to, followed up with on the channel you met them on. Finding new LinkedIn people at scale lives under the Network tab; this is what happens after. A sequence belongs to a stage. A company that moves stage stops getting the old stage's follow-ups the moment it moves, and nothing sends unless the console is armed and the sequence is running.
Following up on Upwork
Messages typed into the same Upwork conversation you already have with them, by the browser extension, from your own signed-in account.
Following up on LinkedIn
Messages sent in the LinkedIn thread you already have with them, by the browser extension. This is the follow-up side; the outreach side is under Network.
Following up by email
For companies that have given you an address. Sent from the console's own armed mailbox.
The queue
Archive
The whole client history in one place: who is still in business, how their site holds up, and how their audience responds. A lead marked Won in the Pipeline joins on its own, and the console re-checks every site and YouTube channel daily. Click a column to sort, a row to open it.
Leaderboards
The top ten on each measure. Click any name to open it. Engagement only counts the last twelve months of posts, so an account that went quiet cannot ride on old numbers.
Archived leads
Prospects who were never signed and have had nothing logged against them for over fifteen days leave the board on their own, so what is left on it is what is actually live. Nothing is deleted. Bring one back and it returns to its old stage.
Activity
Every step logged against every company, newest first, and which companies have gone quiet. A lead nobody has touched in a two weeks is the thing this page is for.