To Our Stakeholders

Why Now

For individual service providers running their business on social media, something changed over the last three years. DMs used to be where you talked about content; now they're where the actual selling happens. Booking a slot, asking about price, negotiating, deciding — all of it now flows through social media DMs. And sellers are drowning in that traffic.

The opening of WhatsApp Business API to individual accounts added another layer: a seller can now technically reach an infrastructure that lets them speak with one voice across every channel — but there's no tool to set it up, run it, and grow with it.

The big players either didn't see this gap or didn't care about it; none of them built for individual service providers. We're building the solution right inside it.

What Happens If Nothing Changes

A customer asks a question. The reply comes four hours later. The customer has already gone to someone else — and the seller doesn't even notice.

This plays out every day, across tens of thousands of the 600,000 individual sellers out there. The revenue loss is invisible, because nobody says 'I lost one.' The customer just leaves. Nothing gets counted.

Let's make this concrete for investors (an estimate from our Fermi model): a seller gets about 10 DMs a day, and roughly 40% of those carry real buying intent. Because of response delays, 2 of those 4 potential customers are lost. At an average transaction value of $20, that's about $14,600 in lost revenue a year for a single seller. Multiply that across the whole market, and the damage becomes hard to even calculate.

Why Existing Alternatives Fall Short

Linktree gives you a showcase, but it doesn't answer the visitor's question. Someone clicking a seller's link wants to learn about the service — and there's no one there to talk to.

ManyChat and similar chatbots fill that gap with technical complexity instead: setup is hard, flows are rigid and brittle. Designing a separate flow for every question requires technical skill most individuals just don't have the time for.

The big CRMs (HubSpot, Pipedrive) are overkill for a coach or a beauty professional. Onboarding takes weeks, pricing runs on annual contracts, integration needs technical know-how — these products were built for businesses with an IT department, not for individuals.

WhatsApp Business on its own doesn't solve it either: a question comes in, someone answers it by hand. No automation, no follow-up, no analytics — just slightly more organized messaging.

None of them combine a 24/7 assistant that answers questions, qualifies visitors, builds a lead list, and hands the seller marketing suggestions. That's exactly the gap talkinbio fills.

What We Do

talkinbio has two parts.

Saule is the AI assistant that works 24/7 on your bio page. When a visitor asks a question, Saule listens, understands, and answers like someone who actually knows your business. It books appointments, logs interested visitors, and flags anything that needs follow-up. When you wake up, you're not looking at missed DMs — you're looking at a sorted, tagged lead list.

Beiwe analyzes those conversations and turns them into weekly marketing suggestions. 'What question came up most this week? Which service got the most interest? What times did visitors show up?' Beiwe answers those questions, so your next content decision is based on data instead of a guess.

Setup takes 10 minutes, no code required. And once the system is running, it keeps working whether you're at your desk or not.

What Makes Us Different

Every Saule conversation carries a small signature underneath it: 'You're chatting with Saule — talkinbio.com.' Everyone who visits a seller's page sees it. And some of them think 'I want that on my own page too' and sign up. So the product grows itself — CAC stays organic without any paid marketing.

That produces a few advantages. First, a viral loop: every active assistant becomes a channel for acquiring new users.

Second, accumulated conversation data: the more Beiwe gets used, the more specialized it becomes. A new competitor can't copy that data advantage overnight — our early users are giving us a strategic head start in data richness.

Third, a local-first architecture: we're already building the localization skeleton that adapts to markets with different languages and payment infrastructure (MENA, LatAm). That means our v2 expansion won't have to start from zero.

Our Revenue Model

Our revenue model is a credit-based subscription. Billing infrastructure ships as part of our roadmap's launch gate; for now, we collect payment manually from early pilots. We have three tiers.

Starter ($9/month, 200 credits) is for the individual seller getting 3-5 DMs a day, setting up an assistant for the first time. Users at this tier are learning what Saule does and testing whether it's worth it.

Pro ($29/month, 700 credits) is for sellers getting 30+ DMs a week, with a steady customer base, who use Beiwe's analytics. This tier is our real revenue engine.

Business ($79/month, 1,800 credits) is for sellers running multiple service lines, handling high DM volume, with automation needs that have outgrown the basics.

Pricing is dollar-fixed; we collect in lira at the current exchange rate. Annual billing comes with a 20% discount — savings for the customer, and a buffer against currency risk for us.

In numbers: effective ARPU is $15, LTV is $300 (assuming 5% churn), and we're targeting a CAC under $100 — our viral signature loop should keep that organic.

Where We're Headed

Right now we're in Stage 1: Problem/Solution Fit. The one metric we track (OMTM) is paying customers, and the counter currently reads 0/10. Our goal: finish 20 problem interviews, confirm the pain points that keep repeating, and get the first 10 pilots paying $9/month.

Stage 2 (550 customers, $100K ARR) is proof of Problem/Solution Fit — crossing that line also tells us whether the viral loop actually works. That's where investor conversations start.

Stage 3 is v2 Global: direct WhatsApp and Instagram DM integration, MENA and LatAm localization, new languages. In our base scenario that's roughly 4,500 customers and $810K ARR — Saule stops living only on the bio page and starts working across every channel. In a more optimistic scenario (6% global capture), that grows to roughly 9,000 customers and $1.6M ARR.

Every step needs proof from the one before it. Right now, we're focused on exactly one thing: the first 10 payments.

Long-term, we don't see talkinbio as just a tool for individuals. Saule and Beiwe are turning into an agent infrastructure that runs across every channel a business communicates through. We're not naming that yet — the product will speak for itself.

How We Work

We follow the Running Lean methodology — not as a slogan, but as the framework that directly shapes how we work.

We validate the problem before we build the product. Customer interviews get finished before development does; if 20 interviews don't surface a recurring pain point, we do more.

We don't offer a free trial — that's not a preference, it's a methodological choice. Ash Maurya's Running Lean is clear on this: free early access collects the curious, not customers. Our first 10 paying customers are the real test of the value hypothesis — payment is commitment.

We keep a Continuous Improvement panel: the Lean Canvas, the Fermi Estimate, the Traction Roadmap, and the Lean Sales Pitch — all of them, including the page you're reading right now, are living documents. They get updated as things change, and saved every time they do. Version discipline is a standard here, not an exception.

We keep our evidence classes visible: what's validated is marked validated, what isn't is marked as such. Inflated claims of proof don't get a pass.

What We're Asking For

From our users: setup takes 10 minutes. Connect your bio link to talkinbio, and watch how many leads Saule collects over a month. If it doesn't create value, don't continue. If it does, now you know.

From our investors: we're an early-stage, bootstrapped startup right now. The right time for an investment conversation is once we cross $100K ARR — but rather than make you wait until then, we wanted to introduce ourselves early. Our numbers are marked by evidence class: validated is validated, estimated is estimated, and the open questions stay open. We'll reach out when we're ready.

From our team: come back to this page whenever you need a reminder of why building this matters. We believe what we're doing is right — proving it is the only thing left to do.