761 Ventures Start a project
Cabinetry and millwork

Cabinet House: A cabinetry site with a redesigned contact flow, wired into the builder’s CRM under its own source

Site and contact page, forms that post through a server side proxy into the builder’s CRM tagged as Cabinet House, and a deploy pipeline repaired so the code on GitHub matches what is live.

WhereSouth FloridaSitecabinethousefl.comUpdatedSeptember 7, 2026
WebsiteContact flowLead routingDeploy pipeline
cabinethousefl.com
Open live site

The situation

  • A cabinetry company working with the same builder, with a site but no connection between its contact form and anyone’s follow up.
  • The code repository was behind the live site: a contact page redesign existed only on the server. Connecting automatic deploys would have silently rolled the live site back.

What changed

  1. Every inquiry now lands on a timeline with follow up rules instead of in an inbox.
  2. The live site and its source code agree, so changes ship with a merge instead of a manual upload.

What we built

A redesigned contact flow

The contact page was rebuilt so a visitor can reach out in under a minute from any device.

Leads into the builder’s CRM, tagged Cabinet House

Both contact forms post to a server side proxy that forwards to the CRM with a secret unique to Cabinet House, so the CRM forces the source and partner users see only their own leads.

A deploy pipeline you can trust

The repository was synced to production and every file verified byte for byte identical before Git was connected. Now a merge deploys, and what is on GitHub is what is live.

Local listing and search cleanup

Listings tidied so the company name, address and phone match the website.

How it fits together, in plain EnglishA static site on Vercel with a small server side function for the contact form. Leads go to the shared CRM with a dedicated secret per company.

Questions people ask

Why does the form go through a proxy instead of straight to the CRM?

The secret that authorizes a lead never reaches the browser, and the CRM can trust the source label. It also means retries are safe and spam is filtered before it reaches the pipeline.

What does a deploy pipeline have to do with marketing?

If the code and the live site disagree, every future fix is a risk. Fixing that first is what makes weekly audits and automatic fixes possible.

Want this for your business?

Two minute intake. A real person reads every one and replies within a business day with what we would change and what it would cost.

Start a project

More case studies

SouthShore Builders

A builder site that feeds its own CRM, with partners seeing only their own leads

Website, local search cleanup, a weekly blog from the builder’s own photos, a CRM with Gmail threads and scoring, an AI assistant named Drew, and a marketing page that pulls Analytics, Search Console and Clarity nightly.

Read the case study
Key Financial Group of Florida

A compliance aware advisor site with a qualifying intake and a 53 post library, built in days

Built pixel for pixel to the approved navy and gold mockup, with a retirement calculator, a three step qualifying consultation form, 53 educational posts with generated covers, its own CRM and an AI assistant named Blair.

Read the case study
Oceans Edge Landscaping

A landscaper locked out of its own domain, relaunched with a new domain, CRM and assistant in a week

New domain and Google Workspace, full site rebuild with schema and a 31 post blog, site search, a CRM that installs on the owner’s phone, an AI assistant named Kai, and nightly marketing reporting.

Read the case study