Product Lead, Invoice Automation

Fotofacturas is Clara's invoice digitization suite. Mexican companies generate millions of CFDIs every month. Most still process them manually — downloading XMLs, reconciling by hand, chasing paper. Fotofacturas fixes that: capture a photo, scan a QR code, send a WhatsApp message, and the invoice is in Clara automatically, validated, categorized, and ready for approval.

This is a role to lead a “Builder Squad” Builder squads are lean by design. Two people, tight scope, high ownership. You'll move faster than any traditional PM role because you have to. This is not a committee product. Every week matters.

• →Own discovery, prioritization, and outcomes across all four Fotofacturas products. That means understanding which surface is growing, which is stuck, and which is a distraction — and making the call.
• →Go deep on CFDI processing: how Mexican tax invoices are structured, what the SAT validation rules are, where OCR and AI extraction fail, and how to design flows that are forgiving of messy real-world documents.
• →Build and maintain the WhatsApp channel as a first-class product surface. Understand the WhatsApp Business API, conversation design, and how to make a chat interface feel like a product, not a hack.
• →Define and track the metrics that matter: invoices processed per week, OCR accuracy rates, time-to-capture, activation rates by channel (app vs. WhatsApp), and Fotofacturas contribution to overall AP automation adoption.
• →Use AI tools as your primary building tool. This squad runs on Claude, GPT, Cursor, and Claude Code. If you're not comfortable using LLMs as a daily work tool, this role is not a fit.

• →Contribute code for straightforward changes (copy, config, feature flags, simple UI, prompt tuning, analytics instrumentation) using AI coding tools. All contributions go through engineer review before merging.
• →Work in Git daily. Read PRs, understand what shipped, follow what's blocked.

• 5+ years in product management, with experience owning an AI-first, OCR, document-processing, or invoicing product
• Track record of shipping products that changed user behavior, not just launched
• Has operated in a lean environment — small team, broad scope, fast iteration — and thrived in it
• Comfortable working with engineers as peers

• Understands CFDI structure and the SAT validation ecosystem. You know what an XML complemento is, what CFDI 4.0 changed, and why validation errors happen.
• Has worked with OCR pipelines or document AI: what makes extraction fail, how to design human-in-the-loop fallbacks, and how to measure and improve accuracy over time
• Comfortable designing conversational product surfaces (WhatsApp, chat, SMS). Understands conversation design constraints and where messaging channels break down as a UX
• Has built or managed AI-first features — LLM extraction, classification, or generation — and knows how to evaluate them beyond "it seems to work"

• Uses AI coding tools (Cursor, Claude Code, or similar) as a primary workflow, not occasionally
• Comfortable with Git: branches, commits, PRs, reading diffs
• Can read and lightly modify code using AI assistance — enough to unblock yourself and prototype without waiting for engineering
• Understands prompt engineering well enough to iterate on LLM-based extraction and classification tasks independently

• Strong prioritization instincts. With four products and one engineer, the biggest risk is building the wrong thing.
• Data-literate. Comfortable with SQL, funnel analysis, and OCR accuracy metrics.
• Clear written communicator. Can write a one-pager that drives alignment without a meeting.
• Stakeholder management across engineering, enterprise clients (Eli Lily), finance operations, and sales.

• High agency. Defaults to action over process.
• Scrappy. Comfortable doing things that don't scale to learn what scales.
• Treats AI tools as core workflow — not a novelty, not something to experiment with on the side.
• Thrives in a Builder squad: lean, fast, no hand-holding.

• Experience with the SAT's CFDI validation APIs or similar fiscal digitization platforms
• Experience with WhatsApp Business API at a product level
• Background in AP automation, expense management, or fintech in Mexico
• Experience managing enterprise or white-label product variants without letting them become custom engineering projects

English required — it's Clara's working language across all markets. Spanish required for this role: the product lives in the Mexican fiscal ecosystem, and deep CFDI knowledge is inseparable from Spanish-language regulatory context. Native or near-native Spanish is a strong preference. Portuguese is a plus.

Mexico. Mexico City strongly preferred.

• We’re the leading B2B fintech for spend management in Latin America.

• Certified as one of the world's fastest-growing companies, a Great Place to Work, and a LinkedIn Top Startup.

• Passionate about making Latin America more prosperous and competitive.

• Constantly innovating to build financial infrastructure that enables each of our customers to thrive.

• Product-led, high-talent-density culture — designed for builders who raise the bar.

• Proud of our open, inclusive, and values-driven environment.

• #Clarity. We say things clearly, directly, and proactively.

• #Simplicity. We reduce noise to focus on what really matters.

• #Ownership. We take responsibility and never wait to be told.

• #Pride. We build products and experiences we’re proud of.

• #Always Be Changing (ABC). We grow through feedback, risk-taking, and action.

• #Inclusivity. Every voice counts. Everyone contributes to our mission.

Claridians in a hybrid mode split their time between working from the office, talking to or visiting customers, or working from home. This hits a balance between bringing people together for in-person collaboration and learning from each other, while supporting flexibility about how to do this in a way that makes sense for each individual and team.

We don't enforce a minimum number of days for most roles, but you're expected to spend time at the office organically, and be at the office most days during your ramp-up or when required by your leader.