Marketing & Growth

How to run a linkedin outreach campaign as Construction and Contractor Founders

Marketing & GrowthFor Construction and Contractor Founders3 apps12 steps~24 min to set up

You run a GC or specialty trade shop under 20 crew. Your best leads come from architects, developers, and property owners you've met on a job site or through a referral — but following up on LinkedIn takes time you don't have when you're also pricing a bid, chasing a sub's COI, and figuring out why your March draws came in short. Most weeks, LinkedIn sits untouched. When you do post, it's inconsistent. You're not sending connection requests to the right people, you're not commenting on the developer posts that would keep you visible, and the GC relationships you want to build sit idle in a queue you never get back to.

Build this on Starch → See the apps used

Marketing & GrowthFor Construction and Contractor Founders3 apps12 steps~24 min to set up

Outcome

What you'll set up

An automated LinkedIn outreach system that sends connection requests to developers, property owners, architects, and commercial real estate contacts matching criteria you set in plain English — running on your schedule without you touching it daily

A CRM that tracks every LinkedIn prospect alongside your email threads and follow-up history, so you know exactly who's seen your request, who's connected, and who you haven't touched in 30 days

A follow-up automation that routes warm LinkedIn connections into your inbox with a drafted first message and flags stale conversations before a deal goes cold

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

LinkedIn Automation CRM Email Agent

Data sources & config

LinkedIn Automation runs through browser automation on your LinkedIn account — no LinkedIn API needed, activity looks human-paced. The CRM connects directly to Gmail via Starch's scheduled Gmail sync, pulling thread history on a schedule so deal context is always current. Email Agent also reads from your synced Gmail and drafts replies inside Starch. Your LinkedIn connection and message history flows into the CRM via browser automation.

Prompts to copy

Run LinkedIn Automation: Send connection requests to developers, property owners, and commercial real estate brokers in [city]. Use this note: 'Hi [first name], I run [Your Company] — we do ground-up commercial and tenant improvement work in [metro]. Reaching out to folks who might need a trusted GC.' Review incoming requests and accept anyone with a title matching owner, developer, broker, or project manager at a development firm. Leave a brief comment on the two most recent posts from people in my feed who are developers or architects.

Build me a CRM for tracking GC business development. I want pipeline stages: Cold Outreach, Connected, Had a Conversation, Active Bid, Closed Won, Closed Lost. Fields per contact: name, company, project type (residential/commercial/mixed-use), estimated project value, how we met, last contact date, and next action. Pull in my Gmail thread history for each contact automatically. Alert me if I haven't touched a Connected or Had a Conversation contact in 21 days.

Set up Email Agent to watch my Gmail for any reply from a LinkedIn connection. When someone replies to a first outreach, draft a response that mentions our recent [project type] work and asks if they have anything coming up in the next 6 months. Flag any unanswered outreach emails older than 7 days.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Install LinkedIn Automation from the Starch App Store. Describe your ICP in plain English: 'Developers, property owners, and commercial RE brokers in [your metro] with active or upcoming construction projects.' Starch builds the targeting criteria from your description.

2 Set your daily outreach limits and connection note template. A note that references your trade, your geography, and a specific project type performs better than a generic one — write it the way you'd introduce yourself on a job site.

3 Tell Starch how to handle incoming connection requests: 'Accept anyone with owner, developer, broker, or project manager in their title at a real estate or development company. Decline recruiters and anyone outside construction or real estate.' Starch reviews the queue through browser automation each morning.

4 Set up daily commenting: 'Leave a brief, genuine comment on the two most recent posts from architects, developers, or GCs in my feed.' This keeps your name visible without you spending 40 minutes on LinkedIn.

5 Install the CRM app from the App Store. Tell Starch the pipeline stages and fields that match how you actually track jobs: project type, estimated value, how you met, bid due date. Starch builds the schema to your description — you're not configuring someone else's template.

6 Connect Gmail via Starch's scheduled Gmail sync. The CRM automatically pulls in email threads for each contact, so when you open a prospect's record you see every email exchange without copying anything manually.

7 Set the 21-day stale-contact alert: 'If a contact is in Connected or Had a Conversation stage and I haven't emailed or logged a note in 21 days, send me a Slack message with their name and the last thing we discussed.' This replaces the Friday afternoon CRM audit you never actually do.

8 Install Email Agent and point it at your outreach threads: 'Watch for any reply to a LinkedIn outreach email. When a reply comes in, draft a response referencing our [trade] work and asking about upcoming projects. Make it sound like me, not a newsletter.'

9 For contacts who connect but don't reply to an initial message, set an automation: 'Seven days after connecting, if no reply, send a follow-up message referencing a specific project type we do — keep it under 3 sentences.' Starch handles this through browser automation on your LinkedIn account.

10 Each Monday morning, pull a CRM summary: 'Show me everyone who moved to Connected or Had a Conversation in the last 7 days, their estimated project value, and my next action for each.' Review it before your week starts instead of digging through LinkedIn notifications.

11 When a LinkedIn connection turns into an active bid conversation, move them in the CRM and let Email Agent handle follow-up sequencing until the bid is out the door or the job is closed.

