Priyesh Tiwarkar's Linkedin Analytics

An agency friend messaged me mid-meltdown: “Priyesh, I’m drowning in tools. ClickUp for tasks, Notion for docs, Sheets for ops, Toggl for time, Stripe for payments... Isn’t there one thing that can just do it all?” The truth? It’s not a tool problem. It’s a workflow problem. What you need is a system built around how you work. Not 5 tools duct-taped together. So we built him one. In just 23 days, we shipped a fully custom ops + task management tool built entirely around how his agency actually runs. Here’s the exact stack we used: – Notion to map flows – Figma for the UI – Cursor + V0.dev for the frontend – Supabase for auth, DB, APIs – Xano for backend logic – Stripe for billing – Zapier, Make & Supabase Edge for automation No fluff. No chaos. Just one clean system. If you’re building something for your team or your clients, this stack works. Period. Want the exact prompts we used with Cursor + V0? Comment TOOLSTACK, and I’ll send them over.

I almost gave up on my business 3 years ago. Here’s what changed my mind… Back in 2021, I just started 12th grade. I was 16, excited to start freelancing, but had no idea how to land my first client. So, I started doing the only thing I could think of: posting videos on Instagram showing the websites I was building. Five months went by. Zero clients. I worked with two people during that time, but it was all unpaid just to build a portfolio. Those five months crushed my self-confidence. I felt stuck. Hopeless. I seriously thought about quitting freelancing and just settling for a mediocre life. Then one day, I was talking to a friend and she said something that changed everything: “You’ve already put so much into this, don’t give up now. What if you’re just one step away from landing your first client?” That image of someone digging and stopping just before hitting the diamond? That was me. So I pushed through. Recommitted to my goals. And in October 2021, I finally landed my first paying client. The rest is history. If you’re feeling stuck right now, just know this: You don’t need to be perfect. You just need to keep going. Have you ever thought of giving up on your dreams?

I’m building a $25k software for a Brewery Reward Company

This video will change how you think about AI One of the most insightful episode of The Diary of a CEO with Raoul Pal and Steven Bartlett

The Exact Process we used to Build an $80K AI-Powered POS System

What if I told you two college students just raised $5.3M… It’s called Cluely AI, built by ex-Columbia students Chungin Lee and Neel Shanmugam. Here’s what it does: 👉 Reads your screen 👉 Listens to the conversation 👉 Gives you live, AI-powered suggestions in meetings, interviews, and calls No one sees it. No one hears it. But you get real-time support, like having a strategist in your ear. That’s not just AI. That’s experience on demand. From a builder’s perspective, this is genius. They didn’t try to replace jobs or disrupt entire industries. They zoomed in on a micro-pain: "People freeze in high-stakes conversations." And they solved that. No fluff. No feature bloat. Just pure utility + clean UX. As someone who's shipped MVPs for startups across industries, here’s what I take away from Cluely’s rise: Solve one pain. Nail it. They didn’t build a dashboard. They built a whisper. You don’t need a complex product. You need a high-context, low-friction experience. Speed still matters. Build. Ship. Iterate. Let the users do the talking. Be unforgettable. Nobody forgets a tool that feels like superpowers. I’m not here to debate ethics. I’m here to applaud clarity of vision. This is what happens when execution meets imagination. For all the founders building tools right now Look at Cluely not just as a product… But as a framework. Solve a very specific problem. Make it feel magical. Deliver it invisibly. The future isn't just AI-powered. It's AI-augmented humans, and that’s where the magic is.

Let’s redesign Trybe Inc's Landing Page! Problem I noticed: - Low conversion & unclear value proposition - Outdated design with poor first impression - Weak CTA placement & confusing navigation - Not aligned with luxury + exclusive event branding How I solved it: - Focused on user journey + founder mindset - Reimagined the color palette and brand identity - Sketched wireframes to map out the new flow - Designed a modern, clean, conversion-focused website Expected results: - Increased applications from ideal founders - Stronger brand positioning for high-ticket events - Clearer messaging leading to higher trust - Simplified journey = reduced bounce rate - Elevated perception: premium event for elite CEOs If you want a website that actually sells and connects with your dream audience, book a FREE strategy call with me (link in comments). P.S. Designers & founders, what do you think? 👀

I'm speechless. I built this landing page in 10 minutes using v0.dev. What would’ve taken my team 3 days, took me less time than a coffee break. No Figma. No code. No team chaos. Just one prompt → clean, working UI. And here’s the thing: I didn’t expect it to work this well. As someone who’s built 100+ pages manually, I’ve always believed in good design, user flow, and clarity. But tools like V0 are changing the game. Not because they replace designers or devs. But because they help you get to version 1 faster than ever. If you're a founder or builder trying to validate fast, this is gold. This is the exact prompt that I used: "Let's build a landing page for my saas that is an AI Business Consultant Voice assistant for business owners and freelancer,s and keep them modern and minimalist, and let's do one by one sections ( to maintain the stile guide ) use Purpule and blues as the color pallet and gradient of it"

