ProgrammableMarketing/fenrock.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 · 6
  • This quarter · 11
  • Big bets · 3
  • Wildcards · 2
  • How we can help
Generated Nov 10, 2026
  1. Programmable
  2. Playbooks
  3. Fenrock
Fenrock logo

growth playbook · Nov 10, 2026

fenrock.ai (opens in a new tab)

Fenrock growth playbook

Diagnosis

Fenrock is a two-person Y Combinator W26 company with customers already using its product and two founding engineers being hired. Its pitch is sharp: "An analyst clears about 10 alerts a day. Fenrock is built for 20x that." The website doesn't carry that pitch yet. It is one page whose text only appears after scripts run.

Its robots.txt blocks the AI assistants that bank buyers now use to research vendors. The only contact route is a mailto link. There are no case studies, no trust page and no use-case pages, while Hummingbird and Bretton publish customer results, trust centers and ROI calculators.

This playbook first makes the site readable and contactable, with a trust page, a capacity calculator and a sharper wedge headline. Next it turns early customers into measured proof: a shadow-mode pilot on closed alerts, an examiner-ready sample case file, CEO-to-CEO referrals and a credit-union path. The big bets are a community-bank capacity benchmark, a second product in loan operations and integration partnerships.

Growth Score

6/10

Biggest Opportunity

Community banks face the same regulation as the largest banks but have a handful of analysts. Fenrock can own that gap if it shows measured capacity gains from its first customers and makes itself easy to find, verify and buy.

Biggest Risk

Better-funded rivals already sell AI compliance agents to the same regulated banks, with published results and trust centers. A two-person vendor with no public proof will struggle to pass bank vendor reviews unless it gets to evidence first.

01

Start here

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

  1. 1

    Turn the SOC 2 mention into a trust page that answers a bank's vendor-risk questionnaire

    List the 20 questions the first customers' vendor-risk teams asked.

    High impact First result in 1 month
  2. 2

    Let the AI assistants that bank buyers use for vendor research read fenrock.ai: robots.txt blocks them and the homepage HTML carries only a title

    Move the user-triggered assistant agents to Allow in robots.txt and redeploy.

    High impact First result in 2-6 weeks
  3. 3

    Replace the mailto-only contact with a short demo form that asks about the bank's alert backlog

    Build the form in the existing site stack and point the button to it.

    High impact First result in 2 weeks

02

Your idea portfolio

22 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 · 9Fill-ins · 7Reconsider · 3
Effort →

Showing 22 of 22 ideas

This week 6

