Posteri — India-first social SaaS

The idea

Existing social schedulers are built for US markets: WhatsApp is missing, GST-aware invoicing is missing, INR-first pricing is missing, and the AI features assume you’re writing in English. Posteri is what a scheduler built for the Indian creator and small brand looks like.

The gap is more specific than “no Indian option”. Search the category and the tools split cleanly in two. One half schedules and publishes but writes nothing — you bring the copy. The other half generates copy with AI but has no calendar, no queue, no accounts connected; you copy the output into another tool. Almost nothing does both ends of the same job in one place, and nothing at all does it for someone posting in Kannada or Marathi.

That second half is the real opening. AI captioning is now table stakes in English and effectively absent for Indian regional languages — not because the models can’t, but because nobody has built the product around it.

Who it is for

Anyone running a business who wants their posting handled without hiring for it — a solo creator, a shop, a small D2C brand. The product is self-serve by design, because the buyer for a ₹500-a-month tool will not sit through a sales call.

There is also an agency plan: an agency subscribes once, then onboards its own clients underneath its account. Same product, different unit of billing, and it is the path where one signup brings twenty managed accounts with it.

The language question

Five languages are specified for launch — English, Hindi, Kannada, Tamil and Marathi — but five is a starting point, not the target. The intent is coverage across Indian regional languages generally, treated as first-class rather than as a token gesture bolted onto an English product. A tool that writes well in Hindi and badly in Tamil has not solved the problem; it has picked a subset of the market and left the rest with the same gap they had before.

That commitment is the differentiator and also, as below, most of the cost.

The approach

Turborepo monorepo — web, admin, worker, shared. Single lint, single build, single deploy pipeline.

Next.js 15 for both surfaces. Supabase for auth, data, and queues. Claude API as the writing co-processor — brand-voice adherence and multi-language captioning.

Meta, LinkedIn, X and YouTube Shorts at launch, with WhatsApp Business posts as the differentiator — the channel every Indian small business actually runs on and every Western scheduler ignores.

The hard part is not the code

The technical spec is finished. What is not finished is the economics, and that is what the launch is waiting on.

Good output in a regional language costs more tokens than good output in English — more context, more iteration, more checking before anything is worth publishing. In a product priced for Indian small businesses, that cost lands directly on the margin of every plan. So the question that decides whether Posteri ships is not whether the feature works; it is what a user costs per month at acceptable quality, and whether a price that works for a shop in Jayanagar still leaves anything behind. That number needs real usage data to establish, not an estimate — and the studio has written up the maths it runs before quoting any AI feature.

The rest of it is the unglamorous part: enough data to tune output quality, and enough runway to reach the point where the answer is known.

Where it is

Spec complete, monorepo underway, nothing public. No launch date, and no honest way to give one until the cost question above is settled. This page will be updated when there is something to show rather than something to describe.