Intern
What you actually do
Day one: referrals are a compliment, not a journey — add who-referred-whom as a field. Write when the ask fires. Write double-pay and silence rules. Do not print business cards first.
You say 'we grow by referral.' There is no field for who sent whom, no ask after completed work, and the referred person arrives as 'organic.' You cannot buy more of what you claim is the engine.
Read it once, then stop negotiating with it. Referral system for academies is a wiring job: fields → ask → stamp → rule. Objects, then edges, then one test conversion. You do not need a new tool to start. You need the first writer to land on one contact this week.
Academies do not have a Referral system problem because they lack CRM + referrals. They have it because referrals are a compliment. They are not a journey.
Wire these objects first: Referrer field, referred source tag, ask trigger after completed work, double-pay rule, silence rule, reward state, GHL contacts linked.
Then these edges, in order: Completed work / delivered / loved → ask workflow to the referrer contact · Referred person writes in → source:referral + referred_by contact/id field · Reward → state on referrer (pending, paid, ineligible) with the rule applied · Silence after ask → stop; no endless 'know anyone?'
Done looks like a test you can repeat: Complete a test delivery. Confirm the ask fires. Submit a referred lead with the referrer named. Confirm both contacts show the link. Apply the double-pay rule on a duplicate referral. If referrals are 'people say nice things', fail.
Start here: Who referred whom is a field
Academies already have CRM + referrals. The leak is not a missing feature. Referrals are a compliment. They are not a journey. Software did not cause it. A missing write-in did: the person exists in one tool and not in the pipeline.
Here is how you actually wire it. Name the objects: Referrer field, referred source tag, ask trigger after completed work, double-pay rule, silence rule, reward state, GHL contacts linked. Then connect these edges, in order: Completed work / delivered / loved → ask workflow to the referrer contact · Referred person writes in → source:referral + referred_by contact/id field · Reward → state on referrer (pending, paid, ineligible) with the rule applied · Silence after ask → stop; no endless 'know anyone?'. If you skip an edge, the next one is decoration. If you add a CRM + referrals feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Complete a test delivery. Confirm the ask fires. Submit a referred lead with the referrer named. Confirm both contacts show the link. Apply the double-pay rule on a duplicate referral. If referrals are 'people say nice things', fail. How you know it worked on the board: Referrer field is used (not 'organic' by default). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Who referred whom is a field An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: referrals are a compliment, not a journey — add who-referred-whom as a field. Write when the ask fires. Write double-pay and silence rules. Do not print business cards first.
Operator
You already feel referrals are a compliment. they are not a journey. Referrals are a compliment. They are not a journey. Protect one sequence for 90 days. The four moves are fields → ask → stamp → rule. The edges are Completed work / delivered / loved → ask workflow to the referrer contact then Referred person writes in → source:referral + referred_by contact/id field. Who referred whom is a field. The ask fires after a completed job, not at checkout panic. The new person is tagged with the referrer. Rewards and silence both have rules so it does not become a coupon farm.
CEO
This is a money leak, not a preference about tools. ' You cannot buy more of what you claim is the engine. Until referrer field is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Completed work / delivered / loved → ask workflow to the referrer contact.
Before
Tuesday. Someone among academies. Referrals are a compliment. They are not a journey. CRM + referrals is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases.
After
Same Tuesday, after write-in exists. Who referred whom is a field. The ask fires after a completed job, not at checkout panic. The new person is tagged with the referrer. Rewards and silence both have rules so it does not become a coupon farm. Completed work / delivered / loved → ask workflow to the referrer contact The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in academies already paid for CRM + referrals. Referrals are a compliment. They are not a journey. They add a page, a form, a calendar. None of it writes into a spec. By Friday the calendar has ghosts and the pipeline still looks like the snapshot.
The fix is not a better template. Who referred whom is a field. Prove write-in: Complete a test delivery. Confirm the ask fires. Submit a referred lead with the referrer named. Confirm both contacts show the link. Apply the double-pay rule on a duplicate referral. If referrals are 'people say nice things', fail. This week is one move: Who referred whom is a field If that feels too small, that is the point. Operators fail by starting at move four.
The leak
You say 'we grow by referral.' There is no field for who sent whom, no ask after completed work, and the referred person arrives as 'organic.' You cannot buy more of what you claim is the engine.
The system
Who referred whom is a field. The ask fires after a completed job, not at checkout panic. The new person is tagged with the referrer. Rewards and silence both have rules so it does not become a coupon farm.
Add two fields: referred_by (contact) and referral_status. When work is complete and the customer is not unhappy, a short ask goes out — SMS or email — with a link that already stamps the referrer.
When the referred person books or buys, the original contact gets a thank-you that is not a public blast. If you pay, write the rule. If you do not pay, write that too. Ambiguous rewards are how this dies in legal or in awkwardness.
Who referred whom is a field. The ask fires after a completed job, not at checkout panic. The new person is tagged with the referrer. Rewards and silence both have rules so it does not become a coupon farm.
Referrals are a compliment. They are not a journey until who referred whom is a field, the ask fires after completed work, the referred person has a source tag, and double-pay and silence both have rules. An ask at checkout panic is like review panic — sometimes it works, usually it is random. After completed work, when they have felt the result, is the trigger.
Wire two contacts: referrer and referred, linked. Attribution conflicts (two referrers, already in pipeline) need a written rule — first touch, last touch, or ineligible. Rewards that live only in a founder's memory will double-pay or never-pay. Put pending/paid on the referrer. DTC might use a Klaviyo flow plus a coupon; still store referred_by. Service businesses might use GHL only. Same objects.
Two databases: a 'referrals' tab in a sheet and GHL sources that all say Instagram. The intern tests the ask and the inbound referred form. They do not design a reward tier tree. One reward, one rule, one field. Silence has a stop so you do not become the friend who always asks. Compliment can remain; the journey is the field.
Referrer field, referred source tag, ask trigger after completed work, double-pay rule, silence rule, reward state, GHL contacts linked.
Completed work / delivered / loved → ask workflow to the referrer contact
Referred person writes in → source:referral + referred_by contact/id field
Reward → state on referrer (pending, paid, ineligible) with the rule applied
Silence after ask → stop; no endless 'know anyone?'
Complete a test delivery. Confirm the ask fires. Submit a referred lead with the referrer named. Confirm both contacts show the link. Apply the double-pay rule on a duplicate referral. If referrals are 'people say nice things', fail.
Day one: referrals are a compliment, not a journey — add who-referred-whom as a field. Write when the ask fires. Write double-pay and silence rules. Do not print business cards first.
referred_by and referral_status on the contact.
After completed work. Never at the register panic.
The new person carries the referrer as source.
Reward or no reward, written. Silence is also a rule.
On one line, for academies: Referrals are a compliment. They are not a journey. Add who gets hurt (calendar, cash, inbox, or reputation). If two people write different sentences, you do not agree yet — stop and agree.
Why: Teams skip this and jump into settings. Then every person is fixing a different problem with the same login.
Done when: One sentence. Shared. No adjectives required.
Referrer field, referred source tag, ask trigger after completed work, double-pay rule, silence rule, reward state, GHL contacts linked.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
referred_by and referral_status on the contact. Then wire: Completed work / delivered / loved → ask workflow to the referrer contact
Why: Academies cannot skip this edge. Referrals are a compliment. If it is not true, CRM + referrals is already a second database.
Done when: Completed work / delivered / loved → ask workflow to the referrer contact is true on a test.
After completed work. Never at the register panic. Then wire: Referred person writes in → source:referral + referred_by contact/id field
Why: Academies skip this and the leak returns as a private language. Wire two contacts: referrer and referred, linked. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Referred person writes in → source:referral + referred_by contact/id field is true on a test.
The new person carries the referrer as source. Then wire: Reward → state on referrer (pending, paid, ineligible) with the rule applied
Why: Academies feel this as Referrals are a compliment. They are not a journey. Two databases: a 'referrals' tab in a sheet and GHL sources that all say Instagram.
Done when: Reward → state on referrer (pending, paid, ineligible) with the rule applied is true on a test.
Complete a test delivery. Confirm the ask fires. Submit a referred lead with the referrer named. Confirm both contacts show the link. Apply the double-pay rule on a duplicate referral. If referrals are 'people say nice things', fail.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Referrer field (Not 'organic' by default), then ask timing (Not at invoice). Write one action or write “hold.” A dashboard with no action is theatre.
Why: What gets reviewed gets run. What only lives in a tool gets ignored the week someone is busy.
Done when: Three numbers. One owner. Fifteen minutes. Actions attach.
Who referred whom is a field
Why: Operators fail by starting at move four. Interns fail by making a 40-item checklist. CEOs fail by adding a second priority. One proven write-in beats an elegant plan.
Done when: The move is true, or you can name the blocker in one sentence.
Referrer field, referred source tag, ask trigger after completed work, double-pay rule, silence rule, reward state, GHL contacts linked.
If objects aren't named, software invents a second database.
Referrals are a compliment. They are not a journey.
referred_by and referral_status on the contact. Then wire: Completed work / delivered / loved → ask workflow to the referrer contact
Academies cannot skip this edge. Referrals are a compliment. If it is not true, CRM + referrals is already a second database.
On CRM + referrals, this means the data model matches how academies actually work — not the snapshot demo. Edge: Referred person writes in → source:referral + referred_by contact/id field
After completed work. Never at the register panic. Then wire: Referred person writes in → source:referral + referred_by contact/id field
Academies skip this and the leak returns as a private language. Wire two contacts: referrer and referred, linked. Spec tags, fields, and states have to be the same objects the next workflow will read.
Who referred whom is a field. The ask fires after a completed job, not at checkout panic. The new person is tagged with the referrer. Rewards and silence both have rules so it does not become a coupon farm.
The new person carries the referrer as source. Then wire: Reward → state on referrer (pending, paid, ineligible) with the rule applied
Academies feel this as Referrals are a compliment. They are not a journey. Two databases: a 'referrals' tab in a sheet and GHL sources that all say Instagram.
Who referred whom is a field
Because the login already exists. ' You cannot buy more of what you claim is the engine. A new feature on a missing spec is a second database. Finish this edge first: Completed work / delivered / loved → ask workflow to the referrer contact.
Day one: referrals are a compliment, not a journey — add who-referred-whom as a field. Write when the ask fires. Write double-pay and silence rules. Do not print business cards first. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Complete a test delivery. Confirm the ask fires. Submit a referred lead with the referrer named. Confirm both contacts show the link. Apply the double-pay rule on a duplicate referral. If referrals are 'people say nice things', fail. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
If it is only in someone's head, a new hire needs a story, reporting cannot be defended, and automations fire on folklore. Writing is how two people mean the same object on Monday.
Because setup was a project, not a review. Attributed (Or you cannot name the engine) is how you stop the leak returning dressed as a new feature. Write the sequence as if you will still be proud of it in six months. Each email does one job. If you need a discount to make it work, the offer is unclear. If you cannot sunset, you do not respect the inbox — including your own domain.
More leads into a leak is a more expensive leak. Who referred whom is a field. The ask fires after a completed job, not at checkout panic. The new person is tagged with the referrer. Rewards and silence both have rules so it does not become a coupon farm. Watch referrer field before you buy traffic. If that number is folklore, acquisition is a vanity spend.
Then you only have time for the objects page and one test conversion. Who referred whom is a field That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because CRM + referrals is “set up”.
Do this
Referrer field, referred source tag, ask trigger after completed work, double-pay rule, silence rule, reward state, GHL contacts linked.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Completed work / delivered / loved → ask workflow to the referrer contact
Skip this
Calling it done because a screenshot looks busy.
Do this
Complete a test delivery. Confirm the ask fires. Submit a referred lead with the referrer named. Confirm both contacts show the link. Apply the double-pay rule on a duplicate referral. If referrals are 'people say nice things', fail.
Skip this
Leaving “Rule” to chance.
Do this
Reward or no reward, written. Silence is also a rule.
The usual miss
Calling CRM + referrals “set up” because someone logged in and imported a snapshot.
Do this instead
referred_by and referral_status on the contact. Then prove write-in: Complete a test delivery.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Completed work / delivered / loved → ask workflow to the referrer contact first. Automations on a missing writer invent a second database.
The usual miss
Adding a page, form, flow, or campaign every time last week hurt.
Do this instead
Name which edge is missing. Fix that edge. Hurt is usually a skipped write-in, not a missing asset.
The usual miss
Reporting that nobody will defend in a meeting — screenshots, vanity opens, 'interested' counts.
Do this instead
Referrer field: Used. Not 'organic' by default. If you cannot say it out loud, it is not a scoreboard.
The usual miss
Hiring or retaining an agency to invent the spec while also running the calendar.
Do this instead
Hands on a known sequence are useful. Hands inside a missing spec pick the louder job (the calendar) and the leak stays.
Referrer field
Used
Not 'organic' by default
Ask timing
After done
Not at invoice
Attributed
Yes
Or you cannot name the engine
This week
Who referred whom is a field
Who referred whom is a field
The ask fires after completed work
The referred person has a source tag
Double-pay and silence both have rules
Want the longer lesson, not the page for this niche? Ask for the review after the work ↗
Working notes
The minimum CRM, pipeline, and nurture spec before you add more pages. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Referral system does not split by niche and city. The wiring is the same: objects, edges, one test conversion. Read a connect map if two tools are already in the stack, or a vertical essay if the language needs to change.
A full calendar and an empty pipeline is two databases.
Read ↗A high score in a CSV is not a qualified opportunity.
Read ↗If the thank-you does not change the contact, the page was a brochure.
Read ↗Show-up and close are the numbers. Traffic without those two is a content hobby.
Read ↗An $8k offer on an $8 process is how you attract the wrong buyer and exhaust the right one.
Read ↗Payment is the start. Day 0–7 decides whether they become a case study or a refund conversation.
Read ↗Email and WhatsApp stay open. A call is for installing the system.