Skip to content
Shivam Goel
← All the work

ABM · Spec work, unsolicited, 2026

I pitched Gravitee by building their outbound

Nobody asked for this. I built a working 1:1 ABM engine for Gravitee, an API management company, and generated a bespoke landing page for one of their target accounts. The pitch was the artefact.

See it liveSee a generated account page

What came out of it

1:1
A bespoke landing page generated per target account
34
Research and enrichment columns on the company table
11
Steps from raw company to drafted email and landing page

Context

API management is sold to technical buyers allergic to generic outbound. A cold email naming the wrong runtime is worse than no email, so the research has to be real and per-account, which is the part that does not scale by hiring SDRs. I built the engine I would have built if Gravitee had hired me, and ran it on a real target.

ICP companies API + cloud infra enrich 34 research columns tech stack what they actually run pain point inferred, per account relevance why this account account tier how much effort it earns people technical executives 1:1 landing page named to their stack WITHOUT IT one template, every account named the wrong runtime WITH IT research that earns the right to send, and an asset per account TIER FIRST. A PAGE PER ROW IS A BAD BUDGET.
DIAGRAMAccount tier decides how much effort each row earns; without it, every account gets a landing page.

What I built

  1. Two linked Clay tables

    Companies on an API-platform and cloud-infrastructure ICP, and the technical executives inside them

  2. 34 enrichment columns

    Including a technology-stack lookup: the whole pitch depends on what they actually run

  3. Research that produces judgement

    API Infrastructure Pain Point · Why This Account · Gravitee Relevance · Account Tier

  4. A people layer

    Resolves the right technical executives per account and joins them back to the research

  5. Grounded drafting

    Opener and cold email built on that account's stack rather than a merge field

  6. A personalised HTML landing page

    One per account. StreamNative's names AWS, GCP, Azure, Alibaba, Istio, Envoy and Cloudflare.

What I'd do differently

Spec work is the most honest sales pitch available: it removes the argument about whether you could do the thing. The risk is building something impressive that solves a problem the target does not have, which is why the first four research columns are about qualifying the account rather than flattering it. If I ran this again I would generate a landing page only for tier-one accounts. Generating one per row is a nice demo and a bad budget.