Tali
Tali was a voice-powered legal timekeeping SaaS that let lawyers create billable time entries through Alexa and Google Assistant.
View original storyProduct snapshot
What it was
Tali let lawyers log billable time through voice assistants, review entries in a web dashboard, and sync entries into legal billing systems.
Who it was for
Problem / value
Reduce manual time-entry work for lawyers who otherwise wrote time on paper and entered it later.
Core workflow
- Log billable time by voice
- Review captured time entries in a dashboard
- Sync entries to legal billing systems such as Clio
Product form
Pricing model
The founder described an initial $90 three-month offer and later $12 per user per month or $120 per user per year pricing.
What happened
Summary
Tali reached paid users, but weak renewal, low repeat usage, and poor acquisition economics showed that the voice-first workflow did not have durable product-market fit.
Outcome
Shut down. The case is best read as a founder-reported warning about interface novelty, retention, and small-account acquisition economics.
Demand signal
The source shows real pain and early willingness to pay, but renewal, daily usage, and trial conversion were too weak to support the business.
Distribution issue
Tali tried inside sales, paid ads, reseller arrangements, and other channels, but small law-firm account sizes made profitable acquisition difficult.
Timeline
- February 2017: The company started after the founder explored a voice-based timekeeping idea for lawyers.
- September 2017: Tali launched a paid beta with Alexa, a web dashboard, and a Clio integration.
- December 2017: The founder reported 101 paid users and about $3,030 MRR.
- Renewal problem: Only 22 of 101 users resubmitted payment details after the team discovered auto-renewal had not been built.
- 2018: Paid users grew, but DAU stayed below 10% of the paid base and trial-to-paid conversion stayed below 3%.
- Shutdown: After spending about $750,000 over 2.5 years, Tali wound down at roughly $3,000 MRR.
Before you build
Why it matters
Voice and AI demos can feel persuasive, especially when they solve a real pain. But if the new interface is less reliable or less habitual than the old workflow, early curiosity will not turn into durable usage.
Primary check
Prove repeat usage, renewal behavior, and acquisition economics before making a new interface the core of a workflow tool.
Relevant if
- You are building a voice, AI, or assistant-style workflow product.
- Your buyer is a small professional-services account with low ARPA.
- Your product depends on replacing an existing habit rather than adding a lightweight feature.
Less relevant if
- Your product is used rarely but has a very high transaction value.
- You already have strong renewal and expansion data from paying accounts.
Pre-build tests
- Run a paid cohort through a real renewal cycle before adding channels.
- Measure weekly active use against the workflow frequency the product promises to replace.
- Calculate whether your account size can support the sales motion before spending on acquisition.
Transferable lessons
- Measure renewal and repeat usage before scaling acquisition.
- Do not make a still-maturing interface the whole product unless it beats the existing workflow.
- Make billing and renewal mechanics part of the validation test, not an afterthought.
If you build this today
Pair voice input with a strong visual workflow, validate retention with real billing behavior, and confirm that small legal accounts can be acquired profitably.