The GUILD Digital Operations Ecosystem
A self-built operating system for a global gemology brand: five interlocking systems stitched into one intelligent loop that eliminated daily dirty work and freed the team to create.
The thesis
Powerful systems are not the same as a powerful operation. Power emerges from how systems connect.
I volunteered to lead overseas Instagram operations at GUILD, a global gemology brand running two distinct entities under one house: GUILD Gem Laboratories (the authority in colored gemstone identification) and GUILD Institute of Gemology (the education arm).
The brief was small: run the accounts. But what I saw on day one was bigger. The team was producing solid content, yet everything around the content — planning, posting, cross-platform distribution, performance review, customer follow-up — was done by hand, by different people, on different days, in different tools. Each step was competent. The whole was leaking.
“Stop optimizing the parts. Design the connections.
I stopped thinking in tasks. I started thinking in systems — independent systems that could each carry weight on their own, but only became an operation when wired together. This is the story of how I designed and built that ecosystem, end to end.
The audit
Before you build the future, you read the past.
I went through every post across both accounts, mapped each piece to topic, format, hook, and outcome, and asked three questions: what worked, what was generic, and what the brand should be saying that nobody else is.
Out of that audit came two things — a content playbook and a brand voice map. I codified the house tone, the headline grammar, the color system, the do/don’t list, and a translation protocol so that a single message could be authored once and travel through any channel without losing meaning.
Most importantly, I gave the two accounts a clear reason to exist side by side, and a clear reason not to look the same.
The split
Two accounts. Two voices. One house.
The split was not a content calendar decision. It was a brand architecture decision. From that day on, every piece of content had a single question to answer: which house does this serve, and how does it prove that?
GUILD Gem Laboratories
Calm, paper-grade rigor. Deeper explanations, gemology breakdowns, behind-the-paper storytelling. We proved authority without losing warmth, and we never sacrificed credibility for virality.
GUILD Institute of Gemology
Warm, energetic, and reactive. Reels-first, light education, community prompts, student stories, quick "did you know" trivia. We grew the audience first, and converted them later.
The system
Five independent systems, one operating loop. Each one powerful on its own. Together, they run the operation.
SMMS — Social Media Management System
A schedule-first calendar: every post has a date, an account, an owner, a status, and a copy. Meta GraphAPI feeds live performance into the same database, so planning and review happen in the same view. The team no longer asks "what is everyone doing today?" — they read it.
LINKS — Instagram Link Wall
A consolidated link surface that pulls from the website, the AURORA competition, the field expeditions, and the course catalog. Configure once, and the link in bio stays current across both accounts without anyone touching a Story.
AURORA — Competition Module
A submission and judging platform for the Aurora Awards, fully integrated with the website. Entries flow into the same database as everything else, so winners become content, content becomes entries, and the loop is one system, not three.
Field Expedition — Website Module
End-to-end expedition flow: a destination page, a waitlist, an automated email sequence. Each new expedition writes its own leads into the CRM, and the SMMS reads those leads to plan a content wave around it.
Tracking & Attribution
A UTM builder and a short-link service on Cloudflare Workers. Every link is tagged at the source, GA4 sees every channel. No more guessing which Story brought which waitlist signup.
The wiring
Connections are the product.
A SMMS by itself is a calendar. A link wall by itself is a Linktree. A competition platform by itself is a form. None of them justify the engineering on their own.
What changes everything is the layer in between. I designed a single source of truth for content, links, and events. When a new expedition opens on the website, the link wall updates, the SMMS plans a content wave around the launch date, the short-link service tags every CTA, and GA4 attributes every signup. The team only writes the caption. The system handles the rest.
How a single content piece travels
- Authored once in the SMMS, against the brand voice map.
- Scheduled with a tagged short link, against the right account.
- Published with a UTM that GA4 can attribute.
- Referenced from the LINKS wall and the AURORA module if relevant.
- Measured, reviewed, and folded back into the next plan.
The outcome
Systems thinking, applied where it actually counts.
The team stopped doing daily dirty work. Planners stopped chasing statuses in chat. Editors stopped retyping the same caption in five places. Designers stopped re-exporting the same asset at three aspect ratios by hand. The systems did it, and they did it the same way every time.
That is the test of a system: it works whether or not the person who built it is in the room. After handover, the operation continued without me. The team kept making content. The brand kept growing. The systems kept their own promises.
“A generalist is not someone who does everything. A generalist is someone who can see the whole, and build the connections the specialists do not have time to draw.