Lucas Perret

lemlist

Operations Lead

Sales Operations Manager

Growth Manager - Product & Ops

Growth.Talent

Community Member

Miuros

Growth Marketer

Pretto

Netatmo

Netatmo is a leading smart home company creating simple, beautiful smart solutions for a safer and more comfortable home.

My missions: 
- Reported weekly business results and marketing campaigns results, shared best practices internally
- Created and managed marketing assets (product sheets, Amazon A+ pages and Amazon store, landing page, user cases...)
- Conducted customer analysis (price sensitivity, average shopping basket, loyalty...) with recommendations

Junior Product Marketing Manager

BNP Paribas Cardif

BNP Paribas Cardif insures 100 million clients in the world. As the insurance subsidiary of BNP Paribas, it is the leading provider of personal insurance solutions.

My missions: 
- Preparation and organisation of the monthly strategic committee with the marketing and commercial directors of the 35 CARDIF countries: presentations intended to train, inform, inspire and raise awareness on the major trends of the market
- Market watch (trends, innovations, competition, new players) and proposal of new insurance concepts
- Identification of the highest potential markets
- Strategic recommendations and key success factors for each of the selected countries
- Analysis of the home & car insurance portfolio

Marketing Strategy Analyst

Synomia

> For a return of 3 months as a Data Consultant. I have been able to support a multitude of stakeholders (SMEs, ETIs, large groups, agencies, firms, institutes, etc.) by responding to their marketing and communication issues.

My missions: 
- Identification of business opportunities on the digital environnent 
- Social listening: data collection, sentiment analysis, identification of customers insights on social media
- Participation in the development of new business solutions
- Organization of training to help clients handling Synomia digital tools

Data Consultant

Synomia - Agence Conseil en Data

> Elected as one of eight key Data startups for the year 2017 by Maddyness and the Hub Institute, Synomia is a Consulting Agency specialized in data marketing.
As a data consultant, my role is to use our home-developed artificial intelligence software to draw insights which serve to define my clients brand’s platform and multi-channel communication strategies, highlight market growth opportunities, and improve customer satisfaction.

Client’s problematics include: production of editorial content, development of marketing offers, building communication strategy, SEO performance and optimization , web marketing, social media monitoring

Main projets: 

- Gap analysis and identification of opportunities
-Performance monitoring 
-Support the creation of editorial content for several clients

Data Marketing Consultant

Starterre

> Starterre is an independent automotive distributor that distributes vehicles of all brands from all over Europe.

My missions: 

Market study
-Competitive intelligence
-Pricing study
-Pricing

Supplier negotiation
-Evaluation and selection of tenders

Quality control:
-Inspection of goods

Junior International Purchaser

Agrati Group Fastening Systems

> Agrati is the worldwide leader in fastening solutions. 

Internal project  for MAN Trucks
-Understanding  business issues regarding a key account
-Process analysis and modelling  (customer service, supply, logistic, IT and quality)
-Gap analysis in order to define new process answering to the customer need
-Participation  to the negociation with suppliers
-Organisation of a big amount of data and information into a report for the top management
-

Sales & Marketing Director assistant

Operations Lead @lemlist

Just a guy obsessed with tech and ways it solves business problems 🤓

I believe people should spend all of their time on meaningful activities such as building relationships with others.

That’s why I spend all of mine solving the inefficiencies I encounter at work by building the right processes and systems for my team.

I am all about networking and discussing anything related to operations, so if you are interested in having a quick chat then feel free to reach out to me. 💌

Blitzit

- Key role in product development, growth, and ideation
- Designing, architecting, cost optimising, team building

What a Story

- Key role in Business growth/ideation
- Workforce/Infrastructure Planning
- Technology innovation and integration in-line with business

ZapBG

allaboutchild

- Key role in website design, strategy, and ideation
- Provided consulting in platform education impact, and cost optimisation

Technical Advisor

Rāunak Hajela

Our long-awaited mobile timer is finally ready 🙌

Now we're just waiting for the Android and iOS review teams to approve the release.

From the outside, it looks like a feature that took months.

But the part users never see is the work that sits behind it.

We're a tiny team building a desktop app and a mobile app that stay perfectly in sync.

One small change in the wrong place and the entire tracking system can break.

→ some days the desktop update creates issues on mobile.
→ some days the mobile build waits because we do not have an API for it yet.
→ some days web developers take decisions that work for desktop but hurt mobile.
→ some days we fix a bug and create another one by accident.
→ some days a crash only happens on one device and we cannot reproduce it.

And between all this there is coordination.

Design reviews.

Testing cycles.

Feedback loops.

Unexpected blockers.

New issues that must be fixed before anything else.

And vague reports like “something isn't working” without clear steps.

We also spent a whole year hiring, firing, and training.

Some devs needed time to learn.

Some didn't understand the vision.

Some left before they found their rhythm.

Finding the right people took almost 11 months.

This is the quiet side of building a product.