Gary Vaynerchuk's $1.80 strategy made me more money than any cold email ever did. When I first heard about it, I thought it was just a clever social media growth hack. But it turned into a mindset shift I still carry every day. What is the $1.80 strategy? It’s simple: - Leave your “two cents” (thoughtful comments) on 90 pieces of content every day. - Not to promote yourself. Not to sell. - But to give value first consistently and generously. It changed my business: I stopped waiting for clients to ask for help. If I knew they’d need something, a tool, a suggestion, an extra deliverable, I gave it without hesitation.  No upsell. No conditions. Just help. And you know what? It built trust. It deepened relationships. And yes, it brought more opportunities than I expected. It also changed my life: That mindset carried over into everything. I listen more. Share more. Offer help before it’s needed. Because giving first feels better and works better than just looking out for myself. Give more than you take. Show up with value first. In business and life, that mindset compounds. If you’ve used this strategy (or something similar), I’d love to hear what changed for you. Drop your story in the comments.

I still remember the first real MVP I built for a client. It was supposed to be simple. A basic tool that helped restaurant owners manage table reservations. We scoped it, designed it, and started building fast. But a few days in… it started crumbling. Not because of bugs. Not because of code. But because of assumptions. We assumed we knew what the user wanted. We assumed the client had clarity. And we assumed speed = success. 🚨 Red flag 1: The core feature made sense to the client, but not to the actual end users. 🚨 Red flag 2: The client kept changing priorities mid-build, which meant rebuilding flows. 🚨 Red flag 3: We didn’t map the user journey properly. Buttons led nowhere. Flows felt confusing. It was humbling. I paused everything. Called the client. And we rebuilt the plan from scratch together. Instead of building what we “thought” was right, we went back to: – Who exactly are we building this for? – What’s the one problem we solve for them? – What’s the bare minimum they need to get value? We stripped it down to the essentials. Skipped the fancy UI. Focused on flow, clarity, and usability. And guess what? That MVP got the first paying customer in week 2. Lesson? "Your first MVP probably won’t be perfect. But it can be directionally right, if you obsess over the user, not the feature set." Since then, I’ve built dozens of MVPs faster, cleaner, and more strategically. But I’ll never forget that first near-failure. It taught me the one rule I still follow today: Build less. Solve better. Ship smarter.

Our client closed his first seed round of $350,000 with our MVP. A few months back, a founder reached out to me in a bit of a panic. He had an investor meeting scheduled in just two days, but he didn’t have a working product. No MVP. No demo. Just an idea. His concept? An AI-powered assistant for small businesses think of it as a virtual consultant that could help make better decisions by analyzing all available data and resources. He needed someone who could not only build fast… …but build something that actually worked. So we jumped on a discovery call right away to understand the need for the product. And made a quick plan that we will be following - Wireframes to lay out the app structure and get instant approvals - User flow to define how users would move through the product - Mood boards to align the branding and visual direction - Core feature development, where the actual functionality came to life All with one single aim of launching in just 24 hours. To speed up development: - We used Cursor for the front end - Supabase for the backend And connected it all with OpenAI’s real-time APIs to power the AI assistant And yeah...we made it happen. A working MVP that actually works, just built in 24 hrs And the result? He walked into that meeting and closed his first seed round: $350,000. Sometimes, speed isn't the enemy of quality, it’s what brings the idea to life. And when the pressure is on, the right process, team, and tool can make magic happen. If you're a founder who’s racing against time and needs a real product, not just slides, you know where to find me.

If I had to build an MVP tomorrow, I wouldn’t Write Code. I’d Use AI Founders ask me all the time: “Should I learn to code or just use AI to build my MVP?” Here’s my honest take: If you’re starting from scratch… writing 1,000+ lines of code, setting up folders, auth, configs manually… You’re already behind. I don’t say that to offend you, I say that because time is your most expensive resource when you’re validating. This is where using AI tools comes in. Not as a shortcut. But as a strategy. Using tools like Cursor, V0.dev, Supabase, and GPT-4o, you can get a working base up in hours, not weeks. Which gives you time to focus on what actually matters: → Talking to users → Launching fast → Iterating faster → Finding product-market fit Now don’t get me wrong You still need to understand structure. If you don’t, your stack will collapse the moment it needs to scale. But here’s the truth: AI won’t replace devs. The devs (and founders) who use AI will replace the ones who don’t. The best founders I work with? They don’t obsess over perfect code. They obsess over shipping the right product fast. That’s what’s working in 2025. Not hype. Just speed, clarity, and action. Would you try AI tools for your next build? Drop your take in the comments.

