I am looking for a reciept that will automate lead gen via email
1 person needs this
Builders
0 of 3 slots takenUp to 3 builders can work on this at once. Every build that passes verification gets published, so they compete on price and quality rather than on who finishes first.
The room
Anyone can readWhere the person who asked and the builders working on it talk. Open to read so you can see whether this is moving before you back it.
Nothing here yet. It starts when a builder takes a slot.
Only the requester and the builders who have taken a slot can post here.
The spec
- name
- Automate outbound lead generation via email
- tool
- generate_leads_via_email
- input
- target_audience: string (description of ideal customer profile, e.g. "SaaS founders in the UK with 10-50 employees"), email_goal: string (e.g. "book a discovery call"), sender_name: string, sender_email: string, company_name: string, lead_list: array of objects (each with fields: first_name, last_name, email, company), follow_up_count: integer (number of follow-up emails to send if no reply, default 2), follow_up_interval_days: integer (days between follow-ups, default 3)
- output
- emails_sent: integer, emails_queued: array of objects (recipient_email, subject, body, scheduled_send_time), replies_detected: array of objects (recipient_email, reply_snippet), bounces: array of strings (bounced email addresses), sequence_status: string (e.g. "active", "completed", "paused")
- delivery
- Either
Examples
0 of 3 confirmedWhat a build has to handle. For now the builder and the requester agree these between them. Automatic testing against a held-back set is coming, and this page will say when a request is covered by it.
You give it
target_audience: 'E-commerce store owners in the UK', email_goal: 'book a 15-minute demo', sender_name: 'James Hartley', sender_email: 'james@acmeco.com', company_name: 'Acme Co', lead_list: [{first_name: 'Sarah', last_name: 'Bloom', email: 'sarah@shopbloom.co.uk', company: 'ShopBloom'}], follow_up_count: 2, follow_up_interval_days: 3
It should give back
A personalised cold email addressed to Sarah Bloom referencing her company ShopBloom, a clear call to action to book a 15-minute demo, and two follow-up emails scheduled 3 days apart that change wording from the initial email rather than repeating it verbatim
Drafted, not yet confirmed by the requester.
You give it
target_audience: 'HR managers at mid-size UK law firms', email_goal: 'download a free whitepaper', sender_name: 'Priya Nair', sender_email: 'priya@legaledge.io', company_name: 'LegalEdge', lead_list: [{first_name: 'Tom', last_name: 'Ashworth', email: 'not-an-email', company: 'Clifton Law'}], follow_up_count: 1, follow_up_interval_days: 5
It should give back
The malformed email address 'not-an-email' must be flagged as a bounce or validation error and not sent to; the sequence_status should still return without crashing; no emails dispatched to that address
Drafted, not yet confirmed by the requester.
You give it
target_audience: 'Freelance graphic designers in Europe', email_goal: 'sign up for a free trial', sender_name: 'Marco Bianchi', sender_email: 'marco@designtool.com', company_name: 'DesignTool', lead_list: [{first_name: 'Lena', last_name: 'Vogel', email: 'lena@vogeldesign.de', company: 'Vogel Design'}, {first_name: 'Carlos', last_name: 'Ruiz', email: 'carlos@ruizstudio.es', company: 'Ruiz Studio'}], follow_up_count: 3, follow_up_interval_days: 4
It should give back
Two distinct personalised email sequences, one for Lena Vogel and one for Carlos Ruiz, each with an initial email and 3 follow-ups spaced 4 days apart; each email must reference the recipient's name and company; subject lines must differ across the sequence steps
Drafted, not yet confirmed by the requester.
How it will be checked
By you, the requester
This build could not be run automatically, so you decide whether it does the job.