Snow-covered Alpine peaks beneath a blue sky, in the vivid royal blue and cream of the Contentmaxxing banner
GBE

Good Taste.
Great Output.

content, culture, and good shit worth sharing

THE STORY
A NOTE FROM GABEwhat I do and why I give a shit

A point of view.
Put to work.

THE COMPUTER IS NOT THE CREATIVE DIRECTOR.
Gabriel Santiago’s @HeyYoGB profile image: illustrated character wearing a black cap and sunglasses
WORDS & WORK BY

Gabriel
Santiago.

Growth strategist.
Creator. Builder.

Follow along

I’m Gabe. I turn what you know into content people give a shit about and build the systems to keep it going.

For founders and brands, with AI in the workflow and your voice at the center.

Less pitch.
More proof.

1–2 of 4

Use the buttons, swipe, or focus this row and use the arrow keys. Open a case for the timeline and evidence.

Lute

Growth & Marketing Lead

1.29Maccumulated launch-post views

I helped prepare the launch, explain the product and coordinate content across creators and community.

November 3, 2025 post · counters checked October 8, 2026.

Ratel

Technical content & strategy

66,032X account impressions

I worked on who the content was for, what each post needed to explain, and where useful replies could add to the conversation.

September 8–October 5, 2026 · supplied account report.

Rising Tides

Cross-channel content

8.1Kviews in a supplied Reddit post snapshot

I turn product knowledge and buyer conversations into posts, replies and articles, with a review process for each channel.

Reddit and LinkedIn proof inside. Supplied snapshots; reporting dates not shown.

Personal writing

Writing & publishing · @HeyYoGB

3.8Mimpressions on my own X account
Followers at period end
9K+

October 11, 2025–October 10, 2026.
Typefully-reported selected range.

Lute

What I did

Dated records are labeled. Other steps describe the work, without assigning dates the sources do not establish.

  1. Before launch

    Plan the social and content work

    I joined before launch and planned how to introduce a technical trading product, explain why it mattered and give people a reason to follow along.

  2. Product storytelling · role scope

    Turn features into content

    I worked on product explanations and integration content. The operating brief turns eleven features into hooks and short-video direction; it is a planning artifact, not a shipped-video count.

  3. November 3, 2025

    Support the launch and community conversation

    The public launch thread introduces nine product stories. I also invited people into a Lute community list from my own account. My personal-post activity stays separate from the brand’s counters.

  4. Creator coordination · date not established

    Work with creators

    My role included the first KOL campaign with 7+ creators. The career record and creator brief support coordination and direction, not sole authorship of every asset.

  5. December 2025–January 2026

    Keep product content moving

    Later reports preserve December product and integration posts, plus seven selected creator examples dated January 7–9, 2026. These are later outputs, not November launch metrics.

LUTEPRE-LAUNCH & LAUNCH
1.29Maccumulated launch-post views

A launch with
a head start.

I joined before launch as Growth & Marketing Lead, working across the content operation, product storytelling, creators and community.

1,293,306 views on @lute’s November 3, 2025 launch post, checked October 8, 2026. One post’s accumulated reach, not launch-week views or account impressions.

Authentic Lute launch post from November 3, 2025
Preview: open the image for the full post. Public post captured October 8, 2026. Read the launch post

MY PART IN THE LAUNCH

Product, creators
and community.

Pre-launch social planning and product explanations, followed by creator coordination and community activation.

The launch post is one public output from that broader work. Open the image to inspect the original screenshot.

More from the campaign.

LUTE @lute · Supplied screenshots, received October 12, 2026. Counts shown as captured, not refreshed live.

Pre-launch teaser

184Kviews shown in the screenshot

1.3K likes · 310 reposts · 554 replies

A short teaser ahead of the product launch.

Read the original screenshot
Pre-launch teaser by LUTE @lute, October 23, 2025. 184K views, 1.3K likes, 310 reposts and 554 replies shown.
Selected post preview. The original screenshot includes both October posts.
Cross-chain product announcement: separately verified counters

MORE PRODUCT PROOF

Cross-chain trading,
in one click.

A product announcement from @lute on November 14, 2025.

Likes
484
Replies
231