The part no one claps for.

The part users never see.

But this is where most of the work actually happens.

Every new app feature goes through this journey.

Every improvement carries more complexity than it looks.

And since we're still in beta, things will break.

Some issues we'll catch early.

Some we'll only discover when hundreds of people start using the app.

We're learning, improving, tightening the system one release at a time.

And if there's one thing this year has taught me, it's this:

Building a good product isn't about speed.

It's about staying consistent long enough for the work to compound.

Raunak Hajela.

Co-founder & CTO of Blitzit | 12 years in software development | Helping UK SaaS founders ship faster with clear product direction (Techstars + Series A/B backed)

OpenAI released “State of Enterprise AI” report 3 days ago.

It analyzed usage data from 1M business customers and surveying 9K workers.

The enterprise usage is accelerating fast.

Weekly ChatGPT messages inside companies grew 8× in the last year.

The shift is not from “no AI” to “AI”.

It’s from experimenting → to building repeatable workflows → to automating real work.

The time savings are meaningful.

Most employees save 40–60 minutes a day.

Heavy users save 10+ hours a week, an entire extra workday.

The case studies were even more interesting:
→ Lowe’s handles over 1M customer questions monthly through an AI assistant.
→ Indeed users find jobs faster with their AI career tools.
→ Moderna cut weeks of analytical work down to hours.
→ BBVA automated thousands of legal queries using custom GPTs.
→ Intercom’s AI resolves more than half of its support calls.

What surprised me was that a big percentage of enterprise users still haven’t touched reasoning models, data analysis or search even though they’re included by default.

For SaaS builders like me, AI is shifting from being a feature to becoming part of the workflow itself.

Teams that learn to use it deeply will pull ahead.

Teams that treat it as “optional” will feel the gap very soon.

If you’re building in tech, this report is worth reading.

Building Blitzit this year has been a mix of wins and wake up calls.

Some days we ship features people love.

Some days we wake up to messages saying the app feels slow or buggy.

That's the truth of running a tiny team trying to build something meaningful.

But even with the ups and downs, one thing stayed constant.

People kept using Blitzit every day.

They kept giving feedback.

They kept pushing us to improve it.

So this week, instead of pretending everything is perfect, we're doing something simple.

We're making Blitzit more affordable for the people who believe in what we're building.

Our lifetime deal is live for Cyber Week at $77.60.

Pay once.

Use it forever.

Get every update we ship, good or bad, as we fix, improve, and grow.

The link is in the comments 👇

#cybermonday #blackfriday #productivity

Most founders struggle with Indian developers for the same reason they struggle with any remote team.


They expect great output without setting up a great environment.


Here's what most founders should do when working with Indian devs, but rarely do:

→ Give clear written requirements instead of hoping the dev gets it.

→ Share the full context, not just tasks.

→ Encourage them to push back instead of staying silent.

→ Use async communication so time zones don't slow everything down.

→ Set expectations for quality early.

→ Create psychological safety so they can admit blockers without fear.

→ Give realistic timelines instead of “we need this tomorrow” every week.

→ Treat them like partners, not task takers.

→ Let them be part of product decisions, not just execution.

→ Pay on time.

→ Stop checking in every hour and let them focus.


And appreciate great work when you see it.


Most developer issues are really “founder systems” issues.


Fix the environment and the output improves on its own.

Most founders say they want talented devs.

But then they treat them like task takers.

Assign task. Set deadline. Ask for update. Repeat.

That's not how you build a good software.

Devs do their best work when they understand the vision behind the task.

When they know why something is important.

Not just which ticket to pick on JIRA.

I've seen avg. devs turn exceptional the moment they feel trusted to think, not just mindless code.

And I've seen talented devs shut down because every decision was already made for them.

When they aren't allowed to question anything.

When their ideas die before they're even heard.

When the message becomes “just do what's told”.

At that point, you didn't hire a dev.

You hired a highly paid typist.

If you want builders, give them room to build.

If you want ownership, give actual ownership.

Share context. Let them question. Invite them into the problem, not just the solution.

Because software only moves fast when the people building it are allowed to think.

December is supposed to be my slow month.

But somehow it always becomes the busiest.

New features to ship.

Critical bugs to fix.

Asana integration, mobile timer, performance upgrades, drag and drop fixes… all on the table.

Winters are tough for me because of muscular dystrophy.

Cold hands, slow movement, less energy.

So I try to keep the workload light.

But this is also the time when the most work shows up.

More ideas.

More opportunities.

More things that need my attention.

The only reason this is even possible is my team.

They handle what I physically cannot.

They keep the product moving when I am slower than usual.

I honestly cannot imagine running Blitzit without them.

There's still a lot we need to improve.

More stability.

More integrations.

More missing pieces to complete.

More polish for the users who use Blitzit daily.

But for the first time in a long time, I feel confident.

Confident in Blitzit.

Confident in our direction.

And confident in the people building it with me ❤️

