Sponsored LinkedIn post
A dedicated post to introduce your brand to my audience.
Founder & [email removed]
Companies pay Tim to write a post about their product on LinkedIn.
This page is where they book it. Below: Tim's audience, recent posts and price. Naano, the platform behind this page, handles the brief, your approval of the post and the payment.
€125per post, fixed price
or 5 posts for €500 · You approve the post before it goes live
Looking for Tim? View LinkedIn profileA creator yourself? Create your own page
AI phone assistants for the leads you chase too slow and the ones you stopped chasing | [email removed]
Most businesses don't lose deals to a better offer. They lose them to a call nobody made. Someone fills in your form at 21:40. They get an autoresponder email. "We will be in touch within 1 business day." By then they've filled in three more forms, and one of those companies rang them back in 40 seconds. That's the whole game, and it has nothing to do with your marketing. I build AI phone and text assistants that make the calls nobody in your business has time to make: - Speed-to-Lead: every new lead called within 30 seconds, qualified, booked. - Database Reactivation: your dormant list worked call by call into booked meetings. - Inbound Receptionist: answers every call, 24/7, qualifies the job, books it, hands the urgent ones to a human. Done for you. You never touch a dashboard. Built for so far for: Zentur.io, Matthew Logovik, Ilaria Santangelo, Prolumios, one aussie financial service company and one aussie mortgage broker I'm not allowed to name. Also, gen8n.dev is my own build. 100+ registered users in 17 days. Here's what I don't have: a wall of case studies with big numbers on it. The biggest work sits under NDA. What I do have is the scar tissue. I know exactly what breaks between "the demo works" and "it runs in production", because I've hit that wall myself. Telephony routing that adds 5 seconds of latency to a call that sounds perfect on playback. A CRM with no sandbox. An agent that offered to book an appointment it had no tool to book. I'm finishing a degree (digitization & entrepreneurship) while building this, so I can talk offer structure and CRM fields in the same breath as prompts and SIP trunks. Both sides of it, buisiness & AI/IT. How I can help you: → Follow me here and on YouTube to see how the systems actually work. → Book a Database Diagnostic on ximus.io or in my Featured section below. → Or DM me "1" and we'll talk personally. And if you're not ready yet, welcome to my profile anyway. I post about where (voice) AI is actually going, how to use it in your business without burning money on it, and now and then something personal. Inquiries: DM or [email removed]
Public LinkedIn data · Sep 18, 2026
Rolling out Voice AI is fucking hard (the build is not the difficult part). Let me explain TL;DR: Testing a voice agent doesn't give the data you need to fix it. Put it live. See it fail in production. With real users. THEN Fix it. In one of my projects, we're currently almost done with the build. The project is quite complex, 5 different scenarios, same agent, call-back loop, etc. All done. Next step? I do test calls. The issue with that is since I've built the thing, I am biased, more patient and subconsciously I just want it to perform good. Also, I'm not the target user of the agent. Not even close. So I can only test it so much, mainly for the technical stuff like latency and are the answers correct based on what the knowledgebase provides. But, and this is SO crucial to understand, I CAN'T test it like an actual user would. They are messy, ask random questions, bring up unrelated stuff, interact in ways I couldn't ever predict. So the way I fix this is: I can't. After me testing, it's my clients turn to test it. But again, it's the same issue here. Yes, my client is way closer to the actual user. They hopefully know better how these interactions happen. But they're biased too. They also ALWAYS try to break the agent (yes, that's okay and normal and wanted) So the actual fix is, there is none. And this is a hard pill to swallow. You can test an agent indefinitely, find minor flaws here, fix a few prompt issues there, but at some point it just needs to go live. It's like building a startup. With your idea, step number 1 is validation. Aka... you guessed it. Talking to customers. And launching a voice agent is the same (almost). Yes, it needs to be built first but to actually see what's wrong with the way the users use it, it needs to be set live. No agent, in fact I reckon no AI system in general, will perform as good as you want it to from the beginning. Without testing in prod. It's always a process of testing, but most importantly using it in production to see what actually goes wrong. This can't be fixed in UAT testing. So, in short: - I build the voice assistant - I test the voice assistant - my client tests the voice assistant - it goes live to actually get relevant data - it WILL fail live, and that's okay. This is what we want to fix it. And with that, I'll leave you alone, enough rant. More when I know more. | Tim
What happens, when somebody calls you Thursday at 7:23pm? Usually... ... nothing. Mailbox, I reckon. If the caller is lucky, a callback the next afternoon. That's kind of the norm, unforunately. And if you ask me, that's kind of a waste. Because with something like shown in the video, this is an easy fix: A phone assistant, answering incoming calls. But don't get me wrong, an "easy" fix still needs serious engineering: - talking in your business tone of voice - integrating into your systems to actually be able to help the caller - when it should be active (24/7? Only after hours? Always, but only if no actual person answers the phone after the 3rd ring?) These receptionists are popping up everywhere. Your competition is probably thinking about one right now. But often, they leave customers frustrated. Because they weren't properly built. So, should we make sure, yours is bulletproof? DM me if yes. More when I know more. | Tim
Should you use Vapi or LiveKit? (And why this question doesn't make any sense) I have extensively used Vapi in the past. Basically built everything on it. Earlier this year, I tapped into LiveKit, and it kinda stuck with me. So natrually, I've asked this question to myself. "Which of the two should I choose?" And the answer is: That's the wrong question. Comparing the two is a flawed approach, because they're not the same. Both let you build voice agents. Yes, that's obvious. But HOW you build them is completely different. In my latest YouTube video I discussed exactly that, explained the differences... and when to choose which of the two. If Vapi vs. LiveKit is a choice you're facing at the moment... Check out the video with the link in the comments. It'll bring you clarity. More when I know more. | Tim
Choose a format for your next LinkedIn collaboration.
A dedicated post to introduce your brand to my audience.
A series of posts to build visibility over time.
Your collaboration, managed on Naano
How does this price compare? B2B creator rates 2026
Based on 30 people who reacted to or commented on my posts. Percentages use the profiles that could be classified.
Based on 30 people who reacted to or commented on my posts. Percentages use the profiles that could be classified.
Based on 30 people who reacted to or commented on my posts. Percentages use the profiles that could be classified.
Storefront by Naano · Create yours
Tim Kramny is a B2B LinkedIn creator based in Australia with 4,616 followers, posting about AI, Software, and Sales. On Naano, one sponsored LinkedIn post by Tim Kramny costs €125, a fixed price per post.
The Naano team casts the creators, writes the briefs, reviews every draft with you and reports results per creator. You approve the shortlist and every draft.