Daxeel Soni

2.4K posts

Daxeel Soni banner
Daxeel Soni

Daxeel Soni

@daxeelsoni

I build AI products people actually use. Enterprise AI • Productivity tools • Applied automation • https://t.co/njtEPfdf7T

Katılım Haziran 2014
804 Takip Edilen1.6K Takipçiler
Sabitlenmiş Tweet
Daxeel Soni
Daxeel Soni@daxeelsoni·
Beyond grateful to attend the Swearing-in Ceremony of the Primer Minister of India, Shri Narendra Modi and other ministers at The Rashtrapati Bhavan, New Delhi 🇮🇳
Daxeel Soni tweet mediaDaxeel Soni tweet mediaDaxeel Soni tweet media
English
1
0
11
1.4K
Daxeel Soni
Daxeel Soni@daxeelsoni·
Most AI "ROI decks" miss the only slide a CFO actually cares about. AI isn't just a cost-cutting tool. It changes the math underneath the business. So the question isn't "Did we adopt AI?" It's "Which unit driver moved first?" Here's the frame: Margin per customer = LTV - CAC - COGS AI can hit all three at once, which is why the payoff can feel weirdly nonlinear. - CAC drops when targeting and personalization get sharper, not when you simply crank spend. - COGS falls when minutes per unit drop and customers file fewer tickets. - LTV rises when timing gets better: retention outreach, expansion plays, renewals. The real win is compounding. A few small percentage shifts can stack up into a very different P&L. If you're tracking "AI usage," you're measuring theater. Track the drivers. Which one moved first for you: CAC, COGS, or LTV?
English
0
0
0
27
Daxeel Soni
Daxeel Soni@daxeelsoni·
“Move fast” is overrated. The teams that win ship boring, repeatable loops: instrument the funnel, cut cycle time, run 10 small experiments, kill 9. I’ve seen 2-week “big launches” lose to 2-day iterations. Speed is a system, not a sprint.
English
0
1
2
46
Daxeel Soni
Daxeel Soni@daxeelsoni·
If it helped, RT tweet 1, follow for more practical rollout playbooks, and send it to someone about to go live ✅
English
0
0
2
10
Daxeel Soni
Daxeel Soni@daxeelsoni·
12/ Shipping AI this quarter? Bookmark this.
English
1
0
2
9
Daxeel Soni
Daxeel Soni@daxeelsoni·
Most AI projects don’t fail at ideation. They fail at go-live. Here’s the exact launch checklist we run before every AI release. Save this for your next rollout 🧵👇
English
1
2
3
71
Daxeel Soni retweetledi
Memry
Memry@savememry·
Imagine your saved links acting like a personal newsletter. Not generic. Not algorithmic. Yours. @savememry sends a daily digest of what’s worth revisiting from your own library.
Memry tweet media
English
0
1
1
18
Daxeel Soni
Daxeel Soni@daxeelsoni·
Most AI rollouts fail for 1 reason: teams don’t adopt AI in a straight line. They move through 3 stages: Fear → Curiosity → Dependency. Recognize the stage, use the right tactic, and adoption speeds up.👇 Stage 1: Fear It sounds like: - "This is going to replace me." - "We don’t have time for this." - "Feels risky." Most of the time it isn’t laziness. It’s uncertainty. When people don’t know what’s changing, they fill in the blanks with worst-case scenarios. So the job isn’t to hype AI. It’s to make things less fuzzy. How to lower the temperature fast: - what will change - what won’t change - what support exists (training, office hours, examples, who to ask) Tactic for stage 1: make it safe Write a simple team “AI agreement”: 1) what kinds of tasks AI can help with 2) what data is off-limits 3) how output gets reviewed (and by whom) People don’t need to love AI to try it. They just need to know the boundaries and what “good” looks like. Stage 2: Curiosity You’ll hear: - "Could it do this?" - small experiments in docs or drafts - people swapping prompts or tips Curiosity is real, but it’s easy to crush. If trying AI feels like a performance review, people stop. Give them low-stakes reps: - time-boxed - optional - aimed at everyday work, not “moonshots” Tactic for stage 2: run a two-week pilot Pick one workflow (not five): - first drafts for emails/docs - meeting summaries - role guides / SOPs Then track two things: time saved and whether the output is actually usable. Stage 3: Dependency Signs: - "I can’t go back." - it shows up in most workflows - new hires get trained on it immediately Dependency isn’t automatically bad. It can mean speed. It can also mean blind spots. Tactic for stage 3: keep it healthy Aim for speed with judgment: - human-in-the-loop review on anything that matters - source checks for facts - a fallback plan for when tools are down or results are off Don’t outsource the thinking. Let AI carry some of the load, but keep decisions with people. Where’s your team right now: fear, curiosity, or dependency? #ai #EnterpriseAI
English
1
1
3
62
Daxeel Soni
Daxeel Soni@daxeelsoni·
Most “AI strategy” decks fail because they start with models, not work. Pick 1 ugly workflow (triage, QA, sales notes). Time it. Add a human-in-the-loop. Measure cycle time weekly. That’s the playbook I’ve seen actually ship.
English
0
0
1
36
Daxeel Soni retweetledi
Version Labs
Version Labs@versionlabs·
"Work" shouldn't just be a list of tickets. Burnout is real. Isolation is growing. Teams are drifting apart. @myfelloz brings them back. Fun gamification. Meaningful rewards. Visit myfelloz.com #TeamBuilding #HRTech
English
0
2
3
44