Your most valuable asset as a SaaS founder is your engaged users.
 
Not the funding. Not the code. Not even your staff.
 
Your engaged users.

Because everything else can be copied or outspent or disrupted in a quarter.

But the trust and connection you build with users compounds for years.

It gets stronger the more you invest in it.

It pays you back in retention, referrals, and honest criticism.

In a world where anyone can clone your features, your relationship with users is the only advantage that grows instead of shrinking.

Every dollar of MRR comes from someone who logs in again and again because your product solves something for them.

Product market fit is not a vibe.

It is a behaviour pattern.

Users who come back without reminders.

Users who complain when something breaks.

Users who bring their friends.

Users who ask for more.

Everything else is replaceable.

Money can be raised.

Features can be rebuilt.

Teams can grow.

But a core group of users who rely on your product?

You cannot hire them.

You cannot buy them.

You earn them.

The products that win are not the most advanced.

They're the ones people quietly build habits around.

Users who open your app before opening WhatsApp.

Users who feel something's missing when your service is down.

Users who refresh the page hoping a new update has arrived.

You can keep improving your UI.

You can rewrite your backend.

You can rebuild features from scratch.

But earning a place in someone’s daily routine?

That is the hardest problem in SaaS.

And the moment you solve it, everything else becomes easier.






---
📌 Like & Repost, if you find this helpful.

And follow me for more.

Some founders treat ‘'hire fast fire fast'' like a productivity hack.


But firing a developer rarely fixes the actual problem.


Most slowdowns don't start with the developer being incompetent.


They start with unclear specs, shifting goals, and rushed decisions.


I've seen founders blame performance instead of admitting the truth:
→ the requirements changed twice in a week
→ the design arrived after development started
→ marketing needed something completely different
→ no one agreed on what ‘'done'' even meant


In that kind of setup, even the most senior engineer will look slow.


But instead of fixing broken coordination, founders take the shortcut.


Fire the dev. Hire a new one. Repeat the same mess.


It is like firing the chef when the recipe keeps changing every 10 minutes.


It feels decisive.


But it solves nothing.


If you want your team to move faster, improve the system.


Not just replace the people trapped in it.

Your devs don't burn out from work.

They burn out from feeling stuck.

I hear this all the time:
“I’m bored.”
“I don't feel like I'm growing.”
“I want to build something of my own.”
“I want to earn more.”

These aren't complaints.

They're signals.

Signals that something inside the team is off.

And no amount of perks or pizza Fridays will fix that.

Your devs want ownership.

They want to understand the problem, not just complete the milestone.

They want to see if their work actually helped a user.

They want small wins, not three-month sprints with nothing to show.

They want space to learn, experiment, and try ideas without feeling judged.

They want to feel trusted enough to think, not just execute.

And most of all, they want to know where they're heading next.

Some devs love backend architecture.

Some love polishing UI.

Some love refactoring messy code.

If everyone is doing everything, nobody is doing their best work.

The quickest way to lose good engineers is to ignore what motivates them.

Great engineers don’t leave for money or titles.

They leave when the work stops feeling meaningful.






---
📌 Like & Repost, if you find this helpful.

And follow me for more.

It's Monday… and it didn't start the way I hoped.


We woke up to several reports about Blitzit feeling slow, laggy, and buggy for some users.


Not the kind of week start any dev wants, but it is part of building software.


Our recent marketing push brought in a large wave of new users. 


This spike puts more pressure on our infrastructure than usual.


This surge in activity exposed some optimisation opportunities that weren't as noticeable before.


We are working on performance fixes across the app and releasing improvements throughout the month.


This is not a setback. It is a reminder that progress is not just shipping new features. 


It is also keeping the foundation stable for the people who rely on us.


And to everyone who reported the problems early, thank you. It helps us focus on the right things.

Some developers make your life harder.

And some make everything feel effortless.

The ones who get the vision without needing a 20 page brief.

The ones who take a sprint and come back with more than you asked for.

The ones who treat the client’s money like their own.

Who feel responsible when something slips.

Who care about the product, not just the tasks.

You cannot teach this.

It is ownership. It is pride. It is love for building software.

It took me almost a year to find someone like that.

We hired. We tried. We failed. We kept looking.

And finally found the kind of nerd we were searching for since Feb.

If you ever find people like this, keep them close.

They don't just build features.

They build your empire with you.

You're not struggling because you lack technical skills.


You're struggling because you believe:

→ you need a co-founder to start
→ you need funding to build
→ you need a big launch to get users
→ you need the "perfect" dev team


You don't.


You need clarity on what to build.


You need a fast way to test it.


And a partner who can turn that idea into reality. Fast.

taplio

The Battle

Lucas Perret

Rāunak Hajela

Followers

Posts

Engagements

Likes

Performance ScoreRāunak Hajela's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Lucas Perret

Rāunak Hajela

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);}Rāunak Hajela's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreRāunak Hajela's LinkedIn Performance