Prince | Building Revvox & HyperBrain Labs (@codewprince) header
Prince | Building Revvox & HyperBrain Labs (@codewprince) profile picture

Founder @hyperbrainlabs | AI-native apps & AI agents · 30+ products shipped · One hit 50K users & Shark Tank India S5

Delhi, India
Joined August 2023
Photo by Prince | Building Revvox & HyperBrain Labs (@codewprince)Photo by Prince | Building Revvox & HyperBrain Labs (@codewprince)Photo by Prince | Building Revvox & HyperBrain Labs (@codewprince)Photo by Prince | Building Revvox & HyperBrain Labs (@codewprince)Photo by Prince | Building Revvox & HyperBrain Labs (@codewprince)Photo by Prince | Building Revvox & HyperBrain Labs (@codewprince)Photo by Prince | Building Revvox & HyperBrain Labs (@codewprince)Photo by Prince | Building Revvox & HyperBrain Labs (@codewprince)Photo by Prince | Building Revvox & HyperBrain Labs (@codewprince)Photo by Prince | Building Revvox & HyperBrain Labs (@codewprince)
Most founders don’t need more features. They need a product that actually ships. I’m Prince, founder of @hyperbrainlabs We build and rescue production AI products in ~21 days. One platform we built was featured on Shark Tank India S5. Today, it serves 50,000+ users across 20+ cities. Here I share: → Real product breakdowns → What breaks in production → How we cut scope without cutting quality → Lessons from shipping products for founders Have an idea-or a half-built app that’s stuck? DM me “MVP”. I’ll tell you what I would cut, keep or fix. No pitch.
1
10
2,470
1 year ago I had a ₹40K/month job. this year: - made ~$30K - now ~$3K/month and growing - 30+ products shipped - one app at 50,000+ users, on Shark Tank India - 3 founders still with us a year later not huge yet. but it's mine, and it's growing.
4
4
203
One of our projects gets handed over this week. The founder gets everything: - The code, in their own GitHub - The server and every login, in their name - A short doc so any developer can pick it up - A call where I walk them through all of it After that, they don't need us to run their app. A lot of founders worry about this before they hire anyone. "What if the agency disappears and I can't touch my own product?" That's why at HyperBrain Labs you own the repo, the cloud and everything else from day one, not just at the end. The funny part is that giving founders full control is exactly why they come back. 3 founders who came to us for one MVP are still with us on retainer, a year later. This week it's 2 client follow-ups and 1 handover. We're still taking only 4 new projects. If you have an idea, or an app stuck at the last 20%, send me a DM or book a free 20-minute call through
1
2
278
monday. 2 clients to follow up with, 1 project to hand over. handing over means the code, the logins and the docs all go to the founder. after that they don't need us to run it
1
1
184
every AI app I've built ends up with the same 4 layers. the model is the easy part. it's maybe 10% of the code. the other 90%: a queue, because LLM calls take 20 seconds and users close the tab a cache, because the same prompt hits 100 times a day logging every prompt and response, because "it gave a weird answer" means nothing without it a fallback model, because your provider will go down on launch day founders ask which model to use. the better question is what happens when it's slow.
1
81
if a Premium payment fails and you renew, the blue tick goes back into review, and mine has been stuck there for a week. Loyal paying user, zero profile changes. @Subscriptions @Support please fix 🙏 @elonmusk
78
week two of a 21 day build is when the "quick add" shows up. the founder isn't trying to blow the timeline. they just had a better idea. what I do with that message: if the first user can finish the job without it, it waits until after launch if it changes login, payments or the data model, it's not a quick add we both look at the scope from day one AI will have the feature done by tonight. that's why it stays off this build.
67
no monitoring on prod is the first thing I check when a founder sends me a Lovable or Bolt app. the app looks done. users show up. something breaks... and nobody knows until a customer DMs them. before I touch a single feature: error tracking on. alerts on payments and webhooks. RLS actually enabled, not just in the plan. solo or Revolut, if you can't see it break you're not in production. you're hoping.
3
1
211
hiring in gurugram: a mobile designer who can also build what they design. 3+ years, on-site. figma to swiftui, AI interfaces for consumer apps, shipped to the app store. location: on-site, gurugram. pay: up to $1,000, one-time. DM me your portfolio, app store links, and the one screen you're proudest of. no portfolio, no review.
1
130
49 steps and the only one i'd never hand to an agent is #37 across 30+ products the agent writes the first draft. every time. i still open auth, payments, webhooks and the rls rules myself before anything ships... and the client owns the repo and stripe from day one that part isn't slow. it's what founders actually pay for
Making the most AI pilled company is the whole game: 1. make a second brain. one folder of markdown files on how you think, write and decide (obsidian) 2. talk to it. voice notes all day (wispr), and an agent files every fact, story and decision 3. make a company brain. customers, calls, numbers, pricing, playbooks, past decisions and why you made them 4. record every call and meeting (granola). the transcripts go straight into the brain 5. keep a facts file. true things about you and the company that agents are allowed to say. this kills made-up claims 6. keep a voice file. your 50 best posts, 20 you hate, and the words you never use 7. put all of it in git (github) so every change has a history 8. write one instruction file at the top (CLAUDE.md or AGENTS.md). read these files before any task, never overwrite, always date 9. give agents memory across sessions so they stop starting from zero (claude-mem, mem0) 10. pipe every data source into one warehouse your agents can query (airbyte → clickhouse). ads, analytics, CRM, payments 11. feed it data nobody else has. it's the only part a competitor can't download the skills 12. don't start from zero. install the good ones first (anthropics/skills, obra/superpowers, mattpocock/skills, addyosmani/agent-skills) 13. grab the marketing ones too (coreyhaines31/marketingskills, cody schneider's graphed skills for static ads and UGC, boringmarketing dot com skills) 14. map every workflow in the company and rank them by money made or saved 15. do each one once while talking out loud, and record it 16. have an agent turn the recording into a skill. when to use it, the steps, the checks, the mistakes to avoid 17. one skill per job. small and boring beats one giant prompt 18. connect your tools with MCPs so agents can act and not only advise (gmail, slack, stripe, linear, notion, posthog, supabase) 19. give agents a browser (browser-use, vercel agent-browser, claude in chrome) 20. give agents a computer of their own for the tools with no API (vercel agent-desktop, orgo) 21. give your best skills away in public. it's the new lead magnet the agents 22. run an orchestrator that never turns off (grok bot, openclaw, hermes). it manages one agent per project, and each of those runs its own sub-agents 23. use coding agents for the building (claude code, codex, cursor, t3, antigravity) 24. wrap them in a harness so they plan, test and remember (ECC, superpowers) 25. manage the whole fleet in one place (paperclip). every agent gets a job, a budget and a log 26. put the skills on triggers (n8n, scheduled tasks). daily, weekly, on every new lead, on every cancellation 27. route your models (openrouter). the expensive one plans and checks (fable 5.2, gemini 4 carbon), the cheap ones do the volume 28. cut the token bill. shorter outputs, smaller tool results (caveman) 29. run a local model for the data that can't leave your machine (gemma 4) 30. track cost per job. if a job costs more than it earns, fix it or kill it the factory 31. build the line. spec agent → builder agents in parallel (git worktrees) → test agent → reviewer agent → deploy (vercel, railway) 32. design goes through the same line (paper MCP), and a skill strips out anything that looks AI made (unslop) 33. every annoying task in the company becomes an internal tool by the end of the day 34. every customer request becomes a pull request before a human reads it (tstack for the PR workflow) 35. reviewer agents with a named bar. "would the best team in the world ship this?" reject until the answer is yes 36. keep 50 real cases with the right answer. rerun them every time a new model drops and switch to the winner 37. humans approve, own the outcome and talk to customers. that's the 10% you keep the loop 38. every finished job writes back to the brain. what worked, what failed, what to stop doing 39. support tickets, analytics and social comments flow in every night 40. every friday an agent rewrites the playbooks from the week's results, and you approve the diff 41. every month, rank everything by profit per human hour. kill one thing and double one thing the growth 42. research with agents before you spend a dollar (perplexity API, last30days skill) 43. outbound runs itself. find the leads, enrich, verify, send (apollo, million verifier, instantly, phantombuster) 44. send prospects finished work in place of a pitch 45. ads run on a loop. an agent writes the creative, publishes through the facebook ads API, kills the losers and scales the winners 46. agents make the creative too. images (nano banana), video (heygen, fal), voice (elevenlabs), music (lyria 3.5, suno) 47. turn every finished job into content. the story, the number, the prompt 48. every customer makes the brain smarter for the next one. that's your network effect 49. once it works, point it at a new niche. same agents, new context The models are the same for everyone but your context is the only part that's yours. Acquire as much of it as you can, as fast as you can. Build loops like this. This is the whole game, happy playing.
1
60
made a full restaurant brand with AI in one sitting. logo, packaging, menu, food photo. no designer, no photo shoot. the brand is fake. Loco Taco doesn't exist. I wanted to see how far the workflow goes before pitching it to a real client. what surprised me: the hard part isn't the images. it's keeping 20 images looking like one brand. every restaurant needs new photos every time the menu changes. that's a service, not a one-off.
3
121
Halfway check: The plan vs. reality. Landing page: Made tweaks, hit a design bug, still stuck. Cold DMs: Sent 3, already ghosted on 2. New offer idea: Messy notes on paper, nothing polished yet. It's not smooth sailing. But progress isn't supposed to feel comfortable. It's supposed to feel real. I'll take messy momentum over fake perfection.
1
52
I'm going all in on HyperBrain Labs again. Last year I ran it as an MVP studio. ~$15K/month. 3 founders who came to me for an MVP are still on retainer a year later. Now it's an AI-native product studio. I help founders turn ideas and broken AI builds into production apps. I'm taking 4 new projects. Only 4. I'd rather ship great work than take every deal. Got an idea or a build that's stuck? My DMs are open."
HyperBrain Labs is back, and we're going all in. Last year we ran it as an MVP studio. ~$15K/month. 3 clients who came for an MVP are still with us on retainer a year later. Now we're an AI-native product studio, helping founders turn ideas into production apps. We're opening 4 slots. Only 4. We'd rather ship great work than take every project. Got an idea or a stuck build? DMs open."
52
the hard part of voice was never making it sound human. it's what happens after the call. booking written to the right calendar, the lead landing in the CRM, a human getting looped in when the agent isn't sure. letting teams fix their own agents is the right bet. nobody wants to file a ticket every time a script changes.
Retell just crossed $100M in revenue run rate. $10M to $100M in 17 months. Profitable. $4.6M raised. From day one, we’ve focused on solving the hardest parts of deploying voice AI in the product itself, so customers can build, manage, and improve their own agents without depending on us. Our bet: the future of the contact center belongs to the teams who run it. Proud of our team. Grateful to every customer who believed in us.
87
nobody argues postgres vs nosql anymore. the AI picks supabase and moves on. the new fight is whether RLS is on. on Lovable and Bolt rescues it's the first thing I check. usually it's off. picking the database got easy. the rules didn't. nitter.cf/thdxr/status/212102113…
remember a few years ago when you'd post shit like "nosql sucks just use postgres" what a different time
1
2
232
back to building full time. 30+ products shipped. one hit 50k users and went on Shark Tank India. now it's AI agents, AI tools, and MVPs again. AI writes the first draft. I still check auth, payments and webhooks by hand. what are you trying to build right now?
3
3
208
AI writes the first draft of every MVP we ship. I still check these by hand before anything goes live: > auth. log out, refresh, log in on a second device. this breaks more than you'd think > payments. close the tab mid-checkout and see what Stripe thinks happened > webhooks. fire the same one twice. if it makes two orders, it's not done > database rules. log in as user A and try to read user B's rows > error tracking. if nothing reports errors, you just don't know yet > ownership. client's repo, client's cloud, client's Stripe. day one 30+ products shipped and this list barely changes. what's the one thing you always check by hand before shipping?
1
4
249
226 of 739 calls our AI marked "talked" were voicemail machines. Vira, the voice agent in Revvox, now listens first, hangs up on the machine, and retries inside calling hours. What metric in your product turned out to be lying?
1
2
253
I'll build your startup's MVP for $2,999. Only 2 founders this month. SaaS, AI app, marketplace, internal tool. Live in ~21 days. Real login, payments, database. You own it all. 20+ products shipped. One went on Shark Tank India. Reply "MVP" and I'll reach out.
1
1
105
I looked at an app this week that looked finished. founder was ready to launch. it was not ready. what I found in 20 minutes: Stripe secret key sitting in the frontend RLS off. any logged-in user could read every row still on the Lovable domain webhook with no retry. one failed payment and the user never gets access auth dies on refresh the screens were perfect. that's the trap. AI builds the demo. someone still has to build the product.
4
117