TTV is the time before customers experience the value promised after 'purchasing' the product (e.g., a free trial or a freemium).
Let's take @canva as an example. You can use it immediately. You get sucked in and don't even notice that you've just become their customer! :)
You can easily minimize #TTV by using the Bowling Alley Framework. It's like using "bumpers" to guide users to the outcome your product promises.
There are two types of bumpers:
1. Product Bumpers
Their goal is to help adopt the product within the application.
a. Welcome Messages — displayed after logging in. It's an opportunity to greet users, make them feel invited, and restate the value proposition. They can also set expectations.
b. Product Tours — Eliminate distractions and allow users to focus only on the most critical options. It commonly starts with the question about what users would like to accomplish with the product. Let your users choose their adventure.
c. Progress Bars — Help users understand what's their progress. It's a good practice to start with a substantial percentage of the bar filled in so that users can feel that they are already underway instead of starting from scratch.
e. Onboarding Tooltips — Helpful messages are displayed when interacting with application elements (e.g., mouse hover). It shouldn't be too intrusive; e.g., forcing users to click every detail on a page may not be a good idea.
f. Empty states — After the first login, many applications are tedious. There is no data specific to you; without it, it's virtually impossible to understand what value you will get once you start using the product.
There are two ways:
a) Present users required steps and prompt them to take action.
b) Prevent it from happening. Dynamics 365 Sales populates every trial with sample data. I presented it at the beginning of this article.
Conversational bumpers work to educate the users, set their expectations, bring them back to the application, and eventually upgrade their accounts. I selected the two most popular forms:
a. User Onboarding Emails — can include welcome messages, usage tips, sales touch (to upgrade accounts), case studies, communicating the benefits, information about trial expiration, or post-trial surveys. You can easily automate most of them.
b. Explainer Videos — The name is self-explanatory. Videos can generate even 1200% more engagement than text and images. I highly recommend it, especially for complex products.
Everyone in AI is talking about Context Engineering.
But just a few explain what the context is.
Save this template. It captures all scenarios and will help you maximize agents' performance: 🧵👇
1. Instructions
Define:
→ Who: Encourage an LLM to act as a persona
→ Why is it important (motivation, larger goal, business value)
→ What are we trying to achieve (desired outcomes, deliverables, success criteria)
💡Providing strategic context beyond raw task specification improves AI autonomy arXiv:2401.04729
2. Requirements (How)
Define:
→ Steps to take (reasoning, tasks, actions)
→ Conventions (style/tone, coding rules, system-design)
→ Constraints (performance, security, test coverage, regulatory)
→ Response format (JSON, XML, plain text)
→ Examples (positive/negative, responses/behaviors)
💡Negative examples might help you address issues identified during error analysis
I spent 12 hours testing 9 LLMs for building AI agents:
- You might easily save up to 83% on costs.
- Reasoning models are not the best.
- Autonomy break fast. A real moat is orchestration.
Here's everything you need to know: 🧵
The task assigned to agents:
- Create a new list inside Kanban (1 Trello board available)
- Search the web to find the recent news about Amazon
- Add all the search results to the Kanban list
Completing this task required:
- Preparing a simple plan
- Using multiple tools in the right order
- Adjusting the plan if anything goes wrong
- Operating autonomously (the system prompt gave no clues about the process)