Closed beta · request access
Read. Enriched. Tiered.
Before your next move.
Forward a lead. Blake reads the thread, researches the company, and ranks it against your ICP. Four tiers, and a reason for each.
The problem
Your reps stopped using the CRM.
You know the one.
It was beautiful. Drag-and-drop deal cards, a colour-coded Kanban, seven fields on every opportunity. Nobody filled them in. Three months later your pipeline was half-real, half-fiction, and the leadership meeting stopped asking for numbers.
Blake starts the other way around. The record fills itself when your rep forwards the email. The fields that matter are there before they decide whether to work the lead. There is no admin because the admin is never asked of a human.
We don't think your reps are lazy. We think they were being asked to do data entry instead of sales.
How it works
Three steps. None of them are “import your CSV”.
Forward the email
Every workspace gets an address like yourco@crm.blakecloses.com. Forward a prospect thread and Blake opens the record. No import, no form, no drag.
Claude reads and researches
Claude reads the thread, pulls the company off the web (industry, size, stack, funding, notable context) and writes the context to the record. The research tab you used to keep open is done for you.
Tiered against your ICP
You describe your ideal customer once. Blake scores every new opportunity against it and drops it into Cadillac, Steak knives, Coffee, or Cold. With the reasoning written out.
Scoring you can argue with
Every opportunity gets a tier and a reason.
Blake scores each new opportunity against your written ICP and tells you why it landed where it did. Disagree? Rewrite the ICP and rerun. No black box, no 0-100 number nobody trusts, no confidence score you have to translate to a human.
Re-scored automatically when the ICP changes or new enrichment comes back.
What you get
Small surface, serious depth.
Pipeline that explains itself
Thirteen stages, probability-weighted forecast, owner filter, TCV computed from deal type and contract length. Nothing to configure on day one.
Compose email per opportunity
Rated opportunities get an AI-drafted reply. TO and CC populate from the deal, BCC routes the response back to the same record. Recompose if it isn't right. Your mail client sends, we don't.
Revenue, matched to companies
Connect Moneybird and Blake mirrors every invoice hourly, auto-matched to existing companies by email domain and name. PDFs viewable inline on any phone. One-click Add to Blake for the rest.
Forms that feed the same pipeline
Embeddable forms with Turnstile, extraction and scoring on submit, Slack and Teams webhooks.
Per-department ICP
Sales and Partnerships can chase the same company in parallel, each scored against their own ICP, on the same shared record.
Activity feed, attributed
Every change logged. Automated work attributed to Blake. Human work attributed to the person. Glengarry references kept to a whisper.
Approval queue for workspaces
Platform owners review each new workspace while we warm up. No random sign-up fills the database with test rows.
EU-hosted, tenant-isolated
Supabase in Frankfurt. Row-level security enforces workspace isolation on every query, with integration tests asserting zero leakage.
A note from the founder
I spent years telling salesmen what closing meant. Short version: read the lead, pick the Cadillacs, put the coffee down for everyone else.
Blake is what happens when you stop yelling and build the thing instead. A workspace you feed leads into and that tells you which ones to open today. Every tier comes with a reason. Every rep gets the same briefing I used to give from a briefcase.
It's in closed beta because I want to be sure it works before I charge for it. If that might be you, ask for a workspace.
Blake · Founder & CEO, blakecloses
Always be closing.
Ask for a workspace. If we think Blake will make your sales motion faster, we'll spin it up and send you the link.
FAQ
Questions we get, answered.
- How does Blake actually ingest leads?
- Three ways. Forward an email to your workspace address (blake@yourco.crm.blakecloses.com). Submit an embeddable form you can drop into a landing page. Or create an opportunity manually. All three paths run through the same extraction, enrichment, and scoring pipeline.
- What does Blake's scoring look at?
- Three inputs: your written ICP for the workspace (or department), the thread contents, and web research on the company (industry, size, stack, funding, notable context). Claude reads all three, picks a tier, and writes out the reasoning. You see the reasoning, not a 0-100 black box.
- Can I change the tiers?
- No. The four tiers are Cadillac, Steak knives, Coffee, and Cold. They're the opinion Blake holds about your pipeline. You rewrite the ICP when the scoring doesn't match your reality, not the tier names.
- Is Blake EU-hosted?
- Yes. Supabase Postgres in Frankfurt (eu-central-1). Every query is row-level-secured on workspace_id, and integration tests seed two workspaces and assert zero leakage on every endpoint.
- How is this different from HubSpot, Pipedrive, or Attio?
- Those tools ask you to do the data entry. Blake does the data entry. They offer you configurability; Blake offers you an opinion. There's a longer side-by-side on the vs HubSpot page.
- Do I need to migrate my existing CRM?
- No. Most Blake users run it alongside their existing CRM for a quarter before deciding. Forward leads to Blake, keep your current CRM for reporting, and compare the pipeline velocity at the end of the quarter.
- Does Blake send outbound email?
- Reply suggestions, yes. Rated opportunities get a Compose email button that drafts a reply your mail client sends from your address, with a tracking BCC that loops the response back to the same opportunity. Full outbound sequences and an in-app dialer are deliberately out of scope.
- How do I get access?
- Blake is in closed beta and we're approving workspaces manually while we warm up. Use the request form. We reply within a day, usually the same afternoon.