Search & market research
Broad searches by industry, geography, company profile, and decision-maker role, refined into your target market.
GTM ENGINEER
For B2B founders and sales teams whose outbound tools and data need to work together.
I identify the problems with your outbound and solve them. The solutions will stay in your system and scale with it, from prospecting and enrichment to infrastructure, campaigns, and CRM.
30 minutes · Your outbound, the bottleneck, and a practical next step.
ICP · buying signals · research
Company fit, contacts, and verification
Segments, CRM sync, email & LinkedIn
Replies, intent, and campaign reporting
SOURCES & SIGNALS
I combine targeted searches with signals that explain who to reach, why they fit, and when to start a conversation.
Broad searches by industry, geography, company profile, and decision-maker role, refined into your target market.
Relevant posts, comments, mentions, and engagement on LinkedIn, X, and other communities.
Job openings, new hires, and role changes that reveal team priorities and emerging needs.
Funding, expansion, technology adoption, and website changes that help explain why an account is relevant now.
Product activity, sign-ups, CRM events, and previous conversations from your own systems.
HOW I CAN HELP
I identify the bottleneck and solve it with the right data, infrastructure, and automation.
Qualified accounts and contacts built around your ICP and buying signals.
ICP / TAM / SIGNALSEnrichment waterfalls, contact recovery, and email verification.
CLAY / ENRICHMENT / VERIFICATIONMailboxes, DNS authentication, warmup, inbox placement tests, and deliverability checks.
MAILBOXES / PLACEMENT / DELIVERABILITYEmail and LinkedIn sequences, personalization, follow-ups, and reply handling.
SEQUENCES / COPY / REPLIESn8n workflows and AI research connecting enrichment, outreach, and CRM.
N8N / APIS / AI RESEARCHClean records, lead routing, and reporting tied to real campaign conversations.
CRM / ROUTING / REPORTINGGTM SYSTEMS
Examples of my work across prospecting, enrichment, campaign routing, and outbound infrastructure.
I refined which companies and people the campaign should target, and the criteria used to select them.
I changed how leads were scraped so the source lists matched the revised ICP.
I updated the mailbox setup and sending settings before launching the campaigns.
For campaigns with 20k+ leads, I refined the ICP, changed the scraping method, and updated the email infrastructure.
Early results from the initial sends, compared with earlier campaigns.
Collect relevant posts and activity through the signal tools.
Check delivery, remove duplicates, and review each person’s role and company.
Send matching profiles to the review list and keep uncertain cases separate.
I connected LinkedIn activity to Clay, then checked who matched the target and who needed to be excluded.
A working Clay intake and a prospect list with clear exclusions.
Identify missing contact fields and reuse the information already in the stack.
Cross-check profiles and contact details against the original person and company information.
Save confirmed matches and list what still needs verification.
I recovered professional profiles and contact details from incomplete lists, using the original identity data to check the matches.
Missing details recovered without replacing good data or adding guessed profiles.
Check mailbox settings, authentication, warnings, and bounce history.
Apply agreed settings and isolate confirmed problems.
Read back the changes and hand over any repairs that still need the provider.
I checked the mailboxes, sending settings, and campaign assignments, then fixed the issues I could confirm.
Consistent sending settings and problematic assignments taken out of the sending flow.
WORKING WITH ME
We agree on the scope and success checks before implementation. The workflows and documentation are handed over to your team.
Review your offer, target accounts, current stack, and the point where the workflow breaks.
A clear problem and agreed priorities.
Choose the data, integrations, and infrastructure needed. Agree on deliverables, dependencies, and checks.
A focused implementation plan.
Implement in your existing tools, test on a bounded sample, and inspect data quality, routing, and saved settings.
A system checked against the agreed scope.
Walk your team through the workflows, rules, documentation, and remaining dependencies. Agree on any further support.
A system your team can operate and maintain.
A LITTLE ABOUT ME
I’m Alessandro Pala, a GTM engineer. I work on the systems behind B2B prospecting and outbound: qualified data, connected tools, campaign operations, and reporting. My background in data engineering and mathematics supports that work.
I enjoy making complicated workflows understandable: clear inputs, explicit rules, reliable outputs. Away from the screen, you’ll find me hiking, fishing, or playing airsoft.
EDUCATION
2023–2026
Università degli Studi di Padova
Machine learning, deep learning, optimization, and numerical methods.
2020–2023
Luiss Guido Carli University
Economic modelling and agent-based systems.
BEFORE WE TALK
B2B founders and sales or revenue teams that need better prospect data, connected outbound workflows, or a clearer view of their sending infrastructure. We use the first conversation to check whether the problem fits my work.
Yes. I start with your existing stack and use tools such as Clay, n8n, Smartlead, and Lemlist where they fit. Any new integration or paid provider is part of the agreed scope.
The scoped workflows, configuration, field mappings or datasets, plus the documentation and walkthrough needed to use them. Deliverables depend on the problem we agree to solve.
The work is built in your agreed accounts and tools. You retain access to the workflows and documentation; any third-party subscription or provider dependency is made clear.
After understanding the problem, I propose the deliverables, dependencies, timeline, and price for that scope. Implementation starts once those are agreed.
Follow-up work, maintenance, and further improvements can be scoped separately. The handover explains how the system works and identifies anything that still depends on your team or a provider.
We discuss your offer, target customers, current stack, and the part of outbound that needs attention. Bring a short description of the problem and the tools you use. The call helps us decide the next step.
LET’S WORK ON YOUR GTM
Tell me about your offer, target customers, current tools, and the part of your GTM workflow you want to improve.

