GTM Engineer for B2B SaaS founders
Outbound starts when the sales rep arrives.
Or now.
Limens builds and operates your pipeline for three months. You validate the ICP and the offer. The rest runs without you.
15 min on video. No slides, no pitch.
What you get
You provide the ICP and the offer. You get a complete pipeline, operated for three months. Nothing to wire up on your end.
- 01300 accounts qualified to your ICP
- 02Scoring on 3 intent signals chosen with you
- 03Founder or decision-maker identified, email verified
- 04Sending infrastructure on a dedicated domain, warmup included
- 053 sequence variants (3 emails each), in your prospects' language
- 06Cadence of 30 emails per day, over 10 to 14 days per wave
- 07Attio pipeline synced continuously
- 08Weekly performance report
Three intent signals
The method is fixed. Three signals max per pilot, chosen with you based on your ICP. Three main families.
Your target hires for a role that maps to a problem you solve. SDR, Head of Data, first dbt engineer, VP Sales with no team. The role stays open a few weeks, and the window closes fast.
Funding round, capital raise, new office, entity restructuring. Budget just opened up. Nobody has decided who to spend it with yet.
A stack change detected on BuiltWith. A public-record filing that reveals a decision invisible to standard tools. You show up at the right moment, with context nobody else has.
Past three, attention scatters.
Three months to deliver
The pilot runs three consecutive months. Not divisible.
Dedicated domain, DNS, mailbox, warmup. Sourcing and enrichment of the first 300 accounts. Copy validated with you.
No outbound during warmup. Non-negotiable for deliverability.
30 emails per day. First replies come in. I iterate on copy and signals based on what the data shows.
Sequence validated against real data. Second wave. Meetings logged in Attio. Final deliverable prepared.
No meetings before month 2. Less than three months isn't honest: the 'reply → iterate → second wave' cycle doesn't fit in one month.
Three workflows to inspect
Architecture, scoring, prompts, and generated copy are public. Same register as your future pilot, on different ICPs.
Built during the Clay bootcamp. The approach, tools, and enrichment choices match what you'll get on your ICP, in your prospects' language.
Who runs Limens
One person from sourcing to reporting.
Richard Angapin, founder. 15 years in technical support: PokerStars, Run It Once, ROI Hunter, Quable. Environments where a reply lands in under 4 minutes or the customer leaves. That's where I learned to dig into a problem until I actually understand what's happening.
I left in 2025 to move into GTM. Same diagnostic reflex, applied to outbound. Clay bootcamp, then daily building. Today I run Limens.
Three tools, operated for you
Market standards. If you want to take it back in-house, everything is portable: the list, the sequences, the CRM pipeline.
Questions people actually ask
How fast are you operational?
Setup in four weeks, warmup included. First commercial sends go out at the start of month 2. Deliverability doesn't allow faster. Anyone promising 'operational in one week' is promising to burn your domain.
How many meetings do you guarantee?
None. The only way to guarantee them is to lie about the ICP or send spam. The system, I do guarantee: it runs as specified. The commercial outcome depends on your offer and your response speed.
Why three months?
Month 1 is pure setup: domain, warmup, sourcing. In month 2, first sends go out and first replies come in. In month 3, I iterate on real data before sending a second wave. Less than three months doesn't hold up: the 'reply + iterate' cycle doesn't fit in one month.
What if it doesn't work?
If after 300 sends the positive reply rate is below 1%, I run a documented audit with you. Two possible outcomes. If the system ran fine but the ICP or offer isn't a market fit: we stop at month 2 and I refund €1,000. If the problem is on my side (copy, signal, list quality): I iterate at no extra cost.
Who is this not for?
Three cases. If any applies, I don't sign.
- You can't qualify replies within 24 hours.
- You don't have a clear offer to sell.
- You're looking for a guaranteed number of meetings.
A system amplifies what's already there. If something is broken upstream, the system makes it visible faster, to more people. You're paying to amplify the problem.
What happens after three months?
Three options to discuss in month 3, based on the data.
- Light continuation: €2,000/month, reduced scope.
- Full retainer: €3,000/month, extended scope.
- Clean exit: you leave with the assets (account list, copy, templates, Instantly setup, signal documentation).
No automatic renewal.
Who's behind Limens?
Richard Angapin, solo. You always talk to the same person, from sourcing to reporting. No junior doing the work while a partner manages the account. More detail above.
Another question?
Fifteen minutes on video. You explain where you stand. You leave with a straight answer: Limens, something else, or nothing at all.
Founder pricing
15 min on video. No slides, no pitch.