Simon Brossard

Whipping up new ideas... | Previously CBO @lemlist

Un truc que j’ai appris après avoir passé 3 ans chez lemlist, en passant de 2 à 22 millions d’euros d’ARR :

👉 90% du succès de ta prospection dépend de la qualité de ta liste de contacts.

Si ta liste est mauvaise dès le départ, tes résultats le seront aussi 🤷‍♂️

C’est exactement pour ça qu’on a lancé Cleon1, spécialisé sur le marché français.

Plus de numéros de mobile fiables et précis.

Moins de temps perdu.

Plus de deals signés.

Simple, non ?

Et en bonus, je partage aussi notre aventure entrepreneuriale, les hauts comme les bas !

Chief Business Officer

MicroAngel

I launched a small angel fund to buy and grow micro-SaaS products for freedom & profit. 

Sharing the whole journey at microangel.so

Currently operating:
- Reconcile.ly
- Postcode Shipping

Founder + Operator

Postcode Shipping

Postcode Shipping puts you in control of your Shopify delivery rates, and scales with your business. From local drop off to global shipping we are with you every step.

Part of MicroAngel Batch 1

Reconcile.ly

Saving the average Shopify merchant over 25 hours in bookkeeping tasks through a revolutionary reconciliation technology connecting Shopify. Xero and any external payment gateways.

Reconcilely is simple, reliable and affordable Shopify accounting.

Part of MicroAngel Batch 1

Simplekeeper

Board Member

Techstars

Mentor

FounderFuel

GrowthHackers

Instructor of the Growth Models & Goalseeking GH University Masterclass

Masterclass Instructor

Batch

Batch lets shoppers make offers you can instantly turn into new Shopify orders & sales.

Shoppers preauthorize what they’re willing to pay and make offers that DTC retailers can instantly transform into new orders with one click, without any back-and-forth necessary. No coupon codes. No risk. 10x ROI guaranteed.

With Batch, brands avoid losing sales due to pricing and can guarantee 100% of their inventory will sell through, every single time. Low offers automatically expire after 7 days. 

Collect offers for free on your Shopify store: www.sellwithbatch.com

Co-Founder

InvoiceSherpa

VP Growth

DigitalFounder

To enable ongoing entrepreneurship, I build, launch and operate a portfolio of digital businesses across eCommerce, business-to-business SaaS and consumer technology.

Digital Founder operates using what it calls “Product Release Trains.” Every quarter, a new product (train) is introduced with a set of tightly defined launch specifications, and this new train departs Validation Station with the target goal of an MVP launch within 4 months and GTM within 6 months. 

Product Release Trains benefit the entire Digital Founder network, comprised of full stack engineers, user experience and interface designers, front end integrators, copywriters, marketers, product practitioners and startup sales addicts. 

Each week, a variety of independent multidisciplinary digital makers (Digital Founders) contribute as much or as little as they like to the list of active Product Trains. Using their talent, Digital Founders can exchange product deliverables for micro equity into the new product. 

As products launch and gain traction, Digital Founders grow their portfolio revenues and decrease their reliance on freelance work for self sustenance, and instead merge their goals as makers into one continuous endeavour featuring independence, creative freedom and venture success.

Founder, Operator

Eyal grows companies of all stages by accelerating the search for product/market fit and building growth systems that acquire more leads, generate more customers, improve margins and increase buying frequency.  

As a full-stack strategic growth leader, Eyal's depth of knowledge is cutting-edge across all core growth disciplines spanning stats, programming, product design, UX principles, behavioral psychology and storytelling. These enable advanced performance in conversion optimization, testing, wireframing, funnel marketing, copywriting and database management.  

Core digital marketing skills frequently appear across growth projects, including but not limited to:
1) Market-fit discovery by systematically testing distribution channels
2) Full stack Ecommerce marketing to grow sales and profit
3) Building paid traffic strategies that acquire customers at a profit
4) Building conversion funnels that reduce acquisition costs while increasing lifetime value
5) Building and executing content strategies that gain new prospects and build relationships
6) Optimization & Testing to diagnose opportunities and test solutions that help squeeze more profit out of existing traffic
7) Developing organic search strategies that will stand the test of time
8) Crafting email campaigns that get delivered opened and clicked
9) Building growth models that map out weekly execution focus
10) Using funnel data & analytics to develop clear and focused KPI dashboards

Eyal deploys growth engineering playbooks that identify, test and implement high-lift product iterations designed to boost user activation, increase monthly and daily use retention, generate user referrals and improve core revenue metrics.

