Clay / Apollo Lead Generation Engineer (Build a Reusable Sourcing Engine, Not a One-Time List)

Company: Foundry Connects Inc. Engagement: Fixed-price pilot first, ongoing volume if it lands Tools required: Clay (waterfall enrichment), Apollo About us Foundry Connects is a mobile-first field service management platform for independent contractors and service pros across 100+ trades: the plumber, electrician, HVAC tech, landscaper, and cleaning company owner who runs their whole business from their phone. We launched commercially in June 2026 and we're building out our outbound and partner pipeline now. What we are actually buying Read this part carefully, because it is the whole job. We are not buying a list. We are buying a reusable, Foundry-owned Clay engine that produces lists on demand, parameterized so we can swap in a new trade or a new state and re-run it ourselves without you in the loop. The list of names is just the proof the engine runs. The engine is the deliverable. If your instinct is to export a CSV and hand it over, this is not the role. If your instinct is to build a table we keep and press again next month for the next batch, keep reading. The two motions the engine has to serve Direct acquisition. Owners of small local trade businesses. These are mostly solo operators and small shops, so they do not show up cleanly in standard B2B databases. The right sources are state contractor licensing boards, Google Maps and local listings, and waterfall enrichment to find the owner's name, cell, and email. Channel partners. Real companies with findable people. Small accounting and bookkeeping firms are the first target, and the natural seed list is Intuit's Find-a-ProAdvisor directory filtered to specific metros. The pilot (your proof the engine works) A bounded, fixed-price first run: Roughly 200 accounting and bookkeeping firms across [TARGET METROS], one primary decision-maker per firm (owner or principal), plus a second contact only where the firm is large enough to have a distinct practice lead, flagged "where available." A contractor sample in [TRADE] in [STATE], sourced from the state licensing board and enriched to verified contact. This scope is deliberate. It tests the one thing we do not yet know, which is whether you can source local, small-trade owners and not just funded companies. Hard deliverables (this is what makes it an asset, not a dump) The Clay table itself, handed over, not just its CSV output. Built parameterized by trade and geography so we can change the inputs and re-run it for the next state or trade ourselves. Built inside our Clay workspace, with you invited in. The tables, sequences, and data stay ours. A written SOP plus a short Loom walkthrough, so a Foundry team member or a builder we bring later can operate and modify the table without you. Full source and logic transparency. Which licensing boards and registries, which providers in the waterfall and in what order, which filters define the ICP. CRM-ready output on the first pass: name, title, company, verified email, phone, source, match-confidence level, and a dedupe indicator. Must-have skills Clay at a real level: building waterfall enrichment tables across multiple providers, not running a template once. Apollo as one provider inside that waterfall. Demonstrated sourcing of local, small-business owners from public registries (licensing boards, local directories, parcel or registry data), not only corporate decision-makers. Clean dedupe and verification discipline. What this role is NOT Not a data-entry or one-time list-scraping gig. Not prospect-facing outreach. First contact, calls, and relationship building are handled by our team, so this is a pure sourcing and systems role. Not a mass-scraping, spray-and-pray operation. Quality and reusability over raw volume. To apply Tell us about one time you sourced hard-to-find local business owners from a public registry and enriched them to verified contact. Name the registry, your waterfall, and the match rate you actually hit on that segment. Then confirm you will build and hand over a reusable, parameterized Clay table, not just its output.