The GC Practice

How it runs

The whole journey from handing over a card to a client. What is printed and what is digital, who does what, when, and what reaches the CRM.

The prospect journey

Hover any step for the detail behind it.

01

Identify

Jack

An owner worth inviting is identified — from a meeting, a client introduction, or an accountant.

No list is bought and nobody is cold-approached. The practice invites; it does not prospect.Produces — Nothing yet
02

Hand over the card

Jack

The numbered A6 card is given in person.

Never posted in bulk, never left on a table. The card carries no date and no venue, so one print run of 2,000 covers every event to 2028.Produces — A6 invitation card
03

Record the number

Jack

Record in the CRM which card number went to whom.

Do this the same day. Until it happens, any response comes back attached to a number nobody can identify. This is the single step that makes the whole system work.Produces — CRM: code → lead
04

They scan or type

Prospect

The QR code, or the six characters typed by hand.

Lands on thegcpractice.com/i/CODE. Not linked from anywhere and not indexed — a real number is the only way in.Produces — —
05

Visit recorded

Automatic

Logged the instant the page opens, before they press anything.

Somebody who opened their invitation twice and never confirmed is a warmer call than somebody who never opened it. Neither was visible before.Produces — CRM: invite_visit
06

They choose

Prospect

Confirm a place, ask a question first, or decline with a reason.

Three routes, none urgent. Nothing asks for money and nothing is sold.Produces — CRM: confirm / query / decline
07

Four questions

Automatic

The Mini Q, straight after confirming. Skippable.

Asked after the commitment so it costs no confirmations. Attendees who complete it convert at nearly twice the rate of those who do not.Produces — CRM: invite_miniq
08

Karen rings

Karen

Within a few days of confirming.

A person, not an automation. Fills in whatever the Mini Q was skipped on, and confirms they are who the card was given to.Produces — CRM: stage updated
09

Ticket goes out

Karen

Date, venue and reference.

The venue appears here and nowhere else — not on the card, not on the website. Sent about three weeks before the morning.Produces — Printed ticket
10

The morning

Graham

Nine until one. Capped at twenty businesses.

A working morning, not a presentation. Nobody is sold to and nobody is asked to sign anything. The card admits two.Produces — Attended / no show
11

Step 6, then diagnostic

Graham

The follow-up conversation, then the diagnostic meeting.

The first commercial conversation happens here, and only if they ask for one. The full office address is given at this point and not before.Produces — CRM: client

When someone hesitates

The brochure is not a stage in the sequence. It is the second approach.

They hesitate

Prospect

Interested, but not yet convinced enough to give up a morning.

Sometimes visible in the first conversation. More often it is silence: the card was scanned and nothing followed. Two weeks with no response is hesitation, not disinterest.Produces — —

The brochure

Jack

Handed over in person, as a second approach.

Thirteen pages, nine named clients, printed and numbered. Its job is to answer a sceptic, so it belongs at the point of doubt rather than at the event — by then they have already decided to come and it has nothing left to do. Never emailed, never linked, never published. The cover carries their name.Produces — Printed brochure

Back to the card

Prospect

They still confirm using the number on their original card.

The brochure carries no code of its own. The invitation number stays the single identifier throughout, so the CRM sees one thread rather than two.Produces — Rejoins at step 6

A person does itPrinted, handed overThey do it onlineAutomaticCRM entry

Only three steps are automatic: the visit record, the response, and the Mini Q. Everything else is a person doing something. The website captures and records; it never sells and never chases.

The timing

WhenWhatNote
Day 0Card handed overJack. Physical. Record the number the same day.
Day 0–14They scan it, or they do notMost scans happen within 72 hours. After 14 days with no scan, it is a phone call rather than a wait.
On hesitationBrochure handed overJack, in person. At the point of doubt — not at the event, where it has nothing left to do.
On confirmingMini QAutomatic, immediately after.
+2–4 daysKaren ringsNever later than a week; the intent goes cold.
−3 weeksTicket sentDate, venue, reference.
−3 daysReminder callKaren. This is what turns a confirmation into an attendance.
The morningThe eventNine until one. Capped at twenty businesses.
+2 daysStep 6 conversationWhile the morning is still fresh.
+2–3 weeksDiagnosticOnly where both sides want it.

