Folio3 Software

After years of building software and leading teams, I'm pretty convinced that the code is actually the easy part. The harder stuff is understanding what's happening around the code. Communication structures. Planning biases. Team dynamics. The way incentives quietly shape every decision people make. https://lnkd.in/dDAM_p-B puts 56 of these principles in one place. Most of them I learned the expensive way. A few that become painfully obvious once you've led teams: Conway's Law. Your system architecture mirrors how your teams communicate. If two teams barely talk, there's probably a painful interface between their services. Brooks's Law. Adding engineers to a late project makes it later. Coordination costs are real, and they compound fast. I've ignored this. It didn't go well. Hyrum's Law. Every observable behavior in an API becomes someone's dependency. Including the bugs. Especially the bugs. The Ninety-Ninety Rule. The first 90% of the work feels fast. The last 10% is where all the integration mess, edge cases, and operational reality lives. Plan for two 90s. Goodhart's Law. Once a metric becomes a target, people optimize for the metric. Sprint velocity. Test coverage. All of them eventually get gamed. What I like about this collection is that it explains estimation failures, architectural decay, and why smart people still make bad technical decisions. The code part is almost never where things actually go wrong. Which of these has matched your experience most closely? #SoftwareEngineering #TechLeadership #EngineeringCulture #CareerGrowth

People think NetSuite development is just: “Create a field, write a script, done.” 😌 Meanwhile me at 11:47 PM: “Why is this User Event triggering the Scheduled Script… which updates the same record again… which somehow starts another process?” 😭 Client: “We only need a small customization.” NetSuite: “Cool. Here’s a 42-step approval process, 3 custom automations, 2 Map/Reduce scripts, 1 hidden client script, and a custom record nobody remembers creating.” ☕🔥 Being a NetSuite Technical Consultant is basically: ✅ Understanding business requirements ✅ Turning manual work into automation ✅ Debugging logic written years ago ✅ Explaining technical issues in simple language ✅ Staying calm during go-live week 😅 Somehow you become: Part developer 💻 Part consultant 📊 Part support engineer 🔧 Part detective 🕵️ Part firefighter during production issues 😂 But honestly… the best feeling is when a client says: “This process used to take hours. Now it happens automatically.” That’s the rewarding part of building ERP solutions. Still writing SuiteScripts. Still optimizing processes. Still tracking mysterious scripts from previous developers 👀 Facebook: https://lnkd.in/d393atdA Youtube: https://lnkd.in/d6UkK_Eb #NetSuite #SuiteScript #OracleNetSuite #ERP #Automation #TechnicalConsultant #DeveloperHumor #BusinessAutomation #TechLife

𝗗𝗮𝘆 𝟭6/𝟵𝟬 [𝗖𝗹𝗮𝘆 + 𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝗠𝗮𝘀𝘁𝗲𝗿𝘆] 𝗥𝗲𝘃𝗲𝗻𝘂𝗲: $𝟴𝟬𝟬 / $𝟴,𝟬𝟬𝟬 𝟭𝘀𝘁 𝗣𝗮𝘆𝗶𝗻𝗴 𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿: ✅ 𝗔𝗰𝗵𝗶𝗲𝘃𝗲𝗱 𝗝𝘂𝘀𝘁 𝗺𝗮𝗱𝗲 𝗺𝘆 𝗳𝗶𝗿𝘀𝘁 $𝟴𝟬𝟬. I've been sitting on this for a couple of days, waiting for the final kickoff call today. We've landed our 1st paying client. Within the first 3 weeks of joining the bootcamp. I've never done freelance or part-time work before. Never really pitched myself or my services to someone. And to be honest, it was nerve-wrecking. But here's what I've come to understand about first money: 𝗧𝗵𝗲 𝟭𝘀𝘁 $$$ 𝗮𝗿𝗲 𝗻𝗲𝘃𝗲𝗿 𝗮𝗯𝗼𝘂𝘁 𝗲𝗮𝗿𝗻𝗶𝗻𝗴. It's all about learning from the real-world use cases & the nuances that come with that. Your net worth is your network. And let me just say - the Clay Bootcamp 🥾 network is transformational. I found the opportunity within the community, reached out, and it clicked. I had my first sales call on Monday. Took him through some of my portfolio - a couple of n8n workflows, Clay tables - answered a few questions around my GTM thought process, and just chatted casually about GTM. "You've got the personality, technical skillset, and ambition that I need." Not sure what he saw - but a compliment never hurts. 😄 Before the kickoff call, I got a few minutes with Nathan Lippi 🥾 for a quick gut-check. His advice was simple: Deliver value; and that's exactly what we're aiming for! So - we're in official building season now. Up until today, I was documenting coursework, assignments, and learnings. Now? We enter real-world scenarios. Actual tooling in production. Building and running live outbound systems for a real client. I'll be honest — this feels really good. $800 won't get me to $8K. I know that. But milestone #1 is checked - getting the first client through the gates. I'm fixated on delivering excellence. You help the client grow, serve his clients better - and the monetary reward follows. That's what matters. The rest follows. One step at a time. Stay tuned. The journey is becoming interesting now. 🚀 ------------------------------ ♻️ If you're a founder or GTM lead exploring outbound, Clay workflows, or AI-powered lead gen - I'm building this entire engine in public. Follow along or reach out directly. #buildinginpublic #claybootcamp #claudecode #GTMEngineering #outbound #firstclient #GTM

