Home Blog The Lab The Autonomous Halt Music

Tag: Business Development

Mason County Business: Olympic Mountain Ice Cream Expands to Port of Shelton, Chamber Keeps Community Connected — Mason County Minute
Big things are brewing on the business front in Mason County.

Olympic Mountain Ice Cream — the beloved local ice cream maker with roots in the Skokomish Valley — is making a major move. The company is expanding into a new 11,500-square-foot facility at the Port of Shelton, backed by a $1.75 million state CERB (Community Economic Revitalization Board) loan. The new space is four times larger than their previous location, with expanded production capacity, a retail storefront open to the public, and an estimated 17 new jobs coming to the community over the next few years. For a region where quality food manufacturing jobs are rare, this is the kind of growth that matters.

Meanwhile, the Shelton-Mason County Chamber of Commerce continues to keep the business community wired together. The Chamber recently hosted its Timber in Mason County luncheon featuring Green Diamond Resource Company — highlighting a business with 130+ years of history in Shelton and an ongoing investment in sustainable forestry practices in the region. The Chamber’s regular Business After Hours events give local entrepreneurs and professionals ongoing opportunities to connect and build the relationships that keep Mason County’s economy moving.

Business Highlights
- Olympic Mountain Ice Cream: Expanding to 11,500 sq ft at Port of Shelton. $1.75M state CERB loan. 4x larger facility with retail storefront. ~17 new jobs expected. Skokomish Valley roots.
- Green Diamond Resource Company: 130+ year Shelton history. Featured at Chamber’s Timber in Mason County luncheon. Ongoing sustainable forestry investment in Mason County.
- Shelton-Mason County Chamber of Commerce: Business After Hours events held regularly. Visit masonchamber.com for upcoming schedule.
- Port of Shelton: Active economic anchor for Mason County industrial and commercial development. portofshelton.com.
Whether it’s ice cream or timber, Mason County businesses keep showing up. Support local when you can.

Sources: Mason County Journal, Shelton-Mason County Chamber of Commerce, Hood Canal Communications (CERB loan announcement), Port of Shelton, MasonEDC.org
April 8, 2026
I Accidentally Built an Operating System for an Industry

