AskTina
AskTina was a live video chat widget that let blog readers place paid per-minute calls to experts through a mobile app.
View original storyProduct snapshot
What it was
AskTina let experts embed a widget on their blogs so readers could place live pay-per-minute calls through an app.
Who it was for
Problem / value
It promised a way for experts to monetize attention through real-time paid advice.
Core workflow
An expert installed the widget, readers saw it on the blog, and interested readers could pay for a live call.
Core dependency
Readers had to prefer paid synchronous calls over free asynchronous content.
Product form
Pricing model
Pay-per-minute calls. Exact pricing is not disclosed, and the reported MVP generated zero paid calls.
Competitors or alternatives
What happened
Summary
AskTina shut down after objective usage data showed that expert installs and widget exposure did not create paid calls.
Outcome
The project was killed because no readers took the paid call action.
Core risk
Audience exposure can look like traction while the paid behavior remains unproven.
Shutdown reason
Readers did not want paid live video calls enough to use the product, and the team had not validated that behavior before building.
Demand signal
AskTina got distribution signals but no paid behavior: 35 experts installed the widget and it loaded 10,000 times, yet readers placed zero paid calls.
Distribution issue
The team used SEO, content, social, and paid channels, and experts installed the widget, but exposure did not convert into the one action that mattered: a paid call.
Timeline
- Built an MVP for paid live expert calls
- Got 35 experts to install the widget on their blogs
- Recorded 10,000 widget page loads
- Generated zero paid calls
- Killed the project after the demand signal was clear
Before you build
Why it matters
Creator and expert tools often mistake audience access for demand. The real proof is whether the audience pays for the new interaction.
Primary check
Prove readers will pay for live access before building a widget, marketplace, or creator monetization workflow.
Checklist
- Would readers pay before seeing a polished widget?
- Which audience problem is urgent enough for a live call?
- Can you collect payment with a manual scheduling link first?
- Pre-sell calls before building the app
- Test one expert category with urgent buyer pain
- Track paid calls, not only impressions
- Deliver calls manually until demand repeats
Relevant if
- You are building a creator monetization tool
- Your product depends on paid calls, paid advice, or expert access
- You have supply-side interest but no buyer payment yet
Less relevant if
- You already have prepaid calls or signed paid pilots
- Your product monetizes through ads or sponsorships rather than direct reader payments
Pre-build tests
- Ask readers to prepay for a call with one expert
- Run a manual concierge call service for one blog
- Test price sensitivity before building the widget
Transferable lessons
- Interview buyers before coding the widget
- Use manual delivery to test demand first
- Do not treat page loads as willingness to pay
- Kill or reshape the idea when the paid action is zero
If you build this today
Manually broker paid expert calls or collect prepayments from readers first, then build software only after a repeatable paid advice workflow appears.