𝗜 𝘄𝗮𝗹𝗸𝗲𝗱 𝗮𝘄𝗮𝘆 𝗳𝗿𝗼𝗺 𝗺𝘆 𝗳𝗶𝗿𝘀𝘁 𝗽𝗼𝘁𝗲𝗻𝘁𝗶𝗮𝗹 𝗰𝗹𝗶𝗲𝗻𝘁 𝘁𝗼𝗱𝗮𝘆. And honestly? It felt like the right call. 𝗗𝗮𝘆 𝟭𝟱/𝟵𝟬 [𝗖𝗹𝗮𝘆 + 𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝗠𝗮𝘀𝘁𝗲𝗿𝘆] 𝗥𝗲𝘃𝗲𝗻𝘂𝗲: $𝟬 / $𝟴,𝟬𝟬𝟬 𝟭𝘀𝘁 𝗣𝗮𝘆𝗶𝗻𝗴 𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿: 𝗧𝗮𝗿𝗴𝗲𝘁 = 𝟯𝟬 𝗱𝗮𝘆𝘀 𝗔𝗰𝘁𝗶𝘃𝗲 𝗖𝗼𝗻𝘃𝗲𝗿𝘀𝗮𝘁𝗶𝗼𝗻𝘀: 𝟯 Until last week, I was staring at zero progress on client acquisition. No conversations. No momentum. Nothing. However, it flipped this week. I'm talking to 3 closable deals. All referral and LinkedIn outreach. Zero ad spend. One of them came from a cold LinkedIn message I sent on a whim to a founder. Just typed it out, hit send, moved on. That turned into a real conversation about building their outbound motion - SaaS AI chatbot, strong TAM, solid offer. But here's where it fell apart. The founder wanted results before investing in the tools and infrastructure needed to actually get those results. It's like hiring a chef - and telling him to bring his own ingredients, his own knives, and his own kitchen. Then you'll decide if he's worth paying. I had to walk away. Hurts, but I got to learn a lot in the process. - How to price myself - How to negotiate with a prospect - How not to quote rates upfront before understanding their AOV, CLV (thanks Azam Ali 🥾 for sharing this), My mentor Bharat Devana 🍁 reframed it perfectly: "Getting a cold lead to the edge of closure - that's a milestone in itself". So I'm taking that. Small wins compound. Yesterday, I also got to connect with Sameer Malla Thakuri - the man ran outbound for the #UFC and was pushing 3M+ emails/month. The guy is an email deliverability wizard. Here's what I took away from that conversation: On email infrastructure: • Inboxkit is the most sought-after all-in-one email infra platform right now - buy domains, spin up inboxes, and integrate directly with your sequencer. One platform. No duct tape. • The golden rule: no email goes out before a 14-day warmup minimum. Skip this and your deliverability dies before your first campaign. • Monitor health everyday: If health falls below 95, put your inboxes to rest The best learning approach is by doing. Next up: I'm setting up my full email infrastructure so campaigns can actually go out. The system is coming together. Slowly. ---------------------------- ♻️ If you're a founder or GTM lead exploring outbound, Clay workflows, or AI-powered lead gen — I'm building this entire engine in public. Follow along or reach out directly. #buildinginpublic #claybootcamp #claudecode #GTMEngineering #outbound #emailmarketing #emaildeliverability #coldoutbound

Most students don’t have a career problem. They have an exposure problem. And most institutions know it — but very few are doing something real about it. That’s why our recent leadership meetup with Mirchawala Institute at Folio3 Dynamics was different. This wasn’t a “let’s collaborate” conversation. This was about fixing the gap between education and actual careers. What we’re building through the Folio3 ERP Center of Excellence (CoE) is simple in idea… but powerful in impact: 👉 Stop guessing careers 👉 Start building them early 👉 Align students with roles that actually exist And the energy in the room made one thing clear — This is going to move fast. A big thank you to Mustafa Mirchawala , Soban Mirchawala (already shaping strong student narratives), and Moghirah Farooqui for making this happen. Great alignment from Folio3 leadership — Muhammad Fahad , Messum Ali Zaidi , Danish Ali Malik (FCCA) , along with Yasir Rahim , Muhammad Hammad Rasheed , and Muzzamil Zahid — as we push this forward with focus. #Folio3 #ERP #CenterOfExcellence #FutureCareers #IndustryGap #Students #Leadership #FunctionalConsulting #CareerBuilding

