PromptBase
Upgrade
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
(claude-4-6-sonnet)
Token size
469
Example input
[BUSINESS AND PRODUCT OVERVIEW]: B2B SaaS project management software for architecture and engineering firms at 299 per month per team, built specifically for AEC workflows like RFIs submittals and punch lists unlike generic tools like Asana or Monday [TARGET AUDIENCE AND THEIR CORE PROBLEMS]: Lead generation — get AEC project managers to book demos [PRIMARY CONTENT GOAL]: Project managers and principals at architecture and engineering firms who struggle with email thread chaos, missed deadlines, and document version control across complex multi-stakeholder projects [CURRENT CONTENT SITUATION]: Company blog with 12 posts getting almost no traffic, irregular LinkedIn posting with minimal engagement, generic project management tips content that performed poorly [AVAILABLE RESOURCES]: 1 part-time content person at 10 hours per week, 500 per month for tools and promotion, founder available 2 hours per week for thought leadership content
Example output
AUDIENCE INTELLIGENCE Segment 1: Overloaded Project Manager at a 75-person Architecture Firm Pain point 1: They spend 3-4 hours per week hunting down the latest version of RFI logs and submittal trackers across email threads, Dropbox folders, and WhatsApp groups. Pain point 2: When something goes wrong on a project, they cannot reconstruct the communication chain quickly — which creates liability exposure. Where they spend time online: LinkedIn (passive scroll, not active), AIA forums, trade publications like Architectural Record. Not on Twitter or TikTok. What triggers them to seek solutions: A project blowup, a client complaint about communication, or a new PM who joins and asks "why don't you have a system for this?" Objections before buying: "We've tried project management software before and the team won't use it." "Our projects are too complex for generic tools." "I don't have time to migrate everything." Segment 2: Principal or Partner Who Has Outgrown Email Pain point 1: They are cc'd on every email thread "just in case" and spend 90 minutes a day reading emails that do not require their attention. Pain point 2: They cannot see at a glance which projects are on track and which are at risk without asking their PMs. Where they spend time online: Industry associations, peer networks, golf courses. Occasional LinkedIn. More likely to read something a trusted peer sends them than to discover content themselves. What triggers them to seek solutions: A near-miss on a major project, a billing dispute they could not resolve because the communication record was incomplete, or hitting a growth ceiling where they cannot take on more projects without more chaos. Objections before buying: "I'm not the one who would use this — my PMs would." "Software never sticks at our firm." "We don't want to change how we work." Segment 3: IT Manager or Office Administrator Tasked With "Fixing the Process" Pain point 1: They have been told to evaluate software options but have no formal process for doing so and no clear criteria for what "good" looks like. Pain point 2: Every PM has a different system they're attached to and getting alignment feels impossible. Where they spend time online: Google searches, software review sites like G2 and Capterra, YouTube tutorials. What triggers them to seek solutions: Being assigned the task by a principal. A new project type (e.g., first federal contract) that requires tighter documentation. Objections before buying: "I'm not sure this is the right tool vs. something we already have." "Training rollout will take months." "I need to get buy-in from 12 people before I can decide." --- CONTENT PILLARS Pillar 1: The AEC Project Communication Problem Core tension: Architects and engineers are highly skilled professionals who are often running million-dollar projects with the communication infrastructure of a 2003 small business. Angle 1: Why email is the most expensive tool in your project stack (and what to track instead) Angle 2: The RFI response time problem: how slow turnaround quietly kills project profitability Angle 3: What general contractors actually want from the architect's communication process (and whether you're delivering it) Pillar 2: Practical Systems for AEC Project Managers Core tension: PMs want processes that work, but most "project management" content is written for tech companies and doesn't translate to construction documents, submittals, or field conditions. Angle 1: How to build a project communication log that actually gets used Angle 2: The 30-minute weekly project review that surfaces problems before they become crises Angle 3: Submittal tracking in 2025: what's changed and what still doesn't work Pillar 3: Growing an Architecture Firm Without Growing the Chaos Core tension: Firm growth is desirable, but every new PM and new project type brings new coordination failures that principals didn't anticipate. Angle 1: The hidden cost of onboarding a new PM at a firm with no documented process Angle 2: How to add a project type (healthcare, federal, multifamily) without rebuilding your entire workflow Angle 3: What separates firms that scale past 50 people from those that plateau Pillar 4: Client Communication and Relationship Management Core tension: Clients are paying premium fees and expect premium communication — but most architecture firms treat client updates as an afterthought. Angle 1: How to run a client update meeting that makes clients feel informed without taking 2 hours Angle 2: The three client questions every PM should be able to answer immediately and most can't Angle 3: Why project documentation is also a client relationship tool (and how to use it that way) --- CHANNEL STRATEGY Primary channel: LinkedIn Why it fits: Project managers and principals at architecture and engineering firms are on LinkedIn, even if they are not heavy users. The audience skews 40+ and professional. Long-form articles and educational posts perform well. A founder with genuine AEC industry experience can build credibility here faster than anywhere else. Best format: Short-form posts with a specific insight or story (150-300 words). Long-form articles that answer a specific question in depth. Occasional document carousels showing frameworks or process breakdowns. Publishing frequency: 3 posts per week minimum. One long-form article per month. Secondary channel 1: Email newsletter Why it fits: This audience does not scroll social feeds for education. But they will read a well-curated weekly email if it consistently delivers practical value. Email also builds the list you own. Best format: One practical tip or insight per issue. Under 400 words. One link to a longer piece or resource. Publishing frequency: Weekly. Secondary channel 2: SEO-optimized blog Why it fits: When this audience has a specific problem, they search for it. Posts targeting specific AEC pain points (RFI management, submittal tracking, project communication templates) can rank and drive demo requests from buyers who are actively looking. Best format: 1,500-2,500 word practical guides targeting specific keywords. Publishing frequency: 1 post per week, repurposed from LinkedIn content. --- CONTENT BY FUNNEL STAGE Awareness content (they have the problem but don't know you): 1. "Why AEC project communication keeps failing — and it's not the people" — LinkedIn post or blog 2. "The real cost of a single missed RFI response" — calculator or data post showing dollar impact 3. "What 50-person architecture firms get wrong about project management" — listicle with specific, non-obvious observations Consideration content (they're evaluating solutions): 1. Side-by-side comparison: "Using our platform vs. managing projects in email" — honest, specific, shows concrete workflow difference 2. Case study: "How [Firm Name] cut project communication time by 40% in 60 days" — real numbers, real workflow change 3. Demo walkthrough video: "What submittals look like in our platform vs. what they look like in your inbox right now" Decision content (they're ready to buy or nearly there): 1. ROI calculator: "How much is project communication chaos actually costing your firm?" 2. Onboarding guide: "How long does it actually take to get your team set up?" — addresses the "it will take months" objection directly 3. Testimonial post: "We almost didn't buy it because we'd tried software before" — voice-of-customer content that names the objection directly Retention content (they're already customers): 1. Monthly "power user tip" email: one non-obvious feature that saves time, with a specific workflow example 2. Client success story featuring a current customer — reinforces their decision and gives them content to share internally --- 30-DAY EDITORIAL CALENDAR Week 1: Post 1 (Monday): "The RFI time bomb: why slow responses are costing your firm more than you think" — LinkedIn post, 250 words — Awareness stage — CTA: "What's your average RFI turnaround? Drop it in the comments." Post 2 (Wednesday): "How to build a weekly project review that actually works" — LinkedIn long-form article, 800 words — Consideration stage — CTA: Download the review template (lead magnet) Post 3 (Friday): Email newsletter — "One thing we've learned from talking to 100 AEC project managers" — Awareness — CTA: Reply with your biggest project communication headache Week 2: Post 1 (Monday): "What general contractors actually want from architects — and whether you're delivering it" — LinkedIn post, 200 words — Awareness — CTA: Share this with a GC and see if they agree Post 2 (Wednesday): Case study post — "How [Firm] handled 3 simultaneous project crises with one system" — Consideration — CTA: Book a 20-minute walkthrough Post 3 (Friday): Blog post published — "AEC Submittal Tracking in 2025: What Changed and What Still Doesn't Work" — Awareness/SEO — CTA: Subscribe to weekly newsletter Week 3: Post 1 (Monday): Founder insight — "The conversation that made me realize email was killing architecture firms" — Awareness — CTA: What's the most chaotic project communication moment you've experienced? Post 2 (Wednesday): "Why software never sticks at architecture firms (and the one thing that changes that)" — Consideration — CTA: Read the full guide (link to blog) Post 3 (Friday): Email newsletter — "The 3-question client check-in that takes 10 minutes and prevents 80% of escalations" — Retention/Awareness — CTA: Forward this to a PM on your team Week 4: Post 1 (Monday): "The hidden cost of onboarding a new PM at a firm with no documented process" — Awareness — CTA: Calculate your cost with our tool Post 2 (Wednesday): ROI post — "If your firm handles 12 projects at once and each has 4 hours of communication chaos per week, here's what that costs annually" — Decision — CTA: Book a demo to see if we can fix it Post 3 (Friday): Email newsletter — "Month in review: what worked, what didn't, what we're publishing next month" — Retention/Community — CTA: Reply with what you want us to cover next --- REPURPOSING SYSTEM Core principle: Every piece of long-form content should generate at least 3-5 shorter assets before it is retired. Example using Week 2's blog post "AEC Submittal Tracking in 2025: What Changed and What Still Doesn't Work": Asset 1 (LinkedIn post): Pull the single most counterintuitive finding from the article and write a 200-word post around just that insight. Link to the full article at the end. Asset 2 (Email newsletter): Write a 300-word version of the article's core argument — the problem, the nuance, and one practical takeaway. Link to the full article. Asset 3 (LinkedIn carousel): Turn the article's 5 key points into a 6-slide carousel. Slide 1 is the hook, slides 2-6 are each key point with one sentence of context, last slide has the CTA. Asset 4 (FAQ blog post): Use the article as source material to write a shorter "People always ask us..." post that addresses the 3 most common questions about submittal tracking. Asset 5 (Sales team enablement): Send the article to the sales team with a note explaining which customer objection it addresses and how to reference it in demos. --- MEASUREMENT FRAMEWORK Leading indicators (early signals that content is working): 1. LinkedIn post engagement rate — Target: 3-5% engagement rate (likes, comments, shares divided by impressions). If below 2%, adjust topics or format. 2. Email open rate — Target: 35-45% for this audience. If below 30%, test different subject lines and sending times. 3. Demo requests attributed to content — Target: 2-4 demo bookings per month that mention a specific piece of content in the intake form. Track via intake form question: "How did you hear about us?" Lagging indicators (business outcomes): 1. Monthly qualified leads from content — Target: 15-25 MQLs per month from content channels within 6 months of starting. Measure via UTM parameters on all content CTAs. 2. New customer attribution to content — Target: 20-30% of new customers in month 6+ should be able to attribute their awareness to a specific piece of content. Measure via first-touch attribution in CRM.
🌀 Claude

Content Strategy Architect

Add to Cart
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
CLAUDE-4-6-SONNET
Tested icon
Guide icon
4 examples icon
Free credits icon
Most content strategies are just posting schedules dressed up in a slide deck. This Claude prompt builds a complete, research-backed content strategy — content pillars, audience pain point mapping, channel recommendations, content formats by funnel stage, 30-day editorial calendar, repurposing system, and success metrics. Works for B2B companies, SaaS products, agencies, consultants, and personal brands. Stop guessing what to post. Start publishing with a system.
...more
Added 4 days ago
Report
Browse Marketplace