Lenz is a fact-checking API — an independent verification layer that checks AI-generated content before it reaches users or downstream systems. Multiple models, five stages, full reasoning trace with every verdict. We’re a small team with a live product, and more signups than we currently follow up with.

This is our first dedicated customer-facing hire and a founding member of the team. You own the relationship end to end, from the first email we send someone to their team running Lenz in production. Every one-on-one conversation a customer has with Lenz is with you — email, calls, LinkedIn, wherever they turn up. Our lifecycle emails go out under your name, so the replies come to you.

What you’ll do

Close the gap between signup and first API call. Many people who sign up never make an API call. Find out why, one account at a time. Most won’t answer the first message, or the third — going back again is the job. Fix what you can with a walkthrough or a working example, and write up the rest for engineering.
Get people on the phone. Email tells you what someone will type; a call tells you what they’re building. New signups, to get them through a first integration; live customers, to hear where they’re taking it next and what would get Lenz into more of their workflows.
Send the outbound. The engine is built and running: it drafts a specific hook for each prospect — usually a real Lenz verification on their own AI output. You review every one, send it from your own address, and handle the replies.
Feed what you learn back into the product. What you hear sets priorities.
Write the playbook. The product side of onboarding is built and instrumented. What doesn’t exist yet is the human side of it — who to reach out to and when, how a first call goes, what happens when an account stalls. What works becomes how Lenz does customer success, and you hire and lead the people who run it next.

We start by measuring this role on the share of signups that make a first API call.

What we’re looking for

You know how to get a response. You’ve worked in sales, customer success, account management, or another customer-facing role where your job depended on moving people to a next step — not just answering when they came to you.
You’re technical enough to be useful without an engineer in the room: demo the product, understand what someone is building, and get them through a first integration. Past that, you hand off to engineering.
You write well. Short, specific, no filler — most of this job is written.
You’ll call someone unprompted, business or technical, about a product they’ve barely used, and go back after they ignore you.
You want to build a function, not join one. Every account is yours, and you work alongside the founders.

Some of our customers are engineers wiring Lenz into a pipeline; others are research, OSINT, and comms teams who need verified output and don’t write code. You’ll need two different approaches, and the judgment to know which one you’re in.