Fabian Hedin's audit covers 8 public posts, including 8 with both reaction and comment counts. The measured median is 359.5 interactions. AI & building products is the most represented detected theme (5/8; themes can overlap). Start with a concrete follow-up to an existing subject, then test the opening and reply invitation across a consistent four-week sample.
8 of 8 posts have both public counts. Their median is 359.5 interactions. Compare future experiments with your own sample rather than an unrelated peer score.
“Today we raised $400M at a $13.3B valuation. Since I’m feeling nostalgic, this is where it started:” has 1,567 visible interactions. That is 4.4× the sample median. Its topic and opening are candidates for a follow-up experiment; this does not identify why it performed.
1 of 8 posts contain a question. Measured posts generated 6.7 comments per 100 reactions. Counts can include the author's replies and do not measure lead quality or sentiment.
The median gap between sampled dates is 13 days; the longest is 63.9 days (7 intervals). Missing posts can exaggerate gaps, so this is not a complete publishing calendar.
Profile & visual identityImage preview, section grades, missing data and specific fixesExplore
SOURCE PROFILE PREVIEW
Fabian Hedin
Headline not supplied by the source
These are source images, which may be resized. An unavailable image does not mean it is missing on LinkedIn.
PROFILE CHECKLIST
Your first impression, section by section.
Open any section to see the evidence and a practical fix. Unknown data is not a failed check.
Profile picture
A+15/15 observed points
15 / 15 points assessable
PassProfile image supplied5/5
What we observed
The source supplied an image URL.
Keep it strong
Choose a current, recognizable photo. Preview the circular crop at comment size and leave space around your head.
PassImage decodes and fits its display shape10/10
What we observed
Returned image: 200 × 200px. Dimensions and decoding were measured on the returned image, which may be a resized LinkedIn thumbnail. Original resolution, face framing, lighting and professional suitability were not assessed automatically.
Keep it strong
Use a square original, check sharpness at full size, and preview the circular crop. A small provider thumbnail does not prove your original upload is low resolution.
Cover & visual identity
A+10/10 observed points
10 / 10 points assessable
PassCover image supplied5/5
What we observed
The source supplied an image URL.
Keep it strong
Use a simple cover that says who you help and what you do. Keep important text clear of the profile-photo overlay.
PassImage decodes and fits its display shape5/5
What we observed
Returned image: 800 × 199px. Dimensions and decoding were measured on the returned image, which may be a resized LinkedIn thumbnail. Original resolution, face framing, lighting and professional suitability were not assessed automatically.
Keep it strong
Preview your cover on desktop and mobile. Start with a 1584 × 396 canvas and keep the message readable without tiny text.
Name & identity
A+10/10 observed points
10 / 10 points assessable
PassReadable display name5/5
What we observed
Source text: “Fabian Hedin”
Keep it strong
Use the name people know you by, consistently across your profile and other professional channels. Single names and all writing systems are supported.
PassName field stays focused on identity5/5
What we observed
Source text: “Fabian Hedin”
Keep it strong
Move URLs, contact details and sales calls to action into About or Contact info. Keep your actual name unchanged.
Headline & positioning
UnknownNeeds source data
0 / 15 points assessable · partial coverage
UnknownHeadline supplied—
What we observed
Not returned in readable form by the source.
What to do
State your role or specialty in the headline, using terms your intended reader understands.
UnknownEnough context to explain your work—
What we observed
Not returned in readable form by the source.
What to do
Use this structure: [role or specialty] · Helping [audience] achieve [outcome]. Replace every bracket with a truthful detail.
UnknownHeadline is concise enough to scan—
What we observed
Not returned in readable form by the source.
What to do
Keep the headline focused on one main promise. Move your longer story into About.
About & descriptions
Partial5/5 observed points
5 / 20 points assessable · partial coverage
PassReadable introduction5/5
What we observed
Truncated source excerpt: “Working with top CTOs, Founders and IOI medalists out of Europe to build the last piece…”
Keep it strong
Lead with who you help, the problem you solve and the work you do today.
UnknownAn introduction with supporting detail—
What we observed
Truncated source excerpt: “Working with top CTOs, Founders and IOI medalists out of Europe to build the last piece…”
What to do
Add a specific example of your work, your approach, and the kinds of opportunities you welcome. Length is a structure check, not a quality guarantee.
UnknownEasy-to-scan paragraph structure—
What we observed
Truncated source excerpt: “Working with top CTOs, Founders and IOI medalists out of Europe to build the last piece…”
What to do
Break About into short paragraphs: current focus, relevant proof, then how to connect.
UnknownA clear next step—
What we observed
Truncated source excerpt: “Working with top CTOs, Founders and IOI medalists out of Europe to build the last piece…”
What to do
End with one relevant next step, such as who should message you and what to include. This automated check recognizes English phrases and links; review other languages manually.
Experience & proof
UnknownNeeds source data
0 / 15 points assessable · partial coverage
UnknownProfessional experience identified—
What we observed
No readable entries were returned. We cannot conclude this section is empty.
What to do
List relevant roles with an accurate title and organization. Connect them to the work you want to do next.
UnknownExperience includes useful descriptions—
What we observed
Not returned in readable form by the source.
What to do
For each relevant role, explain your responsibility, a concrete contribution, and an outcome you can substantiate. Do not invent numbers. Masked source descriptions need manual review.
Education & learning
UnknownNeeds source data
0 / 10 points assessable · partial coverage
UnknownEducation or learning entry identified—
What we observed
No readable entries were returned. We cannot conclude this section is empty.
What to do
Add relevant education or structured learning you want to share. Name the institution or course accurately; formal degrees are not required for a strong professional story.
UnknownLearning context is described—
What we observed
Not returned in readable form by the source.
What to do
Describe your subject, course or qualification and one relevant project or skill. Use the full qualification name where helpful. We assess clarity, never institution prestige or degree level.
Location & context
A+5/5 observed points
5 / 5 points assessable
PassReadable location5/5
What we observed
Source text: “Stockholm”
Keep it strong
Use an accurate city or region if you want it visible. Do not add a home address. Omitted provider data is not penalized.
Read all available profile text
Headline
Not returned in readable form by the source.
About
Working with top CTOs, Founders and IOI medalists out of Europe to build the last piece…
This is a truncated source excerpt.
Experience
No readable entries returned.
Education
Name unavailable
Kungliga tekniska högskolan
Hidden entries are omitted from this readable preview. Source text is not independently verified.
VISUAL REVIEW
Check how your profile looks.
The automatic image grade checks file readability and shape. Use this checklist to review the visual choices it cannot judge.
Is your face recognizable in the small circular crop?
Is the image sharp, evenly lit, and free of distracting clutter?
Does the banner communicate your work without overlapping your photo?
Are colors and typography consistent with your professional identity?
A transparent presentation checklist, not a LinkedIn ranking, talent assessment or prediction of reach. Grade thresholds: A+ 90, A 80, B 65, C 50, D 35, F below 35.
Score = earned points ÷ assessed points × 100. Coverage is assessed weight out of 100. Unavailable and masked data are excluded. Scores with different coverage are not directly comparable.
Truncated text earns only checks already demonstrated in the visible excerpt; the unseen remainder is not marked wrong. Text rules measure structure, not factual accuracy, writing quality or every language equally.
Photo and banner grades cover image availability, decoding and shape only. Face framing, lighting, expression, visual style and authenticity require a human review. No appearance, identity or personality judgments are made.
An education entry is evidence of profile context, not verified credentials. School prestige, age, degree level and background do not affect the score.
Section weights: photo 15, cover 10, name 10, headline 15, About 20, experience 15, education 10, location 5. Passed checks earn their full weight; improvements earn zero; unknown checks are excluded.
PerformanceYour own baseline, strongest posts and publishing rhythmExplore
YOUR OWN BASELINE
Performance, with perspective.
Interactions across the sample
Publication date · UTC
622
04-15
360
05-28
359
06-01
323
06-09
1,567
08-12
197
08-26
406
08-27
172
09-09
View chart data
Measured interactions by post
Date UTC
Reactions
Comments
Total
2026-04-15 17:34
593
29
622
2026-05-28 20:19
350
10
360
2026-06-01 17:01
336
23
359
2026-06-09 13:01
304
19
323
2026-08-12 10:00
1,432
135
1,567
2026-08-26 09:58
187
10
197
2026-08-27 14:22
386
20
406
2026-09-09 14:56
165
7
172
Post totals at collection time. Older posts have had more time to collect reactions and comments.
EARLY VS RECENT SAMPLE
359.5→301.5
Median visible interactions: 359.5 for the earliest 4 measured posts and 301.5 for the latest 4. This compares selected posts of different ages, not account growth.
TYPICAL VS STRONGEST
359.5/1,567
Median / highest measured interaction total. A breakout can lift the average; the median provides another view of a typical sampled post.
Publishing rhythm
Median gap: 13 days · Longest gap: 63.9 days · 7 observed intervals.
Explore 4 groups and supporting posts
Publishing days in UTC — descriptive, not recommended times
Unknown means the source did not verify the format. Small or unequal groups do not establish a winning format.
Hooks and writing structure
Read writing structure for 8 posts
Text rules applied to every sampled post
Opening
Hook type
Words
Paragraphs
Final CTA
Tags / mentions
There is a huge services ecosystem forming around Lovable.
Statement
95
6
Not detected
0 / 0
Nakul Narayan is joining Lovable as Head of Product.
Statement
45
3
Not detected
0 / 0
We have created over 66.8 million git repositories.
Number-led
106
6
Not detected
0 / 0
Today we raised $400M at a $13.3B valuation. Since I’m feeling nostalgic, this is where it started:
Number-led
239
7
Not detected
0 / 0
We released a study today that shows who is behind the more than 50M projects built on Lovable. 720M
Number-led
124
4
Not detected
0 / 0
We switched our default tech stack for our users from a custom Vite setup, to TanStack Start. Our us
Number-led
56
3
Not detected
0 / 0
I'm proud to see Lovable on Redpoint InfraRed 100.
Number-led
141
6
Not detected
0 / 0
Patrik "Totte" Torstensson has joined Lovable as Head of Engineering.
Statement
81
4
Not detected
0 / 0
Hook type uses the first nonempty line. CTA detection checks the final paragraph for a question or action phrase. Paragraphs use blank-line breaks. These rules can miss meaning and linked mentions.
Hashtags in the sample
No data available for this grouping.
Tags travel with the topic, author and format. These associations cannot isolate a hashtag's effect.
Recommended next stepsPrioritized actions, effort and what to measureExplore
PRIORITIZED RECOMMENDATIONS
Less guessing. Clear next steps.
Ordered from building a useful baseline to testing individual writing choices. Potential impact describes the purpose of an experiment, not a promised uplift.
01Develop a specific follow-up
Medium effort
OBSERVATION
The sample includes “Today we raised $400M at a $13.3B valuation. Since I’m feeling nostalgic, this is where it started:”. Its visible interaction total is 1,567.
DO THIS
Build a follow-up to “Today we raised $400M at a $13.3B valuation. Since I’m feeling nostalgic, this is where it started:”. Add a concrete example, a decision you made and one lesson. Keep the format similar so topic development is the main experiment.
Potential impact: Test repeatable interest in an existing subject
Metric to watch: Reactions and comments after the same seven-day window; compare with the baseline median
Median text length is 101 words with 5 paragraphs. 3 of 8 openings are classified as statements.
DO THIS
For the next post related to “Today we raised $400M at a $13.3B valuation. Since I’m feeling nostalgic, this is where it started:”, open with a specific problem and a concrete outcome you can substantiate. Move context into the second paragraph. Avoid invented results or curiosity gaps that the post does not resolve.
Potential impact: Improve clarity; any engagement effect remains to be tested
Metric to watch: Median interactions across at least three comparable posts per opening approach
0 of 8 final content lines contain a detected question or action phrase; 1 posts contain a question anywhere. These are text rules, not semantic judgments.
DO THIS
End one upcoming post with a focused trade-off question connected to ai & building products. Ask readers to share a decision and why. Read replies before deciding whether the discussion was useful.
Potential impact: Test whether a clearer invitation supports useful discussion
Metric to watch: Public comments per post and manual review of reply relevance
04Choose a sustainable publishing experiment
Medium effort
OBSERVATION
8 dated posts span 146.9 days. Observed cadence is 0.3 posts per week.
DO THIS
Choose two slots per week for the four-week experiment below, or reduce the schedule if your capacity is lower. Keep the slots consistent and log every published post. Two slots are a planning choice, not a LinkedIn benchmark.
Potential impact: Create comparable records and a manageable learning loop
Metric to watch: Planned versus published posts, time spent, and median interactions at seven days
0 of 8 posts contain hashtags and 0 contain visible @mentions. LinkedIn may return linked mentions as plain text, so detection can undercount.
DO THIS
Use relevant topic labels only when they clarify the subject. Mention people only when they contributed or are directly relevant. Test a consistent tagging approach on comparable posts; do not attribute performance changes to tags alone.
Potential impact: Keep context and attribution useful
Metric to watch: Median interactions for tagged/untagged samples, with sample sizes and topic differences
Turn one idea related to “Today we raised $400M at a $13.3B valuation. Since I’m feeling nostalgic, this is where it started:” into a concise checklist or document post. Keep a similar topic and ask the same type of question. Label this a new format experiment, not a proven winning format.
Potential impact: Learn whether a different presentation helps explain the same idea
Metric to watch: Public interactions at the same post age; at least three posts in each format before comparison
Content ideas & basic outlineThree starting ideas and a simple structure for your next postExplore
INCLUDED IN YOUR FREE REPORT
A starting point for your next post.
Simple ideas from this profile’s available evidence. Choose one, add your own experience, and review the result.
IDEA 1
The next chapter
Follow up on “Today we raised $400M at a $13.3B valuation. Since I’m feeling nostalgic, this is where it started:”: what changed since publishing, what stayed difficult, and the next step. Only include outcomes you can verify.
Break the work behind “Today we raised $400M at a $13.3B valuation. Since I’m feeling nostalgic, this is where it started:” into three decisions. Add an example or screenshot you have permission to share.
Today we raised $400M at a $13.3B valuation. Since I’m feeling nostalgic, this is where it started:
Three years ago, on my birthday, I wrote Lovable's first line of code. We wanted to build what we believed the future of software creation should look like.
During the first year of extremely hard & dedicated work, we failed to launch our product twice. The third time, something clicked. People started creating real products with it, and inside companies, teams started building the internal tools. Within a year we'd reached millions of founders and employees at half of the Fortune 500.
The growth of LovableLovable hinged on word of mouth. People suddenly had a way to act on their creative ideas, and they told other people about it. That's still true today. More than 60 million projects built, 1.2 million new ones every week, and over 900 million monthly visits to what people build. That’s an order of magnitude more than the reach of lovable itself.
Though the platform evolves, our users' ambition to create has remained constant. Unleashing their ambition, removing any friction, making creation seamless, and empowering a new generation of builders is our mission. Our work is about constantly pushing the frontier of which ideas can be turned into reality.
People do no longer just build their products on lovable, they run & grow their businesses.
Every day, I’m grateful for this team and their hard work. ❤️🚀
Patrik "Totte" Torstensson has joined Lovable as Head of Engineering.
This is a hugely important role for us, as this will directly impact the speed and quality with which we're able to improve the product. Lovable's entire 70-person Engineering team will report to Totte.
Totte has led engineering at every level at Spotify, Google, and Meta. He came recommended to us by Daniel Ek and Marcus Frodín.
He's also Swedish, and moving from SF to Stockholm to work from Lovable's HQ.
Nakul Narayan is joining Lovable as Head of Product.
Lovable's next chapter is about helping people run and grow what they build. Nakul's spent his career helping people build things that last.
Now he'll help our users do the same.
Welcome to the team, Nakul.
I'm proud to see Lovable on Redpoint InfraRed 100.
The list honors 100 transformative companies in cloud infrastructure.
We have done a lot of work on Lovable Cloud. We've acquired, and hired some of the best talent in the world, and the platform now has capabilities for frontend, backend, database, ai inference, and more. It serves hundreds of millions of end users every month, and is hosting more than 50 million applications built by companies ranging from solo-founder startups to the largest enterprises in the world.
I just asked Lovsight, our internal AI data analyst agent built by with Lovable:
> How much traffic does lovable built apps have vs lovable itself?
Lovable sites have 27x more traffic than lovable
Glad this work is being recognized, and I consider it an absolute win that our users are driving more traffic than ourselves!
We switched our default tech stack for our users from a custom Vite setup, to TanStack Start. Our users now create over 1 million applications per week on this new tech stack.
This work included reworking how we serve over 60 billion request every month.
Full writeup on what changed and why: https://lnkd.in/d-YpyH5J
We released a study today that shows who is behind the more than 50M projects built on Lovable. 720M monthly visits to Lovable-built projects show that many of those ideas are reaching real audiences.
Four in five Lovable users come from non-technical backgrounds, and more than half have 11+ years of professional experience. They are bringing customer knowledge, industry context, and lived experience into products they could not have built before.
Many are also building with commercial intent: 55% say they are building a business, and 79% are building something they intend to monetize.
People have always had ideas for what should exist, now more of them have a way to make those ideas real. Check out the report here: https://lnkd.in/dGGHYfQb
We have created over 66.8 million git repositories.
We started in 2023 creating all repos on GitHub in the hot path.
By 2024 we had millions of GitHub repos in one GitHub org, which broke down and resulted in a lot of attention around "Lovable bringing down GitHub": https://lnkd.in/eYEE5Nqp
During the day of the incident we had a war room, and we moved to our own git-remote-s3 setup. It served us well.
We have since worked in tight collaboration with Pierre to optimise the system resulting in a 230% improvement in p50 fetch latency over our s3 setup.
https://lnkd.in/ehGcePE2
There is a huge services ecosystem forming around Lovable.
800,000+ people and agencies are building for clients, and 9 in 10 say they can take on more work with Lovable.
The Lovable Partner Program launches today to support this growing ecosystem.
The program gives builders a way to get certified and discovered, while making it easier for companies to find trusted people to build with.
Lovable has changed the speed and cost of building software, making full-service businesses practical across a much broader range of use cases.
more details here: https://lnkd.in/gavSscJ8
165reactions
7comments
A RECORD YOU CAN RETURN TO
Saved audit history.
Reading a saved report does not start a new collection. A fresh snapshot requires confirmation and uses your current review allowance. Refresh availability and shared spending limits are checked before it starts.
A comparison appears after another audit is saved. A single snapshot cannot establish follower growth.
Help improve this report
Independent analysis of publicly available information. Not affiliated with LinkedIn or the profile owner. Impressions, profile views, private analytics, and follower growth are not available in this snapshot.