Skip to content

Karl Kyamko

A-Z Outbound Engine

Cebu, PhilippinesLinkedIn@karlkyamko in Clay Slack

The work began with a real operating problem and exposed gaps in the first approach. By testing the workflow against evidence, the student turned those gaps into a repeatable system the team can keep improving. Graduated Outbound Orchestration Foundations Cohort 3. 6 builds submitted along the way. Every card below is real work from the program, with the artifact linked where one exists.

1Cohort finished, every submission gradedFrom Clay
6Builds shippedFrom Clay
16Classmates helped, marked by themFrom Clay

Work

Reviewed inside a cohort where it says so. Numbers are the student's.
Case study
Outbound Orchestration Foundations Cohort 3
A-Z Outbound Engine
The team needed to replace manual work with a system that scales. Built A-Z Outbound Engine as a repeatable Clay workflow. The result is a reusable system the team can inspect, run again, and keep improving.
Case study
Assignment: My self-reflection
Looking back Before OOF: I had the cold email setup (domains, mailboxes, warm-up, sequencer) but my list was a rough guess at "B2B agencies". What I wanted to fix: a tight list and personalization that scales. OOF fixed it. Clay now builds the list, enriches it and writes Email 1. Then I scale the winner.
Case study
Build your outbound engine
My Outbound Engine: Clay to Instantly What I built Sequencer needs an upgrade on my plan, so I built the same engine with the sequencer I already use, Instantly. Clay finds the founders, enriches them and writes Email 1 with my Claygent. Last follow-up: 5 days later, one booking link, opt-out by reply.
Case study
Write your outbound message
The email (Justin Kramm, Founder & Host @ Shitshow Creative)Subject Line: mission-driven brandsEmail Body: Hi Justin, Sorry if this is too upfront, but who on your team reaches mission-driven brands first? I help creative agencies turn cold lists into booked calls. Want me to send it over? 44 words.

Skill map

2 Clay use cases proven. Tap or hover one to see the proof and what it is built from.
Proof levelsCertified by ClayVerified workShared, in review
Phase 1

Crawl

Clean, scored data you can trust

1 proven
Phase 2

Walk

Automations that run without you

1 proven
Phase 3

Run

Signals and reps working the same system

0 proven

Data foundation

Reachable accounts and contacts, lower tool spend

Crawl

Grow pipeline

Outreach volume, reply rate and speed to lead

Walk

Building blocks

12 proven. The Clay skills every use case is made of. Tap or hover a use case to see its recipe.

Sourcing2Where records come from
Enrichment2What you learn about them
Logic5What you decide
Activation2Where the decision lands
Operate1Why it keeps working

Credentials

Issued by Clay. Anyone can verify the ID.

Outbound Orchestration Foundations Cohort 3 diplomaOutbound Foundations

Cohort completed, every submission graded
Oct 2026 · CC-DIP-225239A5Verify
0.25% of the Clay community hold this

Badges

5 of 12 earned
First build shipped
Submitted your first assignment
Sep 2026
2.1% of the Clay community hold this
Five builds shipped
Five assignments submitted
Earned
0.87% of the Clay community hold this
Cohort finisher
Every module, every submission, graduated
Oct 2026
0.73% of the Clay community hold this
First reply
Answered a classmate
Oct 2026
1.4% of the Clay community hold this
Helped 10
Ten classmates reacted to your posts
Earned
1% of the Clay community hold this

Teams I've built for

Skills

Levels come from graded work and certifications, not self-report
Outbound Orchestration FoundationsAdvanced
ClayWorking
GTM engineeringWorking

Journey

Graduated Outbound Orchestration Foundations Cohort 3
Diploma earned
Oct 2026
First reply
Answered a classmate
Oct 2026
Joined Outbound Orchestration Foundations Cohort 3
Outbound Orchestration Foundations
Sep 2026
Credentials and badges are issued by Clay. Karl can hide them, not edit them.