I redesigned the website of the #1 Home Sleep Test Provider, Blackstone Medical Services When I first landed on it, it didn’t feel like a wellness website. It was outdated, hard to navigate, and lacked the calm, clarity, and reassurance someone struggling with sleep might need. So I gave myself a challenge: what if their site actually felt like the amazing service they offer? Here’s what I focused on: – Simplifying the layout so it’s easy to follow – Using clean, soft visuals to match the tone of wellness – Bringing trust signals (like testimonials and ratings) to the front – Rewriting the messaging to sound human – Giving everything more space to breathe Before: the site made people work too hard to get what they needed. After: it guides them with clarity and builds trust in seconds. In wellness, your site is often the first place people go for help, so it should feel helpful. If your product makes people feel better, your website should too. Would love your thoughts on the redesign and if you’re building something similar, happy to chat.

Our Client’s Website Was Almost Hacked One of our clients recently installed a plugin while making some changes to their website. What they didn’t realize was that the plugin they installed was laced with malicious code. It injected malware into the site, putting customer data at risk and threatening a complete site failure. Had we not intervened in time, the estimated damage could have easily exceeded $2,000 in recovery costs alone. Here’s What We Did Immediately: - Identified and diagnosed the source of the malware - Removed the infected plugin and malicious code - Rolled the site back to a clean, secure backup - Patched all existing security vulnerabilities - Strengthened defenses to prevent future breaches The Outcome? - Crisis averted - Over $10,000 in potential losses saved - No data loss - Zero downtime The Lesson? Regular Website Maintenance Is Not Optional. This is what most people overlook: - Outdated plugins and themes can introduce serious security risks - Browser updates often cause layout or formatting issues - Adding new content or features requires clean implementation - Infrequent maintenance leaves your site wide open to threats How We Protect Our Clients Every Single Month - Full website and activity reporting - Safe testing and application of all plugin/theme updates - Performance checks and layout consistency reviews - Proactive monitoring and patching of security vulnerabilities Yes, your website needs regular updates. But more importantly, it needs to be done right. Because cutting corners on maintenance today could cost you a whole lot more tomorrow.

Even our first customer support agents had stock options. They all made a million dollars.” That one line from Taavet Hinrikus changed everything for me. It wasn’t about the money. It was about how much he valued his team, especially the people closest to the customers. That mindset shaped how I lead. I don’t have a billion-dollar company (yet), but I do everything I can to take care of my team. That means: - Giving them a real learning budget (books, courses, events, no approvals needed). - Sharing context openly: goals, decisions, what's working, and what's not. - Making sure they have the tools and trust to do their job. - Creating clear and realistic paths for growth. - Finding ways to give ownership, even if I can’t offer equity (yet), I find other ways to make the wins feel shared. People do their best work when they feel supported and involved. That’s the culture I’m trying to build, and I’ve seen firsthand how much it pays off. If you're building something, don't just invest in the product. Invest in the people building it. If you lead a team, I’d love to hear one thing you do that actually makes a difference. Drop it in the comments

“We paid $20,000 for this software… and it doesn’t even work.” A founder reached out to me and told me this! They had built an AI-powered software tool to manage client work, automate approvals, and streamline delivery. But instead of fixing their workflow, it broke it. Even worse, the dev team they hired? Vanished after shipping a half-baked product. No support. No roadmap. No fixes. $20,000 down the drain. When we got involved, we realized: The problem wasn’t just the product. It was how they chose their agency. Here are 5 common mistakes that companies make when choosing a dev team, mistakes that cost this one $20K: 1) No due diligence – They didn’t vet the agency’s past work or ask for references. 2) No clarity on scope – Requirements weren’t documented, so expectations kept shifting. 3) Overpromised timelines – The agency said yes to everything to win the deal. 4) No testing process – They focused on design and delivery, not usability testing. 5) No accountability – Post-delivery support? Missing in action. How to Prevent This Trap?  If you're planning to build a custom tool, take this advice seriously: - Don’t pick an agency based on price or promises; test their process. - Start small. Build to learn, not just to launch. - Focus on user behavior, not vanity metrics. - Stay close to your internal team; they are your best testers. If you’re building right now, don’t make the same mistake. Start small. Stay close to your users. Build to learn, not just to launch. You’ll save money, time, and a whole lot of stress.