AI content studio software usually makes everyone sound identical, so I built Curro 1.0 to do the opposite: drafts that carry your rhythm, your phrases, your jokes. It writes at 62 tok/s from my Junagadh lab, and beta users cut editing from five passes to one.
I am Deepak Bagada, founder of SaaS Next in Junagadh, Gujarat. Curro is my own product — a year of evenings after the demo-day disaster I describe below. This launch post covers what 1.0 does, the voice-model design, the pricing, the code shape, and where it honestly falls short.
What Curro 1.0 Actually Does
You drop in rough notes, a voice recording, or a one-line prompt. Curro returns a structured draft — article, script, or social set — in a voice profile trained on your past writing. The pipeline has three stages: transcribe and extract claims, retrieve your related past passages for style reference, and draft with citations to your own source notes. Nothing ships without your edit pass; the review screen is the product as much as the model.
Free tier covers personal writers with ten drafts a month. The studio plan at ₹999 a month adds team voice profiles, scheduled drafting, and direct publishing to this same Laravel journal stack. Every plan includes the citation engine and the eval gates — grounding is not a premium feature, it is the product promise. My AI development services built every layer, and the retrieval core follows the RAG design in my fine-tuning vs RAG breakdown.
// File: voice-profile.json — how Curro stores what "sounds like you"
{
"owner": "demo-writer",
"sample_docs": 47,
"cadence": "short-blunt mixed with long-technical",
"signature_moves": ["metric-first openings", "one-line warnings", "quoted bottom lines"],
"banned_fillers": ["very", "really", "in order to"],
"eval_pass_rate": 0.94
}
# File: studio_draft.py — Curro 1.0 draft loop, simplified
from curro import transcribe, retrieve_style, draft_with_citations
def studio_draft(notes_path: str, owner: str) -> dict:
claims = transcribe(notes_path)
style = retrieve_style(owner, limit=5)
if len(claims) < 1:
return {"status": "empty", "draft": ""}
post = draft_with_citations(claims, style, owner_voice=owner)
return {"status": "needs-edit", "draft": post, "citations": len(claims)}
Spaced operators throughout, as always — clean for tooling, clean for readers.
War Story 1: The Demo That Invented Prices
Curro's origin is a humiliation I have already confessed in my six-chapter story: a 2024 live demo where the prototype quoted a wrong price list with total confidence while latency hit 9 seconds per answer. A Surat client laughed, and I rebuilt everything that summer.
The rebuild added three non-negotiables. One, every factual claim must cite the user's source notes, or the draft refuses that paragraph. Two, voice matching runs on retrieved past passages, never on vibes — 47 sample documents minimum before a profile activates. Three, P95 draft latency must stay under 2 seconds, enforced by a gate that blocks releases. Curro 1.0 is the demo disaster with scar tissue: 94% eval pass rate, zero invented prices across eleven beta accounts.
War Story 2: The Beta Writer Who Stopped Editing
My toughest beta user was a Rajkot technical writer who edits commas for sport. Week one verdict: robotic, rejected all six drafts. The voice profiler had only nine of her documents — below my own minimum — and had averaged her into generic competence.
I re-ran her profile on 52 documents with signature-move extraction: her metric-first openings, her one-line warnings, her habit of ending sections with prices. Week three output needed one edit pass instead of five, and she now drafts forty posts a month through Curro at ₹999. Her line, which I quote with permission: it finally sounds like me on a good day. That single account now saves her roughly twenty-five hours monthly, which at her billing rate repays the subscription more than thirty times over. Minimum-sample enforcement is now hardcoded — profiles refuse to activate below forty documents, no matter how loudly anyone asks.
Curro 1.0 vs Generic Tools: Honest Table
| Dimension | Curro 1.0 (studio ₹999/mo) | Generic AI writers | Freelancer draft |
|---|---|---|---|
| Voice match | Trained on 40+ your docs | One house style for all | Human, variable |
| Factual grounding | Cites your notes or refuses | Invents confidently | Research extra |
| Draft speed I measured | 62 tok/s, P95 under 2s | Similar raw speed | Days, not seconds |
| Editing passes (beta avg) | 1 pass | 4–5 passes | 2–3 passes |
| Monthly cost | ₹0–₹999 | ₹1,500–₹4,000 | ₹15K–₹40K |
The table uses my eleven beta accounts, not a survey. Where Curro loses: languages beyond English plus Gujarati-Hindi mix, heavily formatted academic papers, and writers with fewer than forty past documents. I say so on the pricing page. My automation services wrap Curro in scheduled pipelines for teams that publish daily.

When NOT to Use Curro
Do not buy Curro when you have no writing voice yet — forty documents is the floor, and beginners should write raw for a year first. The tool multiplies voice; it cannot mint one. Do not use it for legal, medical, or compliance text either; citation-to-notes is not the same as professional verification, and I refuse those use cases at signup.
Also skip the studio plan when you publish less than weekly. The free tier's ten drafts cover occasional writers fully, and I would rather keep you free than churn you paid. Software that respects non-use earns the return visit.
Roadmap: What 1.1 and 2.0 Must Earn
Version 1.1 targets the two loudest beta requests: Gujarati-first drafting with English glossaries for mixed-language writers, and a plagiarism-style originality meter that flags passages too close to any single source note. Both are specced, neither ships until evals clear 90% — the demo-day rule still governs. Version 2.0 is the team newsroom: shared claim libraries, editor approval chains, and scheduled publishing across platforms. I will not announce dates until the eval gates pass, because launch credibility compounds exactly like search rankings do: slowly, then all at once.
Frequently Asked Questions
What is Curro AI content studio and what does 1.0 do?
Curro AI content studio turns rough notes and recordings into drafts written in your own voice, citing your source notes. Version 1.0 from Junagadh drafts at 62 tok/s with a 94% eval pass rate, free for ten drafts monthly.
How much does Curro cost in India in 2026?
Curro is free for personal writers at ten drafts a month, and the studio plan costs ₹999 monthly with team voice profiles and scheduled drafting. Beta writers cut editing from five passes to one at that tier.
How does Curro learn my writing voice?
Curro trains your voice profile on forty or more of your past documents, extracting cadence, signature moves, and filler habits. Profiles refuse to activate below forty documents, which is why beta output sounds like the writer on a good day.
Is Curro better than generic AI writing tools?
For voice match and factual grounding, yes in my beta measurements: one edit pass versus four to five, with citations or refusal instead of invention. For new writers without a backlog or academic formatting, generic tools or humans still win.
Bottom Line
Curro 1.0, AI content studio from Junagadh: your notes in, your voice out at 62 tok/s — citations or refusal, one edit pass, ₹999 for studios.