Ongoing · 18 months in Experiment 2024 — Present

Operator positioning through systems, not posts.

A multi-year build of my own discoverability infrastructure — writing rhythm, tool library, AI-citation surface, and the architectural decisions that turned this site into a compounding asset. The case study where I am simultaneously the operator and the system being built.

6/mo
Inbound enquiries
Qualified leads via organic, no outreach
38
Essays shipped
Long-form, all within the architecture
12
Tools released
Free utilities, citation-engineered
340+
AI citations earned
Across ChatGPT, Perplexity, Gemini
01 · Context

Why I started building this in public

By late 2023, I’d been running growth systems for SaaS clients for years — but my own discoverability surface was almost nonexistent. A modest LinkedIn presence, occasional Twitter activity, no real long-form output, no canonical site I owned. The credibility I’d built was almost entirely relational, propagating through referrals from people I’d worked with directly.

That was fine for as long as I wanted to keep working through the same network. It wasn’t enough if I wanted to build a practice that compounded beyond it. The thing I sold to clients — discoverability infrastructure — I hadn’t built for myself. That gap became the project.

02 · Strategy

The principles I committed to upfront

Most “personal brand” advice points toward the creator playbook — daily posts, hot takes, performance-driven content. I wanted to test whether the same architectural principles I used for SaaS clients would work for operator positioning. Different category, same operating system.

Three principles I committed to at the start:

  • Infrastructure, not campaigns. The output would be evergreen long-form essays, working tools, and structured case studies. Not LinkedIn posts. Not hot takes. Things that compound for years, not hours.
  • Slow cadence, high quality. Target 1–2 substantial pieces per month. Resist the volume pressure even when the metrics felt slow. The whole bet was on compounding, and compounding requires patience.
  • Eat my own dog food. Every architectural decision I made on this site should be defensible by the same frameworks I’d recommend to a client. If I wouldn’t tell a client to do it, I wouldn’t do it here either.

“The thing I sold to clients — discoverability infrastructure — I hadn’t built for myself. That gap was the project. If I couldn’t make this work for me, I had no business making it work for them.”

Y Yash Tulsyani · Building in public, 18 months in
03 · Architecture

The three surfaces I built

The build was layered. Each surface reinforced the others — and each had a specific job in the discoverability flywheel.

System architecture
Surface 01
Essays
Long-form operator thinking — frameworks, mistakes, specific cases. The depth surface where authority gets demonstrated. 38 essays shipped, organised into 5 topical clusters that compound together.
Surface 02
Tools
Free utilities for the operators I want as readers and clients. Built for utility first, citation surface second. 12 tools released, citation-engineered to earn discovery via AI search.
Surface 03
Case studies
Long-form breakdowns of engagement work — strategy, execution, the numbers, and the lessons. The proof surface where credibility gets specific.

Why three surfaces, not one

Single-surface personal brands underperform structurally. A site that’s only essays is read as opinion. A site that’s only tools is read as developer marketing. A site that’s only case studies is read as a sales page. The combination is read as an operator practice — which is exactly the positioning I wanted.

The three surfaces also cross-link aggressively. Every essay points to relevant tools and case studies. Every tool points to the essay that explains the thinking behind it. Every case study points to the services that drove the engagement. The internal-linking architecture isn’t an SEO tactic here — it’s the structural expression of how the practice connects.

04 · Execution

What it took to maintain the cadence

The work isn’t dramatic. It’s the discipline of showing up consistently for 18+ months without flinching when the numbers were slow.

Four operating decisions made the cadence sustainable:

  • Extraction over invention. Most essays started from frameworks I was already using in client work — not topics I had to research from scratch. Recording client calls (with permission) and transcribing thinking I was already doing made writing 5× faster.
  • Calendar protection. Two half-days per week blocked specifically for this work. Treated as non-negotiable. Calendar pressure is the most common reason personal brand builds fail.
  • Quality bar before quantity. Better to publish nothing than to publish below the quality bar. The Insights archive has 38 pieces in 18 months — and would have had 80+ if I’d lowered the bar. The 80-piece version of this site would have been weaker, not stronger.
  • Public commitments only when ready. No “I’m launching a newsletter” announcements before the first 5 issues were drafted. No “I’m building X” tweets before X was functional. Public commitments before output is brittle.

The cadence isn’t fast. It’s steady. Steady compounds; fast usually doesn’t.

05 · Results

What the numbers actually look like

The growth curve looked exactly like the architecture-led SEO curves I’d built for clients: flat for the first 4–6 months, inflecting around month 7, accelerating from month 12 onward. The shape is the same; the timeline is the same; the dynamics are the same. That was the test, and the test passed.

Monthly organic sessions · 18 months Google Search Console · raw data
Month 1 Month 6 Month 12 Month 18 Month 24
  • 6 qualified inbound enquiries per month by month 18 — all organic, none from outreach. The acquisition channel I previously had to push is now a channel that pulls.
  • 340+ AI citations earned across ChatGPT, Perplexity, and Gemini for category-defining queries. The citation surface that didn’t exist 18 months ago.
  • Compounding without proportional investment. The 18th month required less work than the 12th. The system is now running on accumulated authority rather than fresh production.
  • The practice became more defensible. Conversations with potential clients now start mid-context — they’ve read the essays, used the tools, seen the case studies. The discovery work is mostly already done by the time we talk.
06 · Lessons

What I’d tell another operator considering this

Four things, with 18 months of receipts:

  1. The work compounds, but not when you want it to. The first 6 months feel like screaming into a void. The metrics don’t move. The audience doesn’t materialise. You either commit to the architecture for the long arc or you give up and revert to outreach. There’s no middle path.
  2. Slow cadence beats fast cadence almost every time. I shipped 38 pieces in 18 months. The version of me that tried to ship 80 pieces in the same window would have produced weaker work, burned out, and probably abandoned the project. Restraint is the underrated growth skill.
  3. The internal linking and architecture work matters more than the writing quality. Two pieces of evidence: (1) my best-written essays aren’t always my best-performing essays, and (2) the pieces that compound hardest are the ones with the densest internal links and clearest cluster position. Architecture eats craft for breakfast.
  4. This was the highest-ROI work of my last decade. The inbound channel pays back every hour invested at a multiple no client work can match. If I’d started this in 2020, my practice would have a 4-year head start on what it now has.

The build continues. The next 18 months will probably look different — deeper case studies, more tools, fewer essays — as the architecture matures and the operating priorities shift. The framework stays. The discipline stays. The output evolves.

Other case studies