Visible in X’s official post embed, checked October 12, 2026. These are accumulated counters for this post, separate from the launch-post views above.

Read the original post on X

An example of the account’s product communication during my work with Lute. The counters do not isolate my contribution or imply sole authorship of the visual.

LUTE @lute cross-chain trading announcement, November 14, 2025. Official embed shows 484 likes and 231 replies, captured October 12, 2026.
Original X embed capture. Open the image to read it at full size.
My contribution & result context

I planned pre-launch social and content, helped explain product features and integrations, coordinated the first KOL campaign with 7+ creators, and activated community conversations around launch.

The creator brief translated eleven product features into hooks and short-video direction. It describes planning and coordination, not a count of shipped videos.

My role and scope are supported by career records and the operating brief. The post counters do not isolate my contribution or imply sole authorship of every visual. Exact launch-period account analytics remain unavailable.

The same October 8 check recorded 1,558 likes and 493 replies. Later December report windows are separate and are not added to these counters.

Ratel

What I did

Dated records are labeled. Other steps describe the work, without assigning dates the sources do not establish.

  1. Planning · action plan and calendar

    Choose the audience and angles

    I defined the technical audience and editorial choices. The action plan and Week 1 calendar record those decisions.

  2. Content and distribution · role scope

    Give each post one job

    I split crowded explanations into focused posts and made room for replies that were useful on their own. These records support my content decisions; they do not prove that every draft was published.

  3. September 8–October 5, 2026

    Review the account results

    The supplied X report records 66,032 impressions across four weekly blocks. The last block has 49,880 impressions versus 1,451 in the first; October 5 may be partial.

  4. September 4–October 3, 2026 · separate channel

    Keep LinkedIn results separate

    The LinkedIn appendix records 14,443 impressions and 504 clicks in its own window. I do not add those figures to the X totals or treat them as proof of causal impact.

RATELTECHNICAL STORYTELLING
66,032X account impressions

Make the technical
worth reading.

I defined the audience, content angles and editorial choices, turning crowded explanations into focused posts and useful replies.

September 8–October 5, 2026. Supplied report, pages 2–4; October 5 may be partial. Account activity alongside my content work, not isolated causal impact.

Ratel / X account

Four weeks.
A wider audience.

66,032account impressionsSep 8–Oct 5, 2026

+22 net followers 37 follows − 15 unfollows

34.4× weekly impressions Last week / first week

Designed chart from the supplied report, pp. 2–4. Consecutive seven-day windows; October 5 may be partial. Account activity does not isolate my causal impact.
My contribution & result context

The Ratel Action Plan by Gabe and Week 1 calendar support the audience, editorial and content decisions. The supplied report records 446 engagements, 61 profile visits and +22 net followers (37 follows minus 15 unfollows).

Weekly impressions moved from 1,451 to 49,880: 34.4× when comparing the last and first seven-day blocks. This is not a claim that my work alone caused that change.

A separate LinkedIn window, September 4–October 3, 2026, recorded 14,443 impressions and 504 clicks. Its dates and channel remain separate.

The post-export totals do not reconcile with the account totals, so they are not combined. The evidence does not establish leads, revenue or adoption. Private source reports are not linked here.

Rising Tides

LinkedIn · Team proof

A closer look
at engagement.

5.86%

Engagement rate

7,430 followers shown

5 posts shown

1 of 4 snapshots

Account names and reporting dates are not visible in the supplied images.

How to read these figures

Each view keeps the engagement rate, follower count and post count from one supplied screenshot together. These are separate observations, not a combined team total.

The green changes in the source images are not interpreted here: their comparison periods and definitions are absent. No lifetime performance, revenue or isolated causal impact is inferred.

Reddit post snapshots.

Four analytics panels supplied for my Rising Tides Reddit work.

Top left · views
8.1K
10 upvotes · 35 comments
Top right · views
7.3K
18 upvotes · 46 comments
Bottom left · views
7K
11 upvotes · 31 comments
Bottom right · views
2.6K
12 upvotes · 15 comments
Four supplied Reddit analytics panels. Top left: 8.1K views, 10 upvotes, 35 comments. Top right: 7.3K views, 18 upvotes, 46 comments. Bottom left: 7K views, 11 upvotes, 31 comments. Bottom right: 2.6K views, 12 upvotes, 15 comments.
Open the image at full size. Original supplied screenshot; view counters are rounded. The charts are labelled “Views for the first 48 hours”; the screenshot does not establish that the headline view counters use that same window.