[𝗗𝗮𝘆 𝟭/𝟵𝟬 - 𝗖𝗹𝗮𝘆 + 𝗖𝗹𝗮𝘂𝗱𝗲 𝗖𝗼𝗱𝗲 𝗳𝗼𝗿 𝗚𝗧𝗠 𝗠𝗮𝘀𝘁𝗲𝗿𝘆] 𝗣𝗿𝗶𝗺𝗮𝗿𝘆 𝗚𝗼𝗮𝗹: Onboard my first client in first 30 days 𝗥𝗲𝘃𝗲𝗻𝘂𝗲 𝗚𝗼𝗮𝗹: $0 --> $8k Started getting accustomed with using Slack. Always been a Google Chats user. I've went through some of what the gurus & serious GTM engineers in the Clay Bootcamp 🥾 community have been talking about, It sucks to admit... marketing teams are at risk. The potential Claude Code brings to business, is limiteless. It can read, edit, create, or delete files, run commands through terminal, fix its own mistakes, and connect to external services (Apollo, Clay, smartlead, etc) - all from your windows terminal. This sentence from Tanay Mishra 🥾 in our 1st Claude Code Bootcamp lecture, stuck with me : "Claude code with Opus 4.7 is a glimpse of AGI" Nonetheless, All of this only sounds like all of it is already here. Truth is, organizations are still operating the same way, with or without the shiny tools. Many are still evaluating their move to Clay and CC adoption is still in early stages. In the first lab, we built personalized landing pages for a list of prospects based on an ICP, company value props, and brand guidelines, and deployed directly on Vercel - Ready to be distributed. Here's how it works: • Create a claude.md file in your directory. • Add supporting docs (ICPs, prospects list, Brand guidelines, value props, etc). These work as brain cells, claude. • Create front-end-design skill in claude from github. • Prompt naturally, as detailed as possible, following the 𝘴𝘰𝘤𝘳𝘢𝘵𝘪𝘤 𝘲𝘶𝘦𝘴𝘵𝘪𝘰𝘯𝘪𝘯𝘨 method • Create a free account on Vercel and CC handles the rest. 𝘚𝘰𝘤𝘳𝘢𝘵𝘪𝘤 𝘘𝘶𝘦𝘴𝘵𝘪𝘰𝘯𝘪𝘯𝘨 (Pro tip): Before building anything, ask claude to ask you 5 questions to really understand what needs to be built. Helps save valuable iterations. This was just catchup on a missed session. Only about to get more messy, more intense, and technical from here on. A lot to consume. Lets make it worth it! #buildinginpublic #claybootcamp #claudecode #GTMEngineering #outbound #AI

#TDF #MagnifiScience centre, Pakistan's first contemporary and interactive science centre designed to provide hands-on learning experiences to people of all ages and backgrounds. I visited with my family TDF Science Museum and had a genuinely enjoyable experience. The exhibits were interactive and well-designed, making complex ideas easy to understand. I found the experience both educational and engaging.The museum was clean, well organized, and the staff was courteous and helpful. I appreciated how the content encouraged curiosity and learning without feeling overwhelming. Overall, I had a very good time and would recommend TDF Science Museum to students, families, and anyone interested in science. Source: The Dawood Foundation https://lnkd.in/dgs3aw26

I just revamped #KarachiPulse : my civic tech web app for Karachi residents using Anthropic 's newly launched Claude 's Design feature. 🎨 For context: KarachiPulse is a platform I've been building to solve real civic problems which includes live traffic maps, local infrastructure updates, neighborhood pulse checks. The functionality was solid. But the UI? It needed a serious upgrade. Here's what happened when I described my vision to Claude Design: → It understood the context (civic, urban, Karachi-specific) → Generated a full visual direction including color palette, layout hierarchy, card systems → Produced production-ready, responsive UI that actually felt local and intentional → Iterated in seconds when I pushed back on anything What used to take days of back-and-forth with a designer, or hours fighting Figma, happened in a single focused session in a few minutes. This isn't just a faster workflow. It's a fundamentally different one. As engineers, we've always had to either learn design ourselves, wait on designers, or ship "good enough" UIs. Claude Design collapses that gap entirely. If you're an indie dev, a startup founder, or just someone with a side project collecting UI debt, try Claude Design. Your idea deserves to look as good as it works. 🚀 #ClaudeAI #AIDesign #IndieHacker #KarachiPulse #ProductDesign #iOSDev #BuildInPublic #Anthropic

A week ago, I bought Claude Pro to build alongside Tanay Mishra 🥾 in his "Claude Code for GTM" workshop. Heather Melton was kind enough to help me out, but I just couldn't get it set up in my terminal. So I just used it like a glorified ChatGPT. Completely missing the point. Yesterday, a friend finally helped me set it up properly. And within minutes - I understood what all the noise was about. I ran one experiment. Gave it a simple starting point. And just… watched. It didn't ask me what to do next. It didn't need guidance. It reasoned, planned, and executed - completely on its own. The output was something I would have hours trying to coordinate manually. Done. Autonomously. In one session. It wasn't AI assisting me anymore. It was AI working for me. Still just scraping the surface and it's already this powerful. The possibilities are unlimited. #ClaudeCode #GTM