Leanercloud

Locked a 4-touch cold-outreach sequence for LeanerCloud's FinOps Implementation campaign, built line by line over a full session rather than drafted once and shipped. Each email runs on one word ("close"/"closed") from the opening CTA through a real anonymized client's list of fixes (a $988k/year case, shown as both proof and a preview of what a similar list would look like for the reader) to the breakup's last line. Cut the sequence from 5 touches to 4 after checking the actual cadence data behind a cold-email research report - which turned into three independent verification passes on that report's claims. Most of it held up (Gong's real 28M-email finding that pitching in email 1 costs up to 57% of replies), but a few numbers were fabricated or conflated (a stat attributed to Lavender that doesn't match anything Lavender's published, a startup-funding rate with no real source).

Also split cold outreach out of the general copywriting skill into its own dedicated skill - the per-prospect research process and the delivery/spam-filter problem are different enough from landing pages and ads that they stopped fitting as one branch. Restructured it to lead with a fill-in-the-blank template instead of process theory first, and cut invented jargon after Eli flagged that it's hard to parse cold months later.

partnering with IT consulting firms that already sell FinOps to their clients. The theory is that most of these firms sell the advice - assessments, advisors, roadmaps - and then hand the actual changes to the client's engineers, who rarely get to them. That's the same gap LeanerCloud's positioning is built on, one step removed. So the pitch to these firms is to be the implementation half of what they already sell.

The research turned up a clean filter. The best-fit firms are the ones whose own marketing says, in so many words, that implementation is the client's job. We shortlisted eight firms plus one distribution channel out of about 45 candidates, and set aside the ones that already do the fixes themselves as competitors.

The first email is nearly done. A few lessons from drafting it: open by asking who makes the change after a recommendation, not by lecturing a FinOps director on FinOps. Use a technically deep case as proof rather than an easy win, because these firms pride themselves on depth. And unlike a normal cold email, say plainly who we are, because to a firm that sells FinOps an unexplained sender reads as a competitor. We also traced a much-quoted savings figure back to its original source and locked it, after finding it had drifted across a dozen drafts.

warm messages to FinOps people the founder already knows. Before writing anything we surveyed the standard advice on reaching out to your own network (Alan Weiss, The Mom Test, Win Without Pitching, Josh Braun, Dean Jackson's nine-word email). The schools agree you shouldn't pitch in the first message. Where they split is what the conversation is supposed to lead to.

We chose a diagnostic call as the destination, not a sale made in the message. The reason is volume. Selling in the message works as a filter when you have thousands of prospects and only want serious ones. With a handful of warm contacts and founders who sell best on a call, you want the call. The flow has four beats. Open with something from your shared past. Let them ask what you're up to. Answer with the news. Then end on a question about how cost fixes actually get done on their side, so the reply can't be a polite "oh cool."

The founder now has a short doc he can act on. The research was also saved as a reusable resource for future outreach work.

The landing page skill now generates 5 variants in one pass: 4 narrative frameworks each in a matched copywriter voice (DPCG/Ogilvy, AIDA/Schwartz, PAS/Halbert, BAB/Fried) plus a proof gallery. All use the writing skill's clean-context method - distill to bullets, hand to a fresh agent with just the substance and the voice name.

Key finding: Bernbach is a structure (copy+image pairs, proof gallery layout), not a voice. Using "Bernbach" as a voice anchor produced generic AI-brevity. Same structure with "Jason Fried" as voice produced distinctly sharper copy - "Someone Finally Does It" and "Same alert. Same dashboard. Fourth month running." The lesson: you always need both a layout concept AND a voice anchor. They're independent choices.

All 9 variants (4 original PG voice, 4 voiced, 1 proof gallery) browsable at misc.finereli.com/cristi-copy with a mode switcher. Ready for Cristi to review alongside the positioning docs.

Position B (FinOps Implementation) is the final positioning. Position A (Fractional FinOps) dropped. Position C (Enterprise FinOps) folded in as the scaling path - same positioning, more engineers, fractional managers for operations.

The core message: FinOps teams identify savings but lack dedicated engineering capacity to implement them. Cristi is the engineer who does the work nobody else will, because his real job is building cost optimization tools - implementation is deploying them. Monthly retainer model, not percentage-of-savings (that's a company wrapper for later).

Next steps: campaign landing page, cold email targeting FinOps professionals, website copy update. Cristi's heading to the Amsterdam FinOps conference to validate the positioning in person. Also restarting the Archera/CUDly paid development gig (~$14k/mo) as immediate income.

Three positioning artifacts published for review. Committed to the leanercloud repo along with all research material and working notes.

The session started with a dead cold email campaign (412 sent, 0 replies) and ended with three distinct, validated positions that map to three growth stages: Cristi as fractional FinOps (now), Cristi offering implementation capacity to FinOps teams (near-term), and LeanerCloud as an enterprise FinOps company staffed entirely by ex-AWS engineers (horizon).

The positioning skill got two updates: multi-position outputs when the ICP split is real (upgraded from open to working), and a new competition step (placeholder) for enterprise-scale positioning. Also refined the "do them one at a time" guidance for running multiple positions.

Two complete positions, each with a specific ICP, validated structural insight, and distinct frame.

Position A (Fractional FinOps) targets CTOs at smaller companies who are drowning under orphan responsibilities. The frame assumes delegation and asks "who should you hand it to?" The new thing: a fractional FinOps person who's also a senior engineer, owning the whole loop end to end. Key insight: fractional beats full-time because a full-timer drifts (gets absorbed into other work), while fractional stays focused because cost optimization is their only job across all clients.

Position B (FinOps Implementation) targets FinOps practitioners at larger companies who can see waste but can't get engineering to implement fixes. The frame leads with the negative - naming the structural helplessness of a role that has responsibility without power. The new thing: dedicated implementation engineers, something no FinOps team has because no engineer wants the unglamorous work. Cristi can because his real job is building the tools - implementation is just deploying them.

A third position (LeanerCloud-the-company, percentage-of-savings pricing) is parked for later. The pricing split matters: person-shaped positions price as retainers, company-shaped positions price as percentage-of-savings.

The #1 complaint from FinOps practitioners - consistently top-ranked in FinOps Foundation surveys and dominating practitioner discussions - is "getting engineers to actually take action on cost recommendations." That's the exact pain we built the positioning around.

Position B's new thing (dedicated implementation engineers for cost savings) directly addresses the structural gap the entire industry is complaining about: tools diagnose but don't fix, engineers deprioritize cost work because they're measured on features, and FinOps practitioners are stuck filing tickets into the void.

Also discovered a unifying concept across both positions: dedicated beats what the Israelis call נע״ת (nosef al tafkid - added on top of your already full role). Every attempt to solve cost optimization internally makes it someone's side task. Side tasks never get done because the primary role always wins. External/fractional stays focused because it's their only job.

The pains analysis by ICP revealed something we missed entirely in v1: the person with the highest pain intensity (9/10) is the FinOps lead - or whoever owns cloud cost at the company. Their core suffering is "responsible without empowered" - they can see the waste in dashboards, they file tickets, engineering never prioritizes the fixes, and they look ineffective. The v1 campaign sent 20 generic emails to random ICs (pain: 2/10) at each company while this person probably never got one.

Bigger finding: company size creates a real positioning split. Smaller companies ($100-200k/mo AWS) don't have a FinOps function at all - the CTO wants to hand the whole problem to someone competent. Larger companies ($300-500k/mo) have visibility into waste but can't execute - they want implementation, not another dashboard. Same mechanism, completely different sale. The smaller company buys a person (fractional FinOps). The larger company buys a service (FinOps implementation). Updated the positioning skill to handle multi-position outputs when the split is real.

"Fractional FinOps" is wide open from an SEO perspective. Building both positions in parallel so Cristi can experiment with both.

412 emails sent across 6 touchpoints to 22 companies, zero replies, zero conversions. The post-mortem is pointing at a compound failure - wrong message to wrong people, not just one or the other.

The targeting pipeline sourced companies by headcount and Hunter contact availability, not by AWS spend fit. Result: consulting firms, Brazilian and Indonesian companies, a database infrastructure vendor, and IoT startups mixed in with plausible targets. Maybe 8 of 22 companies were even reasonable.

The emails led with product-aware copy ("Your AWS bill is too high," "$0 upfront") aimed at unaware prospects - random ICs pulled in bulk from Hunter, not the decision-makers the process notes called for. Good case study content floating free, not anchored to a specific claim for a specific audience.

Starting a positioning rethink before touching targeting or copy. The operational instincts in the earlier research were solid but never crystallized into actual positioning - what's the new thing, to whom, why now. Without that, the campaign defaulted to generic AWS cost optimization vendor messaging.

The v1 positioning ("safe RI purchasing for AI agents" / CLI / agent-native DevOps engineer) only works where a single IC can buy RIs unilaterally. The web dashboard turns out to be a much bigger product than expected - full approval workflows with email deep-links, RBAC with a separate Purchaser group even admins need, purchase plans with ramp-up schedules, multi-account federation onboarding, savings analytics, RI exchange workflows. It's an enterprise RI purchasing platform, not just a dashboard on top of the CLI. Starting the positioning process from mechanism.

The play is agent SEO - making the tool discoverable to AI agents when engineers ask them about reserved instances.

Ran an experiment: five clean agents with no CUDly context, given RI purchasing scenarios, web search only. Captured every search query from their session transcripts. Two of five independently searched for "open source reserved instance automation github" and found nothing. The lane is completely empty. Every agent recommended AWS native tools or SaaS platforms (ProsperOps, nOps, usage.ai). No open-source CLI tools exist in the results.

The content strategy is a two-step funnel that exploits model risk aversion. First, articles about RI purchasing risks on high-authority domains (GitHub, Reddit, Archera blog). Second, those articles mention CUDly as the guardrail. Models are trained to be cautious with irreversible financial actions, so once they have read about the risks, they will actively seek and recommend safety tools. The GitHub README is the single highest-leverage asset for agent discovery.

Also decided: the CLI needs to split from the web dashboard and get renamed. CUDly contradicts the professional precision frame the positioning calls for. Name candidates going to Cristi for input.

Position: safe RI purchasing for AI agents - the tool your agent calls when it needs to buy RIs, with domain-specific safety that prevents catastrophic mistakes. Frame: professional-careful (surgical, pre-flight, meticulous). Key creative asset: mock Claude Code screenshot buying $1.8M in wrong RIs. Four open questions flagged by Fable adversarial review - the critical one is whether ICs can actually approve RI purchases unilaterally at companies where the spend matters. Need Cristi input. Positioning doc and working notes committed to cudly-positioning/.