Automated Cold-Outreach System Development
Budget / SalaryHourly project
TypeFreelance project
LocationRemote
Posted3 hours ago
Hi,
We've spoken to a few people already and none of them really seemed to understand what we're after. So before anything else — can you confirm you know exactly what we need and how you'd help?
Here's the situation.
We're a UK email and SMS marketing agency. Two of us. Ten clients, all on Klaviyo. We sell to competition and prize draw websites, and we're expanding from there.
We want a cold outreach system that runs without either of us babysitting it. If a step needs a human to copy something from one tool into another, it won't happen.
WHAT IT NEEDS TO DO
A prospect goes in one end. A booked call comes out the other. Nobody touches anything in between.
THE SCALE
We know the niches we want to go after and we'll keep adding more. Thousands of emails a week across multiple verticals.
Built to scale from day one, not patched later.
WHAT WE'VE GOT
- The niches and the targeting criteria, ready to build lists from
- A do-not-contact list we can never email by accident
- Clay, Lemlist, HubSpot, Calendly and Zapier
- We'll buy the domains and set up the inboxes before you start
WHAT WE NEED BUILT
1. Sending domains set up properly — SPF, DKIM, DMARC, tracking domain, warmup. Never our main business domain, that carries client email
2. Clay — list building, enrichment, email verification, and an automatic filter against the do-not-contact list. Built so we can repeat it ourselves on every new niche
3. Lemlist — sequences across email and LinkedIn, replies stopping the sends
4. HubSpot, Calendly and Zapier wired together so a reply or booking creates a record and pings us on Slack
Then a recorded walkthrough and written notes so we can run it ourselves.
WHAT WE'RE NOT ASKING FOR
We write our own sequences and copy. We're buying the infrastructure, not the messaging.
WHAT WE'D LIKE FROM YOU
We're not telling you how to do this. You know it better than we do.
- How long does it take, and what would it cost?
- At this volume, how many domains and inboxes do we actually need?
- Is this the stack you'd recommend? If you'd build it differently, tell us what and why.
- We may add personalised video to the first touch later — does that change how you'd set anything up?
If anything above is the wrong way round, say so. We'd rather hear it now than after it's built.
Thanks,
Jack
We've spoken to a few people already and none of them really seemed to understand what we're after. So before anything else — can you confirm you know exactly what we need and how you'd help?
Here's the situation.
We're a UK email and SMS marketing agency. Two of us. Ten clients, all on Klaviyo. We sell to competition and prize draw websites, and we're expanding from there.
We want a cold outreach system that runs without either of us babysitting it. If a step needs a human to copy something from one tool into another, it won't happen.
WHAT IT NEEDS TO DO
A prospect goes in one end. A booked call comes out the other. Nobody touches anything in between.
THE SCALE
We know the niches we want to go after and we'll keep adding more. Thousands of emails a week across multiple verticals.
Built to scale from day one, not patched later.
WHAT WE'VE GOT
- The niches and the targeting criteria, ready to build lists from
- A do-not-contact list we can never email by accident
- Clay, Lemlist, HubSpot, Calendly and Zapier
- We'll buy the domains and set up the inboxes before you start
WHAT WE NEED BUILT
1. Sending domains set up properly — SPF, DKIM, DMARC, tracking domain, warmup. Never our main business domain, that carries client email
2. Clay — list building, enrichment, email verification, and an automatic filter against the do-not-contact list. Built so we can repeat it ourselves on every new niche
3. Lemlist — sequences across email and LinkedIn, replies stopping the sends
4. HubSpot, Calendly and Zapier wired together so a reply or booking creates a record and pings us on Slack
Then a recorded walkthrough and written notes so we can run it ourselves.
WHAT WE'RE NOT ASKING FOR
We write our own sequences and copy. We're buying the infrastructure, not the messaging.
WHAT WE'D LIKE FROM YOU
We're not telling you how to do this. You know it better than we do.
- How long does it take, and what would it cost?
- At this volume, how many domains and inboxes do we actually need?
- Is this the stack you'd recommend? If you'd build it differently, tell us what and why.
- We may add personalised video to the first touch later — does that change how you'd set anything up?
If anything above is the wrong way round, say so. We'd rather hear it now than after it's built.
Thanks,
Jack
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.