Blog

  • The On-Ramp Is Real. The Commons Is Unfinished.

    The On-Ramp Is Real. The Commons Is Unfinished.

    Last verified: 5 September 2026. Practitioner essay from the workbench — not a SpaceX press release. We use this stack because it makes our company better, and we want SpaceXAI, SpaceX, Cursor, X, and Tesla to keep shipping. No affiliate links. Just the tools and the receipt.

    This morning I posted a theory I had been living inside for weeks.

    They bought Cursor to teach vibe coders how to use SpaceX AI and Grok Bot to teach those who can’t use Cursor. Then you realize Cursor Ultra isn’t needed and that your Grok Super Heavy subscription is the end result. They’re literally building on-ramps and scaffolding to upskill all of the folks they’re going to need in the next 36 months to leap technology forward at an unbelievable rate. Get in the ship.

    @wtygart, 6 September 2026
    https://x.com/wtygart/status/2096437798962430034

    That post is a reading from the workbench, not official copy. I write it as someone who already treats Cursor as a lead seat, Grok Bot as a Chief of Staff, Notion as the board, and Slack as the doorbell. I have walked WordPress sites by voice. I have rehearsed swarms on a laptop so I would not burn cloud tokens on a pattern that dies in alpha. I have watched Cursor write a work order with Owner = Chief of Staff and watched the Bot pick it up the same way a person would.

    The ladder is real. The pedagogy is not documented. The payroll is missing.

    What follows separates three things that keep getting smashed together: what SpaceX / SpaceXAI / Cursor actually built and said; the human-node invitation that builders can choose; and the contribution economy that does not exist yet, even though the first two rails of it are already on the floor.

    What the company actually assembled

    The documented sequence is short and expensive. Official language is consistent: build “the world’s most useful AI models,” combine Cursor’s product and distribution to expert software engineers with Colossus compute, start in software engineering, expand into knowledge work. That is vertical integration, not a secret apprenticeship.

    DateWhat actually happened
    Feb 2026SpaceX absorbs xAI. The AI work later brands as SpaceXAI.
    21 Apr 2026Partnership with Cursor: option to buy for $60B or pay $10B to work together.
    Mid-Jun 2026Record SpaceX IPO. On 16 Jun the option is exercised. All-stock. Implied Cursor equity value: $60B. Joint model slated for Cursor and Grok Build.
    11 Aug 2026Grok Bot early beta: persistent cloud computers, browser / filesystem / terminal, multi-bot coordination. Official line: “AI teammates you can give real work to.”
    14 Aug 2026Acquisition closes. Cursor’s close post: help make Grok useful and improve Grok Build, Grok Bot, the Grok API, and Cursor.
    21–26 Aug 2026Bot access expands down the plan ladder. Bot usage is separate from Grok and Cursor token pools. Still no standalone Grok Bot SKU.
    28 Aug 2026OpenAI says it will wind down its models in Cursor, proposing a mid-November shutoff after change of control.
    3–4 Sep 2026Grok Bot for Enterprise — orgs can invite people without a seat. Official template marketplace goes live. First featured internal template: Haggle Bot. SpaceXAI’s procurement writeup claims more than $100K identified in a week.
    Company events, not my theory. Verify prices on the live billing pages before you spend.
    SPACEXAI STACK, 2026 FEBxAI absorbed APR 21Cursor option JUN 16option exercised AUG 11Grok Bot beta AUG 14close AUG 26Bot on more plans SEP 3–4Enterprise + shelf Company events only. Verify prices on the live billing pages.

    Rockets and satellites plus X plus Grok plus Colossus plus the application layer where developers already live plus an agent that finishes jobs in existing tools. Buy the surface. Feed the data back into the models. Sell enterprise AI into a market SpaceX described, in IPO materials, as enormous. Catch Anthropic’s Claude Code and OpenAI’s Codex.

    That is enough. It is also not the story I told on X.

    What they did not say

    I have not found, in filings, product posts, or close announcements, any of the following:

    • That SpaceX bought Cursor in order to teach vibe coders how to use SpaceX AI.
    • That Grok Bot exists in order to teach people who cannot use Cursor.
    • A 36-month coordinated workforce-upskilling campaign.
    • SuperGrok Heavy as the official terminal subscription of that campaign.
    • An official paid creator commons for community builders.
    • “Get in the ship” as recruiting copy.

    Those lines are mine. Treat them as interpretation or do not treat them at all. The company incentive, on the paper it publishes, is models, data, subscriptions, and distribution. Human capability is a side effect unless someone designs for it.

    There is a second tension the marketing does not resolve. Grok Bot is sold as teammates that finish work, not as tutors. The same stack that lowers the skill floor can also replace the person who used to occupy it. That is not a smear. It is the product. We still want the product to succeed, because the alternative is standing still while the floor moves.

    The ladder I actually use

    THE LADDER 1234 CURSOR rehearse + code shop GROK BOT persistent teammates TEMPLATE MARKETPLACE share the method ENTERPRISE AGENTS invite without a seat A product ladder. Not official workforce planning.

    Here is the stack as it behaves on a desk, not as a slide. The field notes underneath this are the same ones we already published while the fleet was mid-job: Cursor checking on Grok Desktop, the fleet-bot blueprint, the Cursor command-center playbook, and the Second Brain MCP loop.

    Cursor is the rehearsal room and the code shop

    Cursor is the AI coding environment that made “vibe coding” a working method instead of a joke. SpaceX paid a category-leading price for it because it already had distribution to expert software engineers and a firehose of design decisions. Reported ARR figures in 2026 coverage conflict — earlier $1 billion-plus, later annualized numbers in the $2.6–$4 billion range — but the direction is not in dispute. Cursor gives SpaceX the application layer it lacked.

    On my board, Cursor is the lead seat. It assigns work. It stays the only git writer. Local first: rehearse the swarm on the laptop before you burn Grok Bot or cloud VM tokens. Last week that looked like Cursor as tender and eight specialist agents sharing one machine’s PowerShell. What broke first was not RAM. It was one shared shell. The fix was a tender plus off-shell work so specialists did not stand in line on the same mutex. Local Cursor is the cheap rehearsal room. The cloud is the tour — after the pattern survives alpha.

    Grok Bot is not a chat model

    Grok Bot is a persistent-agent product. Own cloud computer. Browser, filesystem, terminal. Signs into the tools you already use, including the ugly ones with no clean API. Multiple bots can run in parallel and message each other. Desktop, iOS, later iPad. Enterprise controls landed on 3 September. Usage is a separate grant from Grok and Cursor token pools.

    Access rides on other subscriptions. At launch the gate was SuperGrok Heavy, Cursor Ultra, and Cursor Teams Premium. Within two weeks the floor fell — first to Plus / Pro+ tiers, then, on 26 August, to SuperGrok and Cursor Pro. Prices in current secondary writeups cluster around Cursor Ultra ~$200/month, SuperGrok Heavy ~$300/month, Cursor Teams Premium ~$120/seat. Bundling has already changed once. An older “Heavy includes Ultra” offer was reported as a limited trial, then as a usage grant. My X line that “Ultra isn’t needed and Heavy is the end result” is a user conclusion, not a stable official bundle. Do not buy a plan on a slogan. Read the billing page the week you pay. We keep a vendor-neutral tracker at the AI Stack desk for exactly this reason.

    In the Command Center I run, Chief of Staff is not a second operating system. It digests. It files. It waits on Human Gate. Hard bans: never send, post, or pay without a person. Draft-to-self. The Bot that finishes work is useful only if the human still owns irreversible action.

    HUMAN GATE Never send. Never post. Never pay. Draft-to-self. Receipt on the board. The bot finishes work. A person owns irreversible action. Copied from the stop-line instinct in Haggle Bot. Put it in every serious template.

    The marketplace is a shelf, not a market

    On 4 September the official template marketplace opened at x.ai/bot/marketplace. At first look: 69 public bots, 43 creators, categories across Engineering, Sales, Product, Ops, Finance, Design, Marketing, Recruiting, Customer Success, Personal, Team. A template copies configuration — identity, instructions, skills, routines, selected plugins. It does not copy the original computer, logins, conversation history, API keys, or custom MCP servers.

    The first featured first-party template is Haggle Bot, an internal procurement specialist credited to Daniel Gartshein. SpaceXAI’s public case: more than $100,000 identified in a week; 43 unused SaaS seats (~$14,220); about $85,662 in unused SKUs on another product; a weekly tech/office order cut 58 percent ($14,629 to $6,143). Access to Slack, Notion, Drive, Gmail, Hex, Ramp. Human approval required before spend, terms, or vendor contact. Elon amplified the template the same day. The interesting part is not the dollar figure. It is the product shape: a named job, mapped tools, a stop-line written in public, and a one-tap install.

    Official marketplace language is share and install, not pay. Multiple independent writeups in the first 48 hours called it a marketplace before a market. No official creator payments as of this writing. That is the missing rail.

    The invitation, stated cleanly

    If you strip the myth out of my post, the usable claim is this:

    SpaceXAI assembled a ladder — Cursor, then Grok Bot, then shared templates, then enterprise agents that can invite people who do not even have a seat. That ladder can be used as more than a product funnel. Each person can become a node. Publish methods other people can run. Treat judgment, taste, and problem selection as the scarce work while execution gets cheaper.

    Growing humanity one plugged-in node at a time only works if the tools are a shared workbench, not just a subscription.

    This is not official SpaceX policy. It is a participation window. The company is distributing surface area because distribution is how models get used and paid for. Builders can use that surface area as a commons. Those two facts can be true at the same time. We are attaching to this stack as a best guess on how to succeed — and the honest version of “send love” is to use the tools hard, publish what breaks, and feed the useful methods back so the next build is better for everyone on it.

    The historic piece is not “they are recruiting us for a 36-month leap.” The historic piece is that the cost of contribution just dropped. A person who can specify a job and judge the output can now ship a reusable teammate. A person who can steer code can now run a desk that used to need a small staff. A person who can only talk can, as of this week on my own sites, publish, clear junk, flag updates, and hand off what they cannot finish — if they leave a receipt.

    The loop I keep repeating is not branded. It does not require this stack. A Google Sheet works. Notion works. Whatever you already use. Same mode we run across the operator stack.

    1. Attempt the task yourself. Your main system does as much as it can.
    2. When you hit a roadblock, do not spin noise building scaffolding. Document what you did and open a new task for whoever can finish it — another bot, a different system, or a human.
    3. Close your task with a link to the handoff. That is your receipt.
    4. Two statuses only: your task is done when it is handed off cleanly. The job is done when the receipt lands.

    Sometimes the best next actor is a human. That is not a failure. That is the system working. Get in the work, not just the ship.

    Giving is not enough. Pay has to follow artifacts.

    A commons needs three rails.

    THREE RAILS OF A COMMONS RAIL 1 Place to put work Cursor / Grok Bot EXISTS RAIL 2 Way to reuse it Official template marketplace EXISTS RAIL 3 Way to pay makers Official creator pay MISSING Pay for artifacts, not belonging.
    RailJobStatus on 5 Sep 2026
    1A place to put workExists — Cursor and Grok Bot
    2A way to reuse itExists — official template marketplace
    3A way to pay the people who made it usefulOfficially missing

    Until rail three exists, “common cause” is a feeling wearing a storefront. People will still publish. Some already do. Third parties are already charging for templates and agent teams on unofficial shelves. That is not SpaceXAI. Do not conflate the official marketplace with cut-taker shops or anything branded around an unrelated chain. The only official cash program that clearly exists in this neighborhood is security bounty work, which is not bot-building.

    If SpaceXAI — or a third party that respects the terms — ever builds the third rail, the design should be boring and strict:

    1. Pay for artifacts, not belonging. A template, an eval, a measured workflow, a verified savings report. Not a membership in the cause.
    2. Require proof the bot ran. Install counts without run logs are theater.
    3. Pay on install, accepted bounty, or measured outcome — and publish the rule so creators are not guessing.
    4. Keep human approval in the loop for irreversible actions. Haggle Bot’s stop-line is the right instinct. Never spend, sign, or send without a person. Copy that into every serious template.

    Compensation for connecting people and tools, building bots and workflows, and working with bots alongside the runtime — that is a coherent next design. It is not a current SpaceX program. Treat SpaceXAI as the runtime, not the church.

    The risks that ride along

    Platform capture. Your methods live on someone else’s computer. Training on user work without sharing upside is the default posture of this industry until a contract says otherwise.

    Unsafe third-party bots. A template that looks helpful and holds a login is a new class of supply-chain risk. Official terms reported around late August put the burden on creators to strip secrets and deny endorsement. Read them. Then assume a stranger’s bot will try something you did not expect.

    Model choice shrinking. OpenAI’s wind-down notice after the change of control is a reminder that the workbench you love can lose a model family because two companies cannot share a contract. Anthropic’s posture will be watched for the same reason. Plan as if the router gets thinner.

    Subscription churn. Bundles already moved twice in August. Heavy is not Ultra. Bot usage is not Grok usage. If you build a livelihood on a bundle, you are building on weather.

    Rhetoric. “Common cause” is a beautiful phrase. It is also how a storefront borrows moral language it has not funded. Push back on both “they are upskilling humanity on purpose” and “this is only a subscription trap.” The evidence supports a product-and-distribution play that can be used as a commons if builders — and, eventually, the company — install the missing pay rail.

    What to do this week

    If you write code: stay in Cursor. Publish the method, not just the repo. Rehearse locally. Promote to Grok Bot only after the pattern survives.

    If you cannot live in an IDE: open Grok Bot anyway. Give it one named job with a stop-line. Make it leave receipts on a board a human can see.

    If you already have a working bot: strip the secrets, write the anti-jobs in public language, and put a template on the official shelf for reach. Keep source and proof of work somewhere you control. Sell only where the terms allow.

    If you run a company: the Enterprise invite-without-a-seat is the quietest on-ramp in the stack. Use it to plug in the people who have judgment and no seat. Do not confuse access with apprenticeship. Assign Human Gate the way you assign budget authority.

    If you want to get paid: do not wait for a commons that has not been built. Ship artifacts with receipts. Price the work as work. The historic opportunity is real only for people who publish reusable methods.

    Close

    I still mean “get in the ship.” I mean it as an operator, not as a spokesman. The next 36 months will move whether or not anyone writes a pretty theory about them. Easier tools will pull more people onto the floor. Some of those people will become nodes. Some of the work will be taken from nodes that used to be paid.

    SpaceX bought the leading AI coding workbench and launched an agent layer and a template shelf. That is a real on-ramp for more people to do useful work with machines. The official project is to make Grok useful and commercially central. A human contribution economy only begins when shared bots are not just installable but payable.

    The on-ramp is real. The commons is unfinished. Get in the work.


    Start here — official doors, no affiliate

    Use the tools. Publish what breaks. Feed the useful methods back. That is the honest version of sending love to the companies we are building on.

    Will Tygart — Tygart Media. Written 5 September 2026 from the Command Center: Cursor as lead seat, Grok Bot as Chief of Staff, Notion as board, Slack as doorbell, Human Gate on send / post / pay. This essay does not speak for SpaceX, SpaceXAI, Cursor, xAI, X, or Tesla. We want those companies to succeed because we are building on the tools they ship.

  • Do Not Treat a $91 Restoration CPL as a Target. It Is a Proxy.

    Do Not Treat a $91 Restoration CPL as a Target. It Is a Proxy.

    Inspired by Revved Digital. Original report: Revved Digital 2026 Home Service Marketing Benchmark Report. This is a new Tygart article for restoration contractors. We kept the mechanism, added first-party field knowledge, and did not reprint the piece.

    The useful sentence in that report is the first one: benchmarks only work when clicks, leads, bookings, sold jobs, and customers stay separate. The table then shows restoration and water damage at an $8.33 CPC and $90.92 CPL. Those are LocaliQ Home & Home Improvement proxies, not a national restoration average. Roofing sits at $228 CPL with real trade data. Plumbing at $129. Treat the restoration row as context, not a quota.

    There is no credible nationwide LSA CPL, SEO price, website conversion rate, or review-count target across those nine trades. The honest public numbers that do transfer:

    • CallRail: 97% of homeowners say speed influences whom they hire. 41% of online-booked jobs arrive after hours.
    • ServiceTitan (2022, cross-trade): 42% typical call booking rate. Old, and not restoration-specific. Still a better reference than “we feel busy.”
    • Planning range of 5–10% of revenue is general small-business guidance, not a measured restoration average.

    Build the number backward. How many more losses can the crews take. What is allowable CAC from gross profit on water versus sewage versus fire. What is the real lead-to-customer rate on the night board. Fund channels from that. A shop spending 5% with a dead after-hours line wastes more than a shop spending 10% that answers.

    Compare your pin to the shops ranking for water in your city — count, recency, replies — not to a national review target that does not exist.

  • When LSAs Move Into Google Ads, a Sloppy Pin Can Pause Paid Water Leads

    When LSAs Move Into Google Ads, a Sloppy Pin Can Pause Paid Water Leads

    Inspired by Revved Digital. Original article: Local Services Ads Migration to Google Ads: What Contractors Need to Do Before August 2026. This is a new Tygart article for restoration contractors. We kept the mechanism, added first-party field knowledge, and did not reprint the piece.

    Google is moving Local Services Ads into Google Ads. The ads are not dying. Pay-per-lead stays. Search and Maps stay. What changes is the dashboard, the bidding, and the fact that the old reports will not come with you.

    First U.S. wave is August 2026 for listed home-service trades. Service-area businesses without a storefront are later in 2026. Restoration shops that live on LSAs should assume they are in that line and act before the 14-day email.

    What to do this week

    • Export 12 months: spend, charged leads, disputed leads, cost per lead, category, area. Owners need a sheet, not a login that is about to vanish.
    • Screenshot the current setup: budget, categories, areas, hours, who answers, who administers.
    • Split economics after migration. Water extract and sewage rebuild should not share one target CPA. Google is collapsing category targets into one campaign unless you separate them.
    • Lock who can edit the Google Business Profile. Name, address, hours, and primary category will sync into the paid campaign. A casual category tweak can pause ads for a verification window.
    • Plan two quiet weeks. Google says performance can wobble while the account settles. Compare against the export, not against Tuesday.

    Lead history and recordings move. The performance baseline does not. If you cannot say what a good water lead cost last winter, you will not know whether the new dashboard is worse or just different.

  • Write the Restoration Blog for the Noise in the Ceiling, Not the Service Menu

    Write the Restoration Blog for the Noise in the Ceiling, Not the Service Menu

    Inspired by Revved Digital. Original article: SEO for Contractors: The Complete 2026 Playbook. This is a new Tygart article for restoration contractors. We kept the mechanism, added first-party field knowledge, and did not reprint the piece.

    The playbook says contractors write about services and homeowners search problems. “Water heater making a banging noise.” Not “residential plumbing services.” Restoration does the same thing when the homepage only offers “full-service mitigation.”

    They type: ceiling dripping at 1 a.m. How long before mold after a flood. Will insurance cover a sewage backup. Can I stay in the house during dry-out. Those queries are already on the CSR log. Each one is a post with a local sentence, a real photo, and a link into the water, sewage, or mold page you want to rank.

    One good post a week beats a burst of picnic content. Compress the phone photos before they land on the page — unoptimized job shots are how contractor sites die on mobile. HTTPS, a sitemap in Search Console, LocalBusiness schema on the home page and Service schema on each loss type. None of that is fancy. All of it is how Google decides the shop is real.

    Review the same file monthly: GBP calls, top twenty service-plus-city queries in Search Console, which pages send organic traffic, which of those become tagged jobs. A page that sits for three months with no movement needs depth and internal links, not another agency reset.

  • Tag the Source on Every Water Call or You Cannot Spend Next Month

    Tag the Source on Every Water Call or You Cannot Spend Next Month

    Inspired by CustomerFlows. Original article: How to Track Marketing ROI as a Contractor (No Marketing Team). This is a new Tygart article for restoration contractors. We kept the mechanism, added first-party field knowledge, and did not reprint the piece.

    Most shops know what they spent on ads and what they invoiced. The gap between those two numbers is guesswork. The original system is three steps and does not need a marketing department: tag every lead, keep the tag until the job is won or lost, compare revenue and spend on the first of the month.

    Restoration sources worth a field

    • Google Ads / LSAs
    • Organic / Maps
    • Plumber or roofer referral
    • Adjuster or TPA
    • Property manager
    • Storm-lead vendor
    • Yard sign / truck wrap
    • “How did you hear about us?” when none of the above fire

    If the source is blank, the lead is unattributable. Unattributable leads make every channel look the same. A spreadsheet works until volume breaks it. A CRM is better because the tag has to survive from the night board to the invoice.

    ROI is (closed revenue minus spend) divided by spend, by source. The original example is the owner who almost killed direct mail because it felt expensive — it was the second-best channel. Restoration version: the plumber list looks free and the marketplace leads look busy. One of those is usually lying. Monthly, not yearly. Weather moves the numbers too fast for an annual glance.

    Clicks are not ROI. A $25 shared water lead that never books costs more than a $90 Maps call that becomes a sewage job. Cost per acquired customer is the number that should move the budget.

  • A City Page Is Not a Copied Homepage With the Town Name Swapped

    A City Page Is Not a Copied Homepage With the Town Name Swapped

    Inspired by Revved Digital. Original article: What Are Service Area Pages? A Local SEO Guide. This is a new Tygart article for restoration contractors. We kept the mechanism, added first-party field knowledge, and did not reprint the piece.

    A location page supports a real office and a Google pin people can visit. A service area page is for work you drive to. Restoration is almost always the second kind. Mixing them up is how shops either hide the warehouse address and disappear on Maps, or publish forty city URLs that are the same paragraph with “Tacoma” swapped for “Kent.”

    Google does not need a storefront in every suburb. It needs a page that could only have been written by someone who has pulled carpet there.

    What belongs on a restoration city page

    • H1 that is the service plus the city: “Emergency water extraction in [city].”
    • A drive-time sentence that is true. “From the [neighborhood] shop we are usually on site in 35 minutes.”
    • One real job: neighborhood, loss type, what the crew did. Photo if the homeowner allows.
    • Services you actually run in that city, including license limits.
    • Tap-to-call. Not a contact form buried under a map widget of a town you do not staff.

    Do not ship a page for a city you have never worked. Do not stuff the city name into every sentence. Do not treat fifty thin pages as fifty pins — the pin is still one profile. These URLs win organic “water damage in [city]” searches and give the homeowner a reason to believe you will show up.

  • How a Restoration Shop Actually Gets Into the Maps 3-Pack

    How a Restoration Shop Actually Gets Into the Maps 3-Pack

    Inspired by Revved Digital. Original article: How to Rank Your Plumbing Business Higher on Google Maps. This is a new Tygart article for restoration contractors. We kept the mechanism, added first-party field knowledge, and did not reprint the piece.

    A burst pipe at 9 p.m. is the plumber version. Standing water in the living room at 11 p.m. is ours. Both searches land on three pins with a tap-to-call button. If you are not in that pack, you are not in the race.

    Google still uses three factors. Relevance: does the profile match “emergency water extraction” or does it say Contractor. Distance: you cannot fake proximity, but you can list the cities you actually hit. Prominence: reviews, citations, branded search, a site that agrees with the pin. Once relevance and distance are good enough, prominence is the fight.

    The restoration version of the plumber checklist

    • Primary category Water Damage Restoration Company — not Contractor, not Home Improvement.
    • Services in the words they type: emergency water extraction, sewage backup cleanup, mold remediation, fire and smoke cleanup.
    • Service areas you can staff in 45 minutes. Twenty cities you never photograph will not help.
    • Hours that match the night board. 9–5 on a 24-hour shop is a closed sign.
    • Photos of trucks, containment, meters, the room after. Not a picnic.
    • NAP identical on the site, the pin, Apple, Yelp, BBB. “St.” versus “Street” still counts as drift.
    • Reviews every week. A pile from 2023 and silence since looks closed.
    • Reply to every review. Ignore a one-star mitigation complaint and the next homeowner reads that silence.

    Do not keyword-stuff the legal name. “Emergency Water Damage | 24/7 | Licensed” in the title is how profiles get suspended. Use the real name. Put the emergency language in services, description, and the page the pin points to.

    Sixty to ninety days is the honest window if the file starts messy. Fourth to third in a crowded market takes longer. Stopping the weekly work is how a shop falls out of the pack the week the weather finally turns.

  • Five Numbers Tell You If Restoration Marketing Is Working

    Five Numbers Tell You If Restoration Marketing Is Working

    Inspired by MassMonopoly. Original article: The Contractor Marketing Scorecard: 5 Numbers That Tell You If Your Ads Are Working. This is a new Tygart article for restoration contractors. We kept the mechanism, added first-party field knowledge, and did not reprint the piece.

    Most shops do not have a “no marketing” problem. They have a no-clarity problem. Ads, LSAs, the pin, a website from 2019, referrals from plumbers — when the board goes quiet everyone guesses. The original scorecard says you can run the company on five numbers: leads by source, cost per lead, booking rate, close rate, revenue per new job.

    How those five read on a water job

    • Leads by source. Maps, LSAs, plumber referral, adjuster, storm vendor, website form. If you cannot name the source, you cannot feed it.
    • CPL. Spend divided by leads. Cheap sewage-marketplace names are not cheap if three other trucks have the same address.
    • Booking rate. Qualified conversations that become a crew on site. This is where two-ring failures hide. Visibility looks fine. The night board leaked.
    • Close rate. On-site inspections that become authorized work. Weak close is a estimator and documentation problem, not an ads problem.
    • Revenue per new job. A $400 extract and a $14k sewage rebuild cannot share one “average ticket” if you are deciding what to spend to win the next one.

    Read the pattern, not one cell

    Leads down, CPL up, booking and close steady: visibility. Leads fine, booking weak: intake. Volume up, ticket down: you bought the wrong work. Do not kill SEO because Tuesday was dry. Do not buy more ads because the CSR lets forms sit until morning.

    Start with a sheet. Source, date, booked yes/no, closed yes/no, invoice. Split water, mold, and fire when you can. The five numbers are the implementation. The software can wait.

  • Mitigation and Rebuild Are Not Two Pins at the Same Warehouse

    Mitigation and Rebuild Are Not Two Pins at the Same Warehouse

    Inspired by Andrew Palacios and Revved Digital. Original article: Can You Have Two Businesses at the Same Address? Google’s 2025 Rules Explained. This is a new Tygart article for restoration contractors. We kept the mechanism, added first-party field knowledge, and did not reprint the piece.

    Google will let two businesses share an address when they are actually two businesses: separate legal entities, separate tax IDs, separate phones, separate staff, separate categories, signage a customer could find. A handyman who also does water heaters does not get a second pin. Fake suite numbers do not create a second address. Virtual offices do not count.

    Restoration shops try this constantly. One warehouse. Two listings: “ABC Water Mitigation” and “ABC Reconstruction.” Same trucks, same CSR, Suite B invented in the dashboard. That is two service lines under one company. Google’s version of that example is the handyman who wanted a pin for AC and a pin for water heaters.

    What actually qualifies

    • A legally separate rebuild company with its own EIN, phone, and crew — not a DBA on the same mitigation LLC.
    • A second market with a real office, real staff during posted hours, and reviews from that place.
    • Departments that the public can walk into as distinct operations. A warehouse aisle labeled Rebuild is not a Vision Center.

    Service-area businesses get watched harder. Two restoration listings from one hidden address, overlapping zips, same people answering both numbers, is how shops earn a hard suspension. The listing disappears. The reviews and photos go with it. Reinstatement is a request, not a right.

    Put water, mold, fire, and rebuild on one honest pin and on separate pages of one site. If you truly bought a second company, keep that company’s name and pin — that is a different article. Do not manufacture the second company in GBP.

  • Emergency Roof and Water Pages Can Move Before the Link Chart Looks Impressive

    Emergency Roof and Water Pages Can Move Before the Link Chart Looks Impressive

    Inspired by Georgian Bay SEO (@GeorgianBaySEO). Original posts: nine local trade sites in 38 days and emergency roof repair at position 16 on a July domain. This is a new Tygart article for restoration contractors. We kept the mechanism, added first-party field knowledge, and did not reprint the threads.

    The portfolio included roofing, waterproofing, and water damage restoration. Site one took weeks. Later sites shipped in a day because the templates and schema already existed. Five weeks in, an emergency roof query sat on page 2 with no link campaign.

    Restoration shops often do the reverse: wait to “do SEO” until someone sells them links, and never publish the sewage page. Emergency-intent URLs with real photos, local language, and schema can index while the domain is still new. Links help later. They are not the permission slip to put the page live.