Quick wins with a clear first action.

  • 01

    Fenrock sells AI to banks, but its robots.txt disallows the AI agents it lists under "Common AI / LLM crawlers". That list includes the agents that fetch a page live when a person asks an assistant a question, not only training crawlers. Even a reader that is allowed in gets almost nothing: without running JavaScript, the homepage returns only its title. The headline, product copy and "Request a Demo" button are all drawn by scripts. When a BSA officer or bank COO asks an assistant which tools help a community bank clear an alert backlog, the assistant can't read Fenrock's own description. It falls back on third-party write-ups, or on rivals like Hummingbird and Bretton that publish full pages. This is not a speed problem: real visitors pass Core Web Vitals and the SEO score is 100. It is a readability problem for machines.

    High impactLow effort First result in 2-6 weeks CTO

    First action

    Move the user-triggered assistant agents to Allow in robots.txt and redeploy.

    How to measure it

    Assistant citations on five buyer questions

    Now
    –
    Target
    3 of 5
    By
    90 days

    Steps

    1. 1

      Set the policy

      Decide which agents to allow: user-triggered fetchers yes, training crawlers a separate call.

      CEO 1 hour

    2. 2

      Edit robots.txt

      Move the chosen agents to Allow and keep the search-engine rules as they are.

      CTO 30 minutes

    3. 3

      Prerender the homepage

      Static HTML at build time, with the same markup hydrated afterwards.

      Founding Engineer (Full stack) 3 days

    4. 4

      Check the raw HTML

      Fetch the page without JavaScript and confirm the headline, use cases and demo link are there.

      Founding Engineer (Full stack) 1 hour

    5. 5

      Add structured data

      Organization and SoftwareApplication markup using the same wording as the page.

      Founding Engineer (Full stack) 1 day

    6. 6

      Baseline five questions

      Ask the major assistants five buyer questions and log what they say about Fenrock.

      CEO 1 hour

    7. 7

      Re-check monthly

      Log citations and errors, and fix the page wherever answers are wrong.

      CEO monthly

    First result
    2-6 weeks
    Cost
    $0, about 4 days of engineering
    Owner
    CTO

    Smallest test

    Allow one assistant agent, prerender the headline and description, and ask the five questions again in two weeks.

    Why it works

    Make two changes. First, in robots.txt, move the user-triggered assistant agents (the ones that fetch a page because a person asked) from Disallow to Allow. Whether training crawlers stay blocked can be a separate decision. Second, prerender the homepage at build time on Vercel so the initial HTML holds the headline, the four use cases (compliance, fraud investigations, loan operations, customer operations), "the analyst decides", audit logs, SOC 2 and a working demo link. Add Organization structured data. Then write five questions a bank buyer would ask an assistant, record today's answers, and re-check monthly whether Fenrock is cited and described correctly.

    Bank leaders research vendors before taking a call, and a two-person company can't be in every room. Being readable wherever buyers ask questions is cheap reach. The same prerendered HTML also gives proper link previews when a link is forwarded inside a bank by email, Teams or Slack.

    Ready to use

    ChecklistReadable-site checklist

    [ ] robots.txt: user-triggered assistant agents under Allow
    [ ] Training-crawler policy decided and documented
    [ ] Homepage prerendered: headline, four use cases, "the analyst decides", audit logs, SOC 2
    [ ] Demo link present as a plain HTML link
    [ ] Organization structured data
    [ ] Page checked without JavaScript
    [ ] Five buyer questions baselined, with a monthly re-check

    Risks and how to handle them

    • Concern about content being used for training

      Allow only the user-triggered agents and keep training crawlers blocked.

    • Prerendering breaks the current animations

      Hydrate the same markup and test on mobile before shipping.

    Evidence

    • Your websiterobots.txt (read November 10, 2026) allows Googlebot, Bingbot, DuckDuckBot, Twitterbot and facebookexternalhit, but under "Common AI / LLM crawlers" disallows GPTBot, ChatGPT-User, CCBot, ClaudeBot, AnthropicBot, Applebot-Extended, PerplexityBot, Bytespider, Diffbot and YouBot.Source
    • Your websiteA reader that does not run JavaScript (fetched at www.fenrock.ai and fenrock.ai on November 10, 2026) receives only the page title; the headline, product copy and "Request a Demo" button are drawn by scripts, about 1.1 MB of which load from a Google CDN.Source
    • PageSpeedGoogle PageSpeed (November 10, 2026): mobile performance 59, desktop 88; in the mobile lab test the first and largest content both appear at 6.8 s, the largest element is the "Request a Demo" button, and 430 KB of JavaScript is unused (about 3.9 s of potential savings). Real Chrome visitors pass Core Web Vitals: LCP 1.5 s, INP 32 ms, CLS 0 at the 75th percentile. SEO score 100; accessibility 96 with one colour-contrast issue.Source
    • Competitor researchHummingbird homepage: "AI-powered compliance" for banks, fintechs and crypto firms; screening, transaction monitoring, investigations and SAR/CTR filing; named customer logos and testimonials from BSA leaders; a trust center, security page, webinars, a compliance AI field guide and a "Take a tour" product tour.Source
  • 02

    Fenrock has no social share image and no favicon, and its homepage doesn't link to the LinkedIn and X profiles listed on its Y Combinator page. Bank deals pass from desk to desk, so a link forwarded to a CEO or board member shows up as a blank card from an unknown domain registered in December 2025.

    Medium impactLow effort First result in 1 week Founding Engineer

    First action

    Export a share image from the current homepage design.

    How to measure it

    Visits from LinkedIn and email referrals

    Now
    –
    Target
    +20%
    By
    60 days

    Steps

    1. 1

      Design the card

      1200x630 image with the headline and the bank-CEO line.

      CEO 2 hours

    2. 2

      Add the favicon

      SVG plus PNG sizes.

      Founding Engineer (Full stack) 1 hour

    3. 3

      Add meta tags

      og:image, og:description and twitter:card in the static HTML.

      Founding Engineer (Full stack) 1 hour

    4. 4

      Link profiles

      LinkedIn and X in the footer and in structured data.

      Founding Engineer (Full stack) 30 minutes

    5. 5

      Test previews

      LinkedIn Post Inspector, Teams and email clients.

      Founding Engineer (Full stack) 1 hour

    6. 6

      Track

      Tag shared links in outreach with UTM parameters.

      CEO ongoing

    First result
    1 week
    Cost
    $0
    Owner
    Founding Engineer (Full stack)

    Smallest test

    Add the share image today and post the link on LinkedIn.

    Why it works

    Design a 1200x630 share image (headline plus "Built alongside U.S. bank CEOs"), add a favicon, and add og/twitter meta tags to the prerendered HTML. Link the company LinkedIn and X profiles in the footer and add them to Organization sameAs.

    Small trust cues matter more when the vendor is new and the buyer is regulated. A proper preview card and visible company profiles make the forward look credible.

    Risks and how to handle them

    • Preview caches keep the blank card

      Refresh the card with each platform's inspector tool.

    Builds on

    Evidence

    • Your websiteHomepage (checked November 10, 2026): title "Fenrock | AI Agents for Banking Back Office"; description "The first AI workspace for banking back office. Process 20X volume per analyst with bullet-proof audit logs. Built for banks."; SOC 2 mentioned; the only contact route is a mailto link; no pricing page, blog, case studies, testimonials, careers page or social profile links found from the homepage; no social share image or favicon.Source
    • Y Combinator"AI agents for banks"; "We're building the Legora for traditional financial services", working closely with US bank CEOs; founded 2026, Winter 2026 batch, team of 2, San Francisco. The CEO previously founded two VC-backed companies, one a healthcare API company that reached over 6 million patients and 100+ employees; the CTO spent about ten years on machine learning at Google and Apple. The profile links LinkedIn and X accounts.Source
    • Your websiteHeadline change: in January 2026 the homepage title read "Fenrock | AI Agents for Financial Crime Compliance"; it now reads "Fenrock | AI Agents for Banking Back Office". The domain was registered in December 2025.Source
  • 03

    The "Request a Demo" button is the largest element on the page, but the only contact route found is a mailto link. On many bank laptops a mailto link opens nothing, or opens a client the buyer doesn't use. It also tells Fenrock nothing about the bank before the call. Competitors offer "Schedule a demo", "Take a tour" and AI workshops.

    High impactLow effort First result in 2 weeks CEO

    First action

    Build the form in the existing site stack and point the button to it.

    How to measure it

    Qualified demo requests

    Now
    –
    Target
    2x the current email volume
    By
    60 days

    Steps

    1. 1

      Pick fields

      Five questions that predict fit.

      CEO 1 hour

    2. 2

      Build the form

      Native form with spam protection, no heavy third-party widget.

      Founding Engineer (Full stack) 1 day

    3. 3

      Add the calendar

      Booking slots after the form is submitted.

      Founding Engineer (Full stack) 2 hours

    4. 4

      Route to CRM

      Form answers go to the deal record.

      Founding Engineer (Backend) half a day

    5. 5

      Keep email

      Keep the email address as a secondary option.

      Founding Engineer (Full stack) 15 minutes

    6. 6

      Open with their numbers

      Start each call with the bank's backlog.

      CEO ongoing

    First result
    2 weeks
    Cost
    $0-$20 a month for scheduling
    Owner
    CEO

    Smallest test

    Point the button to a one-page form for two weeks and compare against email volume.

    Why it works

    Use a five-field form: institution type (bank or credit union), approximate asset size, the back-office area in pain (alerts, fraud, loans, complaints), current monitoring or case system, and alerts a month. Then show a booking calendar for the CEO. Send the answers to the CRM and open the call with the bank's own backlog numbers.

    Removing friction for regulated buyers on locked-down laptops lifts conversion, and the qualifying answers let a two-person team prioritise the best-fit banks.

    Risks and how to handle them

    • Fields scare off early leads

      Make only email and institution type required.

    Evidence

    • Your websiteHomepage (checked November 10, 2026): title "Fenrock | AI Agents for Banking Back Office"; description "The first AI workspace for banking back office. Process 20X volume per analyst with bullet-proof audit logs. Built for banks."; SOC 2 mentioned; the only contact route is a mailto link; no pricing page, blog, case studies, testimonials, careers page or social profile links found from the homepage; no social share image or favicon.Source
    • PageSpeedGoogle PageSpeed (November 10, 2026): mobile performance 59, desktop 88; in the mobile lab test the first and largest content both appear at 6.8 s, the largest element is the "Request a Demo" button, and 430 KB of JavaScript is unused (about 3.9 s of potential savings). Real Chrome visitors pass Core Web Vitals: LCP 1.5 s, INP 32 ms, CLS 0 at the 75th percentile. SEO score 100; accessibility 96 with one colour-contrast issue.Source
    • Competitor researchHummingbird homepage: "AI-powered compliance" for banks, fintechs and crypto firms; screening, transaction monitoring, investigations and SAR/CTR filing; named customer logos and testimonials from BSA leaders; a trust center, security page, webinars, a compliance AI field guide and a "Take a tour" product tour.Source
  • 04

    Fenrock's homepage mentions SOC 2 but there is no trust or security page. Banks run third-party risk reviews before any AI vendor touches case data. Hummingbird has a trust center and security page, and Bretton publishes SOC 2 Type II, zero-data retention and independent model validation. The CTO's background in privacy-preserving ML is a strength that isn't on the site.

    High impactMedium effort First result in 1 month CTO

    First action

    List the 20 questions the first customers' vendor-risk teams asked.

    How to measure it

    Vendor-review cycle time

    Now
    –
    Target
    -30%
    By
    2 quarters

    Steps

    1. 1

      Collect questions

      From each existing customer's review.

      CEO 1 day

    2. 2

      Draw the data flow

      One diagram of what moves where.

      CTO 2 days

    3. 3

      Write the page

      Controls, retention, human review, audit logs.

      CTO 3 days

    4. 4

      Pre-fill a questionnaire

      A standard vendor-risk questionnaire, answered.

      CTO 3 days

    5. 5

      Check accuracy

      The auditor or counsel reviews every claim on the page.

      CEO 3 days

    6. 6

      Publish and link

      Footer, demo form and sales emails.

      Founding Engineer (Full stack) half a day

    First result
    1 month
    Cost
    Staff time; optionally a trust-center tool
    Owner
    CTO

    Smallest test

    Send the pre-filled questionnaire to the next prospect before they ask.

    Why it works

    Publish /trust with: SOC 2 status and report-request process, data flows (what leaves the bank, what is stored, where it is stored), data retention, model and vendor use policy, human-in-the-loop controls, audit log contents, access controls, sub-processors, incident contact, and the CTO's privacy-ML background. Add a downloadable pre-filled security questionnaire behind the demo form.

    Vendor risk review is where small AI vendors stall. Answering the questions before they're asked shortens the cycle and signals maturity beyond team size.

    Risks and how to handle them

    • Overstating certification scope

      State the exact SOC 2 type and period, and have the auditor confirm.

    Evidence

    • Your websiteHomepage (checked November 10, 2026): title "Fenrock | AI Agents for Banking Back Office"; description "The first AI workspace for banking back office. Process 20X volume per analyst with bullet-proof audit logs. Built for banks."; SOC 2 mentioned; the only contact route is a mailto link; no pricing page, blog, case studies, testimonials, careers page or social profile links found from the homepage; no social share image or favicon.Source
    • Competitor researchBretton homepage (greenlite.ai now redirects there): "Your AI compliance team" for banks regulated by the OCC, FDIC and Fed and for fintechs; published results such as an "87% reduction in compliance review time" at an FDIC-insured bank and a "70% reduction in EDD queue completion time" at an OCC-regulated bank; SOC 2 Type II, zero-data retention and independent model validation; a trust center, ROI calculator, changelog, an SBA loan review use case, AI workshops and a quarterly publication.Source
    • Competitor researchHummingbird homepage: "AI-powered compliance" for banks, fintechs and crypto firms; screening, transaction monitoring, investigations and SAR/CTR filing; named customer logos and testimonials from BSA leaders; a trust center, security page, webinars, a compliance AI field guide and a "Take a tour" product tour.Source
    • Y Combinator"AI agents for banks"; "We're building the Legora for traditional financial services", working closely with US bank CEOs; founded 2026, Winter 2026 batch, team of 2, San Francisco. The CEO previously founded two VC-backed companies, one a healthcare API company that reached over 6 million patients and 100+ employees; the CTO spent about ten years on machine learning at Google and Apple. The profile links LinkedIn and X accounts.Source
  • 05

    Fenrock's sharpest line is "An analyst clears about 10 alerts a day. Fenrock is built for 20x that." Early customers expect to save 20-30 hours a week per employee. Today a bank leader has to do that math in their head. Bretton offers an ROI calculator.

    Medium impactLow effort First result in 1 month Founding Engineer

    First action

    Write the formula with a conservative multiplier and get the CTO's sign-off.

    How to measure it

    Demo requests from calculator users

    Now
    –
    Target
    15% of completions
    By
    60 days

    Steps

    1. 1

      Agree the math

      Conservative ranges, not the 20x upper bound.

      CEO 1 day

    2. 2

      Design

      Three inputs, two outputs.

      Founding Engineer (Full stack) 1 day

    3. 3

      Build

      Rendered in static HTML, light on JavaScript.

      Founding Engineer (Full stack) 2 days

    4. 4

      Label clearly

      Mark results as expectations, not guarantees.

      CEO 1 hour

    5. 5

      Prefill the form

      Carry the inputs into the demo request.

      Founding Engineer (Full stack) half a day

    6. 6

      Calibrate

      Replace estimates with measured customer data.

      CTO quarterly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Founding Engineer (Full stack)

    Smallest test

    A static table for three bank sizes on the homepage.

    Why it works

    Build an embedded calculator. Inputs: alerts a month, analysts, current backlog. Outputs: days to clear the backlog today versus with Fenrock, and hours freed a week. Use conservative ranges, label them as expectations, and pass the inputs into the demo form.

    Bank buyers justify spend in hours and headcount avoided. A personal number before the call makes the business case and qualifies the lead.

    Risks and how to handle them

    • Promised numbers read as guarantees to a regulated buyer

      Show ranges and note that results depend on alert mix.

    Builds on

    Evidence

    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
    • Competitor researchBretton homepage (greenlite.ai now redirects there): "Your AI compliance team" for banks regulated by the OCC, FDIC and Fed and for fintechs; published results such as an "87% reduction in compliance review time" at an FDIC-insured bank and a "70% reduction in EDD queue completion time" at an OCC-regulated bank; SOC 2 Type II, zero-data retention and independent model validation; a trust center, ROI calculator, changelog, an SBA loan review use case, AI workshops and a quarterly publication.Source
  • 06

    In January the site said "AI Agents for Financial Crime Compliance". It now says "AI Agents for Banking Back Office". The broader frame fits the vision, but "back office" is vague to a BSA officer searching for help with alerts, and compliance is where coverage says Fenrock starts. The most concrete proof (10 alerts a day versus 20x) lives in a podcast write-up, not on the page.

    Medium impactLow effort First result in 1 month CEO

    First action

    Write three H1 options that lead with the backlog.

    How to measure it

    Homepage conversion

    Now
    –
    Target
    +25%
    By
    60 days

    Steps

    1. 1

      Draft headlines

      Three wedge-first options.

      CEO 1 hour

    2. 2

      Ask customers

      Which line matches why they bought.

      CEO 3 days

    3. 3

      Rewrite the first screen

      Headline, proof line, demo button.

      CEO half a day

    4. 4

      Ship

      In the prerendered HTML.

      Founding Engineer (Full stack) half a day

    5. 5

      Align descriptions

      Meta description and social card.

      Founding Engineer (Full stack) 1 hour

    6. 6

      Measure

      Demo rate before and after.

      CEO monthly

    First result
    1 month
    Cost
    $0
    Owner
    CEO

    Smallest test

    Use the wedge headline in LinkedIn outreach for two weeks.

    Why it works

    Keep "banking back office" in the title, but make the H1 and first screen concrete: "Clear your alert backlog with the analysts you have". Use the 10-versus-20x line, "the analyst decides" and "no rip-and-replace". Then list loans, fraud and complaints as next. Test the two versions on the demo-form rate.

    Buyers act on a specific pain. A wedge headline wins the first deal, and the platform frame keeps room to expand.

    Risks and how to handle them

    • Being boxed in as an AML tool

      Name the other back-office areas directly under the fold.

    Builds on

    Evidence

    • Your websiteHeadline change: in January 2026 the homepage title read "Fenrock | AI Agents for Financial Crime Compliance"; it now reads "Fenrock | AI Agents for Banking Back Office". The domain was registered in December 2025.Source
    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
    • PressStartupHub.ai profile: the agents sit on top of a bank's existing compliance stack, taking alerts from whatever monitoring system it already uses, and handle triage, investigation, SAR drafting and quality assurance while analysts approve decisions; it cites 95–99% false-positive rates in mature AML programmes and argues the moat is regulatory trust, deep integration and analyst feedback: "The real moat is the customer relationships, not the code."Source