{“@context”: “https://schema.org”, “@type”: “Article”, “headline”: “I Accidentally Built an Operating System for an Industry”, “url”: “https://tygartmedia.com/i-accidentally-built-an-operating-system-for-an-industry/”, “datePublished”: “2026-04-04T16:56:11”, “dateModified”: “2026-04-04T16:56:11”, “author”: {“@type”: “Person”, “name”: “Will Tygart”}, “publisher”: {“@type”: “Organization”, “name”: “Tygart Media”, “url”: “https://tygartmedia.com”}}{“@context”: “https://schema.org”, “@type”: “BreadcrumbList”, “itemListElement”: [{“@type”: “ListItem”, “position”: 1, “name”: “Home”, “item”: “https://tygartmedia.com”}, {“@type”: “ListItem”, “position”: 2, “name”: “I Accidentally Built an Operating System for an Industry”, “item”: “https://tygartmedia.com/i-accidentally-built-an-operating-system-for-an-industry/”}]}

Nobody sits down and says “I’m going to build an operating system for an entire industry.” That’s not how it starts. It starts with one client who needs a website. Then another who needs their Google Ads cleaned up. Then someone asks if you can help them figure out why their phone isn’t ringing.

You solve problems. You move on to the next one. You don’t zoom out.

I zoomed out recently — for the first time in a long time — and what I saw surprised me. I hadn’t been building a marketing consultancy. I’d been building a vertical operating system for the restoration industry, one problem at a time, without ever calling it that.

How It Actually Started

The first piece was SEO. A restoration contractor needed to show up when someone searched “water damage restoration” in their city. Straightforward enough. I built the content, optimized the site, tracked the rankings. It worked. They referred someone else. That someone else had a slightly different problem — their ads were running but the calls weren’t converting. So I looked at that.

Call Track Metrics came in because I kept running into the same argument: the client thought the calls were coming from one place, I thought they were coming from another, and neither of us could prove it. CTM solved that. Now every call is tagged to the source — the keyword, the page, the campaign, the full journey. Attribution stopped being a debate and became math.

Then I noticed that the calls were coming in but jobs weren’t closing at the rate they should. That’s not an SEO problem. That’s an operations problem. So I started looking at intake — how calls were answered, how follow-up happened, how estimates were scheduled. An AI intake agent started to make sense. Not because I was trying to build AI products, but because the gap was right there and I could see it.

The Restoration Golf League came from a completely different direction. Restoration contractors need referral relationships with insurance adjusters and property managers. That’s the commercial side of the business. A golf league is one of the best relationship-building structures that exists in professional services — relaxed, repeated contact, shared experience. It wasn’t a marketing idea. It was a relationship infrastructure idea that happened to use golf as the mechanism.

Each tool built for a specific job. The pattern only becomes visible when you step back.

The Inventory I Didn’t Know I Had

When I actually sat down and listed everything that exists right now across the work I’ve been doing, here’s what came out:

A content intelligence platform — a BigQuery knowledge base that logs every session, surfaces patterns, and drives automated publishing. A lead tracking infrastructure built on Call Track Metrics, wired to every traffic source. A referral network of restoration contractors meeting through a structured golf league across multiple cities. A commercial compliance strategy using fire extinguisher inspections as a loss leader to get in the door with property managers. An AI receptionist product purpose-built for restoration intake — Twilio, Claude on Vertex AI, Cloud Run, Firestore. A Company OS model — a fully hosted GCP environment where I run a contractor’s entire revenue infrastructure and take a commission on verified results. A WordPress CRM being built and dogfooded on my own site before being offered to clients. A knowledge cluster of five interconnected websites building topical authority in the restoration and risk intelligence space.

None of those were planned in sequence. Each one was the answer to a specific question that kept coming up. But together they cover almost every layer of how a restoration business actually operates — lead generation, lead tracking, intake, conversion, referral relationships, commercial acquisition, operations tools, and content authority.

That’s not a service menu. That’s a stack.

Golf, AI, SEO, compliance, CRM — they look unrelated until you see the thread connecting them.

Why Accidental Might Be Better Than Planned

I’ve thought about whether it would have been better to plan this from the start. Design the full system upfront, build it in sequence, launch it as a coherent product.

I don’t think so. And here’s why.

Every piece of this was validated before the next one got built. The CTM infrastructure exists because attribution disputes are real and expensive. The AI intake agent exists because I watched calls get dropped after I’d already driven them. The golf league exists because I saw contractors lose commercial accounts to competitors who had better adjuster relationships, not better work. Each problem was visible because I was close enough to the industry to see it — not designing from a distance.

The version of this that gets designed upfront has a different failure mode: it’s theoretically complete but practically wrong. The problems you think exist from the outside are never quite the same as the ones that actually exist on the inside. Building problem by problem, staying inside the industry, means every piece of the stack is load-bearing because it was built under load.

There’s also something that happens when you’re not trying to build a system. You’re more honest about what’s actually needed. You don’t add things because they complete the picture — you add them because the gap is genuinely painful. The result is a leaner, more accurate stack than anything I could have designed in a planning session.

The Question I’m Sitting With

The thing I keep coming back to: is this replicable in other verticals, or is it only possible because of the depth of time I’ve spent inside restoration specifically?

I genuinely don’t know. The honest answer is probably both. The approach — stay close, solve real problems, let the system emerge — is transferable. But the specific inventory I ended up with is deeply shaped by restoration’s particular quirks: the insurance dependency, the emergency-driven intake, the adjuster relationship dynamics, the commercial vs. residential split, the franchise structures, the IICRC certification culture.

A different vertical would produce a different stack. HVAC has different intake patterns. Personal injury law has a completely different referral economy. Healthcare has different compliance requirements and trust dynamics. The method of paying attention and building toward what you see would be the same. The pieces that emerge would be different.

What I’m more confident about: you can’t fake the depth. The reason the stack works is because I know what it’s like to be a restoration contractor well enough to feel the pain of each layer. That knowledge isn’t transferable quickly. It’s accumulated. Someone who decided tomorrow to “build a vertical OS for HVAC” would be designing from the outside. They’d get some things right and miss the things that matter most, because those only become visible from inside.

Looking back, the pattern is obvious. In the moment, it was just the next problem to solve.

What This Changes

Naming a thing changes how you relate to it. Before this realization, I was a marketing consultant who did a lot of different things for restoration companies. That description is accurate but it undersells the coherence of what’s actually there.

Now I think of it differently: I’m a vertical infrastructure builder who happened to start in restoration and went deep enough that the full stack became visible. The individual services aren’t the product. The system is the product. Any one piece of it — just the SEO, just the CTM setup, just the AI intake — is less valuable than the whole because the whole is integrated in ways that individual pieces can’t be.

That changes what I build next, how I talk about what I do, and who I build it for. It also changes what “being done” means — because a vertical OS is never really done. Industries evolve, problems shift, new gaps appear. The work is staying close enough to keep seeing them.

I didn’t plan any of this. I just kept solving the next problem.

Turns out that’s a strategy.

April 4, 2026
The Company OS: What If I Just Ran Your Entire Business and Took a Cut?
{“@context”: “https://schema.org”, “@type”: “Article”, “headline”: “The Company OS: What If I Just Ran Your Entire Business and Took a Cut?”, “url”: “https://tygartmedia.com/the-company-os-revenue-infrastructure/”, “datePublished”: “2026-04-04T16:24:41”, “dateModified”: “2026-04-04T16:24:41”, “author”: {“@type”: “Person”, “name”: “Will Tygart”}, “publisher”: {“@type”: “Organization”, “name”: “Tygart Media”, “url”: “https://tygartmedia.com”}}{“@context”: “https://schema.org”, “@type”: “BreadcrumbList”, “itemListElement”: [{“@type”: “ListItem”, “position”: 1, “name”: “Home”, “item”: “https://tygartmedia.com”}, {“@type”: “ListItem”, “position”: 2, “name”: “The Company OS: What If I Just Ran Your Entire Business and Took a Cut?”, “item”: “https://tygartmedia.com/the-company-os-revenue-infrastructure/”}]}

I’ve been the outside SEO guy for a while now. The vendor. The person you call when your rankings drop or your Google Ads are bleeding money. You pay a retainer, I do the work, and at the end of the month you squint at a report trying to figure out if it was worth it.

I’ve been thinking about burning that model down.

Not because it doesn’t work — it does. But because it fundamentally undersells what I can actually do, and it puts me in a position where I’m always justifying my existence to someone who doesn’t fully understand what I built for them. There’s a better arrangement. And I think I finally figured out what it looks like.

Here’s the idea: instead of being your marketing vendor, what if I became your entire revenue infrastructure?

What I’m Calling the Company OS

I build a lot of things for the businesses I work with. Websites. Content engines. Ad campaigns. Call tracking. CRM setups. AI agents that handle intake and follow-up. I’ve been doing all of this across multiple companies at once. At some point I started noticing that the companies where I’m most involved — where I’m running the full stack, not just one piece — perform dramatically better than the ones where I’m just “doing SEO.”

So I started asking: what if I just owned the whole stack, hosted it, and took a percentage of what I could prove I drove?

That’s the Company OS. Here’s what’s in the box:
- A dedicated Google Cloud VM — your company’s own server environment that I host and manage
- Your website, fully built and optimized by me
- AI-generated content at scale — the kind that dominates local search
- Google Ads and Local Service Ads managed by me
- Call Track Metrics wired to every traffic source — every call tracked to the page, the keyword, the campaign, the full journey
- A CRM and project management tools for your crew
- AI agents handling intake, follow-up, and estimate coordination
Every node in the network — website, ads, calls, CRM, AI agents — connected and managed as one system.

The contractor pays nothing upfront. No retainer. No setup fee. They owe me a percentage of every verified dollar of revenue that came through my system. Call Track Metrics makes it provable. We both look at the same data.

The Numbers I’m Working With

I started this in the restoration contracting space because that’s the vertical I know cold, but the model generalizes to any business where the lead is a phone call.

A mid-size restoration contractor doing $150,000/month in revenue is not unusual in a decent market. Here’s what my costs look like to run the OS for one client: the Google Cloud VM runs about $60–90/month, Call Track Metrics is $150–250/month, content production runs $200–400/month, CRM and project management tools are another $100–200/month. The big variable is Google Ads spend, which I front — somewhere between $2,000–5,000/month depending on the market.

All in, I’m spending $4,000–7,500/month to run the OS for one contractor, including ad spend I’m fronting out of pocket.

At 15% commission on a $150K/month contractor, I’m making $22,500 gross and netting around $15,000–18,000 after fully-loaded costs. Three contractors at that level is $45,000–54,000/month net. Five is north of $80,000/month.

Compare that to what contractors are currently paying for leads. HomeAdvisor sells the same lead to four contractors at $80–200 per lead with a 15–25% close rate — your effective cost per job is $400–1,200, and there’s zero attribution on whether it was a good lead or junk. Thumbtack is similar. My model: you pay nothing unless revenue comes in, and we both know exactly where it came from.

What Makes This Actually Different

There are agencies that do some of this. There are MSPs that host infrastructure. There are lead gen companies that take a fee per lead. What makes this different is that all three things have to be true at the same time.

I own the full stack. Not just ads, not just SEO — the website, the content, the tracking, the CRM, the AI agents. When you remove a piece, the whole thing works less well. That integration is the moat.

Attribution is verifiable. Call Track Metrics is the key that makes the commission model honest. Without traceable data, a performance arrangement is a trust exercise. With CTM, it’s just math. Every party sees the same numbers.

I absorb the cost and the risk. I front the ad spend. I pay for the infrastructure. This is not a retainer with a performance kicker — this is genuinely performance-only. That’s a fundamentally different ask of the client and a fundamentally different commitment from me.

Every call verified. Every dollar attributed. Call Track Metrics makes the commission model honest — no arguments about where the revenue came from.

I haven’t seen anyone do all three cleanly. There are pieces of it everywhere. But not the whole thing, not in one managed system, not with the attribution layer that makes it honest.

What Could Go Wrong (Because I Should Be Honest About This)

The scariest scenario: I front $3,000–5,000 in Google Ads for a contractor and their office can’t close the calls I send them. The leads are real — qualified calls from people with water damage or fire damage — but if the contractor answers poorly or doesn’t follow up, those jobs don’t close and my commission is zero. I’ve eaten the ad spend.

Mitigation: I don’t take on clients whose operations are a mess. I build an AI intake agent so the first response to every inbound call is handled by my system. And I put a close-rate floor in the contract — if it drops below a threshold, we either fix it or I exit.

The second risk: at some point a contractor doing $300K/month realizes they’re paying me $45K/month, every month, and they start looking for the exit. The answer is that the infrastructure I’ve built is genuinely hard to replicate — the domain authority, the content history, the CTM data — and I should be open to renegotiating toward a hybrid model as relationships mature. Don’t be greedy enough to kill a good thing.

Third: Google changes local search. This is always true and always real. But the moat isn’t just SEO. The call tracking, the CRM, the AI intake — I own the communication infrastructure. Even if search displays change, I still own the pipeline.

The Bigger Picture

One VM. One system. Scalable to any vertical where the lead is a phone call and the conversion is trackable.

This started as a restoration contracting idea but I keep thinking about the generalization. The Company OS is not vertical-specific. Anything with a traceable phone-call revenue model could work. HVAC. Plumbing. Roofing. Personal injury law. Dental. Any business where the lead is a call and the conversion is trackable.

The risk of thinking too broadly too early is that I spread myself before I’ve proven the model in one vertical. Restoration is where I have the deepest knowledge and the most infrastructure already built. That’s where this starts.

But the generalization potential is real. If the model works in restoration, the playbook exists. Every vertical is just a new instance of the OS spun up on a new VM with vertical-specific content and keyword strategy.

I’m writing this publicly because I want the pressure of having said it out loud. This is a big change in how I think about my work and my offer. I’m not an SEO vendor anymore — or at least, I don’t want to be. The Company OS is the more honest version of what I’ve actually been building toward.

How does this age? I’ll find out.
April 4, 2026