Skip to content
Architecture 2026-07-01 10 min

CRM Architecture

Data model, pipelines, automation and integration boundaries for custom CRMs.

By Mohammad Zayed

Overview

A custom CRM should mirror how the team actually sells: leads become opportunities that move through a pipeline of stages.

Data model

schema
leads(id, email, source, status)
opportunities(id, lead_id, stage, amount, owner_id)
activities(id, opportunity_id, type, occurred_at)
stages(key, name, probability)

Diagram

CRM flow
Lead ──▶ Qualify ──▶ Opportunity │ ▼ Stage 1 → Stage 2 → … → Won │ ▼ Activities log

A lead progresses to a won opportunity via activities.

Automation

Trigger follow-ups and assignments from state changes; keep rules in one place so non-engineers can adjust them.

Frequently asked questions

Is this the only way to build it?
No. These are reference patterns we reuse. Adapt the boundaries to your constraints, team and compliance needs.
Should I copy this exactly?
Use it as a starting point. Validate each decision against your traffic, data sensitivity and team size.
Can NorthFlow implement this?
Yes. Book a strategy call and we'll tailor the architecture to your product.

Continue reading

Want this architecture for your product?

Book a free strategy call. We'll map your bottlenecks to the right systems and send a clear roadmap — even if we don't work together.

Chat on Telegram

Usually replies within minutes. Chat on Telegram: @northflowstudio

No obligation consultationFounder-led projectsInternational clientsFast responseSecure communication