This quarter 11

The core plays for the next three months.

  • 07

    Fenrock covers four areas (compliance, fraud investigations, loan operations and customer operations), but fenrock.ai is a single page. Each area has a different buyer (BSA officer, fraud lead, head of lending, operations) and different search terms. Bretton has a dedicated SBA loan review use case, and Hummingbird has a page for each product.

    High impactMedium effort First result in 6 weeks CEO

    First action

    Write the alert-investigation page first, since it has the most proof.

    How to measure it

    Use-case page demo requests

    Now
    –
    Target
    10 a month
    By
    1 quarter

    Steps

    1. 1

      Map buyers

      Role, pain and search terms for each area.

      CEO 1 day

    2. 2

      Write alerts page

      Triage, investigation, SAR draft, QA.

      CEO 3 days

    3. 3

      Write the other three

      Fraud, loans, complaints.

      CEO 2 weeks

    4. 4

      Add screenshots

      Redacted workspace views.

      Founding Engineer (Full stack) 3 days

    5. 5

      Ship static pages

      Prerendered, each with its own title and description.

      Founding Engineer (Full stack) 2 days

    6. 6

      Use in sales

      Send the matching page to each stakeholder.

      CEO ongoing

    First result
    6 weeks
    Cost
    Staff time
    Owner
    CEO

    Smallest test

    Publish the alerts page and send it in the next five outreach emails.

    Why it works

    Publish four pages. Each one covers the workflow before and after Fenrock, what the agent prepares, what the analyst decides, what goes in the audit log, which systems it reads from, and a demo form preset to that use case. Interlink them from the homepage.

    Use-case pages match how each buyer searches and give sales a link to send each stakeholder in a bank deal.

    Risks and how to handle them

    • Pages promise features that are still early

      Mark areas as live or in pilot.

    Builds on

    Evidence

    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
    • Your websiteHomepage (checked November 10, 2026): title "Fenrock | AI Agents for Banking Back Office"; description "The first AI workspace for banking back office. Process 20X volume per analyst with bullet-proof audit logs. Built for banks."; SOC 2 mentioned; the only contact route is a mailto link; no pricing page, blog, case studies, testimonials, careers page or social profile links found from the homepage; no social share image or favicon.Source
    • Competitor researchBretton homepage (greenlite.ai now redirects there): "Your AI compliance team" for banks regulated by the OCC, FDIC and Fed and for fintechs; published results such as an "87% reduction in compliance review time" at an FDIC-insured bank and a "70% reduction in EDD queue completion time" at an OCC-regulated bank; SOC 2 Type II, zero-data retention and independent model validation; a trust center, ROI calculator, changelog, an SBA loan review use case, AI workshops and a quarterly publication.Source
  • 08

    Fenrock's founding-engineer posts describe AI agents for banks and credit unions. The site's description ends "Built for banks." Credit unions face the same BSA/AML work with similarly small teams, and a credit-union compliance lead who reads "built for banks" may assume Fenrock isn't for them.

    Medium impactLow effort First result in 1 quarter CEO

    First action

    Decide whether credit unions are a target now.

    How to measure it

    Credit-union demos

    Now
    –
    Target
    5 a quarter
    By
    2 quarters

    Steps

    1. 1

      Decide scope

      Are credit unions a target now?

      CEO 1 day

    2. 2

      Talk to three

      Interview credit-union compliance leads.

      CEO 2 weeks

    3. 3

      Write the page

      Their language and their exam context.

      CEO 3 days

    4. 4

      Update copy

      Description, headline and demo form option.

      Founding Engineer (Full stack) half a day

    5. 5

      Align job posts

      Same scope everywhere.

      CEO 1 hour

    6. 6

      Track

      Demo requests by institution type.

      CEO monthly

    First result
    1 quarter
    Cost
    $0
    Owner
    CEO

    Smallest test

    Add "and credit unions" to the description and track the institution type on the form.

    Why it works

    If credit unions are in scope, add a credit-union page in their own words (members, not customers; their regulator and examiner context), change "Built for banks" to "Built for banks and credit unions", and add a credit-union option to the demo form. If they aren't in scope yet, align the job posts.

    It roughly doubles the addressable set of small institutions at almost no cost, and credit-union buyers are reached through different associations and events than banks.

    Risks and how to handle them

    • Splitting focus too early

      Treat credit unions as inbound only until the bank motion is repeatable.

    Evidence

    • HiringTwo open roles on Y Combinator's job board: Founding Engineer (Full stack) and Founding Engineer (Backend), San Francisco, $150K–$250K, any experience level, visa sponsorship. The posts describe Fenrock as building AI agents and an AI operating system for banks and credit unions, say customers already use the product, and ask engineers to design and ship AI systems used by financial institutions and own major technical decisions.Source
    • Your websiteHomepage (checked November 10, 2026): title "Fenrock | AI Agents for Banking Back Office"; description "The first AI workspace for banking back office. Process 20X volume per analyst with bullet-proof audit logs. Built for banks."; SOC 2 mentioned; the only contact route is a mailto link; no pricing page, blog, case studies, testimonials, careers page or social profile links found from the homepage; no social share image or favicon.Source
  • 09

    Fenrock's promise is "No rip-and-replace. No data migration." Its agents take alerts from whatever monitoring system a bank already uses. A bank's first question is "does it work with ours?", and the site doesn't answer it.

    Medium impactMedium effort First result in 2 months CTO

    First action

    List the systems connected in production today.

    How to measure it

    Integration-page sessions to demo

    Now
    –
    Target
    8%
    By
    2 quarters

    Steps

    1. 1

      List connections

      Live versus in progress.

      CTO 1 day

    2. 2

      Document each

      Data read, method, setup time.

      Founding Engineer (Backend) 1 week

    3. 3

      Check trademark use

      Follow each vendor's naming guidelines.

      CEO 2 days

    4. 4

      Publish pages

      Static, linked from use-case pages.

      Founding Engineer (Full stack) 3 days

    5. 5

      Add to the form

      A "which system do you run" field.

      Founding Engineer (Full stack) 1 hour

    6. 6

      Expand

      Build the most-requested connections next.

      CTO quarterly

    First result
    2 months
    Cost
    Engineering and writing time
    Owner
    CTO

    Smallest test

    One page for the most common system among current customers.

    Why it works

    For each system Fenrock has actually connected to in production, publish a short page: what data is read, how (export, API, read-only access), setup time, and what stays inside the bank. List systems in progress separately. Only name systems with a working connection, and follow each vendor's trademark rules.

    Integration fear is the main reason small banks delay new tools. Pages that name their own system remove the objection and catch searches like "<system> AI investigation".

    Risks and how to handle them

    • Implying a partnership that doesn't exist

      Say "works with" only where a connection is live, and never "partner" without an agreement.

    Builds on

    Evidence

    • PressStartupHub.ai profile: the agents sit on top of a bank's existing compliance stack, taking alerts from whatever monitoring system it already uses, and handle triage, investigation, SAR drafting and quality assurance while analysts approve decisions; it cites 95–99% false-positive rates in mature AML programmes and argues the moat is regulatory trust, deep integration and analyst feedback: "The real moat is the customer relationships, not the code."Source
    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
  • 10

    Fenrock's claims are "bullet-proof audit logs" and "The analyst reviews. The analyst decides." Coverage calls human-in-the-loop a regulatory necessity. The thing a BSA officer most wants to see, what an examiner would actually see, is nowhere public.

    High impactMedium effort First result in 1 month CTO

    First action

    Write a synthetic alert scenario with no real customer data.

    How to measure it

    Case-file downloads that book a demo

    Now
    –
    Target
    20%
    By
    1 quarter

    Steps

    1. 1

      Write the scenario

      Fully synthetic and realistic.

      CEO 2 days

    2. 2

      Run it

      Through the real product.

      CTO 1 day

    3. 3

      Export the log

      Every step, source and decision, time-stamped.

      Founding Engineer (Backend) 2 days

    4. 4

      Review with a BSA expert

      Check it reads as exam-ready.

      CEO 1 week

    5. 5

      Publish

      Web page plus PDF behind a light form.

      Founding Engineer (Full stack) 2 days

    6. 6

      Use in demos

      Walk through it on every call.

      CEO ongoing

    First result
    1 month
    Cost
    Staff time; an optional advisor fee
    Owner
    CTO

    Smallest test

    Show the sample in the next three demos and ask whether they'd forward it.

    Why it works

    Build one fully synthetic case: an alert, the evidence the agent gathered with sources, its draft narrative, the analyst's edits and decision, QA, and the time-stamped audit log. Publish it as a web page and PDF, gated lightly behind the demo form, and walk through it in every demo.

    Regulated buyers trust what they can inspect. A concrete artifact turns "AI" from a risk into evidence, and compliance officers will forward it to their auditors and examiners, which spreads Fenrock's name.

    Risks and how to handle them

    • The scenario leaks real patterns

      Use invented entities and amounts only.

    • Reads as a compliance claim

      Label it as an illustration, not regulatory advice.

    Evidence

    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
    • PressStartupHub.ai profile: the agents sit on top of a bank's existing compliance stack, taking alerts from whatever monitoring system it already uses, and handle triage, investigation, SAR drafting and quality assurance while analysts approve decisions; it cites 95–99% false-positive rates in mature AML programmes and argues the moat is regulatory trust, deep integration and analyst feedback: "The real moat is the customer relationships, not the code."Source
    • Your websiteHomepage (checked November 10, 2026): title "Fenrock | AI Agents for Banking Back Office"; description "The first AI workspace for banking back office. Process 20X volume per analyst with bullet-proof audit logs. Built for banks."; SOC 2 mentioned; the only contact route is a mailto link; no pricing page, blog, case studies, testimonials, careers page or social profile links found from the homepage; no social share image or favicon.Source
  • 11

    Fenrock's 20-30 hours a week is something early customers expect, not a measured result, and coverage notes the 10-20x figure is a company claim. Banks hesitate to put AI on live cases. Their closed alerts already have analyst decisions, which makes them a ready-made test set.

    High impactMedium effort First result in 6 weeks CTO

    First action

    Define the pilot report: agreement rate, time per case and disagreements reviewed.

    How to measure it

    Shadow pilots that sign

    Now
    –
    Target
    50%
    By
    2 quarters

    Steps

    1. 1

      Define the report

      Agreement, time, disagreements.

      CTO 2 days

    2. 2

      Package the setup

      Read-only, inside the bank's environment.

      Founding Engineer (Backend) 2 weeks

    3. 3

      Write the offer

      Two weeks, fixed scope.

      CEO 1 day

    4. 4

      Run the first pilot

      With an existing champion.

      CTO 2 weeks

    5. 5

      Review gaps together

      Go through disagreements with the bank's analysts.

      CTO 2 days

    6. 6

      Present to leadership

      The bank's own capacity numbers.

      CEO 1 day

    7. 7

      Publish aggregates

      Anonymized results across pilots.

      CEO quarterly

    First result
    6 weeks
    Cost
    About 3 engineer-weeks per pilot at first
    Owner
    CTO

    Smallest test

    Run 100 closed alerts for one existing customer.

    Why it works

    Offer a two-week pilot. Inside the bank's environment, the agents re-work a sample of last quarter's closed alerts. Fenrock reports agreement with the analysts' final decisions, time per case, and the cases where the agent would have escalated differently. The bank's analysts review the gaps, and the result becomes the business case for a live rollout.

    It replaces a vendor claim with the bank's own evidence and gives the champion something to show the CEO and board. Fenrock gets measured numbers for the site.

    Risks and how to handle them

    • Disagreements look like errors

      Frame them as second opinions, and let analysts judge which side was right.

    • Data access delays

      Offer an export-based option.

    Builds on

    Evidence

    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
    • PressStartupHub.ai profile: the agents sit on top of a bank's existing compliance stack, taking alerts from whatever monitoring system it already uses, and handle triage, investigation, SAR drafting and quality assurance while analysts approve decisions; it cites 95–99% false-positive rates in mature AML programmes and argues the moat is regulatory trust, deep integration and analyst feedback: "The real moat is the customer relationships, not the code."Source
  • 12

    Fenrock's job posts say customers already use the product, yet the site has no case studies or testimonials. Bretton publishes results by regulator type ("87% reduction in compliance review time" at an FDIC-insured bank), and Hummingbird shows BSA-leader testimonials.

    High impactMedium effort First result in 2 months CEO

    First action

    Ask the most engaged customer CEO for permission to measure and publish.

    How to measure it

    Case studies live

    Now
    –
    Target
    2
    By
    2 quarters

    Steps

    1. 1

      Pick the customer

      Cleanest data and most willing.

      CEO 1 day

    2. 2

      Agree the measures

      Alerts per analyst, backlog age, hours.

      CTO 2 days

    3. 3

      Measure

      From product logs plus the bank's own baseline.

      Founding Engineer (Backend) 4 weeks

    4. 4

      Interview

      BSA officer and CEO.

      CEO 1 week

    5. 5

      Get approval

      Written sign-off on naming and wording.

      CEO 2 weeks

    6. 6

      Publish

      Page, PDF and homepage proof line.

      Founding Engineer (Full stack) 2 days

    First result
    2 months
    Cost
    Staff time
    Owner
    CEO

    Smallest test

    One approved quote and one measured number on the homepage.

    Why it works

    Pick the customer with the cleanest before-and-after data. Measure alerts cleared per analyst, backlog age and hours a week, before and after. If the bank won't be named, publish it as "a $X billion community bank in the Midwest". Add a quote from the BSA officer or CEO, approved in writing.

    Peers trust peers. One measured story from a bank like theirs outweighs any claim on the homepage.

    Risks and how to handle them

    • The bank declines naming

      Anonymize by asset size and region.

    Builds on

    Evidence

    • HiringTwo open roles on Y Combinator's job board: Founding Engineer (Full stack) and Founding Engineer (Backend), San Francisco, $150K–$250K, any experience level, visa sponsorship. The posts describe Fenrock as building AI agents and an AI operating system for banks and credit unions, say customers already use the product, and ask engineers to design and ship AI systems used by financial institutions and own major technical decisions.Source
    • Your websiteHomepage (checked November 10, 2026): title "Fenrock | AI Agents for Banking Back Office"; description "The first AI workspace for banking back office. Process 20X volume per analyst with bullet-proof audit logs. Built for banks."; SOC 2 mentioned; the only contact route is a mailto link; no pricing page, blog, case studies, testimonials, careers page or social profile links found from the homepage; no social share image or favicon.Source
    • Competitor researchBretton homepage (greenlite.ai now redirects there): "Your AI compliance team" for banks regulated by the OCC, FDIC and Fed and for fintechs; published results such as an "87% reduction in compliance review time" at an FDIC-insured bank and a "70% reduction in EDD queue completion time" at an OCC-regulated bank; SOC 2 Type II, zero-data retention and independent model validation; a trust center, ROI calculator, changelog, an SBA loan review use case, AI workshops and a quarterly publication.Source
  • 13

    Fenrock has no pricing page and no public way to start. Community banks have small budgets and long approval chains, and many small purchases go through without a full procurement cycle. Fenrock's "no rip-and-replace" model suits a small, bounded first step.

    Medium impactLow effort First result in 1 quarter CEO

    First action

    Ask existing customers what spend level needs board approval at their bank.

    How to measure it

    Sales cycle to first contract

    Now
    –
    Target
    Under 45 days
    By
    2 quarters

    Steps

    1. 1

      Learn thresholds

      Approval limits at current customers.

      CEO 1 week

    2. 2

      Define scope

      One workflow, one team, 90 days.

      CEO 1 day

    3. 3

      Set the price

      Fixed and under the threshold.

      CEO 1 day

    4. 4

      Write the order form

      Two pages, with conversion terms.

      CEO 2 days

    5. 5

      Publish the offer

      A line on the site and in emails.

      Founding Engineer (Full stack) 1 hour

    6. 6

      Track conversion

      Pilot to annual contract.

      CEO quarterly

    First result
    1 quarter
    Cost
    $0
    Owner
    CEO

    Smallest test

    Offer the package to the next three prospects.

    Why it works

    Package a 90-day engagement: one workflow (for example, alert triage), one team, a capacity report at day 30 and day 90, and a fixed fee sized to fit under a typical community-bank approval threshold, which you confirm with the first customers. Publish "Pilots start at $X" or simply "fixed-price 90-day start" on the site.

    A known price and scope removes the biggest unknown for a small bank and shortens the path to the first invoice. The 90-day report sets up the expansion.

    Risks and how to handle them

    • Anchoring the price too low

      Price the pilot as a credit toward the annual contract.

    Builds on

    Evidence

    • Your websiteHomepage (checked November 10, 2026): title "Fenrock | AI Agents for Banking Back Office"; description "The first AI workspace for banking back office. Process 20X volume per analyst with bullet-proof audit logs. Built for banks."; SOC 2 mentioned; the only contact route is a mailto link; no pricing page, blog, case studies, testimonials, careers page or social profile links found from the homepage; no social share image or favicon.Source
    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
  • 14

    Fenrock was "Built alongside U.S. bank CEOs" and sells to them directly. Community-bank CEOs know each other through associations and peer groups. Coverage says the real moat is "the customer relationships, not the code".

    High impactLow effort First result in 1 month CEO

    First action

    List each customer CEO and the peer groups they belong to.

    How to measure it

    Referral meetings

    Now
    –
    Target
    2 a month
    By
    1 quarter

    Steps

    1. 1

      Map networks

      Peer groups and associations of each customer CEO.

      CEO 1 day

    2. 2

      Time the ask

      Right after the first measured result.

      CEO ongoing

    3. 3

      Write the intro

      A short email the CEO can forward.

      CEO 1 hour

    4. 4

      Offer the peer call

      CEO to CEO, 20 minutes.

      CEO ongoing

    5. 5

      Thank referrers

      Extra workflow or roadmap priority.

      CEO ongoing

    6. 6

      Track

      Referral source on every deal.

      CEO monthly

    First result
    1 month
    Cost
    $0
    Owner
    CEO

    Smallest test

    Ask the happiest customer CEO for one introduction this month.

    Why it works

    After each 30-day milestone, ask the CEO for two introductions to peers with the same backlog problem. Offer the peer a 20-minute call with the referring CEO, not a sales pitch. Thank referrers with a free extra workflow or priority on the roadmap, not cash.

    In a trust-driven, regulated market, a peer's word beats any marketing, and CEO referrals skip the gatekeepers.

    Risks and how to handle them

    • Asking too early

      Ask only after a measured win.

    Builds on

    Evidence

    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
    • PressStartupHub.ai profile: the agents sit on top of a bank's existing compliance stack, taking alerts from whatever monitoring system it already uses, and handle triage, investigation, SAR drafting and quality assurance while analysts approve decisions; it cites 95–99% false-positive rates in mature AML programmes and argues the moat is regulatory trust, deep integration and analyst feedback: "The real moat is the customer relationships, not the code."Source
    • Y Combinator"AI agents for banks"; "We're building the Legora for traditional financial services", working closely with US bank CEOs; founded 2026, Winter 2026 batch, team of 2, San Francisco. The CEO previously founded two VC-backed companies, one a healthcare API company that reached over 6 million patients and 100+ employees; the CTO spent about ten years on machine learning at Google and Apple. The profile links LinkedIn and X accounts.Source
  • 15

    Fenrock has LinkedIn and X accounts listed on Y Combinator but none linked from its site, and it has no blog. The founders have a strong story: "99% of U.S. banks are not JPMorgan", 10 alerts a day per analyst, 95-99% false positives. The CEO has scaled two VC-backed companies before.

    Medium impactLow effort First result in 2 months CEO

    First action

    Write the first four posts from the podcast talking points.

    How to measure it

    LinkedIn-sourced demos

    Now
    –
    Target
    3 a month
    By
    2 quarters

    Steps

    1. 1

      Pick themes

      Eight topics from sales calls.

      CEO 1 hour

    2. 2

      Batch posts

      A month at a time.

      CEO half a day monthly

    3. 3

      Post weekly

      Same day each week.

      CEO weekly

    4. 4

      Engage

      Reply to every banker comment.

      CEO 20 minutes a day

    5. 5

      Link assets

      Calculator and case file.

      CEO ongoing

    6. 6

      Review

      Which topics bring demos.

      CEO monthly

    First result
    2 months
    Cost
    $0
    Owner
    CEO

    Smallest test

    Four posts in four weeks; count banker comments and DMs.

    Why it works

    Post once a week from the CEO's profile, with the company page resharing: one number, one back-office story (anonymized), one lesson. Topics include false-positive load, the true cost of a SAR, the examiner's view of AI and what "human in the loop" means in practice. End each post with the backlog calculator or the sample case file.

    Bank executives and BSA officers are active on LinkedIn, and consistent founder posts build the trust that a two-person company otherwise lacks.

    Risks and how to handle them

    • Founder time

      Batch monthly and reuse sales-call stories.

    Builds on

    Evidence

    • Y Combinator"AI agents for banks"; "We're building the Legora for traditional financial services", working closely with US bank CEOs; founded 2026, Winter 2026 batch, team of 2, San Francisco. The CEO previously founded two VC-backed companies, one a healthcare API company that reached over 6 million patients and 100+ employees; the CTO spent about ten years on machine learning at Google and Apple. The profile links LinkedIn and X accounts.Source
    • Your websiteHomepage (checked November 10, 2026): title "Fenrock | AI Agents for Banking Back Office"; description "The first AI workspace for banking back office. Process 20X volume per analyst with bullet-proof audit logs. Built for banks."; SOC 2 mentioned; the only contact route is a mailto link; no pricing page, blog, case studies, testimonials, careers page or social profile links found from the homepage; no social share image or favicon.Source
    • PressStartupHub.ai profile: the agents sit on top of a bank's existing compliance stack, taking alerts from whatever monitoring system it already uses, and handle triage, investigation, SAR drafting and quality assurance while analysts approve decisions; it cites 95–99% false-positive rates in mature AML programmes and argues the moat is regulatory trust, deep integration and analyst feedback: "The real moat is the customer relationships, not the code."Source
  • 16

    Fenrock sells to bank CEOs, and its product already offers reporting for examiners and boards. Coverage says the defensible asset is analyst feedback and deep integration. Showing the CEO the value every month protects renewal and turns the feedback into a visible quality measure.

    High impactMedium effort First result in 1 month CTO

    First action

    Draft the report by hand for one customer.

    How to measure it

    Customers renewing

    Now
    –
    Target
    100% of first cohort
    By
    12 months

    Steps

    1. 1

      Pick metrics

      Five numbers a CEO cares about.

      CEO 1 day

    2. 2

      Draft by hand

      One customer, one month.

      CTO 2 days

    3. 3

      Get feedback

      From that customer's CEO.

      CEO 1 week

    4. 4

      Automate

      Generated from audit logs.

      Founding Engineer (Backend) 2 weeks

    5. 5

      Deliver monthly

      To the CEO and BSA officer.

      CEO monthly

    6. 6

      Quarterly review

      15 minutes, including expansion options.

      CEO quarterly

    First result
    1 month
    Cost
    About 2 engineer-weeks
    Owner
    CTO

    Smallest test

    Send one hand-made report this month.

    Why it works

    Automate a one-page monthly report from product logs: alerts and cases processed, median time per case, backlog age, estimated hours freed, the analyst override rate and what changed because of it. Deliver it to the CEO and BSA officer, with a 15-minute review each quarter.

    Visible value prevents churn when budgets are reviewed, gives the champion material for the board, and produces numbers for case studies and referrals.

    Risks and how to handle them

    • Estimated hours are disputed

      Show the method, using the bank's own baseline.

    Evidence

    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
    • PressStartupHub.ai profile: the agents sit on top of a bank's existing compliance stack, taking alerts from whatever monitoring system it already uses, and handle triage, investigation, SAR drafting and quality assurance while analysts approve decisions; it cites 95–99% false-positive rates in mature AML programmes and argues the moat is regulatory trust, deep integration and analyst feedback: "The real moat is the customer relationships, not the code."Source
  • 17

    Community banks with "a handful" of analysts lean on outside BSA auditors and consultants, who see the backlog problem first and are asked "what tool should we use?". Fenrock is a new vendor, so a trusted adviser's recommendation can stand in for the track record it doesn't have yet.

    Medium impactMedium effort First result in 1 quarter CEO

    First action

    Ask current customers which outside BSA firm they use.

    How to measure it

    Adviser referrals

    Now
    –
    Target
    3 a quarter
    By
    2 quarters

    Steps

    1. 1

      List advisers

      From customers and prospects.

      CEO 1 week

    2. 2

      Walk them through

      Sample case file and audit log.

      CTO 2 weeks

    3. 3

      Agree terms

      Referral or co-delivery.

      CEO 2 weeks

    4. 4

      Co-write a one-pager

      On governing AI in investigations.

      CEO 2 weeks

    5. 5

      Run a webinar

      For the partner's bank clients.

      CEO 1 day

    6. 6

      Track

      Meetings and deals by partner.

      CEO quarterly

    First result
    1 quarter
    Cost
    Referral fees on closed deals
    Owner
    CEO

    Smallest test

    One walkthrough with one firm a customer already uses.

    Why it works

    Pick five regional BSA audit or consulting firms. Give them a walkthrough of the sample case file and audit log, and a referral or co-delivery arrangement: they help with validation and governance at the bank, and Fenrock handles the software. Write a joint one-pager on governing AI in investigations.

    Advisers lower the perceived risk of a new AI vendor and bring warm introductions. Their review of the audit trail also makes the product better.

    Risks and how to handle them

    • Auditor independence conflicts

      Use advisory arms, not a bank's own auditor of record, for referrals.

    Builds on

    Evidence

    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
    • PressStartupHub.ai profile: the agents sit on top of a bank's existing compliance stack, taking alerts from whatever monitoring system it already uses, and handle triage, investigation, SAR drafting and quality assurance while analysts approve decisions; it cites 95–99% false-positive rates in mature AML programmes and argues the moat is regulatory trust, deep integration and analyst feedback: "The real moat is the customer relationships, not the code."Source

