1. The 'I just fixed this' post
Template: 'Last week a [type of company, e.g. 15-person logistics firm in Linz] came to us because [specific problem, e.g. their order system crashed every Monday morning]. The cause was [plain-English cause]. We fixed it in [timeframe] by [what you did, one sentence]. If your [system/app] does [symptom], it is probably the same thing. Happy to take a look, no charge for the first call.' Use it the same week you finish a real job, while the details are fresh and you can describe them without exaggerating.
2. The 'I will audit 3 of these' post
Template: 'I am doing free 30-minute reviews of [specific thing, e.g. Shopify stores that load slowly on mobile / internal tools built in Access or Excel] for 3 companies this month. You get a written list of what to fix first, even if you never hire us. Comment or DM me with [what you need from them, e.g. your store URL].' Use it when your pipeline is empty and you need conversations this week, not next quarter.
3. The 'hiring vs. outsourcing' post
Template: 'I keep seeing posts like: [paraphrase a common hiring post, e.g. a small firm in Wels looking for one person to handle support, calls and on-site visits]. Many small teams try to hire one person to cover [role A] and [role B]. Sometimes that is right. Sometimes the cheaper move is [what software could do, e.g. a simple ticket system plus a customer portal so one person handles twice the volume]. If you are about to hire for [role], send me the job description and I will tell you honestly which parts software could cover.' Use it when you spot local job posts for support, admin or data-entry roles, because those companies often have a process problem a small build can solve.
4. The 'tagging my network' local post
Template: 'Anyone in [city or region, e.g. Upper Austria / Wels / Linz] running a [type of business, e.g. manufacturing, trades, clinic] still doing [manual task, e.g. scheduling by phone and spreadsheets]? We build small tools that replace that, usually in [realistic timeframe]. Not looking for a big project. Looking for one local company to start with. Tag someone who complains about this.' Use it when you want local clients you can meet in person, and post it in the morning so commenters reach their own networks the same day.
5. The 'rescue project' post
Template: 'If you are a [founder / CTO / head of operations] whose [app/platform] was built by a freelancer or agency that disappeared, I want to hear from you. We take over half-finished and abandoned codebases in [your stack, e.g. Laravel, React, Node]. First step is a [timeframe] code review so you know what you actually have. DM me the stack and what is broken.' Use it to reach non-technical founders and operations leads, who often feel stuck and are ready to pay quickly.
6. The 'honest price' post
Template: 'Questions I get every week: what does a [type of build, e.g. booking system / MVP / internal dashboard] cost? Honest answer from our last [number you can verify] projects: [real range] for [scope], [real range] for [bigger scope]. What drives the price up: [2-3 real factors]. What keeps it down: [2-3 real factors]. If you want a rough number for yours, describe it in a comment.' Use it only with your own real numbers. Price transparency gets buyers to comment because most dev shops refuse to say.
7. The direct DM follow-up
Template: 'Hi [first name], thanks for [commenting / reacting] on my post about [topic]. You mentioned [detail from their comment or profile]. Is that something you are dealing with right now at [company]? If yes, I can send you [the specific free thing from your post] by [day].' Send it within 24 hours to everyone who comments, and to job titles like Operations Manager, COO, Founder or Head of Product who react to your posts. Hulby, an AI cofounder, can draft these posts and DMs and track replies for a founder every day.
People asking this right now
Real, public posts from the last few weeks. Each one is somebody you could help today.
Mistakes to skip
- Listing every technology you know instead of naming one problem for one type of buyer.
- Posting and leaving. Most deals start in the comments and DMs in the first few hours.
- Making up results or client names. Describe real work vaguely before you invent anything.
- Ending without a clear ask like 'DM me your URL' or 'comment with your stack'.
Want this done for your dev shop, every day?
Hulby finds the people asking for what you built, writes every reply and email, and keeps you on it until they pay. Free to start.
Find my first customersQuestions
How often should a dev shop founder post on LinkedIn?
Two to three times a week is enough. Consistency and replying to every comment matter more than volume.
Should I post from my personal profile or the company page?
Personal profile. Company pages get little reach, and buyers want to talk to the person who will build their project.
What if I have no past projects to talk about?
Use the free audit, hiring vs. outsourcing and local post templates. They do not need case studies, only a clear offer.
Who should I connect with before posting?
Founders, COOs, operations managers and heads of product at small companies in your city or niche. Send 10 to 20 connection requests a day without a sales pitch.