Across the last ten years, Eyal has acquired experience performing in B2B and B2C roles spanning gaming, SaaS, eCommerce, marketplaces, bots, blockchain and more while keeping particular attention to building cross-talent relationships in pursuit of future entrepreneurship.

Eyal Toledano

Something is broken about how teams work with AI agents right now, and most people are patching it instead of fixing it.

Every developer on your team has their own CLAUDE.md. Their own skill files. Their own local context. And when someone makes a decision in a meeting or a Slack thread, someone has to remember to go update those files. Manually. Across every developer's setup.

Nobody does. The files drift. Agents start building from stale context. You get PRs that contradict decisions made two days ago.

The real problem isn't file management. It's that decisions have nowhere to live.

Your team makes dozens of decisions every day. Scope changes, priority shifts, architecture choices, tradeoff calls. Where do those go? A Slack thread that disappears? A meeting note nobody reads? A Google Doc that's already outdated?

When a decision changes, it should change once, and every agent on the team should pull from that. There's no need to keep the markdown files up to date or copy-paste anything anywhere. Claude Code or Cursor just knows.

Your PRDs, your tasks, your skill files, your CLAUDE.md are all projections of the same underlying decisions. If the decisions live somewhere real, the projections stay aligned on their own.

And if they stay aligned automatically, progress can explode. Because the synchronization overhead disappears. No more "did you update the spec?" No more agents working from last week's context. The team just moves.

That's what we've been building into Hamster. Decisions get a home. Blueprint holds your product's current state. Methods encode how agents should work. The projections stay aligned because the source of truth is real.

Launching very soon. DM if you want early access.

Here's something I keep seeing that frustrates me.

A team adopts Cursor or Claude Code. Their developers can now ship a feature in a day. Leadership celebrates. "We're 10x faster."

Then you look at the actual output over a quarter. They shipped roughly the same number of features. Sometimes fewer. Sometimes the wrong ones, faster.

What happened?

The critical path changed but the calendar didn't.

Before AI coding tools, execution was the constraint. So PMs had time to write specs, designers had time to make mocks, everyone moved at roughly the same pace.

Now code for some features takes hours to write. But your old review cycle is still 95% of the timeline. Alignment still happens in weekly meetings. Direction still lives in docs that take a week to write. Context still gets lost in every handoff.

Your dev can build anything in a day. But they're still waiting 5 days for clarity on what to build.

The unlock isn't faster execution. It's faster alignment.

I've received many messages this week asking what it actually looks like to build with Hamster. So let me walk through how a feature goes from idea to shipped on our team.

Someone has an idea. A feature, a fix, an improvement. They open Hamster and generate a brief from that hunch. Doesn't need to be polished. Just the direction: what we're building, why, and what done looks like. Takes about 10 seconds.

The team gets notified. From Slack (our bot lives there) or inside the app. They contribute context, push back on scope, flag risks, refine the intent. This takes minutes. The brief captures all of it. Not in a separate comment thread. It's in the brief itself.

The brief owner reviews the feedback, refines, and generates a plan. Hamster turns that aligned brief into structured tasks with full context.

Teammates alignment votes come in and clear the brief to go into production. Otherwise it gets another refinement pass. All in a multi-threaded, multiplayer experience in which the team and Hamster collaborate to refine the brief.

Here's the part that changes everything: 

The Hamster CLI syncs that plan to your local filesystem. A .hamster folder in your repo that is always up to date. For everyone. The plan generates and Claude Code can immediately read those task files and start executing. No MCP setup. No copy-pasting context. No re-explaining the project. The agent just knows what to build and why.

"Let's implement the Q3 onboarding adjustments brief." That's all it takes.

And as the rest of the team ships their own briefs, makes decisions, updates blueprints, your .hamster folder stays in sync. You don't manually update CLAUDE.md. It and all other contextual information stays current without any overhead.

Or, if you don't want to sit in Claude Code orchestrating task by task, Hamster Horde delivers it in the background. You work across multiple briefs at a higher level of abstraction. You can now work across dozens of initiatives at once, jumping from brief to brief to define, refine and align what's to be delivered before handing it off to Hamster or your team to implement. 

Out comes PRs, reviews sail through because the implementation is a step change, not a monster, and it lands into production soon thereafter.

We use this to build Hamster itself. It's just how we work now.

Learn about the Hamster method:

Open article: The Hamster Method by tryhamster.com

taplio

The Battle

Simon Brossard

Eyal Toledano

Followers

Posts

Engagements

Likes

Performance ScoreEyal Toledano's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Simon Brossard

Eyal Toledano

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Eyal Toledano's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreEyal Toledano's LinkedIn Performance