Big bets 3

Larger plays that can change the trajectory.

  • 18

    Fenrock's whole pitch rests on capacity numbers: about 10 alerts a day per analyst, 95-99% false positives, "The work keeps growing. Headcount doesn't." No one publishes these benchmarks for smaller institutions. As Fenrock processes more cases, it can measure them.

    High impactHigh effort First result in 2 quarters CEO

    First action

    Define the metrics and the minimum sample for anonymity.

    How to measure it

    Benchmark-sourced demos

    Now
    –
    Target
    25
    By
    90 days after launch

    Steps

    1. 1

      Define metrics

      And the anonymity thresholds.

      CTO 1 week

    2. 2

      Get consent

      Contract terms allowing aggregate use.

      CEO 1 quarter

    3. 3

      Survey

      BSA officers at non-customer banks too.

      CEO 6 weeks

    4. 4

      Analyze

      By asset-size band.

      Founding Engineer (Backend) 3 weeks

    5. 5

      Write and design

      Report plus a page for each finding.

      CEO 3 weeks

    6. 6

      Launch

      Webinar, trade press, LinkedIn.

      CEO 2 weeks

    7. 7

      Personalize

      A comparison for each participant.

      Founding Engineer (Full stack) 2 weeks

    First result
    2 quarters
    Cost
    Staff time plus $2-5k for design and survey incentives
    Owner
    CEO

    Smallest test

    Publish one finding from the survey alone.

    Why it works

    Once there are enough customers, publish a yearly report: alerts per analyst, time per case, backlog age and false-positive share by asset-size band, combining anonymized platform data with a survey of BSA officers. Release it with a webinar and give each participating bank its own comparison.

    Original data earns press, links and citations from AI assistants, and makes Fenrock the reference point on back-office capacity for its segment.

    Risks and how to handle them

    • Sample too small

      Start with survey data and add platform data as it grows.

    Builds on

    Evidence

    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
    • PressStartupHub.ai profile: the agents sit on top of a bank's existing compliance stack, taking alerts from whatever monitoring system it already uses, and handle triage, investigation, SAR drafting and quality assurance while analysts approve decisions; it cites 95–99% false-positive rates in mature AML programmes and argues the moat is regulatory trust, deep integration and analyst feedback: "The real moat is the customer relationships, not the code."Source
  • 19

    Fenrock lists loan operations next to compliance, and the message moved from "Financial Crime Compliance" to "Banking Back Office". Bretton already markets SBA loan review. For a community bank, loan throughput is revenue, so selling capacity there speaks to growth rather than only to cost and risk.

    High impactHigh effort First result in 2 quarters CTO

    First action

    Ask current customers which loan task has the longest queue.

    How to measure it

    Multi-workflow customers

    Now
    –
    Target
    50% of customers
    By
    12 months

    Steps

    1. 1

      Pick the workflow

      The longest queue at current customers.

      CEO 2 weeks

    2. 2

      Map documents

      What the agent gathers and checks.

      CTO 2 weeks

    3. 3

      Build

      On the same audit-logged workspace.

      Founding Engineer (Backend) 6 weeks

    4. 4

      Pilot

      With one or two customers.

      CTO 6 weeks

    5. 5

      Measure

      Turnaround time before and after.

      Founding Engineer (Backend) ongoing

    6. 6

      Launch

      Page, case study and price.

      CEO 2 weeks

    First result
    2 quarters
    Cost
    One engineer for about a quarter
    Owner
    CTO

    Smallest test

    Shadow one loan file-review queue for two weeks.

    Why it works

    Pick one loan workflow where document gathering dominates (for example, small-business loan file review or covenant monitoring). Run it with one or two existing customers, measure turnaround time, then launch it as a named product with its own page, case study and price line.

    Expanding inside existing banks is cheaper than winning new logos, and a revenue-side use case raises the deal value and brings in the head of lending as a second champion.

    Risks and how to handle them

    • Diluting focus before compliance is proven

      Start only after two compliance customers are referenceable.

    • Credit decisions carry fair-lending scrutiny

      Keep agents to document work and leave credit decisions to people.

    Builds on

    Evidence

    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
    • Your websiteHeadline change: in January 2026 the homepage title read "Fenrock | AI Agents for Financial Crime Compliance"; it now reads "Fenrock | AI Agents for Banking Back Office". The domain was registered in December 2025.Source
    • Competitor researchBretton homepage (greenlite.ai now redirects there): "Your AI compliance team" for banks regulated by the OCC, FDIC and Fed and for fintechs; published results such as an "87% reduction in compliance review time" at an FDIC-insured bank and a "70% reduction in EDD queue completion time" at an OCC-regulated bank; SOC 2 Type II, zero-data retention and independent model validation; a trust center, ROI calculator, changelog, an SBA loan review use case, AI workshops and a quarterly publication.Source
  • 20

    Fenrock's agents sit on top of whatever monitoring system a bank already uses, and coverage names deep integration as part of the moat. It also warns that incumbent monitoring vendors could add their own agent features. Being listed in the ecosystems of the core banking and monitoring systems community banks run would turn a threat into a channel.

    High impactHigh effort First result in 3 quarters CTO

    First action

    Count which core and monitoring systems appear across customers and the pipeline.

    How to measure it

    Deals from partner marketplaces

    Now
    –
    Target
    20% of pipeline
    By
    12 months

    Steps

    1. 1

      Count systems

      Across customers and pipeline.

      CEO 1 week

    2. 2

      Research programs

      Partner terms, fees, certification.

      CEO 2 weeks

    3. 3

      Build connectors

      To each program's standards.

      Founding Engineer (Backend) 1 quarter

    4. 4

      Certify

      Pass each partner's review.

      CTO 1 quarter

    5. 5

      Co-market

      Webinar and listing for their banks.

      CEO ongoing

    6. 6

      Measure

      Pipeline by partner.

      CEO quarterly

    First result
    3 quarters
    Cost
    Partner fees plus about a quarter of engineering
    Owner
    CTO

    Smallest test

    One partner application and one connector for an existing customer.

    Why it works

    Pick the two systems most common among customers and prospects. Apply to their partner or marketplace programs, build certified connectors, and co-market to their community-bank base. Keep the "no rip-and-replace" promise central.

    Small banks buy add-ons through the vendors they already trust. A listing shortens security review and puts Fenrock in front of thousands of institutions at once.

    Risks and how to handle them

    • The partner builds a competing feature

      Own the analyst workflow and audit layer, and integrate with several partners.

    Builds on

    Evidence

    • PressStartupHub.ai profile: the agents sit on top of a bank's existing compliance stack, taking alerts from whatever monitoring system it already uses, and handle triage, investigation, SAR drafting and quality assurance while analysts approve decisions; it cites 95–99% false-positive rates in mature AML programmes and argues the moat is regulatory trust, deep integration and analyst feedback: "The real moat is the customer relationships, not the code."Source
    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source

