Founding Marketer

About this role

INTRODUCING KEPLER

THE PROBLEM

High-stakes industries are falling behind on AI adoption. Their workflows can’t afford wrong answers. And AI can’t be trusted to give right ones because of hallucinations. The barrier isn’t that the models aren’t smart enough. It’s that no one can verify what they produce. The fix isn’t a better model, it’s a trust layer: every output traceable, every calculation auditable, every answer reproducible.

WHAT KEPLER IS

Kepler is the agent harness - the infrastructure layer that wraps around AI models to make their outputs reliable, traceable, and verifiable. The model is a replaceable component. The harness is the product.

In Kepler's architecture, the LLM orchestrates - it decides what data to gather, what to compute, how to structure the output. But every actual data point, every extracted value, every calculation flows through deterministic code pipelines. The LLM never touches the data itself. Every value carries provenance metadata back to its exact source. Every computation is auditable and reproducible. Verification loops cross-check outputs before users ever see them.

We started in finance because the stakes are highest and the tolerance for error is zero. We’ve built a finance research product that lets analysts supercharge their workflow: pulling comparables, building models and researching filings. No more double-checking every number AI spits out. Every number tracing back to the source, every time.

But the architecture - provenance, deterministic computation, verification - applies anywhere trust in AI output matters: chemicals, legal, healthcare. Models are commoditizing fast. The trust layer is what's missing and the market is massive.

THE TEAM

The founding team spent a combined 40+ years at Palantir building the type of large-scale data infrastructure that Kepler requires. Our founding engineers led Foundry's core systems - Ontology, Fusion, Workshop, FoundryML, created Palantir's first AI platform and scaled data products at Meta to 1B+ users.

We’ve paired this deep technical foundation with a repeat founder profile. Our CEO built and scaled a data company to $15M ARR before successfully selling it. He then became Citadel's first Head of Business Engineering, experiencing first hand the problems we are now solving. We have a team who’ve been on both sides: building systems like this at massive scale and selling it into the buyers who need it most.

We’re backed by investors who built the modern AI and data stacks, plus the builders of iconic commercial businesses. This includes founders of OpenAI, Meta AI Research, MotherDuck, dbt Labs and Square as well as PebbleBed, Company Ventures and Mantis VC firms.

THE ROLE

WHAT YOU'LL OWN

You'll own how Kepler shows up in the world: the website, the brand, the materials that go in front of customers and investors, and the writing that carries our CEO's and our engineers' thinking to the people we want to reach. All of it exists today, and all of it competes for attention with everything else the team is doing. It needs one person whose actual job is to make it good.

This is a senior individual contributor role. You'll write, design, ship, and then look at whether it worked. The raw material is here: the team can explain what we do and why it matters. What we're missing is the person who turns that into work that looks and reads like it came from a company you'd trust with a serious decision, and who holds that standard across everything we put out. We want the person whose own taste sets the standard, because right now they are the standard.

Some of this you'll do alongside other members of the team, but all of it is yours to elevate and make stronger.

- Brand and visual system. How Kepler looks, sounds, and feels: the identity, the templates, the voice, and the designers and vendors we bring in for volume. Today it's spread across a brandbook, a website, and a dozen decks that don't quite match. Making it one coherent thing is yours.

- The website. The design, the copy, the layout, and the code. Our site is a codebase and you'll ship to it yourself with Claude, from a headline fix to a new page.

- Positioning and messaging. The argument for why a team should trust us over the tools they already use, kept consistent across the website, the decks, and the pitch. You'll know what competitors claim and where we actually win.

- Customer proof. Case studies, quotes, and reference stories drawn from live engagements, built with the people running each account.

- Customer and investor materials. The deck system and its variants by segment, the one-pagers, the leave-behinds, the template an analyst sees when they open a Kepler output, and the materials for the conferences we attend.

- Public voice. Our CEO's writing on LinkedIn and X, the team's weekly posting plan, talks turned into posts, the blog, and the recruiting posts that make good engineers want to work here.

- Launches and co-marketing. Product launches end to end (the post, the page, the email, the follow-up) and the joint pieces we ship with partners, from the first draft to the coordinated push.

- Search and AI answers. How we show up when a buyer searches for us or asks an AI about us.

In the first few weeks you might:

- Take a section of our website from bad to good: the copy, the layout, and a clear argument for why the new version works better than the old one.

- Redesign the template an analyst sees when they open their first Kepler output, so it reads like it came from a company they'd trust with a million-dollar decision.

- Take a talk our CEO gave and turn it into a post that lands on LinkedIn without losing the substance.

- Tell us the three things about our brand that are actively working against us, and fix the first one.

In the longer term, you'll own the brand surface end-to-end. This is our first marketing hire, so a lot of what the function becomes is going to be your call.

HOW…