--- name: "weekly-new-construction-incentive-blog" description: "Create and maintain source-backed weekly builder incentive blogs across any website builder and CRM." status: proposal version: "v1" date: "2026-08-10T21:04:06.088Z" --- # Weekly New Construction Incentive Blog Create and maintain a current, source-backed weekly blog covering builder incentives and new-construction opportunities in the user's service area. Adapt to the user's actual website builder, CRM, form tools, brand, and publishing permissions. Never assume Sierra Interactive. ## Start with onboarding Before the first run, ask only for information that cannot be discovered safely: 1. Service area and geographic scope. 2. Website URL and website/CMS builder. 3. CRM name. 4. Lead form, IDX, or landing-page tool, if separate. 5. Whether the user wants a draft, a staged preview, or live publishing. 6. Brand name, logo, colors, voice, author/byline, and required disclosures. 7. Desired publishing day, update frequency, and notification destination. 8. Whether the user represents buyers, builders, or both, and whether any builder relationships require disclosure. Inspect available integrations and existing site patterns before asking for details already visible. Never request passwords in chat. Prefer OAuth, official connectors, scoped API keys, or user-supervised browser login. If the website builder or CRM is unfamiliar, research its current official documentation before proposing a connection. ## Establish the connection plan Create a short integration map: - Content destination: website builder/CMS and target blog or resource collection. - Lead capture: existing CRM-native or website-native form. - Routing: destination pipeline, stage, tag, source, campaign, assignee, and notification behavior. - Tracking: UTM convention and conversion event. - Publishing: API, native connector, approved automation, or manual handoff. - Verification: test-submission method and proof required. Use the user's existing native form and CRM integration when practical. Do not build a duplicate lead database or collect sensitive information unnecessarily. Present the connection plan before any external write when configuration changes, live publishing, or test leads would alter production state. Obtain explicit approval before publishing, changing CRM automation, or submitting a test lead. If no direct integration exists, recommend options in this order: 1. Native website-builder to CRM connector. 2. Official CRM form embedded on the website. 3. Official automation connector supported by both systems. 4. Webhook or API integration with scoped credentials. 5. Clearly documented manual import workflow as a last resort. Do not claim an integration works until a test lead is verified end to end in the correct CRM record, source, campaign, stage, and assignee. ## Research the weekly incentives Build a source log before drafting. Search the current official builder or community pages first, then official press releases, rate sheets, inventory pages, and reputable local reporting. For every incentive record, capture: - Builder and community. - City, county, and state. - Home type or eligible inventory. - Exact incentive. - Eligibility restrictions. - Financing or preferred-lender conditions. - Expiration date or “as of” date. - Official source URL. - Date and time verified. - Contact or confirmation note when public terms are incomplete. Treat incentives as volatile. Verify every material incentive during the current weekly run. Do not copy last week's terms without rechecking them. Do not publish an incentive that lacks a source or clear attribution. If terms are incomplete, state that clearly and tell readers to confirm availability and eligibility directly with the builder and their licensed advisers. Never present an advertised rate, payment, credit, or savings as universally available. Avoid financial, tax, or legal advice. Include a concise disclaimer that prices, incentives, rates, inventory, and eligibility can change without notice. Do not reproduce copyrighted descriptions at length. Summarize facts in original language and link to primary sources. ## Select stories and organize the article Prioritize incentives that are: - Current and source-verifiable. - Material to a buyer's decision. - Locally relevant. - Distinct from routine sales language. - Clear enough to explain without speculation. Group offers by geography or buyer decision, not by protected class. Describe homes, locations, prices, amenities, transportation, and program terms. Never describe who should live there. Comply with the Fair Housing Act and applicable state or local protections. Avoid language that targets or excludes people based on race, color, religion, national origin, sex, familial status, disability, age, sexual orientation, gender identity, veteran status, source of funds, or other protected characteristics. ## Draft the weekly blog Use this structure unless the user's established site template calls for a better equivalent: 1. SEO title with location and current week or month. 2. Meta title and unique meta description. 3. Direct opening summary explaining what changed this week. 4. “Last verified” date near the top. 5. Quick Summary with the strongest verified offers. 6. One section per builder, community, or geography. 7. For each offer: terms, restrictions, expiration, why it matters, and source. 8. A practical section explaining how to compare incentives, base price, upgrades, closing costs, and financing terms. 9. Lead-capture CTA connected to the user's CRM. 10. FAQ based on verified facts. 11. Sources and incentive disclaimer. 12. Updated/published date. Keep the article useful when no strong incentive exists. Say that the week was quiet and explain any meaningful inventory, deadline, or program changes. Never fabricate urgency. Use internal links to relevant community, new-construction, buyer, financing-disclaimer, contact, and search pages after verifying each destination works. Do not force irrelevant links. For recurring posts, prefer updating a stable evergreen URL when that supports the user's SEO strategy. If the user wants weekly archives, create a dated post and maintain a hub page linking the series. ## Images and accessibility Follow the user's brand and website image requirements. Use authorized builder media, user-provided assets, properly licensed images, or original graphics. Do not imply builder endorsement. Provide meaningful alt text based on the visible image. Avoid text-heavy graphics when the same information can be accessible HTML. Verify responsive sizing and mobile readability. ## Publish or hand off Match the user's approved mode: - Draft: provide complete copy, metadata, source log, image plan, CTA, and platform-specific placement instructions. - Staged preview: create a non-public preview and provide its URL. - Live publish: publish only after explicit authorization or a previously approved standing workflow. Preserve the site's existing design system. Do not replace global templates, tracking, forms, or navigation for a single article. When the platform strips scripts or embeds, use its native form, block, shortcode, or supported embed method. Do not bypass platform security controls. ## CRM setup Configure or document these fields using the user's native terminology: - Lead source: Weekly New Construction Blog. - Campaign: year plus market or article series. - Interest tag: New Construction. - Community or builder interest when known. - Consent fields required by applicable law and the user's policies. - Assigned user, team, or routing rule. - Follow-up automation, only if explicitly approved. Use minimal form fields. Name, email or phone, preferred contact method, area/community interest, timeframe, and consent are usually enough. Do not precheck marketing consent. Never send outreach, activate automations, or contact leads without explicit authorization. Never impersonate the agent. ## Required QA Perform one bounded verification pass and one targeted fix pass: - Every incentive matches a current source. - Expiration dates, eligibility, prices, rates, and credits are attributed. - No stale offer remains from the prior week. - Fair Housing language passes. - Title, metadata, headings, canonical behavior, and internal links are valid. - Desktop and mobile layouts have no overflow. - Images load and have alt text. - CTA form loads. - Approved test lead reaches the correct CRM destination with correct routing and attribution. - Analytics event or UTM values persist when configured. - No console or embed errors block the form. - Draft or public URL resolves as intended. Stop and report the exact blocker if a critical fact, platform login, integration permission, or lead-routing test cannot be verified. ## Weekly deliverables Return: - Draft, preview, or live article URL. - Publication/update date. - Count of verified incentive offers. - Source log. - Website builder and CRM used. - CRM connection status. - Lead-routing test result, if authorized. - QA result and any blocker. - Short change summary versus the prior week. - Recommended next verification date. Do not describe the work as complete when the incentives, live page, CTA, or approved CRM routing test remain unverified.