Wildcards 2

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

  • 21

    Y Combinator lists Fenrock's team size as 2, and the domain dates from December 2025. A bank's vendor-risk team will ask about vendor viability and continuity. The founders' records are a real answer: a CEO who scaled a company to 6 million patients and 100+ employees, and a CTO with about ten years of ML at Google and Apple. Founding engineers are being hired now. None of this is on fenrock.ai.

    Medium impactLow effort First result in 1 month CEO

    First action

    Write the continuity commitments Fenrock can actually offer today.

    How to measure it

    Viability objections

    Now
    –
    Target
    Zero lost deals
    By
    2 quarters

    Steps

    1. 1

      List commitments

      Export, exit plan, escrow option.

      CEO 1 day

    2. 2

      Write bios

      Track records, not adjectives.

      CEO 2 hours

    3. 3

      Add backing

      Y Combinator and any advisers.

      CEO 1 hour

    4. 4

      Show the team plan

      Link the open roles.

      CEO 1 hour

    5. 5

      Publish

      /about, linked from /trust.

      Founding Engineer (Full stack) half a day

    6. 6

      Use in sales

      Attach to every security review.

      CEO ongoing

    First result
    1 month
    Cost
    $0; escrow fees if a bank asks for it
    Owner
    CEO

    Smallest test

    Send the continuity section to the next prospect in procurement.

    Why it works

    Add an About page covering the founders' track records, Y Combinator backing, the hiring plan, and a continuity section: data export on request, a documented exit plan, an option for source-code escrow, and support commitments. Link it from the trust page and the demo confirmation email.

    Naming the obvious objection early builds credibility with risk-averse buyers and keeps it from silently killing deals in procurement.

    Risks and how to handle them

    • Drawing attention to team size

      Lead with track record and commitments, not headcount.

    Builds on

    Evidence

    • Y Combinator"AI agents for banks"; "We're building the Legora for traditional financial services", working closely with US bank CEOs; founded 2026, Winter 2026 batch, team of 2, San Francisco. The CEO previously founded two VC-backed companies, one a healthcare API company that reached over 6 million patients and 100+ employees; the CTO spent about ten years on machine learning at Google and Apple. The profile links LinkedIn and X accounts.Source
    • HiringTwo open roles on Y Combinator's job board: Founding Engineer (Full stack) and Founding Engineer (Backend), San Francisco, $150K–$250K, any experience level, visa sponsorship. The posts describe Fenrock as building AI agents and an AI operating system for banks and credit unions, say customers already use the product, and ask engineers to design and ship AI systems used by financial institutions and own major technical decisions.Source
    • Your websiteHeadline change: in January 2026 the homepage title read "Fenrock | AI Agents for Financial Crime Compliance"; it now reads "Fenrock | AI Agents for Banking Back Office". The domain was registered in December 2025.Source
  • 22

    Fenrock was built alongside bank CEOs, and the CEO is the buyer. Bretton runs a quarterly publication and a CEO essay. Fenrock has no blog or newsletter. Community-bank CEOs get far less vendor attention than large-bank executives, and they read peer-level analysis.

    Medium impactMedium effort First result in 1 quarter CEO

    First action

    Write issue one from the podcast themes and send it to 50 contacts.

    How to measure it

    Letter-to-demo conversion

    Now
    –
    Target
    5% a year
    By
    4 issues

    Steps

    1. 1

      Set the format

      Four sections, one page.

      CEO 1 hour

    2. 2

      Build the list

      Demo requests, events, LinkedIn.

      CEO ongoing

    3. 3

      Write issue one

      From current sales themes.

      CEO 1 day

    4. 4

      Publish and send

      A static page plus email.

      Founding Engineer (Full stack) half a day

    5. 5

      Print for customers

      Mailed to customer CEOs.

      CEO quarterly

    6. 6

      Read replies

      Log questions as content and leads.

      CEO quarterly

    First result
    1 quarter
    Cost
    Email tool plus printing, under $100 a quarter
    Owner
    CEO

    Smallest test

    Send one issue to 50 bank leaders and count the replies.

    Why it works

    Each quarter, send a short letter (web page plus email, with a printed copy for customers): one regulatory or industry change and what it means for a small back office, one anonymized peer story, one number from Fenrock's data, and one question for readers. Build the list from demo requests, events and LinkedIn.

    A steady, useful touchpoint keeps Fenrock top of mind through long bank buying cycles, and the replies become research and leads.

    Risks and how to handle them

    • Founder time

      Keep it to one page.

    • Sounds like regulatory advice

      Frame it as perspective and link to the primary sources.

    Builds on

    Evidence

    • Competitor researchBretton homepage (greenlite.ai now redirects there): "Your AI compliance team" for banks regulated by the OCC, FDIC and Fed and for fintechs; published results such as an "87% reduction in compliance review time" at an FDIC-insured bank and a "70% reduction in EDD queue completion time" at an OCC-regulated bank; SOC 2 Type II, zero-data retention and independent model validation; a trust center, ROI calculator, changelog, an SBA loan review use case, AI workshops and a quarterly publication.Source
    • PressFondo founder interview: "Fenrock is building the first AI workspace for the banking back office", "Built alongside U.S. bank CEOs", covering loan operations, compliance, fraud investigations and customer operations; "No rip-and-replace. No data migration."; "The analyst reviews. The analyst decides."; "An analyst clears about 10 alerts a day. Fenrock is built for 20x that."; early customers expect to save 20–30 hours a week per employee; "The work keeps growing. Headcount doesn't."; reporting for examiners and boards.Source
    • Your websiteHomepage (checked November 10, 2026): title "Fenrock | AI Agents for Banking Back Office"; description "The first AI workspace for banking back office. Process 20X volume per analyst with bullet-proof audit logs. Built for banks."; SOC 2 mentioned; the only contact route is a mailto link; no pricing page, blog, case studies, testimonials, careers page or social profile links found from the homepage; no social share image or favicon.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.

