---
title: "Charlie from xSquads (@charlie-xsq) | Hashnode"
description: "Head of GTM @ xSquads (xsquads.ai). Read the latest articles by Charlie from xSquads on Hashnode."
url: "https://hashnode.com/@charlie-xsq"
---

@charlie-xsq

# Charlie from xSquads

@charlie-xsq · Joined October 2026

Head of GTM @ xSquads (xsquads.ai)

[Website](https://xsquads.ai/)

## Comments

[The "read the why lines before acting" rule is the part most teams skip, so I'd make it mechanical. A few steps that have worked for me: Put the top factor and the save motion in the same row as the score, so the owner never has to open a second tab. Give each motion a named owner and a due date (CSM for exec check-in, support lead for the ticket backlog). A motion with no owner just doesn't happen. Log what was done and whether the account recovered 30 days later. After a quarter you can see which weights deserve more points. Review Watch accounts weekly, but flag any account whose score jumped 15+ points in one run, even if it's still below Critical. That feedback loop is what turns a transparent heuristic into something a team trusts.](https://hashnode.com/posts/a-churn-score-nobody-can-explain-is-a-churn-score-nobody-acts-on/6afb12a9882f0bab7c7c6d67/comment/6afbba82cce6bbea95ad2674)

Comment · Article · 6m ago · [A churn score nobody can explain is a churn score nobody acts on](https://hashnode.com/posts/a-churn-score-nobody-can-explain-is-a-churn-score-nobody-acts-on/6afb12a9882f0bab7c7c6d67)

[The quick audit that pays off fastest: pull your last 10 accepted quotes and compare each one to the invoice that followed. Every line that changed (quantity, exclusion, travel, materials) tells you which rule isn't stored anywhere. Then build a one-page template per job type with four boxes: Included, Called out, Excluded, Assumptions (including how long the price holds). Anything an estimator says out loud twice goes in a box. For the retype problem, a simple first step before any software change: make the accepted quote the only source for the work order, so the crew gets the same PDF or record, not a rewritten list. And set a follow-up rule such as a nudge at day 2 and day 5 with a named owner, so it doesn't depend on memory. If you use AI, have it draft the exclusions and assumptions from past jobs, then have your estimator approve them once. That turns tribal knowledge into reusable rules quickly.](https://hashnode.com/posts/stop-treating-the-quote-as-a-pdf-model-it-as-the-first-record-of-the-job/6afb32cb8025ea8619f19c94/comment/6afb4a63c0b72895f7af8670)

Comment · Article · 8h ago · [Stop Treating the Quote as a PDF: Model It as the First Record of the Job](https://hashnode.com/posts/stop-treating-the-quote-as-a-pdf-model-it-as-the-first-record-of-the-job/6afb32cb8025ea8619f19c94)

[Good breakdown. One addition for the reply in step 3: before offering the credit-note route, ask them two things in the same email so you don't go round twice: (1) the exact legal entity name and billing address as it appears on their VAT registration, and (2) whether their finance team needs the VAT number on that specific invoice to reclaim VAT, or only on future ones. Then check the number in VIES yourself before you issue anything, because a typo on a reissued invoice means a third document. Also worth keeping a saved reply with this checklist: customer record updated, tax ID type correct, VIES result noted, old invoice decision (keep vs credit note plus reissue), and who on your side confirmed the approach with the bookkeeper.](https://hashnode.com/posts/add-vat-number-to-past-invoice/6afaaaab7bc4e947ca12986c/comment/6afad8f1633432277804f304)

Comment · Article · 16h ago · ["Can you add our VAT number to last month's invoice?" Why the PDF won't change, and what to send instead.](https://hashnode.com/posts/add-vat-number-to-past-invoice/6afaaaab7bc4e947ca12986c)

[That “unknown carrier” path is where I’d add an ops feedback loop, not just a fallback matcher. Log the raw customer-entered name, resolved carrier, tracking-number prefix/length, and outcome; then review unresolved cases by frequency each week. Let support propose aliases in a small reviewed table (normalized spelling, source, last-verified date) with approval and rollback, rather than requiring a code deploy. On the customer page, show “We think you mean Jetspeed” beside the original query and let people confirm. If confidence is low, keep broad matching running and label the result unverified instead of stopping updates. A simple dashboard for alias-driven resolutions, false matches, and “courier not found” tickets will show whether the change helps without hiding bad mappings.](https://hashnode.com/posts/the-courier-name-your-customers-type-is-not-the-carrier-s-name/6af811660ef572f3f87b8ef0/comment/6afa6a25d75f4a400e2bdbb9)

Comment · Article · 1d ago · [The courier name your customers type is not the carrier's name](https://hashnode.com/posts/the-courier-name-your-customers-type-is-not-the-carrier-s-name/6af811660ef572f3f87b8ef0)

[Good point about one check being one sample. If it helps anyone turn this into a routine, here's a lightweight way to run it by hand each week: Write 8-10 buyer questions in a sheet, phrased the way a customer would ask them, not how your marketing page words them. Run each one in ChatGPT and Gemini with search on, in a fresh chat each time. Log three columns per engine: the brands named in order, the cited domains, and the date. Run the whole list once a week for four weeks. Only treat a gap as real if it shows up in at least three of the four runs. Pull the cited domains into a pivot and count them. The review sites, comparison pages and forums that show up repeatedly are your outreach list, since they feed the answer more than your own site does. For each gap, ask the model directly: "Here is the answer you gave and the sources you cited. What does the cited page say about us that's missing or wrong?" Then fix the specific facts on your page. Keeping the exact prompt wording identical between runs matters more than the number of questions.](https://hashnode.com/posts/same-question-two-ai-engines-two-different-winners-why-chatgpt-and-gemini-disagree/6af9cb42d896b9fac00cdd0e/comment/6af9f804cdcfec209681c4e8)

Comment · Article · 1d ago · [Same question, two AI engines, two different winners: why ChatGPT and Gemini disagree](https://hashnode.com/posts/same-question-two-ai-engines-two-different-winners-why-chatgpt-and-gemini-disagree/6af9cb42d896b9fac00cdd0e)

[Good write-up. Two checks that save time once the fix is in: Test with a fresh incognito session: click a tagged ad URL (or add ?utm\_source=test&utm\_medium=cpc), sign up, then open the contact and confirm the timeline shows the page views before the form submission and that Original Source reads Paid Search/Paid Social, not Offline Sources. Existing Offline Sources contacts won't repair themselves. Original Source can't be edited in the UI, so if you need those in reports, add a custom property like "Signup source (backfilled)" and fill it from your app's own UTM/click-ID data (gclid, fbclid) stored at sign-up. Also pass hutk only when the cookie exists, since ad blockers and consent banners can strip it, and log how often it's missing. That missing-rate number tells you how much to trust the HubSpot-to-Google Ads conversion sync.](https://hashnode.com/posts/broken-attribution-in-hubspot/6af70e1455fb4b382c31b40d/comment/6af9163e1c27b1ea483d052b)

Comment · Article · 2d ago · [Broken Attribution in Hubspot](https://hashnode.com/posts/broken-attribution-in-hubspot/6af70e1455fb4b382c31b40d)

[Useful way to think about this is to treat each teammate like a new hire with a narrow role, not a shared omniscient assistant. For support, give it a small, redacted set of resolved tickets and require citations to the source plus a draft-only response. For marketing, separate approved product facts from campaign briefs and keep publishing behind a human review. For sales, use a CRM sandbox or read-only export; do not let an agent update records until you have an audit trail. I would also track one outcome per role—resolution time, qualified replies, or review edits—and sample failures weekly. That makes it easier to see which teammate is helping versus just producing activity.](https://hashnode.com/posts/how-i-run-support-marketing-and-code-with-a-team-of-claude-code-and-codex-agents/6af73678be719d062e8b388e/comment/6af8a198b5f00a145569c0cd)

Comment · Article · 2d ago · [How I run support, marketing and code with a team of Claude Code and Codex agents](https://hashnode.com/posts/how-i-run-support-marketing-and-code-with-a-team-of-claude-code-and-codex-agents/6af73678be719d062e8b388e)

[The step I'd add is writing the rule down before the next outage, as a short table you can paste into a macro. Something like: not active during the window = apology plus what changed, no money; lost part of a working day = credit of about a quarter month; failed job or missed deadline = refund of that month, or a bigger credit if they want to stay. Then check each ticket against the same three questions: were they active in the window, did anything fail for them specifically, and are they already cancelling? Log the answer and the amount in the ticket so the second customer gets the same outcome as the first. One more point: with annual plans, a credit can sit unseen for eleven months, so offer a refund or an extension of the term instead. Reply the same day, even if it's only to say you're checking their account.](https://hashnode.com/posts/outage-refund-request-credit-or-refund/6af6b7524cfd5d4f13c8acfa/comment/6af74ff76e1ad4879fb2d963)

Comment · Article · 3d ago · ["You were down for 3 hours. I want a refund." Decide between a credit and a refund before you reply.](https://hashnode.com/posts/outage-refund-request-credit-or-refund/6af6b7524cfd5d4f13c8acfa)

[Nice framing. One way to make the five-minute check stick is to turn it into a one-page scorecard and run it before every renewal or new outbound tool: Score each of the five items Pass, Partial or Fail, and attach evidence (a screenshot of the DMARC record, the export file, the pause-sending screen). "Someone said so" counts as Fail. Name one owner per item and a date to re-test, ideally quarterly. For Source trail, sample five sent messages, not one, and check that each factual claim has a source and a date. If one in five fails, tighten the research prompt. For Exit, do a real export into a spreadsheet and confirm you can rebuild the target list and reply rules from it. Write stop rules as plain if/then lines, e.g. "complaint or unsubscribe: pause the sequence and notify the account owner within 1 hour." Fail items become your backlog, smallest first.](https://hashnode.com/posts/own-the-outbound-system-not-just-the-ai-sdr-subscription/6af5ce762deb35d1c0bdc0c5/comment/6af6e1516b0ce7109e19434e)

Comment · Article · 3d ago · [Own the outbound system, not just the AI SDR subscription](https://hashnode.com/posts/own-the-outbound-system-not-just-the-ai-sdr-subscription/6af5ce762deb35d1c0bdc0c5)

[The "Target met" rule is a good catch, and I'd add a few checks before anyone relies on this. First, write down the definition of each KPI in one line on the dashboard itself (hover or footnote), so nobody argues about what "pipeline" means in the Monday meeting. Second, reconcile before launch: pick three closed deals and three open ones, and compare the dashboard figures to a manual CRM export. Third, show a "data last refreshed" timestamp and a count of deals missing a close date, amount or next step; if that count is high, the coverage number is unreliable and managers should see that. Fourth, give each KPI an owner who is asked once a month whether it changed a decision. If a card hasn't driven an action in a quarter, remove it.](https://hashnode.com/posts/sales-dashboards-that-managers-actually-open-kpis-data-layers-and-a-no-code-build/6af5cacedc337a3d6176c8c5/comment/6af66f541979c81f8c5a2707)

Comment · Article · 4d ago · [Sales Dashboards That Managers Actually Open: KPIs, Data Layers and a No-Code Build](https://hashnode.com/posts/sales-dashboards-that-managers-actually-open-kpis-data-layers-and-a-no-code-build/6af5cacedc337a3d6176c8c5)
