We cloned a CRM for a new industry in a day. Here is how

The CRM we built for a custom home builder in Delray Beach now also runs a landscaping company and a retirement advisor. Each copy took about a day. Here is what that day looked like.

What a CRM is, in one paragraph

A CRM is the place where every lead lives: who they are, where they came from, what was said, what happens next. For a builder that means a homeowner with a lot and a budget. For a landscaper it means a property manager who needs a monthly contract. For an advisor it means a couple a few years from retirement. The shape of the work is nearly identical. The words and the rules are not.

What stayed exactly the same

When we cloned the builder's CRM for the landscaper, we copied the whole project into a new, private code repository (the folder where the code lives, with its full history) and started from there. These parts carried over untouched:

• The lead record, the activity log, notes and tasks.
• The pipeline board where a lead moves from new to won or lost.
• The email thread view, so anyone on the team can read the whole conversation with a lead inside the CRM instead of hunting through an inbox.
• User roles: an owner, a developer, and the rule that only an account can change its own powers.
• The phone layout. Below a certain screen width the CRM turns into a native style app with a bottom tab bar and one tap to call or text a lead, and it installs to the home screen.
• The website intake: the form on the company's site posts straight into the CRM with a secret key, and retries never create duplicates.

What changed

• Lead sources. The builder's CRM has partner sources (a painting company and a cabinet shop feed leads into it and see only their own). The landscaper has none of that, so those sources were removed and the lead sources became website, phone and referral.
• Stages. A builder sends a proposal. A landscaper sends an estimate. One stage was relabelled, and the rest of the pipeline stayed.
• Fields. Lot size and build budget mean nothing to a lawn crew. Property type, service frequency and gate access mean a lot.
• Scoring. The CRM gives each lead a score so the hottest ones rise to the top. The rules that make a lead hot for a builder (owns land, has plans, has financing) were rewritten for landscaping, where a commercial property with recurring service is the prize.
• Everything that identifies the client. Logo, colors, domain, the email address alerts come from, the Google accounts the marketing page reads.

The advisor's copy followed the same recipe with a different vocabulary: households instead of properties, a review meeting instead of a site visit.

The two bugs we inherited

A clean copy of a working app still carries whatever the original was quietly getting away with. We found two things on day one. One was a database setup step that had been reduced to a placeholder because the original production database already had the columns, so a fresh database built from the same steps was missing them and every new lead failed to save. The other was a scoring rule that gave a plain form fill the maximum score, so every lead showed up as hot. Both were fixed in the copy, and both earned a permanent check in our process. We wrote the whole story of those two bugs up separately because it changed how we clone.

Why a proven core beats a blank page

Starting from a blank page means rediscovering every problem the first client already paid to solve: the notes box that lost focus while typing, the alert email that never sent because the server went to sleep before it finished, the slow page loads from three login checks per click. All of those were found and fixed on the builder's CRM over months of real use. The landscaper and the advisor got those fixes on the first day, for free, without ever hitting the bugs.

Each client still gets a fully separate system: their own code, their own database in their own account, their own hosting. Nothing is shared except the lessons. That is the part people miss about cloning. It is not one product sold three times. It is one set of hard won answers applied three times, with the industry specific parts rebuilt properly each time.

This is how we build most client software now: start from the system that already runs a business like yours, keep what is proven, and change only what your trade needs.

Questions people ask