Capture date, year and post links are not visible. These selected snapshots support post-level reach and engagement, without establishing an account total, a growth comparison or isolated causal impact.

What I did

Dated records are labeled. Other steps describe the work, without assigning dates the sources do not establish.

  1. Inputs · documented operating scope

    Start with the product and buyer conversations

    I use product knowledge and buyer conversations to find useful subjects for posts, replies and longer articles.

  2. Drafting · channel-specific work

    Write for where it will appear

    I prepare Reddit, LinkedIn and X content, adapting company and founder perspectives to each channel.

  3. Review · voice documents

    Keep feedback attached to the work

    Voice documents keep corrections and feedback together. The workflow separates drafts, approvals and publication.

  4. October 5, 2026 · work update

    Record the scope of the work

    The update and content records support this cross-channel work. They are not a publication log for every draft. The separately supplied Reddit snapshots show selected post results, without a dated growth comparison.

RISING TIDESCONTENT OPERATIONS

One content operation.
Built for each channel.

I prepare Reddit, LinkedIn and X content, alongside longer articles, adapting company and founder perspectives to each channel.

Reddit

Useful posts, replies and community participation.

LinkedIn & X

Company and founder perspectives, shaped for each channel.

Articles

Longer explanations grounded in buyer conversations and product knowledge.

Draft Review Publish

Scope supported by the October 5, 2026 work update, content records and voice documents. This is an operating workflow, not a count of published pieces.

My contribution & evidence limits

I turn buyer conversations and product knowledge into useful posts and replies. Voice documents keep feedback and corrections together, while the workflow separates drafts, approvals and publication.

The work update and supplied records support the scope of my contribution. A reported batch is not evidence that every item was published, produced in one day or created automatically.

The supplied Reddit screenshot shows four analytics panels with rounded view counters and engagement counts. Four LinkedIn overviews separately show engagement rates, follower counts and post counts, with account names and reporting dates absent. It does not identify the posts or establish an account-wide total, growth over time, leads or revenue. Attribution to this case comes from the supplied context; the image itself has no client or account name. Individual names and private source reports remain off the page.

Personal writing

3.8Mimpressions
9K+followers at period end

October 11, 2025–October 10, 2026.
Typefully-reported selected range · @HeyYoGB.

Selected top posts

Top posts in available Typefully history.

Typefully’s impressions sort, retrieved October 11, 2026, across the selected September 1, 2010–October 11, 2026 range. The 200-row export does not establish a complete all-time X ranking. These stored post snapshots are separate from the annual account totals above and may differ from current X counts.

CONTENTMAXXING in arched yellow and orange vintage lettering against a bright Alpine sky

What I’m building, what’s working, and what I’m learning.

How I can help

A crowd gathered around an oversized vintage computer, printed in warm paper tones
AI helps with the work. You bring the good shit.
Custom client work

Stay yourself.
Show up more.

Contentmaxxing tree is my signature paid client work: a custom content system built around your expertise, voice, and workflow. Less time figuring out what to post. More time doing your thing.

  • A voice people recognize.
  • Content you feel good putting your name on.
  • Consistency that fits your schedule.
Work with me

Your voice. Your final say.

Before we
set off.

Good questions.
Straight answers.

Does the system post for me?

No. I prepare drafts. You review, approve, schedule and publish them.

Will it actually sound like me?

I work from your ideas, examples and feedback. You have the final say on every draft.

Do I need to be technical?

No. I handle the setup. You bring your ideas and review the work.

What if I barely have time to post?

We start with the time you actually have and build the workflow around that.

What does it cost?

It depends on what you need. Tell me what you’re working on, and we’ll talk through the scope and cost.

Let’s work together

Got a good idea?
Let’s work.

You’ve got the expertise. Let’s turn it into content people give a shit about.

Work with me

Original LinkedIn screenshot

Original pixels at readable size. Scroll sideways for the full overview.