Janis Zech
Berlin Metropolitan Area
49K followers
500+ connections
View mutual connections with Janis
Janis can introduce you to 10+ people at Weflow
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Janis
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
About
Previously grew Fyber from $0-76M ARR. Now scaling Weflow.ai, a Revenue AI Platform used…
Articles by Janis
-
Why RevOps should become the AI Orchestrator of the GTM Org
Why RevOps should become the AI Orchestrator of the GTM Org
TL;DR Soon, every revenue team will be built around humans and agents working together. But someone needs to own these…
109
33 Comments
Activity
49K followers
-
Janis Zech shared thisLast month, the CRO of a $47M ARR logistics SaaS reached out to us: “We have no deal visibility. No surprise, 38% of our opps slipped last quarter." He was on edge about missing another quarter. Here's how we fixed it in 3 steps: 𝗖𝗢𝗡𝗧𝗘𝗫𝗧 - $47M ARR - SaaS for the logistics industry - Selling to MM ($10-60k ACV) & ENT ($60-500k) We mapped 3 key reasons why they struggled with visibility. (& how we solved them with her RevOps team): 𝟭. 𝗠𝗶𝘀𝘀𝗶𝗻𝗴 𝗯𝘂𝘆𝗲𝗿 & 𝗼𝗽𝗽𝗼𝗿𝘁𝘂𝗻𝗶𝘁𝘆 𝗮𝗰𝘁𝗶𝘃𝗶𝘁𝘆 𝗱𝗮𝘁𝗮 Reps manually logged emails & meetings from Outlook (if at all). Problem: - Attachments were not logged in SFDC - 55% of deal contacts missing - 74% of meetings missing - 62% of emails missing Impact: - Unclear activity velocity (active vs. stalling) - Last activity date field not populated - Next meeting scheduled not visible - Unclear email reply rates RevOps also couldn't analyze funnels or closed-won patterns. Fix: We implemented Weflow's Activity & Contact Capture solution to auto-capture emails and meetings and map them to the right opportunity. 𝟮. 𝗠𝗶𝘀𝘀𝗶𝗻𝗴 𝗠𝗘𝗗𝗗𝗜𝗖𝗖 𝗱𝗮𝘁𝗮 Their reps were expected to follow MEDDICC. They used a variation depending on the buyer (MM vs ENT). Problem: - Low MEDDICC adoption - ≈43% of MEDDICC fields in SFDC were empty Impact: - No deal visibility - Hard to coach reps on deals - Late-stage surprises kept killing deals Fix: We started by fixing their data first. - Complete CRM data = more visibility - Better data = better MEDDICC coaching - Better visibility + coaching = less deals slipped We implemented two things: - Weflow's AI notetaker that auto-populates SFDC key fields (like MEDDIC, next steps..) from call transcripts. - Weflow's AI Playbook that looks at all emails, meetings, call transcripts and objectively evaluates if MEDDICC criteria are met. 𝟯. 𝗡𝗼 𝘃𝗶𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗶𝗻𝘁𝗼 𝗯𝘂𝘆𝗶𝗻𝗴 𝗰𝗼𝗺𝗺𝗶𝘁𝘁𝗲𝗲 Selling to logistics companies meant multi-threading across operations, procurement, IT, legal and finance. But no one had a clear picture of who was engaged. They ran long 1-1s & deal reviews to see if deals were multi-threaded and if a path to power existed. Problem: - Reps didn't add contacts to Salesforce - Contact roles were incomplete or missing - New stakeholders/contacts entered email threads and meetings, but they didn't make it into Salesforce Impact: - No visibility into buying committee - Couldn’t track stakeholder engagement - No way to confirm if reps had access to power Fix: We covered this with the activity capture solution (see point 1), which automates contact creation and contact roles. -- PS: 300+ B2B revenue teams use Weflow to automate Salesforce data hygiene with AI and get better deal visibility. DM for your free trial or learn more: Weflow(.)ai
-
Janis Zech shared thisEveryone in RevOps loves the Revenue Bowtie. Here's 27 Claude skills I’d build for each of its 7 stages: 𝟭. 𝗔𝘄𝗮𝗿𝗲𝗻𝗲𝘀𝘀 - /ICP scoring: tiers accounts on firmographic, technographic, intent and timing signals. - /Visitor-to-account: matches deanon web traffic to target accounts and roles. - /Signal scoring: rolls hiring, funding and exec-movement signals into one "in-market now" score. - Data enrichment: enriches account data via a multi-source waterfall. 𝟮. 𝗘𝗱𝘂𝗰𝗮𝘁𝗶𝗼𝗻 - Sequence writer: writes the full multi-touch sequence for a segment, in your voice. - Outbound play builder: designs the whole play - channels, cadence, branch logic for each buyer. - Personalized opener: writes the opener and angle per prospect. - Reply and intent classification: tags inbound replies and routes them. 𝟯. 𝗦𝗲𝗹𝗲𝗰𝘁𝗶𝗼𝗻 - Conversation intelligence: pulls the MEDDICC data from call transcripts. - Qualification copilot: runs discovery and qualification against SPICED and MEDDICC the same way for every rep. - CRM data capture: writes fields, next steps and close dates back to the record from the call. - Objection handling: six-category objection taxonomy plus battlecards for live calls. 𝟰. 𝗠𝘂𝘁𝘂𝗮𝗹 𝗖𝗼𝗺𝗺𝗶𝘁 - Pipeline intelligence: scores every open deal against stage exit criteria. - Deal inspection: flags late-stage deals slipping or single-threaded before the forecast call. - Deal desk and CPQ guardrails: structures pricing, discounts and proposals inside your guardrails. - Forecasting and analytics: models pipeline velocity, win probability and closed-won ranges. - Security and legal acceleration: drafts security questionnaires and first-pass redlines from your templates. 𝟱. 𝗢𝗻𝗯𝗼𝗮𝗿𝗱𝗶𝗻𝗴 - Success plan copilot: builds the 30/60/90 success plan and tracks activation milestones. - Early health and risk signals: watches first-30-day usage and flags a stalling new account. - Support triage: classifies and routes tickets and surfaces the blocker early. 𝟲. 𝗥𝗲𝘁𝗲𝗻𝘁𝗶𝗼𝗻 - Renewal risk and forecast: scores each renewal and forecasts the number. - Voice of customer and sentiment: reads calls, tickets and reviews for sentiment themes and named risks. - Health scoring: turns signals into a health score with early warnings. - Executive and stakeholder coverage: maps the buying committee and flags accounts with no exec relationship. 𝟳. 𝗘𝘅𝗽𝗮𝗻𝘀𝗶𝗼𝗻 - Up and cross-sell scoring: reads consumption and seat data for accounts ready to grow and names the play. - Product-usage signals: turns product telemetry into "who hit the expansion trigger this week." - Advocacy mining: mines calls and tickets for happy customers, references and case-study candidates. RevOps, any skills you’d add to this list?
-
Janis Zech reposted thisJanis Zech reposted this"Going regional" sounds like an org chart change. It's really a bet on whether RevOps can hold the GTM engine and company together. I've now lived that bet twice. First at Signifyd, and now at Aircall. Two months into my VP RevOps role here, I sat down with Janis Zech (CEO and Co-Founder at Weflow) on the RevOps Lab podcast to talk it through. Last week at Dreamforce, I finally got to meet him in person too! Here's what I keep relearning... When you shift from a global functional model to regional GMs, each region starts running its own P&L. AMER, EMEA, APAC, and our Global Small Business. That's the point of the model. It's also the risk. One company can quietly split into four. So RevOps has to operate like a product org. Our product is the GTM operating system (e.g. lead scoring & routing, capacity modeling, signals-based command centers, sales process, forecasting). And our mandate is to be the "glue" that holds the GTM engine together. Not just the glue between marketing, partnerships, sales, and CS like before. The glue between the GMs themselves. Shared definitions, shared stages, one forecast methodology, so it all still rolls up to a single number we can all take to the board. Set the standard globally. Calibrate locally. Be the connective tissue in between. That's the balance I'm most focused on getting right at Aircall. How are you keeping your company aligned across regions? Full podcast episode here: https://lnkd.in/dyG5tiNu
-
Janis Zech posted thisAfter talking to 50+ RevOps leaders last week at Dreamforce, here is what I believe will become the modern RevOps playbook: 1) Marketing Ops - merging with GTM engineering. Using signals is table stakes. Go deeper into signal stacking and read how in-market an account is, how strong the intent is. Route budget to accounts most likely to convert instead of spraying spend across everyone who triggered a signal. 2) Sales Ops - biggest priority is automating non-selling tasks, esp CRM updates. Solve for capturing and mapping activity data. Driving consistency across methodologies (MEDDPICC/MEDDIC…) is crucial. Understand which criteria are usually missed/are not consistently adhered to. 3) CS Ops - Use data to mine expansion/renewal signals and continuously monitor health scores. Use similar data and signals as Sales Ops but for onboarding, expansion, and renewal. More CS orgs are now running like sales teams, with the same rigor on pipeline and forecast. 4) Enablement - shifts from point-in-time to continuous. The once-a-year SKO is dead. AI can now continuously show you what great looks like. Mirror that across the entire revenue org. Use AI tools to track progress in discovery quality, methodology adherence over time. Sharing progress helps show quantifiable impact, which wasn’t possible before. 5) Systems - the job is building a unified data layer. Combine structured and unstructured data into a single layer. That layer is what makes AI orchestration possible. Governance is now about both humans and agents. 6) Deal Desk - AI takes the repetitive 80% of redlining. Deal Desk moves upstream so value engineering and business cases can happen much earlier in the sales cycle, without potentially relying on discounts. With this, deal desk sits much closer to forecast and headcount. 7) Leadership - Differentiate high-impact projects from all the AI slop and execute on them. Stakeholder management, alignment, and change management will be most crucial as you execute these projects. 8) GTM Engineering - Whether we like it or not, GTM Engineering is/will be a part of RevOps. Right now, it is focused on outbound and a little bit of marketing, but the goal is to use it across the customer journey. The analyst role is getting absorbed into GTM engineering. 9) AgentOps - New job for RevOps. Goal: to help govern agents, monitor consumption, and curb agent costs across the GTM org. As RevOps becomes the AI orchestrator of the GTM org, this becomes a core part of the RevOps JTBD. Which of these are you already seeing in practice today?
-
Janis Zech shared thisAI agents are about to create an entirely new role inside RevOps. 𝗠𝗼𝗹𝗹𝗶𝗲 𝗕𝗼𝗱𝗲𝗻𝘀𝘁𝗲𝗶𝗻𝗲𝗿, VP RevOps at ZoomInfo (1B+ ARR), just gave me a glimpse of what it could look like: She calls it AgentOps and believes it could change the entire RevOps function in the next 2-3 years. Naturally, I had to get her on the pod and bombard her with questions about this new role. Here’s a peek at what she told me: 𝟭) 𝗙𝗶𝗿𝘀𝘁, 𝗪𝗧𝗙 𝗶𝘀 𝗔𝗴𝗲𝗻𝘁𝗢𝗽𝘀? The way DevOps owns software uptime, AgentOps owns AI agents' daily health. The role covers: 1) monitoring agents to see if something’s broken, 2) running QA, 3) tracking consumption against a budget. The job also has a strategic angle: deciding which parts of a process humans own vs. agents. 𝟮) 𝗗𝗼 𝘄𝗲 𝗿𝗲𝗮𝗹𝗹𝘆 𝗻𝗲𝗲𝗱 𝗮 𝗻𝗲𝘄 “𝗼𝗽𝘀”? We do. In 2026, Companies pushed AI adoption by asking everyone to "just use AI". While it helped drive adoption, it also created chaos. Everyone now has their own agents, but there’s no central view of what’s deployed, what’s (not) working. Agent ops will be that central role in the GTM, that governs the entire agent setup in companies. 𝟯) 𝗔𝗿𝗲 𝘄𝗲 𝗵𝗶𝗿𝗶𝗻𝗴 𝗮 𝗻𝗲𝘄 𝗽𝗲𝗿𝘀𝗼𝗻 𝗳𝗼𝗿 𝘁𝗵𝗶𝘀 𝗿𝗼𝗹𝗲? For now, Mollie doesn't see a net-new "Agent Ops Manager" hire. Rather, she sees this as a skill landing on the operators who love to build (which I know most operators do). You still define, monitor, iterate, and control the process. One layer of it just runs on an agent now instead of a person. 𝟰) 𝗗𝗼𝗲𝘀 𝘁𝗵𝗶𝘀 𝗿𝗼𝗹𝗲 𝗵𝗲𝗹𝗽 𝗥𝗲𝘃𝗢𝗽𝘀 𝗽𝗿𝗼𝗴𝗿𝗲𝘀𝘀 𝗶𝗻 𝘁𝗵𝗲𝗶𝗿 𝗰𝗮𝗿𝗲𝗲𝗿? Absolutely. The future GTM org will combine humans and agents to execute tasks. RevOps folks who climb up the ranks will be the ones who know how to make agents and humans work together. The old path of analyst to manager to VP, measured how many people reported to you. Now, companies will prioritize impact over headcount. You get senior by running the most important systems for the revenue org. 𝟱) 𝗜𝗳 𝗜’𝗺 𝗲𝗮𝗿𝗹𝘆 𝗰𝗮𝗿𝗲𝗲𝗿 𝗥𝗲𝘃𝗢𝗽𝘀, 𝗵𝗼𝘄 𝗱𝗼 𝗜 𝘂𝗽𝘀𝗸𝗶𝗹𝗹 𝗳𝗼𝗿 𝘁𝗵𝗶𝘀 𝗿𝗼𝗹𝗲? Know how to build. This isn’t about vibe coding an internal tool. It’s about understanding what problem you’re solving, the inputs, the data model, and the data quality. Learn how to own and manage the agent's entire foundation. AgentOps will change the entire identity of the RevOps role. By owning AI agents, RevOps will go from a tactical, reactive role to becoming the AI orchestrator of the GTM org - major strategic win. If you’re in RevOps, you HAVE to listen to the episode. It will shape the next few years of your career. Link in the comments.
-
Janis Zech shared this📣 We're bringing our RevOps meetup to London!! (and we have a special GIFT for RevOps this time) On Sept 23rd, Weflow + the RevOps Chat community are taking over Soho for a night to bring together the coolest RevOps folks. It’s going to be a night full of 🍕 Free pizza + 🍻 Drinks + 🎶 Music + tons of RevOps conversations PLUS, this time, we have a GIFT for everyone. Our team has spent weeks creating it; I can’t wait to share it with everyone who is attending. (hint: it’s going to make you better at AI) Details for the meetup: - When: Wed, Sept 23, 6:30pm onwards - Where: Huckletree Soho | Ingestre Court Spots are limited, and they're going fast. Link in my featured section. See you soon! How cool are these photos from our previous meetups?
-
Janis Zech shared thisBack from Dreamforce. I'm exhausted BUT so excited. Four highlights because I flew home more grateful than tired: 1) The people. So many of the RevOps leaders we already work with, and a bunch we're about to start working with. It was GREAT meeting everyone in person. 2) A week with Chris Nethercote, our new Head of Sales for the US. Onboarding him in person and mapping out Weflow's US expansion side by side felt amazing. Chris - super excited to have you at Weflow 3) The scale. Dreamforce reminds me every single time how big software really is. Watching the keynotes, seeing the people building the frontier of this up close, does not get old. 4) What really amazed me - how much real pain still lives in data capture, and how it costs teams in sales efficiency and predictability. Every conversation made me more certain that what we're building matters now more than ever. If we missed each other in the madness, my DMs are still open, let's chat. Had a great time meeting all of you - Olav Abel Lindberg, Arpit Sharma, Samarth Mital, Noah Marks, Andy Mowat, Brigette Sjoboen, Odelya Arnold, So-Eun Park, Kathryn Traulsen, Chloe Barritault, Darren T., Matthew Volm, Greg Robin, Pavel Reznikov, Chris Mayberry, Dan Jiao, Michael Watson, Fadi Khoury, Richard Perez Until next time!
-
Janis Zech shared this4y ago, it was hard to defend Weflow against Gong. Today, we’ve replaced Gong at 100+ companies. Here are the most common pushbacks I’ve heard from RevOps over the years: 𝟭. “𝗔𝗹𝗹 𝗼𝘂𝗿 𝗱𝗮𝘁𝗮 𝗹𝗶𝘃𝗲𝘀 𝗶𝗻 𝗚𝗼𝗻𝗴, 𝗜 𝗱𝗼𝗻’𝘁 𝘄𝗮𝗻𝘁 𝘁𝗼 𝗹𝗼𝘀𝗲 𝗶𝘁” All your recordings, transcripts, and coaching data live in Gong. You fear that switching will mean losing your data. But: you never owned that data in the first place. Gong wants to keep your data. That’s why they don’t sync transcripts or activities back to Salesforce native objects. They keep it in their “Revenue Graph”. We believe you should own your data. That’s why Weflow syncs everything back to native Salesforce objects. The good news: we can still import your existing Gong data to Weflow. You’ll keep recordings, transcripts, summaries, coaching insights, and activity logs - and we sync it cleanly into your CRM. You won’t lose your data by making a switch; you’ll get more ownership of it 𝟮. “𝗧𝗵𝗲 𝘁𝗲𝗮𝗺 𝗹𝗶𝗸𝗲𝘀 𝗚𝗼𝗻𝗴 𝗮𝗻𝗱 𝗱𝗼𝗲𝘀𝗻’𝘁 𝘄𝗮𝗻𝘁 𝘁𝗼 𝗹𝗼𝘀𝗲 𝗮𝗻𝘆 𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹𝗶𝘁𝘆" Literal quote by a prospect. And I get it: Gong does a lot. You’re scared of trading down or not being able to do everything you used to with Gong. Almost every RevOps leader I’ve demoed to fears this - and ends up being surprised by how much they’re gaining. Weflow does activity capture, conversation intelligence, forecasting AND building AI agents in one platform. If you don’t want to take my word for it, check it out yourself. Try us out in sandbox here: https://lnkd.in/eyGpNqXG 𝟯. “𝗜 𝗱𝗼𝗻’𝘁 𝗵𝗮𝘃𝗲 𝘁𝗵𝗲 𝗯𝗮𝗻𝗱𝘄𝗶𝗱𝘁𝗵 𝗳𝗼𝗿 𝗮 𝘁𝗼𝗼𝗹 𝗿𝗲𝗽𝗹𝗮𝗰𝗲𝗺𝗲𝗻𝘁 𝗿𝗶𝗴𝗵𝘁 𝗻𝗼𝘄” I get it. You’re RevOps; you barely get time from firefighting all day. Tool migration is the last thing you want on your plate. Good news is, our technical setup takes 45 mins. Literally. Full onboarding and rollout is 2 weeks on average, depending on the customer’s bandwidth. Most of that time is our CS team helping you set up Weflow and running internal training sessions, so it’s not a burden for you. I don’t mean to brag, but a customer told us that “It's probably been the most flawless rollout of any product I've ever been involved with.” (quoting Scott Jones, SVP GTM Intelligence & Enablement at KORE) If you’re still unsure, happy to introduce you to any of our customers who have migrated from Gong! Every time I answer these pushbacks, I see RevOps agreeing with me. The no. of customers who switched over is proof enough. Think about these before your renewal is up. PS: If any of these sound familiar to you, drop me a DM or check us out here: Weflow(.)ai
-
Janis Zech reposted thisJanis Zech reposted thisI am very excited to share that after an unplanned, but wonderful career break (what a summer to take a break!), I have started a new role in RevOps with Sitecore. The thing that drew me to Sitecore, in particular, was the team - experienced, committed and driven - who have built an environment I believe will grow in. During my job search I listened to a great podcast between Weflow and Andy Mowat, and what really resonated with me was the advice by Andy that choosing who you work for should be a driving factor in making a career decision. My experience in the past is that learning from leaders who know what good looks like is the greatest career accelerator you can have (shout out to Leslie Symonds and Tanaka Chiimba). That is what I feel I have done by choosing this role and I am so excited about learning from excellent leaders. Thank you Tanya Tobin (OGeran), Paul Adams and Jason Cumine for your trust in me. I am looking forward to great things!
-
Janis Zech liked thisNine functions, one precondition. Points 2 and 5 on this list are not two priorities among nine. They are the ground the other seven stand on. In the mid-market companies I work with in Romania, there is rarely a RevOps team. There is one person, a CRM updated only when someone remembers, and activity data that lives in inboxes. Signal stacking, continuous enablement and AgentOps all assume that data exists and is trusted. Most of the time, it doesn't. The playbook is right. The sequence is what decides whether it works: capture first, orchestrate second.
-
Janis Zech liked thisJanis Zech liked thisI believe RevOps is evolving beyond being primarily a systems, process, and reporting function. The next generation of RevOps should be the operating intelligence behind the GTM organization — connecting data, pipeline, performance, and AI to help the business understand what is happening, why it’s happening, and what to do about it. That’s what I’m looking for in this role. Someone who can: • Go deep on lead generation and pipeline creation • Inspect funnel health, conversion, velocity, quality, and productivity • Identify leading indicators before they show up in the financial results • Connect Marketing → BDR → Sales → CS performance • Diagnose the root causes behind changes in GTM performance • Build a rigorous, data-driven GTM operating cadence • Use AI and automation to fundamentally improve how we analyze the business and operate the revenue engine • Get into the details and build the analysis, models, workflows, and tools — not just manage them This is a hands-on leadership role. You’ll work closely with Sales, Marketing, CS, Finance, and GTM Engineering to build a more predictable and intelligent growth engine. If you’re excited about where RevOps is headed — and want to help define what that looks like in a growing PE-Backed SaaS company — I’d love to hear from you. And if someone comes to mind, I’d really appreciate an introduction.
-
Janis Zech liked thisJanis Zech liked thisIt’s only called a GTM Engineer if... it comes from the GTM region. Otherwise it’s just sparkling RevOps 🥂 💅
-
Janis Zech liked thisJanis Zech liked thisThank you to Janis Zech and Philip Wagner for organising the Weflow-sponsored RevOps Meetup! It was great to catch up with the London RevOps community and geek out over RevOps. The theme that emerged for me during these conversations is how much AI has influenced our profession, and not always for the better, especially when rollouts aren't governed, or the data foundation or process has yet to catch up. Equally, that's what makes our profession both invaluable and strategic. Great catching up with the Fennels too: Jennifer Kedzierski Darryl HeffernanRhys-Leon GbenobaJames Roberts
Experience
Education
Volunteer Experience
Recommendations received
2 people have recommended Janis
Join now to viewView Janis’ full profile
-
See who you know in common
-
Get introduced
-
Contact Janis directly
Other similar profiles
Explore more posts
-
Travis Kirk Lowry
Vinyl Capital • 5K followers
AI commoditizes automation and intelligence, which means that saas companies (which historically either automate stuff or present stuff as 'insights' on 'dashboards') will face an insane amount of competition and thus their racketeering adjescent seat based pricing will crumble. that said I tend to see a lot of ecom bro's or PE saas guys on linkedin with hot takes that are like 'nah uh, have you tried it, its too hard'. and I think thats also right! but I think its only right for a short period of time. the chart below focuses largely on enterprise, where the legacy saas companies' tam is big enough to warrant a legit effort by a new entrant, and more likely, the in house tech teams are strong (or egotistical) enough to try to bring it in house. the ecom guys and the PE guys tend to focus on the long tail and on blue collar businesses.... operators that are, mostly, too dumb, too ideological, or too busy to try to vibe code something. so yeah, *today*, I think its more likely that some of the thousands of developers at capital one bring a saas tool's functionality in house or that a team in india copy/pastes it for 1/20th the cost than I think that a dude with a room temp iq selling white label Chinese slop on Shopify is going to vibe code a new sms delivery tool. but thats today. tomorrow is coming fast.
18
2 Comments -
Meshack Ayaga
Boost KE • 412 followers
How Do We Measure the Health of an Economic Ecosystem? We often measure success through familiar metrics: Revenue. Valuation. User growth. These matter. But when building economic ecosystems, they only tell part of the story. The deeper question is: How healthy is the ecosystem around the company? A strong ecosystem isn’t defined by one successful startup. It’s defined by how many participants can grow within the system. Especially in emerging markets, better questions might be: • How many vendors gain consistent market access? • How many young people move from learning to earning? • How many SMEs integrate into formal supply chains? • How many institutions collaborate instead of operating in silos? These signals reveal something deeper than growth. They reveal coordination capacity. In fragmented environments, growth can look impressive but remain fragile. In aligned ecosystems, growth becomes durable. Africa’s next generation of platforms may not win by simply optimizing transactions. They will win by expanding participation. The real advantage may not be controlling markets. It may be enabling ecosystems. What metrics do you think best reflect a healthy economic ecosystem? #OpenWealth #EconomicReform #EcosystemThinking #AfricaRising
3
-
Marvin Sanginés
notus • 43K followers
My COO Luca Wetzel and I have a 90 minute c-level meeting every week. Even if it’s just the 2 of us. Even if “nothing happened.” Even if we’re busy. It HAS to happen - here’s why: For context, this is basically the L10 meeting from EOS. The idea is to start at 50,000 ft and slowly zoom in: • share headlines + updates • go through KPIs/scorecards • track rocks (big initiatives) • issues to discuss/solve Some weeks it doesn’t feel like going through all this will provide much value. If there are 100 small fires burning, the motivation is to put those out first. We can save the big questions for later… The problem is, “later” can become another week, another month… suddenly it’s the end of the quarter and we haven’t met any of our goals. Just this 1 meeting per week stops that from happening. How we run ours: 1. Go through the company scorecard We got the template from Ryan Deiss and adjusted it to meet our needs. It covers all company metrics - financials, forecasts, etc. - and shows us how we’re actually doing beyond day-to-day deliverables. ___ 2. Discuss initiatives/bottlenecks Our main initiative right now is improving our service standards across all projects. We’ve added full funnel support to help our clients execute our entire GTM playbook. Now we’re updating our fulfillment structure, bringing in new leadership positions, and making sure we provide an even better service to all of our clients. ___ 3. Go over the issues list Each, Luca and I, have our own document that we prepare beforehand, in which we write down every detail that needs discussion. The goal here is to address potential friction points or elephants in the room. Identify. Define. Resolve. Follow up with people where needed. This is how we prevent disagreements and ensure internal politics don’t take over the business. — Without a weekly check-in, I can easily convince myself nothing is wrong. This meeting is what keeps us aligned. If everything is fine, then great. If not, we’ll catch it, and we’ll talk it through. Looking forward to the next one, Luca Wetzel 💆🏽
77
15 Comments -
Mitchell Forbes
ARRtist • 13K followers
Faster content. Cheaper outbound. Is that actually winning you the buyer? Christian Reichert, CRO at Shiftmove, doesn't think so and he's bringing that case to the ARRtist AI Summit 2026, where he's hosting a roundtable on: "The AI Efficiency Trap: Why Faster Content and Cheaper Outbound Won't Win the Buyer". Every GTM team is chasing the same efficiency gains right now: more emails, more content, more volume, all powered by AI. But efficiency and effectiveness aren't the same thing. If your outreach gets cheaper and faster while buyers get more selective and skeptical, you're optimizing for the wrong metric. Join his roundtable to unpack where the AI efficiency trap is already hurting GTM teams, and what actually wins the buyer instead. 📅 October 8, 2026 📍 ARRtist AI Summit, Berlin 🎤 Roundtable: The AI Efficiency Trap: Why Faster Content and Cheaper Outbound Won't Win the Buyer See you in Berlin!
9
-
Yuval Ben-Itzhak
Evolution Equity Partners • 6K followers
A common mistake in AI pricing is confusing compute cost with economic value. A frequent question I get from founders is: How should we price AI agents? Tokens cost money. They impact gross margin and cash flow. So pricing discussions naturally start there. But that is the wrong starting point. Yes, AWS, OpenAI, Anthropic and other AI infrastructure providers charge by tokens and usage. That makes sense. They are infrastructure layers. Like cloud providers or mobile operators, they monetize general-purpose capacity. They accelerate everything, but they do not own a specific business outcome. A software company is different. You are not selling compute. You are selling a use case. You are selling a business outcome. Customers do not buy tokens. They buy economic acceleration. For AI to command meaningful pricing, it must materially shift the business's economic clock. The real value of AI is when it pulls forward the moment of outcome: Revenue recognized earlier. Risk eliminated sooner. Capital deployed faster. Decisions made in minutes instead of days. That is what expands willingness to pay. If you price like infrastructure, you cap your upside at compute cost plus margin. If you price like a software company tied to outcomes, you price against economic impact. When you materially shorten time to value, you are no longer competing on budget. You are competing against opportunity cost. And opportunity cost has no ceiling. If you are building an AI agent, the key question is not: “How many tokens does it consume?” It is: “How much economic time does it remove from the system?” Price against that. Evolution Equity Partners #AI #AIAgents #PricingStrategy #B2B #SaaS #Startups #VentureCapital #ProductStrategy #WillingnessToPay
20
4 Comments -
Nick Mehta
Bessemer Venture Partners • 110K followers
"The One Where a Famous VC Made Me Cry - And I'm Grateful": The year was 2002 (OK, Boomer!) My first startup (Chipshot) that we founded in our dorm rooms went from hot to not and shut down in 2000. The next startup (XDegrees) that I joined shut down 18 months later. I was 25 with a big ego and no money. One of our startup's VCs was a legendary investor. I pinged him to get career advice and he kindly accepted. I went to his office - incredibly a tiny little room with space for 2 uncomfortable chairs. I awkwardly sat and handed him my printed resume (remember kids - this was a LONG time ago...) [VC with no eye contact]: "Nick - I look at your resume and see... Chipshot: FAILURE... XDegrees: FAILURE... you'd better watch out or people are going to see you as a serial FAILURE. Go somewhere where you won't FAIL.” I politely thanked him and went back home. And bawled. There were some serious young man tears landing on my IKEA patio swing that night, people. Yet the next morning, I decided to listen to his advice. I cold emailed some already successful companies and ended up getting a PM job at one. I started on probably the most boring software product in the world, but at least it didn’t go out of business! Eventually I became a VP and GM and subsequently got to restart my dream of startups and founding companies. What do I take away from this? Well, none of us know the counterfactual. Maybe if I had ignored the investor’s 2002 advice, I would have gone on to start some epic trillion dollar company. Maybe. But 24 years later, I’m grateful that the investor had the guts to step beyond the bounds of politeness to share what he thought I needed to hear. And I work to be that candid (perhaps with a bit more bedside manner!) with others. Easier said than done.
169
49 Comments -
Miranda Mickelson Evans
Roosetta Group (Roosevelt… • 16K followers
15 February 2026 update. "We Love Investors". Roosetta is currently both connected and interconnected with 2,927 venture capital investors partners principals associates at 337 VC firms - 75% "tier one", or, approx. 2,200 VCs among the elite top 50 firms. As well, we have been specifically involved in Leadership Hires involving 17 of these Top 50 VC firms. Similarly, we are involved with approx. 2,500. Private Equity top firms, and have been invested in, and active with PE funds for over 45 years - with an equal measure of connections to preeminent investors identified as veteran ANGELS and FAMILY OFFICES. Roosetta, just on LinkedIn, therefore, maintains 6,000+ active investor connections, with an equal measure (6,000) in our private, separate database. Roosetta est. total is 12,000 investors.
-
Praveen Kumar Panjiar
NICHE Digital Media • 4K followers
𝗪𝗵𝗮𝘁 𝗶𝗳 𝗩𝗖𝘀 𝗮𝗿𝗲𝗻’𝘁 𝗶𝗻𝘃𝗲𝘀𝘁𝗶𝗻𝗴 𝘀𝗶𝗺𝗽𝗹𝘆 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝘆𝗼𝘂𝗿 𝗽𝗶𝘁𝗰𝗵 𝗹𝗮𝗰𝗸𝘀 𝗘𝗠𝗢𝗧𝗜𝗢𝗡, 𝗻𝗼𝘁 𝗹𝗼𝗴𝗶𝗰? Naval Ravikant says it bluntly: 𝗥𝗮𝗶𝘀𝗶𝗻𝗴 𝘃𝗲𝗻𝘁𝘂𝗿𝗲 𝗰𝗮𝗽𝗶𝘁𝗮𝗹 𝗶𝘀 𝗮𝗻 𝗲𝗺𝗼𝘁𝗶𝗼𝗻𝗮𝗹 𝘀𝗮𝗹𝗲, not a rational one. Why? →Because investors don’t fund pitch decks… →They fund people they feel something about. Naval puts it perfectly: “𝗥𝗮𝗶𝘀𝗶𝗻𝗴 𝗺𝗼𝗻𝗲𝘆 𝗶𝘀 𝗲𝘀𝘀𝗲𝗻𝘁𝗶𝗮𝗹𝗹𝘆 𝘆𝗼𝘂𝗻𝗴 𝗳𝗼𝘂𝗻𝗱𝗲𝗿𝘀 𝘀𝗲𝗱𝘂𝗰𝗶𝗻𝗴 𝗼𝗹𝗱𝗲𝗿 𝗶𝗻𝘃𝗲𝘀𝘁𝗼𝗿𝘀. 𝗬𝗼𝘂’𝗿𝗲 𝘁𝗿𝘆𝗶𝗻𝗴 𝘁𝗼 𝗴𝗲𝘁 𝘁𝗵𝗲𝗺 𝘁𝗼 𝗹𝗼𝗼𝗸 𝗮𝘁 𝘆𝗼𝘂 𝗮𝗻𝗱 𝘀𝗲𝗲 𝘁𝗵𝗲𝗺𝘀𝗲𝗹𝘃𝗲𝘀 𝗶𝗻 𝘆𝗼𝘂.” And emotional decisions never come from checklists. No one falls in love because someone is “pretty good” at a bunch of things. They fall in love because of ONE overwhelming trait. VCs are the same. According to Naval, startups win when they’re exceptional in at least one of the 4 things: 💎 1. 𝗔 𝘄𝗼𝗿𝗹𝗱-𝗰𝗹𝗮𝘀𝘀 𝘁𝗲𝗮𝗺 Show you've done something extraordinary before starting this company. Signals > promises. 🛠 2. 𝗔 𝗽𝗿𝗼𝗱𝘂𝗰𝘁 𝘁𝗵𝗮𝘁 𝗺𝗮𝗸𝗲𝘀 𝗶𝗻𝘃𝗲𝘀𝘁𝗼𝗿𝘀 𝘀𝗮𝘆 “𝘄𝗼𝘄” Don’t pitch with a half-built prototype and excuses. Investors are users — let them click, play, and decide instantly. 📈 3. 𝗥𝗲𝗮𝗹 𝗰𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝘁𝗿𝗮𝗰𝘁𝗶𝗼𝗻 Nothing beats users who grow organically. “Give us money and then we’ll get customers” is the fastest way to lose a round. 🌐 4. 𝗦𝗼𝗰𝗶𝗮𝗹 𝗽𝗿𝗼𝗼𝗳 𝘁𝗵𝗮𝘁 𝗰𝗼𝗺𝗽𝗼𝘂𝗻𝗱𝘀 One investor → attracts two more. One respected advisor → credibility boost. Momentum matters more than founders think. Naval’s bottom line: 👉 You don’t need to be good at everything. 𝗬𝗼𝘂 𝗷𝘂𝘀𝘁 𝗻𝗲𝗲𝗱 𝘁𝗼 𝗯𝗲 𝗲𝘅𝘁𝗿𝗮𝗼𝗿𝗱𝗶𝗻𝗮𝗿𝘆 𝗮𝘁 𝗼𝗻𝗲 𝘁𝗵𝗶𝗻𝗴 𝗶𝗻𝘃𝗲𝘀𝘁𝗼𝗿𝘀 𝗳𝗮𝗹𝗹 𝗶𝗻 𝗹𝗼𝘃𝗲 𝘄𝗶𝘁𝗵. If you’re a startup raising in 2026, watch the full keynote. It will change how you fundraise → https://lnkd.in/gucXQ8-w 👉 Catch all the resources at Foundevo.com, your goldmine of startup and fundraising playbooks. Subscribe (FREE) → https://www.foundevo.com/ 👉 Follow CompareBizTech, your go-to platform for discovering software and AI tools tailored for startups and SMBs.
3
-
Gaurav Jha
TAG Capital GmbH • 5K followers
🚨 Most early-stage founders don't have a bad idea. They have bad expectations. Over the last 18+ months, we've taken TAG Capital GmbH through 4 accelerator programs: – angel-backed – VC-backed – German Federal Ministry (unlocked public grants) – and one more across the globe Each one runs at a different speed, with different expectations, different investors and a completely different definition of "ready". In the last two weeks alone, I've spoken to 100+ founders. The pattern 👇 Early-stage founders are consistently: – too close to their idea – optimising for hype, not validation – underestimating what investors actually expect – treating fundraising as a starting point, not an outcome What these programs forced us to do at TAG: – build a product and tech stack that could survive outside a pitch deck – validate with paying customers across multiple perspectives – treat pre-seed as an acceleration of a working engine That balance between validation, revenue and fundraising readiness has been one of our biggest unlocks. 💡 I want to share those learnings with a small group of founders. ✅ 30-min deep-dive on your idea, market and next 30–60 days ✅ Critical feedback, no ego-massage ✅ Best practices from angel, VC and government-backed programs ✅ Concrete written action points you can execute immediately 🎯 Pitch your startup in one line in the comments. I'll send the best ones a 50% discount code (limited slots). ❤️ Impact-driven founders (health, climate, inclusion, etc.): DM or connect with the note "impact" + one liner. This one's on me. Booking link in the comments 👇
45
4 Comments
Explore collaborative articles
We’re unlocking community knowledge in a new way. Experts add insights directly into each article, started with the help of AI.
Explore More