we just raised another $25M after 10x'ing our ARR in 5 months. the crazy part is this almost never happened.
17 years ago, I watched Iron Man as a 10-year-old kid in Delhi. that night, I pulled my first all-nighter teaching myself to code. not because I wanted to build apps or make money.
because I wanted to build Jarvis.
my parents gave me 1 hour of screen time per day. so I coded in secret, sleeping every alternate night through middle school and high school. built 50+ apps. got a cease and desist from Google at age 12.
all for this one obsession: making computers understand us like humans do.
fast forward to today:
- we've raised $81M total to build the voice operating system
- growing revenue 40% month-over-month this year
- 70% user retention after one year (unheard of in consumer)
- teams at 270 of the Fortune 500 use Wispr Flow daily
our Series A2 was led by @hanstung at @notablecap (who was an early investor in five companies that made it to $100B valuation like Slack, Tiktok, and Airbnb). we also brought on @StevenBartlett as an investor and partner.
but here's what matters more than the money:
we cracked voice input. not transcription - actual understanding. our users hit "send" in under 0.5 seconds without checking. they trust it blindly. that's never existed before.
in a recent benchmark, Wispr came out as 3-4x more accurate than OpenAI, ElevenLabs, and Siri.
and we're just getting started. voice input was step one. now we're building the assistant that actually does things for you.
to my co-founder @SahajGarg6 - there's no one else I'd rather build Jarvis with than my college roommate and closest friend.
to our team pulling all-nighters and shipping magic - you're the reason that 10-year-old kid's dream is becoming real.
we're hiring cracked engineers and growth marketers who want to build the future of human-computer interaction.
the keyboard had a good 150-year run.
time to build what comes next.
PS: like, retweet, and bookmark to get wispr flow for free for 3 months ❤️
— Written with @WisprFlow
Some ex-princes take island trips with men named Jeff.
Others find a Bitcoin glitch in a damp Blackpool flat.
Both tell you what people do when they think no one is watching.
Your MONDAY LISTEN is:
👂 Coining It by @GlobalPlayer@LewisGoodall17
👌 EARMARKED by Jojo Rating 5/6
Struggled with this one. I’ve been a little despondent with the collective “us.” The world feels like a wheel of no fortune spun by Tr^mp-style spectacle.
Read it. Tell me where it misses, and what I should push further. tinyurl.com/GIRLTAKEN
Starting a new mobile native app project, wish me luck.
- No technical background
- going to build on no-code tool @bubble - spent the last 3 months learning the tool
My goal
- zero to MVP in 30 days
- share my daily progress
Days 6–7
Felt a bit all over the place, so I’m taking a step back to get organized and use my time more efficiently.
On another note — just discovered Google Stitch. It’s the real deal for UX and UI inspiration
Days 2–5 of building my first mobile native app (no-code + non-tech background).
Made progress, hit roadblocks, and discovered I kinda suck at design 😅
Might try Mobbin for UI inspiration. Any other design tools or sites I should check out?
@vcdxb@bubble 1. Building complex app experiences helps
2. Read the manual at least once, lots of hidden gems
3. Upload the manual (or exam topics) to ChatGPT/NotebookLM & simulate exam-style prompts
4. Use LLMs to dive deeper into unclear concepts
Hope this helps, just what worked for me!
@mneary0 Thanks Matt, I have to say, the last few chapters on webhoook, oAuth were quite brutal for a non technical person. But I appreciate the level of detail you went into. Def will need to rewatch those once I get to that stage.
I bought @mneary0 bubble course back in 2023. I gave up after the first few videos. In Aug this year my itch to build something came back so I decided to start again. So after 2 months, with a 9-5 job, long nights & weekends, I finally finished it today. Next step-start building
@emmanuel_s@NocodeTalks Microsoft used to have something like this and when their team started working on an user posted request, they would charge the status of that item as 'working on it' and would give regular updates with an estimated timeline. This way users are aware of the pipeline.
@NocodeTalks This is valuable information for the team when we think about our roadmap, but it's not automatic. it's not because something crosses x votes that we automatically build it. I don't think any team does it this way.
What’s the point of releasing a new ideaboard when you don’t share exactly when any idea will turn into features?
Or some devs feel like they don’t have any work, so they just revamped its UI.
forum.bubble.io/t/feature-enha…
OxyContin scattered the pieces so far, they may never be gathered. The domino fell, the ruin spread, and the clean-up manual was never written.
Now on my Substack: Hooked (Part I) - The Gallows of a Pill tinyurl.com/HOOKED-part-1
I built a Morning Brew-style daily newsletter that writes itself with AI (now at 10,000 daily readers)
(and I’m nuts for open-sourcing it)
The AI system behind @therecapai clones how a human writer would function, but each step is packaged into an agentic workstream.
The full automation handles:
- Daily scrapping hundreds of reddit threads, hackernews, twitter posts, Google news API to build a massive data lake of 'daily AI news'
- Dozens of custom prompts to pull the top daily stories from this data lake, write short breakdowns, & format the newsletter
- Builds custom images based on each story with ChatGPT image generator
This was 5 MONTHS of iterating and fine-tuning prompts to get the output and content to an extremely high quality state (no AI slop)
and call me crazy, but I'm giving it away for free.
Just Retweet, follow me, and comment on this thread "NEWSLETTER"
and I'll DM you the full n8n template that you can copy/paste and fine-tune to your use-case as well as a full hour long video breakdown explaining the build.
Also you can see the actual contents of the newsletter for yourself with the link below—proof of the quality that is possible with AI.
RIP media companies 💀 AI is here.
@vcdxb Yes, mostly don’t follow the tutorial in full. A nudge at the point where we copy-paste key is the ultimate help, along with one final checklist before deploying.
Google maps keys in the bubble exposed like we are exposing bubble app url.
50% of the app who add the google maps key - literally doesn't restrict it to domain.
I have so many google maps api keys. All exposed - public.
Bubble should at least do something about this.
How hard to put the text: "Please domain-restrict your google maps key" and link on how to do it?
Footnotes. Side notes. Soft obsessions. And— rabbit holes.
Every story leaves scraps. The detours, the tangents, the Googles at 2 a.m. Sometimes the side note isn’t decoration— it is the story. A rabbit hole I couldn’t drop.
Fall in ⬇
earmarkedbyjojo.substack.com/i/172791837/fo…