The engineering accounts that grow all share one move: they translate. They stand in front of a real condition — a cracked slab, a corroded connection, a bouncy floor — and explain in plain language what it is, whether it matters, and what happens next. Creators in this space have drawn audiences in the hundreds of thousands doing exactly this, covering construction mistakes and structural red flags, because the public’s curiosity about why buildings stand or fail is bottomless. Your license is what makes your version of that content different from a random contractor’s: a PE explaining a crack carries authority the algorithm can’t fake.

What doesn’t work is the corporate feed — project award announcements, ribbon cuttings, stock photos of hard hats. That content serves the firm’s ego, not the viewer’s curiosity, and it converts nobody. The test for every post should be: would a stressed homeowner, a busy architect, or a skeptical contractor stop scrolling for this? A ribbon cutting fails that test. A forty-second video titled ‘should you worry about this crack’ passes it every time.

Remember you’re feeding two funnels. Homeowners and small developers find you through explainers and call you directly for inspections and residential work. Architects and contractors — your referral spine — follow quietly on LinkedIn and remember you when a project needs a stamp. The same site footage, cut two ways, serves both.

Lead with the field explainer. On your next site visit, film forty seconds: point at the condition, name it, explain what it tells you, say what you’d check next. Cracks are the evergreen subject — which ones are cosmetic, which deserve a phone call — but the format works for drainage, settlement, deflection, rot, and every retrofit you touch. Blur or avoid anything that identifies the property, and hedge appropriately: you’re explaining categories of problems, not issuing free diagnoses.

Second, how-it-works teaching. Why do buildings need expansion joints? What does a soils report actually say? What’s the difference between a bearing wall and a partition, and why does your contractor keep asking? Whiteboard sketches, napkin diagrams, and simple physical demonstrations — a foam beam, a stack of blocks — make abstract mechanics legible. This is the content that gets saved and shared, and saves are the metric that predicts inquiries.

Third, project narratives for the professional audience. On LinkedIn, write short case notes: the constraint, the options considered, the solution, the lesson. Architects share these with colleagues; contractors remember them at bid time. Round out the calendar with team content — a day in the life of a field engineer, the plotter jamming during a deadline — and recruiting posts, because every firm we talk to is also fighting for talent, and the same feed that wins clients wins hires.

An engineering practice should measure social media like a referral program, not a popularity contest. Three numbers matter: saves, profile visits, and inquiries. Saves tell you a viewer filed your explainer for future use — that’s a homeowner planning a call or an architect bookmarking a resource. Profile visits tell you a post made someone want to know who you are; make sure the profile answers it in one line, with your service area, your stamp, and a link to an inspection-request or contact page. Inquiries are the only number that bills hours.

Separate your funnels when you review. Instagram and TikTok metrics tell you about the direct-client funnel: inspection requests, residential retrofits, small developer work. LinkedIn metrics — which are quieter but heavier — tell you about the referral funnel; a single comment from an architect is worth more than a thousand anonymous views. Log every new project’s source religiously. When a builder says they saw your crack video, that’s the data point that justifies the whole program.

Review monthly in one sitting. Rank posts by saves and inquiries, kill the weakest format, and double the strongest. A unified dashboard across platforms — SocialBlaze’s analytics do this — turns the review into twenty minutes. And resist the vanity trap: a viral clip seen by students overseas is pleasant, but a quiet post that made one local architect call is the business.

This week assumes two site visits and about three hours of total effort. Nearly everything is captured in the field during work you already do; the Friday scheduling session is where the week actually gets assembled and queued.

Week 1: Foundation and first capture

Start with the profile, because every good post will send strangers there. Rewrite the bio to name your city, your services, and your audience in one line, and point the link at an inspection-request or contact page rather than a homepage. Decide your two platforms — we recommend Instagram plus LinkedIn, with TikTok receiving the same video files — and let the rest lie fallow. Then build the capture habit: put a recurring reminder on every site visit to film one forty-second condition explainer. This week, just capture; don’t publish yet. Collect four or five clips, note what felt natural, and draft plain-English scripts for two teaching topics you explain to clients constantly. Post once from existing material — a project photo with a substantive caption — to signal life.

Week 2: Publish the explainers

Ship your first three field explainers this week, one every other day, each covering a single condition in plain language. Expect them to feel rough; publish anyway, because the format improves only through repetition. Add one whiteboard teaching clip — load paths and bearing walls are reliable first subjects — and your first LinkedIn case note, structured as constraint, solution, lesson in under two hundred words. Reply to every comment within a day; early conversation teaches the algorithms who should see you, and homeowners’ follow-up questions are a free content backlog. End the week with a fifteen-minute review: which post earned saves, which earned profile visits, and which question in the comments deserves its own video next week.

Week 3: Distribution and referral seeding

Week three is about getting the content in front of the people who send work. Cross-post your best explainer to TikTok with an adjusted caption, and add location tags everywhere — your market is geographic and local discovery is the point. On LinkedIn, deliberately engage: comment substantively on posts from five architects and five contractors you’d like more work from, because your name in their notifications is marketing older than the internet. Tag collaborators on project posts where contracts allow. Try one opinion post — a detail you wish builders would stop doing, framed constructively — and watch it travel further than anything neutral. Keep the capture habit running on every site visit, and keep the posting rhythm at three to four per week without exception.

Week 4: Measure, systematize, schedule ahead

Close the month by converting the experiment into a system. Pull the month’s numbers and rank every post by saves and inquiries; kill the weakest format and double the strongest. Write the system on one page: three content pillars, the weekly slots, who films on site days, who schedules the Friday batch. Start the inquiry log if you haven’t — every new call gets asked how they found you, forever. Then schedule the entire next month in one sitting: four Mondays of explainers, four Wednesdays of LinkedIn notes, the teaching and culture slots filled from your capture backlog. A practice that schedules monthly survives proposal season; one that posts when inspired goes dark by the second deadline and starts over in a year.