ProgrammableMarketing/sixtyfour.ai (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 7
  • This quarter · 13
  • Big bets · 3
  • Wildcards · 1
  • How we can help
Generated Nov 9, 2026 1 view
  1. Programmable
  2. Playbooks
  3. Sixtyfour
Sixtyfour logo

growth playbook · Nov 9, 2026

sixtyfour.ai (opens in a new tab)

Sixtyfour growth playbook

Diagnosis

Sixtyfour went from $0 ARR in May to $4 million by October 2026 with a 12-person team. It has a public benchmark (RECON) that it leads by a wide margin and has repositioned from sales and recruiting research to trust, risk and investigations. Hiring for a Product Marketing Lead, a Founding Social Growth Lead, AEs and a growth intern shows the next step: distribution.

The funnel is behind the product. The site calls the API self-serve, but /pricing returns 404 and every button goes to a demo form. The Free plan, signup page and prices appear only inside blog posts. Atlas, the engine behind the benchmark win, has a placeholder page, and the YC job posts still describe the old sales-and-recruiting pitch.

This playbook first opens the self-serve door: pricing, signup buttons, a split demo page, benchmark-to-trial and the Atlas page. It then adds proof and comparison pages, free tools, partner integrations with the trust and safety stack, and product-qualified leads for the AEs. Big bets: make RECON a standing industry leaderboard and become the due-diligence layer inside KYB and KYC platforms.

Growth Score

7/10

Biggest Opportunity

Sixtyfour already has a free plan, a signup page, an MCP server and a benchmark it wins by about 30 points. Connecting them on the website turns every benchmark reader and developer into a trial user, while AEs keep the enterprise deals.

Biggest Risk

Pipl, Middesk and Social Links sell to the same fraud and investigations buyers with years of customer proof, and agent-search APIs such as Parallel make self-serve trials easy. With almost no published customer stories and no visible pricing, Sixtyfour's accuracy lead can get lost in a demo queue.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Publish the free plan you already have: a /pricing page and a "Start free" button where the site now says "self-serve"

    Copy the plan facts from the MCP post and the credit costs guide into a draft /pricing page.

    High impact First result in 2 weeks
  2. 2

    Split the demo page: a free API key for builders, a calendar for enterprise teams

    Tag the last 60 days of demo requests as builder or team and count each.

    High impact First result in 3 weeks
  3. 3

    Turn the benchmark's "Try Sixtyfour" into "run it on a subject you know", straight to signup

    Repoint the RECON "Try Sixtyfour" button to app.sixtyfour.ai/signup.

    High impact First result in 2 weeks

02

Your idea portfolio

24 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 7 ideas are marked Unexpected: plays you are unlikely to have tried.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 3Big bets · 10Fill-ins · 9Reconsider · 2
Effort →

Showing 24 of 24 ideas

This week 7

Quick wins with a clear first action.

  • 01

    Sixtyfour has a Free plan (64 credits), paid plans from 100 credits a month, $0.30 top-ups and a working signup page. But sixtyfour.ai/pricing returns 404, there is no pricing link in the nav or footer, and every homepage button goes to the demo form, although the homepage calls the Research API "a self-serve API". The only place a visitor can find the plans is in the middle of a blog post about the MCP server. Third-party directories fill the gap with contradicting numbers. A developer who wants to try the #1-ranked people research API has to book a call or guess.

    High impactLow effort First result in 2 weeks Product Marketing Lead

    First action

    Copy the plan facts from the MCP post and the credit costs guide into a draft /pricing page.

    How to measure it

    Website-sourced signups

    Now
    –
    Target
    3x the current weekly signups
    By
    60 days

    Steps

    1. 1

      Gather the facts

      Plans, credits, top-up price and Enterprise-only items from the MCP post and the credit costs guide; confirm current plan prices in billing.

      Product Marketing Lead 1 day

    2. 2

      Write the page

      Plan columns, a per-task cost table, Enterprise column, FAQ on credits and refunds of unused Atlas credits.

      Product Marketing Lead 2 days

    3. 3

      Build and link it

      /pricing in the nav and footer; "Start free" next to every "Book a demo" on the homepage, Research API page and header.

      Member of Technical Staff 2 days

    4. 4

      Fix the docs link

      Point "See the docs for current access and pricing" to /pricing and link it from the credit costs guide.

      Member of Technical Staff 1 hour

    5. 5

      Track the path

      Tag signups by source page in the analytics tool.

      Growth Intern 1 day

    6. 6

      Ask directories to update

      Send the new page to directories that list conflicting plan numbers.

      Growth Intern 1 day

    7. 7

      Review weekly

      Signups, free-to-paid and demo volume, so sales can see the page is not taking enterprise deals.

      Product Marketing Lead weekly

    First result
    2 weeks
    Cost
    Staff time only
    Owner
    Product Marketing Lead

    Smallest test

    Add a "Start free" button to the homepage header today and count signups for two weeks.

    Why it works

    Build /pricing from what already exists: the Free plan (64 one-time credits), the Individual and higher plans, $0.30 top-ups, and an Enterprise column for Atlas, the high and xhigh tiers, custom rates and the SOC 2 report. Translate the credit table into plain costs per task, such as "research one person, low tier: 1 credit" and "find a work email: 0.5 credits". Add "Start free" next to "Book a demo" in the header, the homepage hero, the Research API page and the API section, all pointing at app.sixtyfour.ai/signup. Keep enterprise-only items clearly labelled "talk to us" so AEs still own the big deals.

    Developers and agent builders decide in minutes and leave when the price is hidden. Demo-only rivals (Pipl, Middesk, Social Links) cannot win that buyer, while Parallel can, because it shows prices and a free allowance. A visible free plan also lets enterprise evaluators test quietly before they talk to sales, so AE calls start warmer.

    Ready to use

    Copy/pricing page outline

    Hero: Research people and companies, every finding cited. Start free with 64 credits.
    Columns: Free (64 one-time credits) | Individual (100 credits a month) | higher plans | Enterprise (Atlas, high and xhigh tiers, custom rates, SOC 2 Type 2 report, DPA)
    What a credit buys: research a person, low tier 1 | medium 20 | company, low 1 | find work email 0.5 | find phone 3 | search 0.1 per result
    Top-ups: $0.30 a credit
    FAQ: Do failed jobs cost credits? Do unused Atlas credits return? Can I use it from my AI assistant (MCP)?
    Buttons: Start free | Book a demo

    Risks and how to handle them

    • Enterprise buyers anchor on the small plans

      Show an Enterprise column with Atlas, xhigh, SOC 2 and custom rates, priced as "talk to us".

    • Free credits attract low-value users

      Keep 64 one-time credits and require work email or Google sign-in, as signup already does.

    Evidence

    • Your website/pricing returns 404 on www and apex (checked twice, November 9, 2026) and no pricing link appears in the nav or footer. The homepage calls the Research API "a self-serve API", but its buttons (Learn More, See it on your own case, Book a demo) all go to /demo and the only account link is Login. The Research API page says "See the docs for current access and pricing."Source
    • Your websitePlan details appear only inside a blog post on the MCP server (November 5, 2026): "The Free plan includes 64 credits, given once to the organisation created at sign-up. Paid plans start at 100 credits a month on the Individual plan. Top-up credits cost $0.30 each, with a $50 minimum on an active paid plan." The post ends with a Sign up link to app.sixtyfour.ai/signup.Source
    • Your docsCredit costs guide: People Intelligence micro 0.3, low (default) 1 and medium 20 credits per record for all organizations; high 40 and xhigh 250 per unit (Atlas) on request. Company Intelligence low 1, medium 5. Find Email 0.5, Find Phone 3, search 0.1 per result, verify-age 40. No dollar price per credit; "Enterprise contracts can set custom rates." Atlas, high and xhigh are enabled for Enterprise customers on request.Source
    • Your websiteA working signup page exists ("Create your Sixtyfour account", email or Google). Blog posts link to it (the MCP post and the search benchmark post), but the homepage, the Research API page and /demo do not; the RECON page's "Try Sixtyfour" button goes to the app root rather than signup.Source
    • Third-party listingAn AI agent directory lists Sixtyfour plans as Free (64 credits), Individual $24, Starter $264, Growth $864 and Enterprise, but contradicts itself on the credits in each plan.Source
    • Competitor researchParallel ("Where agents find answers") offers pay-as-you-go pricing from $1 per 1,000 searches, signup credit, a recurring $5 monthly free allowance and a "Start building for free" link to its playground.Source
  • 02

    The demo page asks for six fields and sends everyone to a scheduling calendar, with no self-serve alternative. A developer who only wants an API key takes the same slot as a fraud team at a payments company. The AEs being hired are meant to close existing pipeline, so a demo queue mixed with builders who just want a key wastes their time.

    High impactLow effort First result in 3 weeks Account Executive

    First action

    Tag the last 60 days of demo requests as builder or team and count each.

    How to measure it

    Share of demos that become opportunities

    Now
    –
    Target
    +30%
    By
    60 days

    Steps

    1. 1

      Sort past requests

      Builder vs team from the use and website fields.

      Account Executive 1 day

    2. 2

      Write the choice

      Two short paths at the top of /demo.

      Product Marketing Lead 2 hours

    3. 3

      Build the routing

      Builder path to signup; team path to the calendar.

      Member of Technical Staff 1 day

    4. 4

      Send a builder email

      Quick-start, MCP setup and credit costs after signup.

      Growth Intern 1 day

    5. 5

      Add a reply promise

      One business day for team requests.

      Account Executive 1 hour

    6. 6

      Measure

      Demo-to-opportunity and builder activation, monthly.

      Growth Intern monthly

    First result
    3 weeks
    Cost
    Staff time only
    Owner
    Account Executive

    Smallest test

    Add one line under the form: "Just need an API key? Start free."

    Why it works

    Add a short choice above the form: "I want to build with the API" (straight to signup with free credits and the quick-start) or "My team needs investigations" (the current form). Use the existing "How do you want to use Sixtyfour?" answer to route: enterprise use cases to an AE calendar, single developers to signup plus a docs email. Add a response promise ("we reply within one business day").

    Both groups move faster: builders get a key in a minute, and AEs spend calls on teams with budget, which matters with a $4 million ARR pipeline to nurture.

    Risks and how to handle them

    • Big teams pick the builder path

      Flag company domains from target segments to AEs after signup (idea 17).

    Builds on

    Evidence

    • Your websiteDemo page: six fields (name, work email, company, how did you hear, how you want to use Sixtyfour, website), then a scheduling calendar; no self-serve alternative and no response-time promise.Source
    • HiringAccount Executive (San Francisco, $120K-$350K): "We are growing very fast, going from $0 ARR in May, to $4mm as of October 2026." AEs will "take on some of our pipeline, continue to nurture it and ultimately close it"; the final interview is a live sales call with a real customer.Source
    • Your websiteA working signup page exists ("Create your Sixtyfour account", email or Google). Blog posts link to it (the MCP post and the search benchmark post), but the homepage, the Research API page and /demo do not; the RECON page's "Try Sixtyfour" button goes to the app root rather than signup.Source
  • 03

    RECON shows Sixtyfour XHigh at 70.6% weighted accuracy against 41.1% for the best outside system, but the page says "Cost and latency are out of scope." Buyers comparing an API ask what each right answer costs. Sixtyfour already publishes credit costs for every tier, so it can answer that question itself before a rival does.

    Medium impactLow effort First result in 2 weeks Product Marketing Lead

    First action

    Pull credits used per subject from the RECON runs.

    How to measure it

    RECON page conversion

    Now
    –
    Target
    +25%
    By
    60 days

    Steps

    1. 1

      Pull run costs

      Credits and time per subject for each Sixtyfour tier.

      Member of Technical Staff 1 day

    2. 2

      Price outside systems

      Only from each vendor's public price page, dated.

      Growth Intern 2 days

    3. 3

      Build the chart

      Accuracy against cost per correct fact.

      Product Marketing Lead 2 days

    4. 4

      Publish

      On /recon-benchmark and in the RECON blog post.

      Product Marketing Lead 1 day

    5. 5

      Launch

      A short thread with the chart on X and LinkedIn.

      Founding Social Growth Lead 1 day

    6. 6

      Link to pricing

      Each tier links to the plan that unlocks it.

      Member of Technical Staff 1 hour

    First result
    2 weeks
    Cost
    Staff time only
    Owner
    Product Marketing Lead

    Smallest test

    Publish cost per correct fact for the Sixtyfour tiers only.

    Why it works

    Add a column to RECON: credits (and dollars at the top-up rate) per correct fact for each Sixtyfour tier, plus the published list price for outside systems where one exists. Add median time per subject. Show that Low and Medium are cheap for screening at volume and XHigh is for the cases that matter, which maps straight onto the plans.

    Accuracy alone invites "but it must be expensive". A cost-per-correct-fact chart turns the benchmark into a buying guide and steers each buyer to the right tier.

    Risks and how to handle them

    • Outside prices change or are not comparable

      Date every price, link the source and show only where a public price exists.

    Builds on

    Evidence

    • Your websiteRECON benchmark (evaluations run by HUD, September 8 to October 6, 2026): 140 people, 514 verified fields; Sixtyfour XHigh 70.6% weighted accuracy, 84.4% recall at 85.9% precision, against 41.1% for the best outside system (Parallel Ultra 2x). The harness is public on GitHub; the dataset is by request. "Cost and latency are out of scope." Buttons: Book a demo and Try Sixtyfour.Source
    • Your docsCredit costs guide: People Intelligence micro 0.3, low (default) 1 and medium 20 credits per record for all organizations; high 40 and xhigh 250 per unit (Atlas) on request. Company Intelligence low 1, medium 5. Find Email 0.5, Find Phone 3, search 0.1 per result, verify-age 40. No dollar price per credit; "Enterprise contracts can set custom rates." Atlas, high and xhigh are enabled for Enterprise customers on request.Source
    • HiringProduct Marketing Lead: will "decide what we say publicly and where"; leads launch weeks with demos, benchmarks against competitors and case studies; growth stunts such as "live investigation runs, bounties, free tool drops"; builds blogs, teardowns and comparison pages; owns traffic, signups and pipeline and instruments attribution. Nice to have: marketing to compliance, security, trust and safety or investigations buyers, and developer or API marketing.Source
  • 04

    RECON and the search benchmark are Sixtyfour's most persuasive pages, and the homepage banner sends visitors there. But RECON's "Try Sixtyfour" button lands on the app root, not the signup page. The benchmark's own advice is to test a research tool on subjects whose facts you can verify, which is exactly the trial a reader wants to run.

    High impactLow effort First result in 2 weeks Product Marketing Lead

    First action

    Repoint the RECON "Try Sixtyfour" button to app.sixtyfour.ai/signup.

    How to measure it

    Benchmark-sourced signups

    Now
    –
    Target
    150 a month
    By
    60 days

    Steps

    1. 1

      Repoint the buttons

      RECON, the RECON blog post and the search benchmark post.

      Member of Technical Staff 1 hour

    2. 2

      Rewrite the copy

      "Run it on a subject you can verify" with the free credit count.

      Product Marketing Lead 1 hour

    3. 3

      Prefill a first task

      Company research at low tier from the signup source.

      Member of Technical Staff 3 days

    4. 4

      Show the benchmark in-app

      A short note on tiers and accuracy beside the first result.

      Product Marketing Lead 1 day

    5. 5

      Track

      Signups and first runs by benchmark page.

      Growth Intern weekly

    6. 6

      Hand off

      Company domains in target segments go to an AE.

      Account Executive ongoing

    First result
    2 weeks
    Cost
    Staff time and free credits
    Owner
    Product Marketing Lead

    Smallest test

    Change one button today and compare clicks for two weeks.

    Why it works

    Change the RECON and search-benchmark buttons to "Run it on a company or person you can verify: 64 free credits", linking to signup with a prefilled first task (a company research run at low tier, or the reader's own employer). After signup, show the result next to the benchmark's accuracy figures.

    Benchmark readers are evaluators with a question already in mind. Letting them check accuracy on a subject they know turns a claim into their own proof.

    Risks and how to handle them

    • Readers research private individuals

      Default the first task to a company and keep the existing terms and abuse controls.

    Evidence

    • Your websiteRECON benchmark (evaluations run by HUD, September 8 to October 6, 2026): 140 people, 514 verified fields; Sixtyfour XHigh 70.6% weighted accuracy, 84.4% recall at 85.9% precision, against 41.1% for the best outside system (Parallel Ultra 2x). The harness is public on GitHub; the dataset is by request. "Cost and latency are out of scope." Buttons: Book a demo and Try Sixtyfour.Source
    • Your websiteA working signup page exists ("Create your Sixtyfour account", email or Google). Blog posts link to it (the MCP post and the search benchmark post), but the homepage, the Research API page and /demo do not; the RECON page's "Try Sixtyfour" button goes to the app root rather than signup.Source
    • Your websiteSearch benchmark post (October 13, 2026): on Exa's open-source benchmarks, Sixtyfour's people search top result is relevant for 90.4% of queries vs Exa's 72.0%, and company search 86.4% vs 61.8%. The post links to app.sixtyfour.ai/signup.Source
  • 05

    Atlas is in the main Product menu, and the xhigh tier that topped RECON at 70.6% is billed as Atlas. Yet the Atlas page says "More on Atlas soon. We're building out the rest of this page" and offers only "Request access". The most valuable product, with the strongest proof, has the thinnest page.

    Medium impactLow effort First result in 2 weeks Product Marketing Lead

    First action

    Remove the placeholder line and add the RECON result with a link.

    How to measure it

    Atlas requests per month

    Now
    –
    Target
    2x
    By
    60 days

    Steps

    1. 1

      Remove the placeholder

      Replace it with the RECON headline result.

      Product Marketing Lead 1 hour

    2. 2

      Show one investigation

      Illustrative subject, findings, sources and confidence.

      Head of Trust & Safety 3 days

    3. 3

      Explain budgets

      Scout and X-High credit ranges and unused-credit refunds.

      Product Marketing Lead 1 day

    4. 4

      Show the outputs

      Report, PDF export, workspace export and API.

      Member of Technical Staff 1 day

    5. 5

      Link it

      From RECON, solution pages and pricing.

      Member of Technical Staff 2 hours

    6. 6

      Do Lattice next

      Same treatment for the Lattice beta page.

      Product Marketing Lead 1 week

    First result
    2 weeks
    Cost
    Staff time only
    Owner
    Product Marketing Lead

    Smallest test

    Replace the placeholder sentence with the RECON result today.

    Why it works

    Rebuild /atlas around the benchmark: the RECON result, one worked investigation with the cited trail (an illustrative subject, as on the solution pages), what the Atlas report and PDF export include, the credit budget per investigation (Scout 50-500, X-High 250-2,500) and who gets access. Link it from RECON and each solution page.

    Enterprise buyers searching for the product the AE mentioned should find proof, not a placeholder; it also gives the AEs a page to send after calls.

    Risks and how to handle them

    • Sample investigation exposes a real person

      Use an invented or consenting subject, as the solution pages already do.

    Evidence

    • Your websiteAtlas, in the main nav as a product, says "More on Atlas soon. We're building out the rest of this page" with Request access and Book a demo buttons; the Lattice (Beta) page is also still being built, with access by request.Source
    • Your docsCredit costs guide: People Intelligence micro 0.3, low (default) 1 and medium 20 credits per record for all organizations; high 40 and xhigh 250 per unit (Atlas) on request. Company Intelligence low 1, medium 5. Find Email 0.5, Find Phone 3, search 0.1 per result, verify-age 40. No dollar price per credit; "Enterprise contracts can set custom rates." Atlas, high and xhigh are enabled for Enterprise customers on request.Source
    • Your websiteRECON benchmark (evaluations run by HUD, September 8 to October 6, 2026): 140 people, 514 verified fields; Sixtyfour XHigh 70.6% weighted accuracy, 84.4% recall at 85.9% precision, against 41.1% for the best outside system (Parallel Ultra 2x). The harness is public on GitHub; the dataset is by request. "Cost and latency are out of scope." Buttons: Book a demo and Try Sixtyfour.Source
  • 06

    Every Sixtyfour job post on YC ends with a company description saying the platform "turns that intelligence into automated research workflows for sales, recruiting, and marketing". The homepage now says "Trust, risk, research and investigation teams run on Sixtyfour", and the old headline "Build your own AI Recruiters" is gone. Candidates for the marketing roles, and investors who see the posts, read the pitch Sixtyfour has moved away from.

    Medium impactLow effort First result in 1 week Chief of Staff

    First action

    Edit the YC company description.

    How to measure it

    Qualified applicants for marketing roles

    Now
    –
    Target
    +25%
    By
    60 days

    Steps

    1. 1

      Write one paragraph

      The trust, risk and investigations pitch with one proof point.

      Product Marketing Lead 1 hour

    2. 2

      Update YC

      Company description and all job posts.

      Chief of Staff 1 hour

    3. 3

      Update socials

      LinkedIn, X and GitHub bios.

      Founding Social Growth Lead 1 hour

    4. 4

      Find old copies

      Search directories for "sales, recruiting, and marketing".

      Growth Intern 1 day

    5. 5

      Request fixes

      Ask each directory to update.

      Growth Intern 1 week

    6. 6

      Recheck

      Quarterly, after each positioning change.

      Chief of Staff quarterly

    First result
    1 week
    Cost
    $0
    Owner
    Chief of Staff

    Smallest test

    Update the YC company description today.

    Why it works

    Rewrite the YC company description and the shared blurb on all five job posts to match the homepage: research infrastructure for trust, risk and investigations, with the RECON result and the ARR growth already shared in the AE post. Check the LinkedIn, X and GitHub bios, and directory listings, for the same old wording.

    The marketing hires will be judged on telling one clear story; it should start in the post they apply to. Consistent descriptions also shape how search and AI assistants summarize the company.

    Risks and how to handle them

    • Existing sales and recruiting customers feel dropped

      Keep a line that the API still powers data products and recruiting workflows.

    Evidence

    • HiringThe company description on Sixtyfour's YC job posts still says the platform "turns that intelligence into automated research workflows for sales, recruiting, and marketing", while the homepage now says "Trust, risk, research and investigation teams run on Sixtyfour." The homepage headline changed from "Build your own AI Recruiters" (late 2025) to "Powering The World's Most Consequential Decisions".Source
    • HiringFounding Social Growth Lead: make Sixtyfour and the CEO essential follows on X and LinkedIn; "Turn customer use cases into stories, starting with trust and safety teams"; success means posts lead to demos, intros, candidates and investors; prefers "five posts people quote than fifty they scroll past".Source
  • 07

    Real visitors load the homepage fast (field LCP 1.6 s and CLS 0 both pass), but responsiveness fails: INP is 270 ms at the 75th percentile against a 200 ms target. The page has 2,376 DOM elements, mostly animated product mockups, plus about 0.75 s of render-blocking requests and a 186 KB analytics script.

    Medium impactLow effort First result in 1 month Member of Technical Staff

    First action

    Record a performance trace of a tap on the homepage on a mid-range phone.

    How to measure it

    Homepage INP (real visitors)

    Now
    –
    Target
    Under 200 ms
    By
    45 days

    Steps

    1. 1

      Trace

      Find the long tasks behind slow taps.

      Member of Technical Staff 1 day

    2. 2

      Calm the animations

      Pause off-screen mockups; lighter static frames first.

      Member of Technical Staff 2 days

    3. 3

      Trim the DOM

      Render below-the-fold sections lazily.

      Member of Technical Staff 2 days

    4. 4

      Defer analytics

      Load the analytics script after first interaction or idle.

      Member of Technical Staff 2 hours

    5. 5

      Unblock rendering

      Inline critical CSS and preload fonts.

      Member of Technical Staff 1 day

    6. 6

      Verify

      PageSpeed now, field data after 28 days.

      Growth Intern monthly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Member of Technical Staff

    Smallest test

    Pause off-screen animations and re-run PageSpeed.

    Why it works

    Profile the hero and workflow animations, pause or simplify those off-screen, cut the DOM by rendering mockups as lighter static frames until they scroll into view, defer the analytics script and inline the critical fonts. Re-test in PageSpeed and watch the field INP over 28 days.

    Evaluators click around the demo mockups; slow taps make a precision product feel sluggish. It is also a clean ranking signal.

    Risks and how to handle them

    • Less animated hero converts worse

      Keep the hero animation; slow down only what is off-screen.

    Evidence

    • PageSpeedHomepage, November 9, 2026: real visitors fail Core Web Vitals on responsiveness (INP 270 ms at p75, target 200 ms) while real LCP (1.6 s) and CLS (0) pass. Lab mobile score 78; render-blocking requests cost about 0.75 s; 2,376 DOM elements; the analytics script is the largest third party at 186 KB.Source

This quarter 13

The core plays for the next three months.

  • 08

    The homepage shows ten customer logos, including TRM Labs, Airwallex, Mercor and Turing, and a "Proven impact, in their words" carousel numbered 1-7, but only the Casco quote is readable on the page and nothing links to a case study. Financial Crime, Fraud & Abuse and Threat Investigations name no customers and give no results figures. The sitemap has no case study pages at all.

    High impactMedium effort First result in 6 weeks Product Marketing Lead

    First action

    Ask the three happiest logo customers for a 20-minute interview.

    How to measure it

    Solution page conversion

    Now
    –
    Target
    +30%
    By
    1 quarter

    Steps

    1. 1

      Choose customers

      One per solution, with results you can measure.

      Account Executive 2 days

    2. 2

      Interview

      Question, identifier, finding, result.

      Product Marketing Lead 2 weeks

    3. 3

      Get approval

      Customer sign-off on every number and quote.

      Account Executive 2 weeks

    4. 4

      Publish

      /customers pages plus a result line on each solution page.

      Product Marketing Lead 1 week

    5. 5

      Fix the carousel

      All quotes as readable text with roles.

      Member of Technical Staff 1 day

    6. 6

      Distribute

      Posts, AE follow-ups and the newsletter.

      Founding Social Growth Lead ongoing

    First result
    6 weeks
    Cost
    Staff time only
    Owner
    Product Marketing Lead

    Smallest test

    Publish the Casco story in full on the Workforce Risk page.

    Why it works

    Pick one logo customer per solution (for example a blockchain-intelligence firm for Threat Investigations, a payments company for Financial Crime, a talent platform for Workforce Risk) and write a short case study: the question, the identifier, what Sixtyfour found, time saved or fraud caught, with a quote. Put a one-line result on each solution page and link to the full story. Make the carousel's seven quotes readable text.

    Compliance and trust and safety buyers buy from peers. A single measured result per segment does more than a wall of logos, and it gives AEs and the social lead stories to use.

    Risks and how to handle them

    • Customers in fraud and security will not be named

      Offer anonymized stories ("a top-10 crypto exchange") with real numbers.

    Evidence

    • Your websiteHomepage: banner claiming #1 on people research with a link to the benchmark; ten customer logos (Mercor, Gryphon Investors, Cloaked, TRM Labs, ZoomInfo, Airwallex, GOTV, Delphi, Moritz, Turing); a "Proven impact, in their words" carousel numbered 1-7 with one quote readable on the page, from Casco's CEO ("We see fake North Korean workers apply to Casco"); none links to a case study page.Source
    • Your websiteSolution pages: Financial Crime ("Follow the business. Find the people behind it."), Fraud & Abuse and Threat Investigations name no customers and give no results figures; examples are illustrative. Workforce Risk names one customer (Casco). Every page's main buttons go to /demo.Source
    • Your websiteSitemap (49 URLs, checked November 9, 2026): 36 blog posts, 5 solution pages, /atlas, /lattice, /recon-benchmark, /demo, /brand, /security and the terms page. No pricing page, no case study pages, no comparison pages, no integrations page.Source
  • 09

    The Product Marketing Lead role explicitly includes comparison pages, and the site has none. Sixtyfour's closest rivals for fraud, KYB and investigations buyers (Pipl, Middesk, Social Links) all hide pricing behind a demo. Sixtyfour can show cited findings, a public benchmark and, once idea 1 ships, a free plan. Its only comparison content so far is an "Exa alternatives" post aimed at developers.

    High impactMedium effort First result in 1 month Product Marketing Lead

    First action

    Ask AEs which rival comes up most in live deals.

    How to measure it

    Comparison-page conversions

    Now
    –
    Target
    40 a month
    By
    90 days

    Steps

    1. 1

      Pick rivals

      The three most common in deals.

      Account Executive 1 day

    2. 2

      Check facts

      Each rival's own site and docs, dated.

      Growth Intern 3 days

    3. 3

      Write pages

      Fair tables, best-fit sections and "use both" guidance.

      Product Marketing Lead 1 week

    4. 4

      Review claims

      Legal review of claims and trademarks.

      Chief of Staff 3 days

    5. 5

      Publish

      /compare pages linked from pricing and solutions.

      Member of Technical Staff 1 day

    6. 6

      Refresh

      Quarterly, or when a rival changes its offer.

      Product Marketing Lead quarterly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Product Marketing Lead

    Smallest test

    Publish one comparison and track its conversions for a month.

    Why it works

    Write three fair comparison pages: what each tool is best at, where Sixtyfour differs (cited research from one identifier, the API and MCP, published accuracy, self-serve trial), and when to use both, since the company's own stack post places Sixtyfour beside verification and decisioning tools. Date every claim and link sources.

    Buyers search "Pipl alternative" and "Middesk vs" late in their decision. Fair pages win that traffic and teach AI assistants how to describe Sixtyfour.

    Risks and how to handle them

    • Out-of-date claims about rivals

      Date every claim, cite the rival's own page and refresh quarterly.

    Builds on

    Evidence

    • HiringProduct Marketing Lead: will "decide what we say publicly and where"; leads launch weeks with demos, benchmarks against competitors and case studies; growth stunts such as "live investigation runs, bounties, free tool drops"; builds blogs, teardowns and comparison pages; owns traffic, signups and pipeline and instruments attribution. Nice to have: marketing to compliance, security, trust and safety or investigations buyers, and developer or API marketing.Source
    • Competitor researchRivals' own homepages: Pipl ("Make better risk decisions", for enterprise fraud and risk teams), Middesk ("Decide who to do business with", business verification plus AI agent investigations) and Social Links (OSINT from "850+ open sources") show no pricing and offer only a demo.Source
    • Your websiteSitemap (49 URLs, checked November 9, 2026): 36 blog posts, 5 solution pages, /atlas, /lattice, /recon-benchmark, /demo, /brand, /security and the terms page. No pricing page, no case study pages, no comparison pages, no integrations page.Source
    • Your websiteSixtyfour's trust and safety tech stack post (November 4, 2026) puts Sixtyfour in the account-investigation layer, next to identity verification (Persona, Veriff, Jumio), device intelligence (Fingerprint, Incognia), fraud decisioning (Sift, SEON, Sardine) and case management (Cinder, Tremau); it ends with Request a Demo.Source
  • 10

    The PMM role names "free tool drops" as a growth stunt, and the blog already ranks for the questions: who owns an LLC, verify a vendor, verify a business address, investigate a phone number, tell if a LinkedIn profile is fake. Company research at micro or low tier costs 0.3 to 1 credit, so a free company-only tool is cheap to run.

    High impactMedium effort First result in 6 weeks Product Marketing Lead

    First action

    Pick the two how-to posts with the most search traffic and scope a company-only tool for each.

    How to measure it

    Tool-to-signup rate

    Now
    –
    Target
    8%
    By
    90 days

    Steps

    1. 1

      Pick topics

      Highest-traffic company questions from the blog.

      Growth Intern 2 days

    2. 2

      Define output

      Fields, sources and the red-flag list.

      Head of Trust & Safety 3 days

    3. 3

      Build

      On the Company Intelligence API, micro or low tier, with rate limits.

      Member of Technical Staff 2 weeks

    4. 4

      Add abuse controls

      Company subjects only, daily caps, logging.

      Member of Technical Staff 3 days

    5. 5

      Launch

      As a launch week with clips and posts.

      Founding Social Growth Lead 1 week

    6. 6

      Link and measure

      From how-to posts; runs, signups, cost.

      Growth Intern weekly

    First result
    6 weeks
    Cost
    Engineering time plus credits for free runs
    Owner
    Product Marketing Lead

    Smallest test

    Ship one tool as a simple form for a two-week launch.

    Why it works

    Launch two or three company-focused free tools on their own pages: enter a business name or domain, get a short cited summary (registration, officers named in filings, web presence, red flags), limited to a few runs a day without signup and more with a free account. Link each tool from the matching how-to post.

    Free tools earn links and searches that articles cannot, and every run demonstrates the cited-findings format. Company-only scope keeps privacy risk low.

    Risks and how to handle them

    • Tool is used to research private people

      Accept only company names and domains; route people research to signed-in users under the terms.

    Builds on

    Evidence

    • Your websiteBlog: 35 posts, 29 in Trust & Safety, mostly how-to guides (how to find out who owns an LLC, verify a vendor, investigate a phone number, tell if a LinkedIn profile is fake); no newsletter or subscribe box; posts end with a demo request.Source
    • HiringProduct Marketing Lead: will "decide what we say publicly and where"; leads launch weeks with demos, benchmarks against competitors and case studies; growth stunts such as "live investigation runs, bounties, free tool drops"; builds blogs, teardowns and comparison pages; owns traffic, signups and pipeline and instruments attribution. Nice to have: marketing to compliance, security, trust and safety or investigations buyers, and developer or API marketing.Source
    • Your docsCredit costs guide: People Intelligence micro 0.3, low (default) 1 and medium 20 credits per record for all organizations; high 40 and xhigh 250 per unit (Atlas) on request. Company Intelligence low 1, medium 5. Find Email 0.5, Find Phone 3, search 0.1 per result, verify-age 40. No dollar price per credit; "Enterprise contracts can set custom rates." Atlas, high and xhigh are enabled for Enterprise customers on request.Source
  • 11

    Sixtyfour's homepage closes with "See what our agents find", but the only way to see it is a demo. The safest, most shareable subject for people research is the person asking. The social lead is hired to create posts people quote and send to group chats, and a self-lookup with cited sources is that kind of post.

    Medium impactMedium effort First result in 6 weeks Founding Social Growth Lead

    First action

    Define the ownership check and what the share card shows.

    How to measure it

    Self-lookup signups

    Now
    –
    Target
    1,000 in the first month
    By
    1 quarter

    Steps

    1. 1

      Design consent

      Verify control of the identifier before running.

      Head of Trust & Safety 1 week

    2. 2

      Build the flow

      Low-tier people research on the verified user.

      Member of Technical Staff 2 weeks

    3. 3

      Design the card

      Counts only, no personal details.

      Founding Social Growth Lead 3 days

    4. 4

      Write the checklist

      How to shrink your own footprint.

      Product Marketing Lead 3 days

    5. 5

      Seed it

      Founders and team post their own results first.

      Founding Social Growth Lead 1 week

    6. 6

      Measure

      Runs, shares, signups and later paid conversions.

      Growth Intern weekly

    First result
    6 weeks
    Cost
    Engineering time plus about 1 credit per run
    Owner
    Founding Social Growth Lead

    Smallest test

    Run it for the team and twenty friendly founders; count who shares.

    Why it works

    Let a signed-in user run a low-tier people research on themselves, after verifying they control the email or professional profile used as the identifier. Show the cited footprint, with a one-click share card that shows only counts ("14 sources, 3 old usernames") and no personal details. Pair it with a privacy checklist post.

    It shows the product's power without anyone researching a stranger, turns founders and operators into demos of their own, and builds the trust narrative that accuracy matters.

    Risks and how to handle them

    • Misuse to look up others

      Run only after proof of control; no free-text subjects.

    • Results unsettle users

      Lead with the privacy checklist and keep share cards free of personal data.

    Builds on

    Evidence

    • HiringFounding Social Growth Lead: make Sixtyfour and the CEO essential follows on X and LinkedIn; "Turn customer use cases into stories, starting with trust and safety teams"; success means posts lead to demos, intros, candidates and investors; prefers "five posts people quote than fifty they scroll past".Source
    • Your website/pricing returns 404 on www and apex (checked twice, November 9, 2026) and no pricing link appears in the nav or footer. The homepage calls the Research API "a self-serve API", but its buttons (Learn More, See it on your own case, Book a demo) all go to /demo and the only account link is Login. The Research API page says "See the docs for current access and pricing."Source
  • 12

    Twenty-nine of the 35 blog posts are trust and safety how-tos, and readers arrive with a live problem: a suspicious vendor, a phone number, a business address. Each post ends with a demo request, the slowest possible next step for someone mid-investigation.

    Medium impactLow effort First result in 1 month Growth Intern

    First action

    Map each of the 29 posts to one product task.

    How to measure it

    Blog-sourced signups

    Now
    –
    Target
    2% of blog sessions
    By
    90 days

    Steps

    1. 1

      Map posts

      One task per post.

      Growth Intern 1 day

    2. 2

      Design the box

      Task name, one input, free credits note.

      Product Marketing Lead 2 days

    3. 3

      Build

      A reusable block that links to signup with the task.

      Member of Technical Staff 1 week

    4. 4

      Roll out

      Top ten posts by traffic first.

      Growth Intern 2 days

    5. 5

      A/B test

      Box vs demo-only ending.

      Growth Intern 4 weeks

    6. 6

      Extend

      All how-to posts if it wins.

      Growth Intern 1 week

    First result
    1 month
    Cost
    Staff time and free credits
    Owner
    Growth Intern

    Smallest test

    Add the box to the three highest-traffic posts.

    Why it works

    Add a small box to each how-to post that matches its topic: "Check a business address", "Investigate an email", "Research a vendor". It opens signup with the right task prefilled. Keep the demo link for teams. Test the box against the demo-only ending.

    Matching the next step to the reader's task converts better than a generic call, and these posts already attract the target buyer.

    Risks and how to handle them

    • Fewer demo requests from the blog

      Keep the demo link and route team-domain signups to AEs (idea 17).

    Builds on

    Evidence

    • Your websiteBlog: 35 posts, 29 in Trust & Safety, mostly how-to guides (how to find out who owns an LLC, verify a vendor, investigate a phone number, tell if a LinkedIn profile is fake); no newsletter or subscribe box; posts end with a demo request.Source
    • HiringGrowth Intern (Fall 2026): posts on LinkedIn and X, supports launch weeks with demo clips, case studies and "benchmarks against tools buyers already use", runs keep-or-kill channel experiments, researches competitor claims and owns reporting on traffic, signups and sources.Source
  • 13

    The blog publishes several trust and safety guides a week, from ban evasion to money mules, and calls its content "field briefs", but it has no newsletter or subscribe box. Readers who are not ready to buy have no way to come back.

    Medium impactLow effort First result in 2 months Head of Trust & Safety

    First action

    Add a subscribe box to the blog template.

    How to measure it

    Newsletter subscribers

    Now
    –
    Target
    1,500
    By
    2 quarters

    Steps

    1. 1

      Add the box

      Blog template and the end of each post.

      Member of Technical Staff 1 day

    2. 2

      Set the format

      Pattern, case, update, checklist.

      Head of Trust & Safety 2 days

    3. 3

      Write issue one

      Ban evasion or fake candidates.

      Head of Trust & Safety 1 week

    4. 4

      Promote

      Posts on X and LinkedIn with a sample.

      Founding Social Growth Lead ongoing

    5. 5

      Flag engaged readers

      Repeat openers at target companies go to AEs.

      Account Executive monthly

    6. 6

      Review

      Opens, replies and pipeline from subscribers.

      Growth Intern monthly

    First result
    2 months
    Cost
    Email tool and staff time
    Owner
    Head of Trust & Safety

    Smallest test

    Add the box and send one issue to the first subscribers.

    Why it works

    Add a subscribe box to every post and send a monthly brief: one new fraud pattern with a worked (anonymized or illustrative) investigation, one RECON or product update and one checklist. Write it from the Head of Trust & Safety's experience to keep a practitioner voice.

    Trust and safety is a small, tight community; a respected monthly brief keeps Sixtyfour in mind until the budget appears, and gives AEs warm leads who open every issue.

    Risks and how to handle them

    • Becomes a sales email

      Keep one short product item per issue.

    Evidence

    • Your websiteBlog: 35 posts, 29 in Trust & Safety, mostly how-to guides (how to find out who owns an LLC, verify a vendor, investigate a phone number, tell if a LinkedIn profile is fake); no newsletter or subscribe box; posts end with a demo request.Source
    • PressTech Funding News (July 10, 2026): customers concentrate in blockchain-intelligence firms, payments companies and trust and safety teams; about twelve people, eight engineers, including an early trust and safety leader with two decades in the field; the CEO: "Breadth is a vanity metric."Source
  • 14

    The docs list an Ashby integration, but the Workforce Risk page, written for staffing platforms, security teams and contractor operations, names no applicant tracking system. Recruiting teams decide on candidate-fraud tools by asking "does it work in our ATS?", and the page cannot answer.

    High impactMedium effort First result in 1 month Product Marketing Lead

    First action

    Add one paragraph and a screenshot of the Ashby integration to the Workforce Risk page.

    How to measure it

    Workforce Risk pipeline

    Now
    –
    Target
    +40%
    By
    1 quarter

    Steps

    1. 1

      Show Ashby

      Section, screenshot and short clip on Workforce Risk.

      Product Marketing Lead 3 days

    2. 2

      Publish an integrations page

      All six current integrations with docs links.

      Member of Technical Staff 3 days

    3. 3

      Ask buyers

      Which ATS each workforce prospect uses.

      Account Executive 2 weeks

    4. 4

      Build the next one

      The most requested ATS.

      Member of Technical Staff 4 weeks

    5. 5

      List in marketplaces

      Ashby first, then each new ATS.

      Product Marketing Lead 2 weeks

    6. 6

      Co-market

      A joint post on spotting fake candidates.

      Founding Social Growth Lead 1 month

    First result
    1 month
    Cost
    Engineering time
    Owner
    Product Marketing Lead

    Smallest test

    Add the Ashby section and count Workforce Risk demos for a month.

    Why it works

    Add an "Works inside Ashby" section to Workforce Risk with a short clip of a flagged candidate inside the ATS, and an integrations page listing Ashby, Salesforce, HubSpot, Slack, GitHub and Google Sheets. Then build the next ATS integrations recruiting buyers ask for, and list Sixtyfour in each ATS marketplace.

    Integrations remove the biggest operational objection, and ATS marketplaces put Sixtyfour in front of recruiting teams at the moment they look for fraud tools.

    Risks and how to handle them

    • Integration claims run ahead of the product

      List only live integrations, labelled with what they do.

    Evidence

    • Your docsDocs list integrations with Salesforce, Slack, GitHub, HubSpot, Ashby and Google Sheets; a hosted MCP server, agent skills and a coding-assistant plugin; plus Monitors ("Track fields and get notified on change"), Workflows with templates and schedules, Search (deep, filter, lookalike) and a guide to report wrong data.Source
    • Your websiteWorkforce Risk page ("Know who's behind the application") serves security teams, staffing and talent platforms and contractor operations; it says Sixtyfour does not replace background screening and names no ATS integration.Source
    • Your websiteSitemap (49 URLs, checked November 9, 2026): 36 blog posts, 5 solution pages, /atlas, /lattice, /recon-benchmark, /demo, /brand, /security and the terms page. No pricing page, no case study pages, no comparison pages, no integrations page.Source
  • 15

    Sixtyfour's own tech stack post places it in the account-investigation layer next to case management (Cinder, Tremau), fraud decisioning (Sift, SEON, Sardine) and identity verification (Persona, Veriff, Jumio). Analysts work inside those tools all day. Today they would have to copy an identifier into a separate app.

    High impactHigh effort First result in 1 quarter Account Executive

    First action

    Ask current customers which case-management and fraud tools they use.

    How to measure it

    Integration-sourced accounts

    Now
    –
    Target
    10
    By
    2 quarters

    Steps

    1. 1

      Survey customers

      Which tools sit next to Sixtyfour.

      Account Executive 1 week

    2. 2

      Pick one partner

      The tool most customers share.

      Account Executive 1 week

    3. 3

      Build the action

      Send identifiers, return cited findings via webhooks.

      Member of Technical Staff 4 weeks

    4. 4

      Pilot

      With one shared customer.

      Head of Trust & Safety 4 weeks

    5. 5

      List it

      Partner marketplace and integrations page.

      Product Marketing Lead 2 weeks

    6. 6

      Co-market

      A joint webinar or case study.

      Product Marketing Lead 1 month

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Account Executive

    Smallest test

    Build a Slack or webhook recipe a customer can wire into their case tool themselves.

    Why it works

    Start with case management: build an "Investigate with Sixtyfour" action that sends the flagged account's identifiers to the API and writes cited findings back to the case, using the existing webhooks. Approach the vendors' partner programs with a joint customer, then list the integration in their marketplaces and on the new integrations page.

    Integrations inside the analyst's daily tool turn Sixtyfour into a habit rather than an extra tab, and partner marketplaces are distribution that demo-only rivals already use.

    Risks and how to handle them

    • Partner programs move slowly

      Build on public APIs first and start with a shared customer's request.

    Builds on

    Evidence

    • Your websiteSixtyfour's trust and safety tech stack post (November 4, 2026) puts Sixtyfour in the account-investigation layer, next to identity verification (Persona, Veriff, Jumio), device intelligence (Fingerprint, Incognia), fraud decisioning (Sift, SEON, Sardine) and case management (Cinder, Tremau); it ends with Request a Demo.Source
    • Your docsDocs list integrations with Salesforce, Slack, GitHub, HubSpot, Ashby and Google Sheets; a hosted MCP server, agent skills and a coding-assistant plugin; plus Monitors ("Track fields and get notified on change"), Workflows with templates and schedules, Search (deep, filter, lookalike) and a guide to report wrong data.Source
  • 16

    Sixtyfour has a hosted MCP server, an agent skills repo and a coding-assistant plugin, with setup guides for the popular code editors. Its GitHub org has 16 followers and the skills repo 5 stars. Developers find tools like these in MCP registries, plugin directories and awesome-lists, and those places drive installs.

    Medium impactLow effort First result in 1 month Member of Technical Staff

    First action

    List the five MCP directories with the most traffic and submit to the first.

    How to measure it

    New MCP connections

    Now
    –
    Target
    5x
    By
    90 days

    Steps

    1. 1

      Pick directories

      MCP registries, plugin directories and awesome-lists.

      Growth Intern 1 day

    2. 2

      Polish the READMEs

      Install line, free credits, RECON result.

      Member of Technical Staff 1 day

    3. 3

      Submit

      One listing per directory, tagged URLs.

      Growth Intern 1 week

    4. 4

      Record a clip

      60-second install and first query.

      Founding Social Growth Lead 2 days

    5. 5

      Post

      On X and LinkedIn with the clip.

      Founding Social Growth Lead 1 day

    6. 6

      Track

      Connections and paid conversions by source.

      Growth Intern weekly

    First result
    1 month
    Cost
    $0
    Owner
    Member of Technical Staff

    Smallest test

    Submit to two directories this week.

    Why it works

    Submit the MCP server and skills to the main MCP registries and plugin directories, with a one-line install and the free credit count. Add a README badge and a 60-second install video. Track installs by source with a tag in the setup URL.

    Developer distribution is mostly listings and word of mouth. Each listing is a permanent, free entry point, and RECON gives the listing a clear reason to choose Sixtyfour.

    Risks and how to handle them

    • Low-quality installs

      Measure paid conversion by directory and drop the weakest.

    Evidence

    • Your docsDocs list integrations with Salesforce, Slack, GitHub, HubSpot, Ashby and Google Sheets; a hosted MCP server, agent skills and a coding-assistant plugin; plus Monitors ("Track fields and get notified on change"), Workflows with templates and schedules, Search (deep, filter, lookalike) and a guide to report wrong data.Source
    • GitHubGitHub org: 5 public repos (skills, benchmarks, demos, a coding-assistant plugin manifest, notebooks), 16 followers; the benchmarks repo has 3 stars and the skills repo 5.Source
    • Your websitePlan details appear only inside a blog post on the MCP server (November 5, 2026): "The Free plan includes 64 credits, given once to the organisation created at sign-up. Paid plans start at 100 credits a month on the Individual plan. Top-up credits cost $0.30 each, with a $50 minimum on an active paid plan." The post ends with a Sign up link to app.sixtyfour.ai/signup.Source
  • 17

    Once self-serve opens, free accounts from payments companies, marketplaces and staffing platforms will test quietly. The AEs are hired to nurture and close pipeline, and the ARR went from $0 to $4 million in five months, so the best new pipeline will come from accounts already using the product.

    High impactMedium effort First result in 1 month Account Executive

    First action

    Define the fit list and the usage trigger.

    How to measure it

    PQL-sourced opportunities

    Now
    –
    Target
    15 a month
    By
    90 days

    Steps

    1. 1

      Define fit

      Segments, company size and work-email rule.

      Account Executive 2 days

    2. 2

      Define triggers

      Credits used, bulk jobs, requests for on-request tiers.

      Product Marketing Lead 2 days

    3. 3

      Build alerts

      Into the CRM with a usage summary by type.

      Member of Technical Staff 1 week

    4. 4

      Write the outreach

      Offer a credit top-up and an Atlas trial.

      Account Executive 1 day

    5. 5

      Respond fast

      Within one business day of the trigger.

      Account Executive ongoing

    6. 6

      Review

      Conversion by trigger type.

      Growth Intern monthly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Account Executive

    Smallest test

    Pull this month's free accounts by domain and call the five best fits.

    Why it works

    Score each new organization on company domain (segment and size), what it ran (Atlas-style questions, bulk jobs, workforce or KYB fields) and credits used. When a good-fit account uses most of its 64 credits or asks for a tier that is "on request", alert an AE with a summary of what they researched by type, never the subjects.

    Teams that hit a limit have proven intent and know the product; a timely, informed offer of more credits or Atlas access converts far better than cold outreach.

    Risks and how to handle them

    • Outreach feels like surveillance

      Share usage by type only and offer help, not pressure.

    Builds on

    Evidence

    • HiringAccount Executive (San Francisco, $120K-$350K): "We are growing very fast, going from $0 ARR in May, to $4mm as of October 2026." AEs will "take on some of our pipeline, continue to nurture it and ultimately close it"; the final interview is a live sales call with a real customer.Source
    • Your websitePlan details appear only inside a blog post on the MCP server (November 5, 2026): "The Free plan includes 64 credits, given once to the organisation created at sign-up. Paid plans start at 100 credits a month on the Individual plan. Top-up credits cost $0.30 each, with a $50 minimum on an active paid plan." The post ends with a Sign up link to app.sixtyfour.ai/signup.Source
    • Your docsCredit costs guide: People Intelligence micro 0.3, low (default) 1 and medium 20 credits per record for all organizations; high 40 and xhigh 250 per unit (Atlas) on request. Company Intelligence low 1, medium 5. Find Email 0.5, Find Phone 3, search 0.1 per result, verify-age 40. No dollar price per credit; "Enterprise contracts can set custom rates." Atlas, high and xhigh are enabled for Enterprise customers on request.Source
  • 18

    Sixtyfour is SOC 2 Type 2 compliant and has a template DPA and a public subprocessor list, but the report and DPA are on request through a compliance portal and nothing explains where findings come from or how accuracy is measured. Financial crime and trust and safety buyers send every vendor through security and compliance review, which slows the AEs' deals.

    Medium impactLow effort First result in 1 quarter Account Executive

    First action

    List the ten questions security reviewers asked in the last five deals.

    How to measure it

    Sales cycle length

    Now
    –
    Target
    -20%
    By
    2 quarters

    Steps

    1. 1

      Collect questions

      From recent security reviews.

      Account Executive 2 days

    2. 2

      Write answers

      Sources, citations, accuracy, retention, access.

      Member of Technical Staff 1 week

    3. 3

      Review

      Accuracy and legal wording.

      Chief of Staff 3 days

    4. 4

      Publish

      /procurement linked from /security and pricing.

      Product Marketing Lead 1 day

    5. 5

      Use in deals

      Send after every first call.

      Account Executive ongoing

    6. 6

      Update

      After each new audit or policy.

      Chief of Staff quarterly

    First result
    1 quarter
    Cost
    Staff time only
    Owner
    Account Executive

    Smallest test

    Send a one-page PDF version in the next five deals.

    Why it works

    Publish a /procurement page: SOC 2 Type 2 (request button), DPA, subprocessors, data source categories and how findings are cited, how RECON measures accuracy, how to report wrong data, retention and access controls. AEs send it on the first call so the reviewer starts early.

    Most enterprise delays happen in review, not in the buying decision. A single page answers the standard questions before they are asked.

    Risks and how to handle them

    • Over-promising on data handling

      Have the security owner approve every statement.

    Evidence

    • Your websiteSecurity page: SOC 2 Type 2 compliant, report on request; a compliance portal holds policies and a template DPA, shared on request; subprocessors listed publicly.Source
    • HiringAccount Executive (San Francisco, $120K-$350K): "We are growing very fast, going from $0 ARR in May, to $4mm as of October 2026." AEs will "take on some of our pipeline, continue to nurture it and ultimately close it"; the final interview is a live sales call with a real customer.Source
    • Your docsDocs list integrations with Salesforce, Slack, GitHub, HubSpot, Ashby and Google Sheets; a hosted MCP server, agent skills and a coding-assistant plugin; plus Monitors ("Track fields and get notified on change"), Workflows with templates and schedules, Search (deep, filter, lookalike) and a guide to report wrong data.Source
  • 19

    Sixtyfour already has Monitors ("Track fields and get notified on change"), billed at 0.2 credits per active row per check. Yet every solution page describes a one-time investigation at onboarding. Financial crime teams need ongoing due diligence, and marketplace and contractor risk changes after day one.

    High impactMedium effort First result in 2 months Account Executive

    First action

    Pick three customers with large onboarding volume and offer the 30-day monitor.

    How to measure it

    Revenue from monitored records

    Now
    –
    Target
    15% of new ARR
    By
    2 quarters

    Steps

    1. 1

      Define the package

      Fields watched, check frequency, alert channels.

      Head of Trust & Safety 1 week

    2. 2

      Price it

      Per monitored record per month, from the 0.2-credit probe.

      Account Executive 3 days

    3. 3

      Pilot

      Three customers, 500 subjects each, 30 days.

      Account Executive 1 month

    4. 4

      Capture results

      Changes found that mattered.

      Head of Trust & Safety 1 week

    5. 5

      Add to pages

      Each solution page and pricing.

      Product Marketing Lead 1 week

    6. 6

      Offer at renewal

      To every customer.

      Account Executive ongoing

    First result
    2 months
    Cost
    Pilot credits and staff time
    Owner
    Account Executive

    Smallest test

    Run one monitor on one customer's last 100 subjects for 30 days.

    Why it works

    Package "Continuous due diligence": every subject researched at onboarding is added to a Monitor that watches ownership, adverse media and new linked accounts, with Slack or case-tool alerts. Add it as a line on each solution page and as an Enterprise add-on priced per monitored record. Offer existing customers a free 30-day monitor on their last 500 subjects.

    Recurring monitoring turns one-off lookups into steady usage revenue and makes Sixtyfour harder to replace.

    Risks and how to handle them

    • Too many low-value alerts

      Alert only on fields the customer chooses, with a weekly digest by default.

    Evidence

    • Your docsDocs list integrations with Salesforce, Slack, GitHub, HubSpot, Ashby and Google Sheets; a hosted MCP server, agent skills and a coding-assistant plugin; plus Monitors ("Track fields and get notified on change"), Workflows with templates and schedules, Search (deep, filter, lookalike) and a guide to report wrong data.Source
    • Your docsCredit costs guide: People Intelligence micro 0.3, low (default) 1 and medium 20 credits per record for all organizations; high 40 and xhigh 250 per unit (Atlas) on request. Company Intelligence low 1, medium 5. Find Email 0.5, Find Phone 3, search 0.1 per result, verify-age 40. No dollar price per credit; "Enterprise contracts can set custom rates." Atlas, high and xhigh are enabled for Enterprise customers on request.Source
    • Your websiteSolution pages: Financial Crime ("Follow the business. Find the people behind it."), Fraud & Abuse and Threat Investigations name no customers and give no results figures; examples are illustrative. Workforce Risk names one customer (Casco). Every page's main buttons go to /demo.Source
  • 20

    The social lead is asked to turn customer use cases into stories, starting with trust and safety, and the PMM role lists "live investigation runs" as a stunt. The solution pages already contain good illustrative investigations (a merchant with a look-alike director, a candidate whose public work predates the claimed history), but they stay on the website.

    Medium impactLow effort First result in 1 month Founding Social Growth Lead

    First action

    Turn the Financial Crime page's merchant example into the first case file.

    How to measure it

    Case-file engagement

    Now
    –
    Target
    Median 50 reposts
    By
    1 quarter

    Steps

    1. 1

      Pick cases

      Eight illustrative investigations for two months.

      Head of Trust & Safety 1 week

    2. 2

      Write the template

      Identifier, steps, sources, open question.

      Founding Social Growth Lead 1 day

    3. 3

      Make visuals

      Screenshots or a short screen recording.

      Growth Intern weekly

    4. 4

      Post

      Company account and the CEO's.

      Founding Social Growth Lead weekly

    5. 5

      Reply

      Engage with practitioners in the comments.

      Founding Social Growth Lead daily

    6. 6

      Review

      Keep or kill formats monthly.

      Founding Social Growth Lead monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Founding Social Growth Lead

    Smallest test

    Post one case file and compare it with the last ten posts.

    Why it works

    Each week, post one short case file on X and LinkedIn: the starting identifier, three or four steps the agents took, what was cited, and the open question a human still had to resolve. Use invented or consenting subjects, or patterns drawn from customer work with permission. End with a link to the matching free tool or how-to post.

    Step-by-step investigations are the kind of post practitioners save and share, and they show the cited, careful style that sets Sixtyfour apart without a sales pitch.

    Risks and how to handle them

    • A post exposes a real person

      Only invented or consenting subjects; review before posting.

    Evidence

    • HiringFounding Social Growth Lead: make Sixtyfour and the CEO essential follows on X and LinkedIn; "Turn customer use cases into stories, starting with trust and safety teams"; success means posts lead to demos, intros, candidates and investors; prefers "five posts people quote than fifty they scroll past".Source
    • HiringProduct Marketing Lead: will "decide what we say publicly and where"; leads launch weeks with demos, benchmarks against competitors and case studies; growth stunts such as "live investigation runs, bounties, free tool drops"; builds blogs, teardowns and comparison pages; owns traffic, signups and pipeline and instruments attribution. Nice to have: marketing to compliance, security, trust and safety or investigations buyers, and developer or API marketing.Source
    • Your websiteSolution pages: Financial Crime ("Follow the business. Find the people behind it."), Fraud & Abuse and Threat Investigations name no customers and give no results figures; examples are illustrative. Workforce Risk names one customer (Casco). Every page's main buttons go to /demo.Source

Big bets 3

Larger plays that can change the trajectory.

  • 21

    RECON is already rigorous: 140 people, 514 verified fields, runs by HUD, a public harness and a 98.5% judge agreement with human review. Sixtyfour's own post admits it built the benchmark and offers five of the 23 configurations. Turning it into an independently governed, regularly updated leaderboard would make it the accuracy standard for people research, with Sixtyfour as the team that set it.

    High impactHigh effort First result in 2 quarters CEO

    First action

    Write the submission rules and governance in one page.

    How to measure it

    External RECON submissions

    Now
    –
    Target
    5 vendors
    By
    2 quarters

    Steps

    1. 1

      Set governance

      Rules, an advisory group and HUD as runner.

      CEO 1 month

    2. 2

      Build a held-out set

      New subjects each quarter with primary-source answers.

      Member of Technical Staff 6 weeks

    3. 3

      Open submissions

      Through the public harness.

      Member of Technical Staff 2 weeks

    4. 4

      Invite vendors

      Every system on the current board, and new ones.

      Product Marketing Lead 1 month

    5. 5

      Publish quarterly

      Leaderboard, cost, latency and failure cases.

      Product Marketing Lead quarterly

    6. 6

      Launch each round

      Launch week across X, LinkedIn and the newsletter.

      Founding Social Growth Lead quarterly

    First result
    2 quarters
    Cost
    HUD runs, dataset building and staff time
    Owner
    CEO

    Smallest test

    Invite two outside vendors to run the current RECON and publish their results.

    Why it works

    Publish RECON results each quarter, open submissions from any vendor through the public harness, add a fresh held-out set each round to prevent overfitting, and invite an advisory group from trust and safety and investigations practitioners. Add cost and latency columns (idea 3). Launch each round as a launch week.

    Categories are often defined by whoever owns the scoreboard. Buyers and analysts cite a recurring, neutral benchmark, and each round brings a fresh wave of attention.

    Risks and how to handle them

    • Seen as self-serving

      Independent runner, outside advisors and published failure cases.

    • A rival overtakes Sixtyfour

      That is the price of credibility; the scoreboard still shows Sixtyfour as the category's reference.

    Builds on

    Evidence

    • Your websiteRECON benchmark (evaluations run by HUD, September 8 to October 6, 2026): 140 people, 514 verified fields; Sixtyfour XHigh 70.6% weighted accuracy, 84.4% recall at 85.9% precision, against 41.1% for the best outside system (Parallel Ultra 2x). The harness is public on GitHub; the dataset is by request. "Cost and latency are out of scope." Buttons: Book a demo and Try Sixtyfour.Source
    • Your websiteSearch benchmark post (October 13, 2026): on Exa's open-source benchmarks, Sixtyfour's people search top result is relevant for 90.4% of queries vs Exa's 72.0%, and company search 86.4% vs 61.8%. The post links to app.sixtyfour.ai/signup.Source
    • PressTech Funding News (July 10, 2026): customers concentrate in blockchain-intelligence firms, payments companies and trust and safety teams; about twelve people, eight engineers, including an early trust and safety leader with two decades in the field; the CEO: "Breadth is a vanity metric."Source
  • 22

    The Financial Crime page says KYB APIs confirm a business exists and who its officers are, and KYC APIs confirm a document and its holder, while Sixtyfour adds research on those people, their other entities, adverse media and undisclosed relationships. That is a description of an add-on. Verification platforms sell to the same fintechs and payments companies at far larger volume.

    High impactHigh effort First result in 2 quarters CEO

    First action

    List the KYB and KYC providers current customers use and pick one with a shared customer.

    How to measure it

    Partner-sourced ARR

    Now
    –
    Target
    $1M
    By
    4 quarters

    Steps

    1. 1

      Map overlap

      Which verification providers customers use.

      Account Executive 2 weeks

    2. 2

      Define the add-on

      Inputs, outputs, tiers and price.

      CEO 2 weeks

    3. 3

      Approach two partners

      With a shared customer as the pilot.

      CEO 1 month

    4. 4

      Build the connector

      Their case IDs in, cited findings out.

      Member of Technical Staff 6 weeks

    5. 5

      Pilot

      One quarter with the shared customer.

      Head of Trust & Safety 1 quarter

    6. 6

      Launch

      Joint announcement and marketplace listing.

      Product Marketing Lead 1 month

    First result
    2 quarters
    Cost
    Engineering and partnership time; revenue share
    Owner
    CEO

    Smallest test

    Run a shared customer's escalated cases through Sixtyfour for one month.

    Why it works

    Package the Research API as an enhanced due diligence add-on that verification platforms can resell or embed: their customer flags a case as needing a deeper look, Sixtyfour returns cited findings in their interface, and both share the revenue. Start with one KYB provider and one KYC provider, with a joint customer in each.

    Partners bring distribution that a 12-person team cannot build directly, and the cited-findings format fits the audit trail their customers already keep.

    Risks and how to handle them

    • Partners build it themselves

      Lead with RECON accuracy and keep the deepest tiers exclusive to Sixtyfour.

    • Channel conflict with direct sales

      Clear account rules: partners own volume screening, Sixtyfour owns Atlas deals.

    Builds on

    Evidence

    • Your websiteSolution pages: Financial Crime ("Follow the business. Find the people behind it."), Fraud & Abuse and Threat Investigations name no customers and give no results figures; examples are illustrative. Workforce Risk names one customer (Casco). Every page's main buttons go to /demo.Source
    • Competitor researchRivals' own homepages: Pipl ("Make better risk decisions", for enterprise fraud and risk teams), Middesk ("Decide who to do business with", business verification plus AI agent investigations) and Social Links (OSINT from "850+ open sources") show no pricing and offer only a demo.Source
    • PressTech Funding News (July 10, 2026): customers concentrate in blockchain-intelligence firms, payments companies and trust and safety teams; about twelve people, eight engineers, including an early trust and safety leader with two decades in the field; the CEO: "Breadth is a vanity metric."Source
  • 23

    Candidate fraud is Sixtyfour's most quotable story: the only named testimonial is a CEO saying "We see fake North Korean workers apply to Casco", and the blog has guides on fake candidates, fake references and resume verification. Sixtyfour sees patterns across many hiring investigations that no single employer can see.

    High impactHigh effort First result in 2 quarters Head of Trust & Safety

    First action

    Ask workforce customers for consent to include aggregated results.

    How to measure it

    Report-sourced pipeline

    Now
    –
    Target
    30 opportunities
    By
    2 quarters after launch

    Steps

    1. 1

      Get consent

      Aggregated, anonymized use from workforce customers.

      Account Executive 1 month

    2. 2

      Define measures

      Gap types and how they were resolved.

      Head of Trust & Safety 2 weeks

    3. 3

      Pull data

      Aggregates only, minimum group sizes.

      Member of Technical Staff 3 weeks

    4. 4

      Write

      Findings, fairness guidance and a checklist.

      Head of Trust & Safety 1 month

    5. 5

      Launch

      Report page, webinar and press outreach.

      Product Marketing Lead 1 month

    6. 6

      Follow up

      Downloads from target companies go to AEs.

      Account Executive ongoing

    First result
    2 quarters
    Cost
    Staff time and launch costs
    Owner
    Head of Trust & Safety

    Smallest test

    Publish three aggregated statistics in one blog post.

    Why it works

    With customer consent and only aggregated, anonymized data, publish a yearly report: share of investigated applicants with unresolved identity or history gaps, the most common inconsistencies, which roles and remote setups attract them, and how teams resolve them without rejecting genuine thin-footprint candidates. Release it with a webinar for security and talent leaders and a free checklist.

    Original data earns press and backlinks, and it makes Sixtyfour the source for a fast-growing hiring-risk topic while staying consistent with its "evidence, not verdicts" stance.

    Risks and how to handle them

    • Findings stigmatize groups of candidates

      Report on behaviors and inconsistencies only, never on nationality or other personal characteristics, and repeat the "thin footprint is not a verdict" guidance.

    • Too little data

      Start as a half-year brief and grow it.

    Builds on

    Evidence

    • Your websiteHomepage: banner claiming #1 on people research with a link to the benchmark; ten customer logos (Mercor, Gryphon Investors, Cloaked, TRM Labs, ZoomInfo, Airwallex, GOTV, Delphi, Moritz, Turing); a "Proven impact, in their words" carousel numbered 1-7 with one quote readable on the page, from Casco's CEO ("We see fake North Korean workers apply to Casco"); none links to a case study page.Source
    • Your websiteWorkforce Risk page ("Know who's behind the application") serves security teams, staffing and talent platforms and contractor operations; it says Sixtyfour does not replace background screening and names no ATS integration.Source
    • Your websiteBlog: 35 posts, 29 in Trust & Safety, mostly how-to guides (how to find out who owns an LLC, verify a vendor, investigate a phone number, tell if a LinkedIn profile is fake); no newsletter or subscribe box; posts end with a demo request.Source

Wildcards 1

Unexpected experiments, each with a cheap way to test it.

  • 24

    The PMM role lists bounties among the growth stunts, RECON's harness is public, and the docs already have a "report wrong data" flow. The OSINT and investigations community is exactly the audience Sixtyfour sells to, and it respects people who invite scrutiny.

    Medium impactMedium effort First result in 1 month Product Marketing Lead

    First action

    Write the rules: eligible subjects, proof standard, payouts and the end date.

    How to measure it

    Bounty participants who sign up

    Now
    –
    Target
    300
    By
    2 months

    Steps

    1. 1

      Write rules

      Consenting subjects only; primary-source proof.

      Head of Trust & Safety 1 week

    2. 2

      Set payouts

      Per verified finding, with a cap.

      CEO 1 day

    3. 3

      Build intake

      On the existing report-wrong-data flow.

      Member of Technical Staff 1 week

    4. 4

      Launch

      Launch week on X and LinkedIn and in OSINT communities.

      Founding Social Growth Lead 1 week

    5. 5

      Verify

      Review each submission against its source.

      Head of Trust & Safety 3 weeks

    6. 6

      Publish

      Leaderboard, payouts and what changed in the agents.

      Product Marketing Lead 1 week

    First result
    1 month
    Cost
    Bounty pool plus review time
    Owner
    Product Marketing Lead

    Smallest test

    Run it on the team's own profiles, with team consent, for one week.

    Why it works

    Run a time-boxed bounty on consenting or public-figure subjects: researchers submit facts the agents missed or got wrong, with a primary source. Pay per verified finding, publish a leaderboard of researchers, and fold confirmed misses into the next RECON round and the agents' evals.

    It earns attention and goodwill in the buyer community, turns critics into contributors and produces real data to improve accuracy, all in line with the "claims we can prove" stance.

    Risks and how to handle them

    • Encourages digging into private people

      Only consenting volunteers or public figures; no home addresses or family details accepted.

    Builds on

    Evidence

    • HiringProduct Marketing Lead: will "decide what we say publicly and where"; leads launch weeks with demos, benchmarks against competitors and case studies; growth stunts such as "live investigation runs, bounties, free tool drops"; builds blogs, teardowns and comparison pages; owns traffic, signups and pipeline and instruments attribution. Nice to have: marketing to compliance, security, trust and safety or investigations buyers, and developer or API marketing.Source
    • Your websiteRECON benchmark (evaluations run by HUD, September 8 to October 6, 2026): 140 people, 514 verified fields; Sixtyfour XHigh 70.6% weighted accuracy, 84.4% recall at 85.9% precision, against 41.1% for the best outside system (Parallel Ultra 2x). The harness is public on GitHub; the dataset is by request. "Cost and latency are out of scope." Buttons: Book a demo and Try Sixtyfour.Source
    • Your docsDocs list integrations with Salesforce, Slack, GitHub, HubSpot, Ashby and Google Sheets; a hosted MCP server, agent skills and a coding-assistant plugin; plus Monitors ("Track fields and get notified on change"), Workflows with templates and schedules, Search (deep, filter, lookalike) and a guide to report wrong data.Source

03

How Programmable can help

Where an idea in this playbook is something Programmable builds or runs, it's listed here with what we'd do. Everything else is yours to run.

ProgrammableDigital

Show it, don't just describe it

These ideas need something to show: a demo, a video, an animation, graphics or a deck. Digital turns screenshots or the site into all of them, in the company's own brand.

Make a demo (opens programmable.digital in a new tab)
More example playbooks and reviews

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • NUFACE growth strategyMakes FDA-cleared at-home microcurrent devices (TRINITY+, MINI+, FIX MicroWand, NUBODY), activator gels, boosters and attachments, sold…22 growth ideas
  • PrizePicks growth strategyA sports entertainment app: daily fantasy Player Picks, Team and Culture Picks through its regulated prediction-markets arm, Free2Play…22 growth ideas
  • Lead Assassin growth strategyAn outbound and GTM engineering agency that builds pipeline systems (Clay enrichment, cold email and LinkedIn sequencing, CRM and RevOps…23 growth ideas
  • BamLabs growth strategyAn embedded GTM engineering team in Surry Hills, Sydney. BamLabs builds, runs and improves go-to-market systems: CRM enrichment, market…21 growth ideas
  • Vapi growth strategyA developer platform for building, testing and running voice AI agents: telephony, real-time speech-to-text, LLM and text-to-speech…21 growth ideas
  • Handshake growth strategyA career network connecting students, graduates and professionals with employers and universities, plus Handshake AI, which supplies…21 growth ideas
  • Cresta growth strategyAn AI platform for customer experience: autonomous AI Agents, real-time Agentic Assist for human agents, Deputy Agent for back-office…21 growth ideas
  • Outpost growth strategyA tech-enabled Reddit marketing agency: it maps where a brand's buyers talk, posts openly as the brand or named team members, builds and…22 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 9, 2026, and cites them throughout. Sixtyfour did not commission, review or endorse it, and Programmable is not affiliated with Sixtyfour. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Sixtyfour runs its business.

Something wrong, or do you represent Sixtyfour? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 308 ideas

    Open the self-serve door: pricing page, signup buttons, split demo page, benchmark-to-trial, cost per correct fact, Atlas page, updated YC descriptions, homepage responsiveness, and the first comparison page.

  2. Days 31 to 6010 ideas

    Proof and pull: case studies per solution, free tools, self-lookup, run-this-check boxes in the how-to posts, a field-brief newsletter, the ATS story, developer directories, product-qualified leads, a procurement kit and weekly case-file posts.

  3. Days 61 to 906 ideas

    Ecosystem and category: trust and safety stack integrations, Monitors as expansion, a standing RECON leaderboard, KYB and KYC partner add-ons, a fake-candidate report and a Beat RECON bounty.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value findings with a cited source for every fact. The most cited problem: platform-internal signals miss who is really behind an account.

  • Starting from a single identifier
  • Registry checks confirm a business exists but not who runs it
  • In their words: “who is behind the account”

Market

Competitive landscape

4 competitors compared: Pipl, Middesk, Social Links and Parallel.

  • Gap to exploit: Self-serve, priced access to investigation-grade people research
  • Pipl: Demo-only, no public pricing
  • Middesk: Business-first, lighter on the people behind entities

Hiring signals

Sixtyfour (12 people, $0 to $4 million ARR between May and October 2026) is hiring for distribution.

  • Product Marketing Lead: Launch weeks, benchmarks, comparison pages, free tools and bounties; owns signups. Ideas 1, 3, 9, 10, 24.
  • Founding Social Growth Lead: X and LinkedIn for the company and CEO, trust and safety stories first. Ideas 6, 11, 20.
  • Account Executive: $0 to $4mm ARR from May to October 2026; close existing pipeline. Ideas 2, 17, 18, 19.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks firstNew accounts get 100,000 free enrichment credits with code BETA100K (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammableMediaAn AI note taker, interpreter and webinar host for your calls (opens programmable.media in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence