TEKIN METHOD
02

Objects and links

Your org models the nouns. Your agents act through the verbs.

Account, Contact, Case.
Who may say
"refund"?

1

The object world

How CRM was built.

Account, Contact, Case, Order. Each object stands for a thing in the real world, with fields that describe it. The model answers one question very well: what exists.

2

The link world

How agents work.

Agents don't create accounts for fun. They refund, approve, discount, close. Every one of those is a verb that moves something along a link, from one person or record to another.

3

The missing model

Salesforce models the nouns well, and agents act through the verbs. Almost nobody models who may say the verb, up to which limit, and who answers when the limit is crossed.

4

Two ways to look at the same org

QuestionObject viewLink view
What you drawThings and their fieldsWho may change what
What failsBad dataAn action nobody owned
What you askIs the record right?Was it allowed, and by whom?
Where it livesSchemaLimits, approvals, decision records
5

One question for any problem

Which link has no owner, no limit, or no answer for silence? Ask it and you usually find the cause.

Usually faster than reading the code.
6

A small example

Case → refund → payment.

✓
CaseExists. Well modelled.
?
RefundThe link. Owner? Limit? Silence?
✓
PaymentExists. Well modelled.
7

What this is not

Not a graph database and not a new data model. The objects stay as they are. The links get an owner, a limit and a record.

Reading
a link

Fromwho or what starts it
Verbrefund, approve, close
Limitup to where
Ownerwho says yes above
Silencewhat happens if nobody answers