Hamza JameelField sheet Nº 005

Free field sheet · Nº 005
Issued 26 Sep 2026

KeywordCRM

The Custom CRM Spec

What to decide before anyone quotes you a price

Checks
39
Do first
8
Parts
7
Cost
Free
Hamza Jameel
Prepared byHamza Jameel10+ yrs · $8M+ ad spend managed · 150+ page-one rankings
Checked 0/39Top

Off-the-shelf CRMs fail because they model somebody else's sales process. Custom ones fail because nobody wrote the process down first. This is the document that prevents both, fill it in before you talk to any developer.

Part 1 of 70/4

The decision itself

Build only if you can point at a specific thing your process does that the off-the-shelf options genuinely cannot.

  1. If you cannot, buy one. Custom is more expensive forever, not just to build.

  2. Under five, adoption is a conversation. Over twenty, it's a project with training.

  3. Custom software without an owner becomes legacy software in about six months.

  4. Rule of thumb: ongoing is 20-30% of build cost annually.

Part 2 of 70/6

Map the actual process

Write what happens today, not what should happen. The gap between those two is where every failed CRM project lives.

  1. This becomes validation. Vague stages produce a pipeline nobody trusts.

  2. Becomes your stalled-deal alerts later.

  3. Most specs ignore this and every real pipeline does it.

  4. Reason codes here are where your best marketing insight comes from.

Part 3 of 70/6

Data model

  1. Resist adding objects you cannot name a report for.

  2. Every required field is a small tax on every user, every time.

  3. Free text where a picklist belongs makes reporting impossible later.

  4. Decide now. Retrofitting deduplication onto dirty data is painful.

  5. Especially if you hold data on EU or UK individuals.

Part 4 of 70/7

Integrations

Each one is a commitment to maintain something you do not control.

  1. Two-way sync is significantly more work and the commonest scope surprise.

  2. Without this you are optimising ad spend against platform-reported conversions instead of revenue.

  3. In the GCC, ignoring WhatsApp makes the CRM incomplete in practice.

Part 5 of 70/5

Automation

  1. Ambiguity in automation produces silent wrong behaviour.

  2. Over-notifying trains people to ignore the system entirely.

Part 6 of 70/6

Reporting

Specify the reports first. They determine the data model, discovering a missing field after launch means backfilling history you no longer have.

  1. The report that decides where marketing budget goes.

Part 7 of 70/5

Launch

  1. Importing years of dirty data poisons a clean system on day one.

  2. Two live systems means neither is trusted.

  3. Book it now. Nobody books it afterwards.

Want me to look at yours?

If you have gone through this and want a second pair of eyes, book a free call. We open the account together and look at what is actually happening. No deck, no pitch.

More free sheets

Sources
  1. Built from CRM implementations at hamzajameel.com/crm-development/