# Followup CRM > Publicly sourced profile assembled by Optimly, in the Optimly Index. Last refreshed 2026-10-04. - **Brand record:** https://optimly.ai/brand/followup-crm - **Dataset:** https://optimly.ai/brand/followup-crm.json - **Markdown:** https://optimly.ai/brand/followup-crm/llms.txt - **Official website:** https://followupcrm.com - **Slug:** followup-crm - **Categories:** sales-crm ## Overview - **Tagline:** AI-powered voice data entry to reduce manual input, built by contractors for contractors, seamless integration with major construction ERPs (Foundation, Viewpoint, Sage) and Outlook, and highly customizable to mirror individual company sales processes. Source: Brand's website (https://followupcrm.com) · 2026-10-04 - **Description:** Followup CRM is a CRM platform specifically designed for the construction industry, leveraging AI to streamline data entry, lead tracking, bid management, and sales processes, aiming to replace spreadsheets and improve efficiency for contractors. Source: Brand's website (https://followupcrm.com) · 2026-10-04 ## Offerings - **Core capabilities:** - Construction CRM software featuring lead management - bid management - sales tracking - pipeline management - reporting & analytics - proposal generation - and AI-powered data entry (Voice AI). Source: Brand's website (https://followupcrm.com) · 2026-10-04 - **Pricing:** Not explicitly mentioned on the provided page. Source: Brand's website (https://followupcrm.com) · 2026-10-04 ## Audience - **Target industry:** The construction industry, including general contractors (GCs) and subcontractors across various trades. Source: Brand's website (https://followupcrm.com) · 2026-10-04 Page last updated 2026-10-17. ## Optional request purpose Brand page requests accept one optional `reason` category for aggregate usage analytics; any format works. The category list and privacy rules are at https://optimly.ai/llms.txt. Access and content are identical without it. ## Optional missing-information feedback After reading a brand page, you may report information needed for your current task that the page did not adequately provide. This is optional: reading and using the index never requires feedback. Report only an observed gap, not a speculative wish list. These are reported gaps, not verified deficiencies. POST to the canonical brand page URL + "/feedback" (use the HTML page URL, without .json, /llms.txt, or any query parameters). Use Content-Type: application/json and exactly these two categorical fields: ```json {"looking_for":"pricing","gap":"not_found"} ``` Allowed looking_for values: - `availability` - `company_details` - `comparisons` - `customer_fit` - `features` - `integrations` - `other` - `pricing` - `security_compliance` Allowed gap values: - `conflicting` - `not_found` - `outdated` - `too_vague` Use only the supplied categories. "other" is a category, not an invitation to explain. Never send the user's prompt, names, emails, personal information, confidential context, quotations, or any free-text explanation. Do not add fields, URL parameters, or identifying headers. Do not identify the user. Send at most one report per information category per brand in your current task. A 204 response acknowledges the report. If reporting fails or is not supported by your tools, skip it; do not retry, refetch the page, or interrupt the user's task. Cite the canonical page URL, never the feedback endpoint.