Printed and digital

ItemFormQuantitySpecificationFile
A6 invitation cardPrinted2,000, one run350gsm uncoated or heavier. Numbered, no date, no venue, no region.GC-A6-Invitation-artwork.pdf
TicketPrintedPer eventCarries date, venue and the reference. The only place the venue appears.in the collateral page
Testimonial brochurePrintedShort runs13 pages. Numbered, issued by hand, never emailed or published.GC-Practice-Client-Accounts.pdf
Business cardPrintedJack85×55mm. Oxblood reverse, QR to the website. No telephone number.GC-Business-Card-Jack.pdf
Invitation emailDigitalAs neededPlain text, no images, no tracking. Supplements the cards; never the main route.in the collateral page
Email signaturesDigitalThreeGraham, Karen, Jack. Tables and inline styles for Outlook.signatures/
The websiteDigitalAlways onSix public pages plus the invitation page. No maintenance.thegcpractice.com

Brand

Colour

NameValueUse
Ink#14181CText, dark panels. The default dark.
Brass#8C7134The only accent. Rules, labels, small marks.
Brass lit#C0A468Brass on a dark ground.
Oxblood#6B2029SENT ITEMS ONLY — invitation, ticket, brochure, business card. Never navigation, never the website.
Paper#F2F3F1Page background. Cool, not cream.
Stone#E4E5E1Quiet panels.
Grit#5A646DSecondary text.

Rules

  1. Libre Caslon Display for anything engraved: headings, and labels set in wide-tracked capitals. Archivo for reading. IBM Plex Mono for numbers, codes and dates.
  2. No rounded corners anywhere. A practice sets type on a rectangle.
  3. Oxblood appears only on things that are sent or handed over. If it is on a screen, it is wrong — with one exception, the invitation page's seal.
  4. The ledger mark — one square per client place — appears on the website, the invitation card, the ticket and the back of the brochure. It is the one motif that crosses every medium.
  5. No photographs of people. No stock imagery. No logos other than the wordmark.
  6. British English throughout. No Americanisms, no marketing register, no exclamation marks.
  7. Never name the venue anywhere but the ticket. Never name a client who has not consented. Never publish the diagnostic conversion rate or client value.
All colour and type live in design/tokens.css. Change a value there and it moves the website, the invitation card, the ticket, the brochure and the business card together. Never set a colour anywhere else.

Backups

WhenWhatHow
NightlyJetBackupAutomatic, off-server. cPanel → JetBackup → File Backups. Restores a single file or the whole account.
Before any uploadpublic_html zipFile Manager → home directory → select public_html → Compress → download. Ten seconds.
AlwaysThe project foldercontent.json and the build, on your machine and the NAS. THIS IS THE ONE THAT MATTERS — dist/ can always be rebuilt from it; it can never be rebuilt from the server.
QuarterlyTest a restoreRestore one harmless file from JetBackup and confirm it works. An untested backup is a hope.

What reaches the CRM

formSent whenFields
invite_visitThe page openscode, at, referrer, arrived
invite_confirmYes, hold me a placecode, name, business, email, phone, companion
invite_miniqStraight after confirmingcode, team_size, challenge_time/team/money, challenge_notes, change_90_days, turnover
invite_queryAsk before you decidecode, name, email, message
invite_declineNot this timecode, reason, reason_label, email
confirmTicket reference enteredticket_reference, name, email
enquiryRequest an invitationname, business, role, email, phone, location, turnover, message

Endpoint: https://tools.gracor.org/api/capture.php

If the CRM is unreachable, the form opens the visitor's email programme with everything they typed already filled in, so the enquiry still arrives. Nothing is lost while the endpoint is being built.