7 min Read
How Linkroo Uses AI for LinkedIn Content
A look at the content engine behind Linkroo, and what it took to make AI-assisted posting sound like a person.
Nikhil Sharma
Key takeaways
- The hard part of a content engine is not generation, it is capturing the raw thinking that generation works from
- A model given your own ideas produces your voice; a model given a topic produces the category average
- Scheduling and formatting automate completely, the point of view does not automate at all
- The review step is what separates leverage from volume, and removing it is the most common failure
Linkroo started because the bottleneck in publishing consistently was never writing. It was remembering what I thought.
Interesting things happen during work. A problem gets solved in an unexpected way, a client says something that reframes an assumption, a pattern shows up for the third time and finally becomes visible. All of it is genuinely worth writing about, and almost none of it survives to the end of the week.
By the time somebody sits down to write, the specific thing is gone and what remains is a general topic. And a general topic is exactly the input that produces generic output, with or without a model.
Capture is the product
The design decision that mattered was making the system about capture first and generation second.
Ideas get logged as they happen, in whatever fragmentary form they arrive. A sentence. An observation with no conclusion yet. A note that says this keeps happening and I should work out why. No structure required, because requiring structure at capture time is how capture stops happening.
The value accumulates quietly. After a few months there is a body of specific, dated, genuinely held observations. That is the raw material, and it is the thing nobody else has, which is precisely why output built from it does not sound like everyone else's.
What generation is actually for
Given a fragment and a format, turning one into the other is mechanical work.
The thinking already happened. What remains is structure: an opening that earns attention, one idea developed properly, an ending that does not trail off. That craft is real and it is repetitive, and repetitive craft is exactly where models earn their place.
The same fragment can become a short post, a longer piece, a carousel outline or the seed of an article. Each is a transformation of something that already has a point of view.
What the system explicitly does not do is decide what is worth saying. Prompted with a topic and no source material, it produces the same competent, familiar output as every other tool pointed at the same topic. That output is worse than posting nothing, because it spends attention you then have to earn back.
Voice comes from examples, not adjectives
Every attempt to describe tone in the abstract produces the same result. Professional but approachable. Confident, not arrogant. Those phrases describe the entire market.
What works is showing the system your actual writing. Ten pieces you are happy with teach it more about your voice than any description, because voice lives in sentence rhythm, in which words you avoid, in whether you use a colon or start a new sentence. None of that survives being summarised into adjectives.
This has a useful implication. If you have nothing you are happy with, no tooling helps. The first job is writing a few things properly by hand, which then becomes the reference.
The step people remove
The review before publishing is what separates leverage from volume, and it is the first thing removed when the calendar gets demanding.
It does not need to be long. Read it. Does it say what you meant. Would you be comfortable if someone assumed you wrote every word. That is a minute, and it is the difference between a stream of content that builds something and a stream that fills a schedule.
I have watched this go wrong at scale elsewhere on this site, with over a hundred generated posts that produced no meaningful traffic and read exactly as they were made. The tooling was not the problem. Removing the last human step was.
What automates cleanly
- Reformatting one idea across formats and lengths.
- Scheduling and sequencing so nothing is copied around by hand.
- Surfacing older captured ideas that have become relevant again.
- Reporting on what landed, feeding back into what to capture more of.
All downstream of a person deciding something was worth saying.
The principle
Capture aggressively, generate mechanically, review always. That is the whole system, and the first and last parts are the ones that cannot be bought.
FAQ
Quick answers to the most common questions about this topic.
It is a content engine built around capture rather than generation. Ideas get logged as they occur, usually in fragments, and the system helps turn those fragments into posts across formats. The generation is the easy part; the capture is what makes the output sound like a specific person.
Content built from your own thinking performs. Content generated from a topic prompt does not, because it reads as familiar and there is a great deal of it already. The distinction is not whether a model was involved, it is whether there was a point of view for it to work from.
By feeding it your own writing rather than describing your tone. Adjectives like professional and approachable produce the average of everyone who has ever written a brand guideline. Ten real examples of your own work produce you.
Deciding what to say, and the last read before publishing. Everything between those two can be automated safely, and neither of them can.
Existing schedulers are good and cheap. What they do not solve is capture, which is the actual bottleneck for most people with something worth saying. That is the part worth building if you are going to build anything.

Written by
Nikhil Sharma
Founder, DigiBenders
Twelve years shipping software, five of them leading a studio in New Brunswick. I build the software and run the marketing around it, which is an unusual combination and the reason most of my work arrives by referral. One person accountable, and everything ends up in your name.
You read the thinking
Now tell me what you are actually building.
If this was useful, the call usually is too. You describe the problem, I tell you what it takes and whether I am the right person for it.
Thirty minutes, no pitch
Honest read, including when the answer is no
Replies within one business day
Keep reading