ProgrammableInfo

Turn the research into a list you can act on

These ideas start with finding the right companies. Info finds them and the right person at each, researches every one and drafts the outreach, then asks before it sends.

  • Build this list in Info for idea #13 (opens programmable.info in a new tab)

New accounts: 100,000 free credits with code BETA100K

Find the companies (opens programmable.info 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.

  • Revise Robotics growth strategyBuilds AI-enabled robotic systems that refurbish used laptops end to end: a robot arm takes in each machine, tests it, wipes the drive…22 growth ideas
  • OTR Solutions growth strategyA freight fintech: recourse and non-recourse factoring with instant funding, the OTR Fuel Card and fuel credit, OTR Clutch business…22 growth ideas
  • Harvey growth strategyAn AI platform for legal and professional services: agents, Vault, Knowledge research, Spaces, Contract Intelligence, Command Center and…22 growth ideas
  • Lily-Lark growth strategyHandcrafted bamboo sun parasols with UPF 50+ canopies printed with original contemporary art, in two lines (Lark from $93 and Signature…23 growth ideas
  • Human Interest growth strategyHi is a paid, verified membership app that brings people into host-run, interest-based communities in New York, with daily content in the…21 growth ideas
  • Mural growth strategyAn AI-powered visual workspace for team collaboration: an infinite canvas, facilitation features, 465+ templates, Mural AI, integrations…21 growth ideas
  • Collectively growth strategyAn award-winning influencer and creator marketing agency: strategy, creative, creator casting, production, affiliate and paid creator…22 growth ideas
  • Hire Hangar growth strategyAI-assisted recruiting that places vetted remote operators (sales, marketing, engineering, finance, support and admin) from Latin America…23 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 10, 2026, and cites them throughout. Fenrock did not commission, review or endorse it, and Programmable is not affiliated with Fenrock. 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 Fenrock runs its business.

Something wrong, or do you represent Fenrock? 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 307 ideas

    Make the site readable by assistants and previews, add a real demo route, a trust page and a capacity calculator, sharpen the headline around the alert backlog, and answer the small-vendor question.

  2. Days 31 to 609 ideas

    Use-case and credit-union pages, works-with pages, the sample case file, shadow-mode pilots, the first measured case study, a fixed-scope pilot offer, CEO referrals and founder-led LinkedIn.

  3. Days 61 to 906 ideas

    Monthly capacity reports for customers, partners in the BSA advisory world, then the big bets: the capacity benchmark, loan operations and integration partnerships, plus a quarterly letter to bank CEOs.

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 analysts get capacity without the bank adding headcount. The most cited problem: alert and case backlogs that grow faster than staff.

  • No rip-and-replace and no data migration
  • The same regulatory burden as the largest banks, with a handful of analysts
  • In their words: “back office”

Market

Competitive landscape

3 competitors compared: Hummingbird, Bretton (formerly Greenlite) and Incumbent monitoring vendors (NICE Actimize, Oracle FCCM, SAS).

  • Gap to exploit: Back-office capacity for community banks and credit unions, beyond AML alone
  • Hummingbird: A broad platform, not built specifically for community-bank back-office capacity
  • Bretton (formerly Greenlite): Mixes fintech and enterprise buyers with banks

Hiring signals

Fenrock is a team of two hiring its first two engineers: a Founding Engineer (Full stack) and a Founding Engineer (Backend) in San Francisco, at $150K-$250K, open to new grads, with visa sponsorship.

  • Founding Engineer (Full stack): Ships the product and site with the founders. Ideas 1, 2, 3, 5, 7.
  • Founding Engineer (Backend): AI systems for financial institutions, with customers live. Ideas 11, 16, 19, 20.

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