12 Monthly, ask the CRM: 'How many connections did I make this month, how many turned into conversations, how many are active bids, and what's the total estimated value in my pipeline?' Use this to decide whether to increase outreach volume or shift the ICP criteria.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

April 2026 Outreach Push — Commercial TI Pipeline

Sample numbers from a real run

Connection requests sent (LinkedIn Automation)	120
Accepted connections	34
Replies to first message	9
Active bid conversations opened	3
Estimated bid value in pipeline	1,850,000

In April, LinkedIn Automation sent 120 connection requests to developers, commercial RE brokers, and property owners in the Denver metro over four weeks — about 6 per day, human-paced through browser automation so LinkedIn didn't flag the account. 34 accepted. Email Agent drafted a first message for each new connection referencing recent tenant improvement work; 9 replied within a week. Three of those turned into phone calls about upcoming projects: a 4,200 SF office TI at $480K, a warehouse fit-out at $620K, and a multifamily common-area renovation at $750K. The CRM tracked all 34 connections with their last contact date and project type, and flagged 6 connections who hadn't heard from you in 21 days — two of those produced late replies that might turn into Q3 bids. Total time spent by you on LinkedIn that month: under 30 minutes reviewing the weekly summary Starch sent on Monday mornings.

Measurement

How you'll know it's working

Connection request acceptance rate (target: 25–35% for a well-targeted ICP)

Reply rate on first outreach message (tracks whether your note and targeting are working)

Connections-to-bid-conversation conversion (the number that tells you if LinkedIn is actually producing work)

Total estimated bid value sourced from LinkedIn outreach per month

Stale contacts rescued by 21-day alert (measures how much pipeline you'd have dropped without the follow-up)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Doing it manually on LinkedIn

Free, but realistically gets done about once a month when you remember — inconsistency kills the relationship-building effect that makes LinkedIn work for contractor BD.

Dux-Soup or Expandi (LinkedIn automation tools)

Purpose-built for LinkedIn volume, but they don't connect to your CRM, your email, or your job data — you still need to track everything manually and stitch the follow-up together yourself.

HubSpot Sales Hub

Solid CRM and sequencing, but you're paying $90–$450/month per seat, spending days configuring it, and it won't run your LinkedIn outreach — you'd still need a separate tool for that.

Spreadsheet + manual LinkedIn

Zero cost, full control, and you already know how to use it — but a spreadsheet doesn't send follow-ups, doesn't alert you when a contact goes cold, and doesn't draft your replies.

On Starch RECOMMENDED

One platform — linkedin automation, crm, email agent all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Will LinkedIn flag or restrict my account if Starch is running automation?

LinkedIn Automation runs through browser automation — Starch acts the way a person would, at human-paced speeds, not via the LinkedIn API. This is how it avoids the rate limits that get most automation tools flagged. That said, no automation tool can guarantee LinkedIn won't ever restrict an account; keeping daily volumes reasonable (under 20–25 connection requests per day) reduces that risk significantly. Starch lets you set those limits when you configure the app.

I don't have a CRM right now — do I need to set one up before I start outreach?

No, but you'll want one running within the first week. If you start sending 20+ connection requests a day with no system to track who replied and who's been sitting for 21 days, you'll lose the warm leads. The Starch CRM takes about 10 minutes to describe and set up — tell it your pipeline stages and the fields that matter to your business, and it builds the schema for you. You can also start with the pre-built CRM template from the App Store and adjust from there.

My connections are mostly on LinkedIn but my real BD happens through email and phone. Does this actually help if I'm not a heavy LinkedIn user?

Yes, and that's actually the right use case. LinkedIn Automation handles the top-of-funnel — finding and connecting with the right people so they know your name. Once someone connects or replies, Email Agent picks up the thread in Gmail, which is where your actual conversations happen. You don't have to live in LinkedIn for this to work; Starch runs the front-end while you handle the relationship from your inbox.

Can Starch pull my Buildertrend or CoConstruct project data into any of this?

Buildertrend and CoConstruct aren't in Starch's scheduled-sync providers, but Starch automates them through your browser — no API needed. You can build an automation that pulls active job names and statuses from Buildertrend via browser automation and surfaces them in your CRM, so when you're talking to a prospect you can reference your current capacity honestly. Describe what you want and Starch builds it.

Is my LinkedIn login and message data secure? Starch isn't SOC 2 certified.

Starch is honest about this: it is not SOC 2 Type II certified today. Browser automation sessions run through isolated browser instances — one session per task, not shared. Your LinkedIn credentials are stored in Starch's credential vault. If SOC 2 certification is a hard requirement for your business, that's worth knowing upfront.

I want to target developers in a specific zip code or project type. How specific can the ICP get?

Pretty specific. You describe the ICP in plain English — 'developers and property owners within 30 miles of [city] who work on commercial or mixed-use projects between 5,000 and 50,000 SF' — and LinkedIn Automation uses that as its targeting criteria when browsing and selecting who to reach out to. You can also tell it which titles to skip (recruiters, individual agents, residential-only buyers) so it's not wasting requests on the wrong people.