Sign in to view Ben’s full profile
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.
Sign in to view Ben’s full profile
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.
Toronto, Ontario, Canada
Sign in to view Ben’s full profile
Ben can introduce you to 10+ people at Highline Beta
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.
21K followers
500+ connections
Sign in to view Ben’s full profile
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 Ben
Ben can introduce you to 10+ people at Highline Beta
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 Ben
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.
Sign in to view Ben’s full profile
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.
Websites
- Company Website
-
http://codified.co
- Company Website
-
http://yearonelabs.com
About
Highline Beta is a corporate venture…
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
Articles by Ben
-
Corporates Need to Take a Portfolio Approach to Innovation
Corporates Need to Take a Portfolio Approach to Innovation
Successful startups usually don’t win with their first idea or first product. There are many examples of startups that…
26
4 Comments -
Why it’s Important for Big Companies to Regularly Launch New VenturesJan 24, 2017
Why it’s Important for Big Companies to Regularly Launch New Ventures
As Steve Blank said, “A [big] company is a permanent organization designed to execute a repeatable and scalable…
19
1 Comment -
Introducing Highline BETA – a Startup Co-Creation CompanyJul 11, 2016
Introducing Highline BETA – a Startup Co-Creation Company
Today, I’m launching a new company: Highline BETA. I’m co-founding Highline BETA with Marcus Daniels.
92
18 Comments -
Assembling the Avengers (Or How Startups Evolve Their Team Structures to Scale)May 26, 2016
Assembling the Avengers (Or How Startups Evolve Their Team Structures to Scale)
Who doesn’t like the Avengers, right? The first movie was awesome. The second one was…still fun.
9
-
Four reasons to use the One Metric That MattersApr 27, 2016
Four reasons to use the One Metric That Matters
Editor's note: This is an excerpt from "Lean Analytics: Use Data to Build a Better Startup Faster," by Benjamin…
25
1 Comment
Activity
21K followers
-
Ben Yoskovitz posted thisHere are 5 things I refuse to give up as a product builder despite my heavy use of AI: 1. Human validation: Despite how fast it is to build things, I still believe in the idea of "slow to go fast". Slow means talking to people, testing ideas & learning before you dive head first into building. While I believe synthetic user research can play a meaningful role in validation, I'm not looking to replace human research. Talk to your users / customers. Ask "why?" Dig deep. 2. Plainly written requirements documents: Jumping into AI-generated code is super enticing. But rushing things usually results in garbage. There's something about a well-written, clear PRD that's valuable. Turns out it'll help your AI write better code and help everyone else working with you understand what the hell is going on. AI can generate PRDs and other product documentation but it leans so far away from being plain-spoken. And there's a good chance you don't read all its output, which sneaks bad ideas or decisions into the product. Write your own documentation, try it. It'll force you to think more deeply, challenge yourself (and others) and ultimately should lead to a better product. 3. Exploration of edge cases: Everyone loves a good happy path. "Just don't stray from the path," is not advice that people listen to. Suddenly people are using your product in unexpected ways. They're filling in fields "strangely" or trying to do things you hadn't thought of. Sigh. I like thinking about edge cases, because it forces me to anticipate how people might use a product, or where it might break in the future (aligning with a future roadmap). "If we do this now, how will that impact something tomorrow?" Is that too detail-oriented? Maybe. Can it bog things down? Occasionally. Is there a risk of over-thinking? Yes. But edge cases help define scope, risks and trade-offs. All of those are important. 4. Human testing: There are some things you can ship without human testing. But I don't like the idea of replacing human testing completely. Humans are unpredictable. They also provide nuanced, qualitative feedback that isn't easy to get from code-based or AI-based testing. If a human is going to use your product (or point its agent at your product), then you need to test with humans. 5. Thinking: All of this comes down to thinking. If you outsource too much of the thinking and crafting to AI or skip the thinking because you figure you can "fix things really quickly later," you're going to build crappy products. Building a great product that people will use regularly and pay for remains insanely hard. AI hasn't made that process easier. If anything it's leading people to skip steps and build more crap. AI is insanely powerful but you still have to wrangle it intelligently and that takes a lot of work.
-
Ben Yoskovitz posted thisThe irony of AI: The more you use it to produce more "stuff" the more people expect you to produce more "stuff". We're quickly heading into a cycle of limitless output. More output might feel good initially, but it might destroy everything. No one is producing more time while producing more "stuff" even if they've got agentic employees that are supposedly processing "stuff" and streamlining "things." I love what Cory Doctorow wrote recently about sending someone unverified AI output, "...is an attempt to coerce a stranger into unpaid labor on your behalf." Even if they're not a stranger, you're still outsourcing the actual work (read: "thinking") to the recipient. If there was ever a time to hang our hats on "quality over quantity" it's now.
-
Ben Yoskovitz shared thisToday, I'm excited to launch something that's not work-related. It's not even AI-focused. I know, I said it... I built a word game. 📕 🎉 It's a game I used to play with my kids. We called it the "license plate game" (although if you look that up, it's something else). We'd see a license plate while driving and try to make a word out of the letters. Super simple, and very fun. The game gives you letters - say C * D * M. You have to make up words that start with C, end in M, and have a D in the middle. Condominium for example. The game gives you 2, 3, 4 and 5 letters. That's it. Wordle meets Spelling Bee (sort of). The game is called WordSpine. There are two versions: 1️⃣ WordSpine Sprint - 10 words in a row, get them completed as fast as you can. 2️⃣ WordSpine Pro - 4 rounds, 10 words each. More difficult, not timed. You can play for free as a guest, or create an account to save & track progress, see stats and get badges. This is an early test, but I'd love feedback! Try it out: https://wordspine.com
-
Ben Yoskovitz posted thisThis is NOT about AI. Say what? Pardon me? Are you out of your mind? I don't think so. But I did just build a fun word game that I think people will really enjoy. Web-based to start (eventually I'll build native apps if there's interest). Anyone want to try it? I need testers & feedback. It's got some similarities to Wordle and Spelling Bee. Comment or message me. Thank you!
-
Ben Yoskovitz shared thisNo one reads anymore. Truth is this has been a problem for a while, but it's getting worse. People's attention spans are deteriorating and LLMs through chat interfaces have created a new expectation of instant answers. Honestly, I think in many situations people spend MORE time chatting with an LLM than necessary, but it FEELS like progress. This is bleeding aggressively into product design. I'm seeing it with Candor, the synthetic user research platform we're building. Here's a simple example: 1. When creating an interview guide we have an option Project Context field. The field has a description and a sample written into the field. But a few pilot customers have thrown in huge descriptions that don't match the intent of the field. They put in instructions, questions they want the AI interviewer to ask, and more. 2. Candor, like many tools, has a "garbage in, garbage out" problem. If a research study has bad inputs, the quality of results may be lower. So we need a way to fix this, but if people don't read and they move super quick with an expectation of instant results and value, how do you solve the problem? 3. We're taking a couple approaches, although I'm not sold on either. One is to run a quality check on the inputs and provide feedback. If an input doesn't make sense or may lower the quality of results, we warn the user. This becomes, hopefully, a teachable moment, but also stops people from getting so-so results and then deciding Candor sucks. The second is Candor Bot, which is a chat interface for best practices that has context on what's being input into fields. We hope people will engage with Candor Bot to learn how to use Candor well. It's possible Candor is too complicated to use, but synthetic research requires precise inputs so that the synthetic users respond properly. So we're trying to work within certain parameters and constraints, without reducing quality. What's the implication for product design? 1️⃣ UI/UX is changing quickly. At some point I suspect most software UIs will be replaced by MCP servers / APIs integrated into a person’s AI interface of choice. People barely want to log into different software products any more. But that’s a discussion for another time. 2️⃣ LLMs have set an expectation of instant results. If your product takes a few minutes to do something or explain something, you might be in trouble. 3️⃣ People are trusting LLM output a lot, in an effort to move faster and feel like progress is being made. They’re blindly copying & pasting things everywhere, whether it’s a report or into an input field in your software product, without stopping to think. The reality is that you’re no longer designing for a user. You’re designing for a user plus their AI, and the AI is going to do more and more of the work.
-
Ben Yoskovitz posted thisWorkslop is taking over. With near-infinite capacity to create content, reports, analysis, etc. people are generating massive, unreadable documents. They don't even know what's in the documents, because they can't read through and edit things thoroughly. So now people send "work" to others and expect the people receiving the work to do a lot of heavy lifting. Sigh. I'm experiencing this firsthand, but fighting it. Here are 6 things I'm encouraging the team at Highline Beta to do: 1. Write first, then use AI to edit. Not the other way around. The quality isn’t close, and you can’t defend something you didn’t think through. The pull to go the other direction is enormous. Resist it. 2. Ownership matters. Whenever you send something to a client, prospect or anyone else, you are responsible for it. You own the thing you sent, whether you produced it or not. That ownership means you now stand behind what was produced and sent. Tough to do when AI wrote it all. 3. Define “done” before you generate. I do this when building software with Claude Code: three to five pass-or-fail checks written down before any work starts. Same for a document. If you can’t say what good looks like in advance, the model will happily hand you 22 pages of not-that. A smaller version of this: write out the sections of the document, why you need them, what they should contain and how you expect them to link together. Better prompting (to some extent) can wrangle AI to produce better quality. 4. Treat length as a cost you’re imposing on someone else. If your document needs a “how to read this” section, cut it in half. Then cut it again. Editing is critical, but not if your eyes glaze over and you’re going through the motions. 5. Be ready for follow-ups. We don’t send things to clients hoping they file them away and ignore them. We want them digging in, asking questions, challenging us and connecting dots. We have to be prepared for that. If we can’t do that, we’re not doing our jobs. 6. Design for people who won’t read. Content needs super clear summaries that are actionable. Software products need to assume people skip all instructions and just copy & paste AI generated stuff into them. Think about how our output can do more of the work and make it easier for recipients to digest, learn and action things quickly.
-
Ben Yoskovitz posted thisMachine generates. Machine consumes. Two humans exchange the illusion of work. You've seen this already. Someone feeds a pile of analysis into a model, writes a long prompt, out comes 22 pages. The recipient opens it, sees 22 pages, drops it into their own AI and asks for a summary. Nobody learned anything. Nobody was responsible for anything. Nothing of value was exchanged. We recently wrapped a client engagement where every strategic brief opened with a section called "How to read this document." (We edited these, btw!) I laughed the first time. By the third one I stopped laughing. Nobody ever wrote a "how to read this" section when they had to type the whole thing themselves. The cost of writing forced you to decide what mattered. That cost is gone. So nothing gets cut, and the job of figuring out what matters falls on whoever opens the file. This is the Catch-22: the faster you can generate stuff, the more you're asked to generate, and the less time anyone has to read any of it. Researchers are already calling the result "workslop": work that looks polished but has no substance, so the recipient does the thinking the sender skipped. Produce less. Mean it. Be able to defend it.
-
Ben Yoskovitz shared thisIs anyone else feeling this way? You build something fast with AI and get a nice dopamine hit. It's amazing how far AI can take you, and so quickly! A few prompts and you've got a fully functioning prototype. Every time I do it, I'm still amazed. Because it's legit amazing. But then things get...tougher. ➡️ You actually need to talk with users and get feedback, because there's a decent chance you're pointing AI in the wrong direction, building stuff people don't want. You're almost certainly over-stuffing the product with features. ➡️ You need to setup better development environments, implement tests, error logging and more. All the stuff you know developers do for production-grade software, but you never had to, because you're not a developer. Bug fixing? Sigh. Yawn. ➡️ Wait, is this software secure? What does that even mean? 2FA huh, now? Oh oh... That amazing fun feeling you experienced while hacking away with AI to prototype every idea you could possibly come up with disappears fairly quickly when things get real. I'm living this experience now. I'm in the weeds now trying to turn an idea into something real, and it can be a grind. Engaging users is re-energizing for sure, so that's where I'm focused, although when a user says, "meh" it hurts... 😏 Ultimately I have to remind myself: you're not doing this for the dopamine hit, you're doing it to solve a problem for someone and create value. But bloody hell, building scrappy stuff with AI is so much fun.
-
Ben Yoskovitz shared thisIs specialization dead? Not quite, but generalists are having a real moment. The T-shaped model has survived for 40+ years. Deep expertise in one domain (vertical bar of the T). Enough breadth to collaborate across disciplines. In the old model, the horizontal bar of the T was about perspective and collaboration. You were expected to understand what engineers do, or how marketers think, or how data teams work. Well enough to direct someone else to do it, or give another expert what they needed. You weren't expected to ship the thing yourself. That's definitely changing. Marketers are doing data analysis. Designers are shipping code. Operations people are building automations that used to require an entire engineering sprint. Product managers are building the things they used to only spec out. The horizontal bar of the T is no longer just about "understanding what others do, with a willingness to collaborate." The horizontal bar of the T is now about having a diverse set of skills (read: generalist) so you can do "all the things." Not perfectly, but well enough to do more than what you specialize in. AI is driving this aggressively. If you're hiring: the horizontal bar is becoming your primary filter, not a tiebreaker. Can this person operate across domains? What have they actually built or figured out recently? Generalists > Specialists. Not because a specialty is irrelevant, but because there's an expectation that a specialist can now do much more . If you're an individual: pick one adjacent domain and get your hands dirty. Not a course. Not a certification. Build something. Ship something. Fail at something and figure out why. The people building that broader foundation right now, even imperfectly, even messily, are the ones who'll have the most options when this shakes out.
-
Ben Yoskovitz liked thisBen Yoskovitz liked thisI feel incredibly fortunate that my first job was actually in tech. I was only 16, but as an awkward homeschooled kid in Montréal, I had the skills and the flexibility they needed. I still remember going in for the interview. I was so nervous. I started part-time as a "Jr. Web Designer." This was circa 2006 when we were still using apps like Dreamweaver, and slicing designs from Photoshop into <table> layouts. (If you know, you know! 😅) It's been 20 years. I'm still in tech, and I still feel like I've got a lot to learn.
-
Ben Yoskovitz liked thisBen Yoskovitz liked thisYour next customer might not be human. AI agents are moving from helping us make decisions to increasingly making decisions and transacting on our behalf. That creates an entirely new growth surface: building for agents, not just humans. What happens when your next customer never visits your website? My latest CIO in Beta: https://lnkd.in/gMQvuMgv Highline Beta #AgenticAI #FutureOfFinance #CorporateVentures #CIOinBeta
-
Ben Yoskovitz liked thisBen Yoskovitz liked thisIt’s been exactly 12 months since I left VC to become a full-time solopreneur. Here’s an honest look at how it’s going: For context, I write a weekly newsletter about startup GTM & pricing (Growth Unhinged) and advise companies 1:1. Despite seeing other creators strike out on their own, I was pretty anxious about it. But the opportunity to built something of my own felt too compelling to pass up, despite the extra risk. Now I can’t imagine going back on the corporate treadmill.* > Learning: Be prepared to fail more in 12 months than the prior 15 years I’ve always seen myself as a bit of a perfectionist. That needed to change, fast. I got rejected by multiple insurance companies before I managed to get covered. It took about 65 emails and 94 days to get paid for a $10k invoice. I’ve cycled through three business entities in the past year (sole proprietor > LLC > S-corp). I even missed what was supposed to be my first official payroll. Ouch. But I’m starting to take this in stride. (I tell myself that anyway.) > Learning: Building a 7-figure business as a solopreneur is now possible I set a big goal for myself this year: scale to $1 million in revenue with 0 employees. I’ll exceed that goal in September (🤯), which is wild to say out loud. What makes this possible is better tech (yes, including AI) that now allows me to wear dozens of hats. I use 14 tools on a near-daily basis. Some my processes will always be old school though. I write the newsletter myself. And I create all my visuals (in Google Slides lol). > Learning: Monetizing yourself is trippy (and, yes, I initially under-charged) People are often curious about how I make money. I’ll try to be transparent in case this helps someone else. 1. Reader subscriptions: 10-15% of revenue 2. Brand partnerships: 55% of revenue 3. Consulting & advising: 25% of revenue 4. Speaking fees: 5-10% of revenue > Learning: The more time you spend on the business, the more your ambitions grow I was worried that becoming a solopreneur might end up like a sabbatical or early retirement (I'm still 38 lol). The opposite happened. I’ve got a ton in store for the rest of this year so please watch this space. — I wrote more about the journey here: https://lnkd.in/g5vj-hZH Thank you again for being part of the journey 🍻 -KP — *PS, this photo is from trekking the Tour du Mont Blanc with my Dad a couple weeks back. Not having a boss made this much more feasible!
-
Ben Yoskovitz liked thisBen Yoskovitz liked thisMirage PMF is a useful warning about mistaking human-heavy AI traction for product-market fit. But AI creates another problem: the old warning signs can arrive much later. Work that once looked obviously unscalable can now scale surprisingly far. Nothing necessarily breaks. And that can make it much harder for founders to tell whether the work is building leverage or just accumulating. Keep doing the messy work. Just figure out what's compounding.
-
Ben Yoskovitz liked thisBen Yoskovitz liked thisThis is a photo of me and my mom. Her Alzheimer’s was the impetus for starting SecondEcho. I watched memories and stories disappear, and kept thinking there had to be a better way to save them before they were gone. Now, as I talk to Chloe on SecondEcho, it captures those memories and automatically weaves them into my life story, connecting the people, places, photos and moments along the way. We take thousands of photos and create endless digital content. But the stories that give those things meaning are still incredibly easy to lose. SecondEcho started with a simple idea: exploring a new way to save memories. SecondEcho Jonathan Gallivan Coco Usher Anna-Maria Kontos Jean-Philippe Baillargeon REIMAGINE AI
-
Ben Yoskovitz liked thisBen Yoskovitz liked this12-Month MBA for PMs (better than any $135K program) 👨🎓 Month 1: - Inspired by Marty Cagan - Empowered by Cagan and Chris Jones - The Right It by Alberto Savoia 👨🎓 Month 2: - Continuous Discovery Habits by Teresa Torres - The Mom Test by Rob Fitzpatrick - The Lean Product Playbook by Dan Olsen 👨🎓 Month 3: - Business Model Generation by Alexander Osterwalder - Running Lean by Ash Maurya - Testing Business Ideas by Strategyzer 👨🎓 Month 4: - Radical Focus by Christina Wodtke - No Rules Rules by Reed Hastings - Team Topologies by Manuel Pais and Matthew Skelton 👨🎓 Month 5: - Product-Led Growth by Wes Bush - The Product-Led Playbook by Wes Bush - Hooked by Nir Eyal 👨🎓 Month 6: - This is Marketing by Seth Godin - GTM Strategist by Maja Voje - Hacking Growth by Sean Ellis 👨🎓 Month 7: - Talk Like TED by Carmine Gallo - The Copywriter's Handbook by Robert Bly - Never Split the Difference by Chris Voss 👨🎓 Month 8: - Thinking, Fast and Slow by Daniel Kahneman - The 7 Habits of Highly Effective People - Superconnector by Paugh and Gerber 👨🎓 Month 9: - The Making of a Manager by Julie Zhuo - The Psychology of Money by Morgan Housel - Accounting for Non-Accountants by Wayne Label 👨🎓 Month 10: - Lean Analytics by Alistair Croll and Ben Yoskovitz - North Star Framework Field Guide (free PDF): https://lnkd.in/djvDpyVW - Are You Tracking The Right Metrics (free): https://lnkd.in/d9Mw3Bp8 👨🎓 Month 11: - Jobs-to-be-Done by Tony Ulwick - Escaping the Build Trap by Melissa Perri - Build by Tony Fadell 👨🎓 Month 12: - Playing to Win by Roger Martin - The Invincible Company by Strategyzer - No AI books on the list. On purpose. You learn AI by doing, not by reading. 7 steps, 10 minutes, no coding: https://lnkd.in/dE6tuFXa - Bonus (recommended): - Getting a PM Job by Aakash Gupta - Working Backwards by Bryar and Carr - The MBA Pathology by Marty Cagan: https://lnkd.in/dw6kpwTv - 650+ free PM learning resources in the welcome email: https://lnkd.in/d7g76cqZ - All it takes is 45-60 min/day of reading or audiobooks. P.S. You can network for free on LinkedIn. ------ P.S. Want to learn how to build AI products as a PM? 8 AI PM cohorts (Anthropic, Google, OpenAI) in the price of one + $1,500 off only for my community: 👉 https://lnkd.in/dS6sgqnZ Everyone who enrolls by Sep 5 can attend my Claudathon for PMs for free: https://lnkd.in/dWNfApWB
Experience & Education
-
Highline Beta
******** *******
-
****
***** ******
-
***** ****** **********
***** ******
-
****** **********
**** ********** undefined
-
View Ben’s full experience
See their title, tenure and more.
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
or
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Publications
-
Lean Analytics
O'Reilly Media
The Lean movement has revolutionized how we create products and companies. It focuses on customer development, tackles the risky parts first, and focuses on finding real, unmet needs.
At the core of this is iteration—a cycle of learning and adapting that’s driven by data. Lean Analytics gives you blunt, practical advice and proven approaches for learning from the abundance of data all around you.
This book is about analytics, done right: lean, mean, and iteratively. Filled with…The Lean movement has revolutionized how we create products and companies. It focuses on customer development, tackles the risky parts first, and focuses on finding real, unmet needs.
At the core of this is iteration—a cycle of learning and adapting that’s driven by data. Lean Analytics gives you blunt, practical advice and proven approaches for learning from the abundance of data all around you.
This book is about analytics, done right: lean, mean, and iteratively. Filled with behind-the-scenes case studies and day-one tools, it’s an essential ingredient for any smart startup.Other authorsSee publication
Projects
-
Focused Chaos: A bi-weekly newsletter for founders, investors and startup employees
See projectA bi-weekly newsletter focused on helping founders, investors and startup employees manage the chaos that is building & investing in startups. Topics will include: product management, analytics, Lean Startup methodology, startup-investor relationships, raising capital and more.
-
Lean Analytics
- Present
A book on using data to build a better startup faster, written with Alistair Croll and due out in early 2013.
Other creatorsSee project
Languages
-
French
-
-
English
-
Recommendations received
14 people have recommended Ben
Join now to viewView Ben’s full profile
-
See who you know in common
-
Get introduced
-
Contact Ben directly
Other similar profiles
-
Allan Wille
Allan Wille
Telfer School of Management at the University of Ottawa
6K followersGreater Ottawa Metropolitan Area
Explore more posts
-
Yusuf Gad
Win the Brand War • 4K followers
Dependency is the drug. Your software is the needle. Founders spend two years perfecting the needle and zero hours on the drug. No drug, no habit. Amazing technology is everywhere now. Every investor's inbox holds forty decks of it and not one reason for the client to stay. Salesforce has one. Nobody quits it. The cost of leaving is the product. If you vanished tomorrow, would your biggest client shrug or panic? A shrug means you built a science project. Panic means you built a business. Engineer the drug first. The needle is the easy part.
-
Kiffany Schoeman
KSI Consulting • 905 followers
Culture doesn't scale by accident. Most founders build culture early—when everyone fits in a room, shares values, and knows each other. Then they hire fast, and suddenly the culture they built gets diluted. The companies that scale with culture intact aren't the ones that get lucky. They're the ones that intentionally codify what matters, hire for it, reinforce it, and evolve it as they grow. That's not about ping pong tables or free snacks. It's about clarity on values, consistency in how you treat people, and leadership that models what you say you believe. Culture is your competitive advantage. But only if you treat it like the strategic priority it is.
4
-
Rob Palumbo
Tre'dish • 14K followers
Great press for Mercator.ai in GlobeSt.com! "Canadian startup Mercator.ai is developing an artificial intelligence platform that aims to forecast future construction activity, giving contractors and eventually investors and developers a way to anticipate shifting demand in commercial real estate markets. The platform is designed to help general contractors identify upcoming projects long before a builder is even attached. If successful, the same technology could eventually guide developers, investors, and other real estate players in anticipating what types of properties will be needed and where. The company was launched in Canada and worked with some of the country’s largest contractors, but its leadership quickly found that the local market posed significant hurdles. “The Canadian markets were actually quite challenging for us to go and build,” CEO Chloe Smith told GlobeSt.com. “There's a lot of different regulations, and it’s very, very expensive to access data sets.” Rather than starting in its home market, Mercator chose to focus on Texas, where accessing the right information was comparatively simpler. That access is critical because the platform relies on both clear and nuanced signs of development activity. Rezoning applications, building and trade permits, and other scattered data points are fused together to form a broader picture of what projects are about to emerge. The challenge lies in turning fragmented and largely unstructured information into something coherent. Mercator uses large language models to interpret documents, such as zoning files or permit applications, and machine learning tools to categorize the data so it can be analyzed. “Sometimes we bring in PDFs, so we actually have to go and process all those PDFs ourselves and pull out the relevant fields and create all of that schema and metadata,” Smith explained. Creating that schema provides the backbone of a structured database, while metadata helps define exactly what each field or entry represents. The immediate goal is to give general contractors an advanced prospecting tool, enabling them to identify early-stage projects before competitors. But Mercator’s ambitions stretch beyond construction leads. “The evolution of our product and where we're headed is really in market analysis,” Smith said. “Where are we growing? How are cities changing? How can we help folks forecast where they need to be? Because a lot of times the reason why the construction industry sees losses in terms of companies shutting down is because they're not able to get ahead of the curve fast enough.” If the platform works as intended, contractors could gain insight into shifts in demand—for instance, if multifamily projects slow down while demand grows for warehouses, medical office buildings, or data centers. Investors, too, could use the same intelligence to target the right land, choose the best partners, and position themselves in high-growth areas before competitors catch on."
6
1 Comment -
Darshil K.
CREDX • 7K followers
Canada just had one of its most quietly explosive funding weeks — and nobody’s talking about it. So we did. From AI to climate, fintech infra to robotics, Canadian founders didn’t just raise capital… they raised conviction. Investors backed real problems, real markets, and real revenue — not “AI but with vibes.” Here’s what stood out this week (Nov 30–Dec 6): 🇨🇦 Canada funded actual builders — Deeptech with customers — Climate tech with measurable impact — Fintech infra powering real payments — Robotics + automation companies replacing manual processes — Healthcare platforms solving real bottlenecks No hype. No wishful thinking. Just execution over ego. The full breakdown includes: 📌 Every funded startup 📌 Who backed them 📌 How much they raised 📌 One-line explanation of what they’re building 📌 Market insights investors won’t say out loud 📌 The trendlines shaping Canada’s 2025–26 VC landscape If you're a founder, investor, or operator… this week's Canada edition is a must-read. 👉 Full Newsletter: https://lnkd.in/ebYDBuSh CREDX Letters — raw. real. founder & investor first.
2
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