loops
Describe a loop once. Kumo runs it forever.
A loop is recurring work Kumo owns end to end: watch the trigger, do the work, report back in Slack. These are the 27 loops teams hand it first.
Run the marketing machine
Campaigns, intent, and attribution worked on between the weekly reviews instead of during them.
every monday · 8:00 am
Kumoapp8:03 AM
$18.4k spend, 22 MQLs, 6 opps sourced. Paid social down, webinar up. Breakdown in thread.
The Monday campaign readout
Written before standup, not rebuilt by hand during it.
when a target account visits pricing
Warm the intent signal
Site intent matched to the account, campaign history checked, and the owning rep handed a reason to reach out.
every month
Attribution without the spreadsheet
Which campaigns actually sourced closed revenue, traced through the CRM and reported without a BI project.
on demand
Turn the call into a case study
Recordings and CRM outcomes drafted into a customer story, ready for a human edit.
Turn signals into pipeline
Kumo sees the signal and runs the loop the moment it fires.
Maya9:12 AM
@kumo when a positive reply lands: enrich the sender, book the meeting, open the opp, ping the owner.
👀 1Kumoapp9:13 AM
Loop saved. First reply handled: meeting Thu 2 PM, opp open, rep pinged.
Triage every reply
Set it in a thread once. No positive reply sits overnight again.
when a champion changes jobs
Follow the champion
New company enriched, your history together checked, warm outreach queued.
when a target account raises
Catch the raise
Round and exec team enriched, outreach personalized on the news, sent the same day.
when hiring spikes at an account
Spot the hiring spike
An account hiring for the role you serve joins a live list, right contacts attached.
on demand
Clone your best customers
“Find 500 companies like our top 20.” Scored, tiered, pushed to the CRM.
every morning
Who to touch today
One DM per rep: warm accounts, fresh signals, and why now.
Keep your data alive
B2B data decays fast. Kumo treats hygiene as a nightly loop, not a quarterly project.
call with northwind ended · 3:42 pm
Kumoapp3:44 PM
CRM updated: next step, close date, champion. Follow-up drafted.
The CRM updates itself
The call ends. The record is already right.
every night
The nightly sweep
Stale fields re-enriched, dupes merged, dead deals flagged. Report by morning.
when a lead comes in
Speed-to-lead
Form fill to enriched, ICP-scored, routed lead in minutes.
every day
Don't burn the domain
Bounces, inbox placement, and reputation watched across every mailbox.
Win the meeting, save the renewal
The research is done before you ask. The follow-through happens without you.
acme renewal quiet for 14 days
Kumoapp8:05 AM
Flagged to the owner with an angle: the security review that stalled it.
Catch the deal going quiet
Flagged with context and an angle, not just a reminder.
30 min before every external call
Never walk in cold
Deal history, call notes, and attendee background, posted before you join.
when usage drops or a champion leaves
Catch churn early
Usage dips, ticket spikes, champion exits: CS gets the save motion, early.
when a renewal is 60 days out
Walk into the renewal armed
Usage, open tickets, and every promise made on past calls, gathered before the conversation starts.
Reports that write themselves
The reports your team rebuilds by hand every week, delivered on schedule.
every friday · 8:00 am
Kumoapp8:02 AM
Coverage 3.1x. Four deals slipped, two need next steps. Full report in thread.
Friday pipeline report
In your channel before the review, not after it.
every week
Watch the competition
Pricing, changelogs, reviews, and job posts, digested into updated battlecards.
at scale, per contact
Personalize at scale
Every row researched: site, posts, podcasts. Every opener written one by one.
when the loop doesn't exist yet
The loop that doesn't exist
Kumo writes the code, calls the API, glues the systems, runs it on a schedule.
It ships code, too
Kumo has its own computer. When the loop needs real code, it writes it.
Eli2:07 PM
@kumo three customers hit the CSV export timeout today. Find it, fix it, open a PR.
👀 1Kumoapp2:19 PM
PR open: exports stream in batches now. Tests pass, review when ready.
From ticket to PR
Not a summary of the bug. The fix, with tests, waiting for review.
when the error tracker spikes
Catch the regression
New error grouped, offending commit found, owner pinged with the diff.
when a ticket is really a bug
Triage to the right place
Support threads become Linear issues with repro steps, or a fix on a branch.
every release
Release notes, written
Merged PRs turned into notes humans want to read, posted where customers look.
on demand
The internal tool you never built
A dashboard, a migration, a script: built in the sandbox, shipped the same day.
your first loop
Put a loop to work this week
Connect your stack, describe the work in a thread, Kumo takes it from there.
Hire your Agent