opencode-knowledge-work 0.0.0-stage → 0.1.0

package/content/small-business/skills/small-business-grant-rfp-writer/reference/opportunity_sources.md

@@ -0,0 +1,90 @@
+# Opportunity sources
+
+Where opportunities live, and how to filter a daily feed down to the few worth reading.
+
+---
+
+## Federal contracting
+
+**SAM.gov** — the central federal contract opportunity system. Search by NAICS, set-aside type, agency, place of performance, and posting date. Set-aside filters are the highest-value ones for a small business.
+
+**DLA DIBBS** — Defense Logistics Agency bid board. High volume, short turnarounds, largely commodity items. This is the feed behind a workflow of 50 bids a week in under two hours a day, and it only works because the filter is brutal and the qualification is fast.
+
+**Agency-specific portals** — several agencies post outside or ahead of SAM. Worth checking directly for the two or three agencies that matter to the organization.
+
+**Prime contractor subcontracting pages** — large primes carry small-business subcontracting obligations and publish opportunities. Consistently under-worked by small businesses, and often a better win rate than bidding prime.
+
+---
+
+## Grants
+
+**Grants.gov** — federal discretionary grants. Filter by eligibility category, CFDA or Assistance Listing number, and agency.
+
+**Agency grant pages and forecasts** — many agencies publish a forecast months before the notice. That lead time is worth more than anything else on this list, because it is the only way to prepare rather than react.
+
+**Foundation directories** — Candid and equivalents. Foundation 990s are public and show exactly who they funded, for how much, and for what. That is the highest-signal free research available in the nonprofit space.
+
+**State and municipal portals** — smaller, less competitive, and frequently a better fit for a small organization than federal money.
+
+**Corporate and community foundations** — local giving programs, often relationship-driven rather than competitive.
+
+---
+
+## Filtering a daily feed
+
+The whole point of a daily feed is that almost none of it is for you. Screen before anything reaches the owner.
+
+**The filter, in order — cheapest checks first:**
+
+1. **Eligibility category** — entity type, set-aside status. Kills most of the list instantly
+2. **NAICS or program area** — is this the work the organization does
+3. **Geography** — place of performance or service area
+4. **Dollar size** — against realistic capacity, both floor and ceiling
+5. **Deadline feasibility** — a good fit due in four days with a portal registration requirement is a no
+6. **Incumbent presence** — a recompete with a happy incumbent is usually a no
+
+**Report the counts.** The filter is only trusted if the owner can see what it threw away:
+
+```
+DIBBS, Jul 24: 312 solicitations
+  → 47 in your NAICS
+  → 19 small-business set-aside
+  → 11 within your size range
+  → 4 with feasible deadlines
+  → 2 recommended for full go/no-go review
+
+Cut for deadline: 5 (all due within 3 days)
+Cut for size: 8 (over USD 2M, above your bonding)
+```
+
+**Show the near-misses once a week, not daily.** Repeated patterns in what gets cut are strategic information — if bonding capacity is killing eight bids a week, that is a business decision worth raising, not just a filter statistic.
+
+---
+
+## The pipeline record
+
+Keep every opportunity ever touched, in one place, with a state:
+
+| State | Means |
+|---|---|
+| Watching | Forecast or anticipated, not yet posted |
+| Reviewing | Posted, go/no-go in progress |
+| Pursuing | Go decision made, drafting |
+| Submitted | In, with the submission date and confirmation |
+| Won | Awarded — post-award obligations now apply |
+| Lost | Not awarded, with the debrief if one was taken |
+| No-bid | Declined, with the reason |
+
+**The no-bid reasons are the most valuable column in the table.** Nearly every solicitation recurs annually, and next year's decision takes ninety seconds instead of an evening because the reasoning is already written down.
+
+**Take the debrief on federal losses.** It is usually available on request, most small businesses skip it, and it is the only place the actual scoring becomes visible.
+
+---
+
+## Frequency
+
+**Daily** for high-volume commodity feeds like DIBBS, where speed is the entire advantage.
+
+**Weekly** for grants and most contracting. Grant cycles are slow and a daily check finds nothing most days.
+
+**Forecast review quarterly.** Agency forecasts are how a small organization gets ahead of a solicitation instead of scrambling after it, and quarterly is enough to catch them.

package/content/small-business/skills/small-business-grant-rfp-writer/reference/org_profile.md

@@ -0,0 +1,81 @@
+# Organization profile
+
+Built once, read by every later step. Without it, every search is guesswork and every go/no-go is slow.
+
+---
+
+## What it holds
+
+**Identity and registration**
+
+| Field | Why it matters |
+|---|---|
+| Legal name and entity type | Eligibility turns on it constantly |
+| EIN | Required on nearly every application |
+| UEI (Unique Entity ID) | Mandatory for federal awards |
+| CAGE code | Federal contracting |
+| SAM.gov status and expiry | Expired registration is an instant disqualification |
+| State charity registration | Required in most states to solicit funds |
+| 501(c)(3) determination letter | Attached to nearly every foundation application |
+
+**Classification**
+
+NAICS codes for contracting, NTEE code for nonprofits, size standard against the relevant NAICS, and any set-aside certifications: 8(a), HUBZone, WOSB or EDWOSB, SDVOSB, minority-owned, state and local equivalents.
+
+**Certifications are the highest-leverage field in the profile.** They cut the eligible universe down to something a small organization can actually compete in, and set-aside solicitations are where the realistic wins live.
+
+**Capacity**
+
+Annual budget or revenue, staff count, service area, bonding capacity, insurance limits and carriers, audit status and most recent audit date, indirect cost rate and whether it is federally negotiated, and accounting system adequacy where a funder tests it.
+
+**Programs**
+
+Program areas with the outcome data behind each: who is served, how many, over what period, with what results. Real numbers with real sources.
+
+**People**
+
+Key staff with actual credentials, degrees, licenses, and years of experience. Board composition where funders ask for it.
+
+---
+
+## Past submissions — the real asset
+
+Past applications and proposals, won and lost, are the single most valuable input to every future draft.
+
+**Gather them** from Drive, M365, or uploads — from a store confirmed as the organization's, searched by its name, per `../../../shared/tenant-scope.md`. Index each one with: funder or agency, opportunity title and number, date, amount requested, outcome, and the score or debrief if there was one.
+
+**Extract the reusable pieces:**
+
+- Organizational background and history boilerplate
+- Program descriptions, by program
+- Staff bios
+- Past performance write-ups, by contract or grant
+- Logic models, theories of change, evaluation plans
+- Budget narratives and standard cost categories
+- Letters of support and who provided them
+
+**Losses are more instructive than wins.** A debrief that says the past performance section scored 12 of 40 tells you exactly what to rebuild, and most organizations file the loss and never read it again.
+
+---
+
+## Keeping it current
+
+The fields that expire will silently disqualify a submission if nobody watches them:
+
+- **SAM.gov registration** — annual renewal, and lapses are common
+- **State charity registrations** — annual, per state
+- **Insurance certificates** — annual
+- **Audit** — the most recent one, which funders date-check
+- **Certifications** — 8(a) has a nine-year term; HUBZone requires recertification
+
+Put each expiry on the calendar with at least 60 days of lead time. An expired SAM registration discovered on submission day has ended otherwise-winning bids.
+
+---
+
+## Two shapes of organization
+
+**The nonprofit.** Riverbend Literacy Council, a four-person nonprofit running adult reading programs. Profile is heavy on program outcomes, 501(c)(3) status, board composition, audit, and foundation relationships. The material that wins is outcome data and a credible theory of change.
+
+**The contractor.** Okonkwo Mechanical, bidding public-facility HVAC work. Profile is heavy on NAICS codes, bonding capacity, past performance on comparable contracts, licensed staff, and set-aside certifications. The material that wins is past performance on similar-size, similar-scope jobs.
+
+**The go/no-go differs sharply between them.** A nonprofit's hard stops are usually eligibility and geography. A contractor's are usually past performance thresholds and bonding. Build the profile knowing which one the organization is, because it determines which checks kill a bid fastest.

package/content/small-business/skills/small-business-grow-pipeline/SKILL.md

@@ -0,0 +1,92 @@
+---
+name: grow-pipeline
+description: Fills the funnel end to end without the owner babysitting it — reads the market and the competition for context, builds a ranked list of named prospects with a reason attached to each, writes personalized outreach in the owner's own voice, and logs every touch to the CRM. Chains lead-finder, outreach-composer, and crm-autopilot behind a web-native market read, with an owner approval at every handoff. Use this whenever the owner wants more pipeline rather than one specific piece of it, including phrasings like "I need more leads," "fill my funnel," "who should I be calling and what do I say," "find me customers like my best ones and reach out," "build me a prospect list and write the emails," or "sales has gone quiet, get something moving." Reach for it when the owner describes wanting new business generally rather than asking for a list or a single email.
+allowed-tools: Read, WebFetch
+---
+
+Run the pipeline-building chain: a web-native market read for context, then `lead-finder` for the list, `outreach-composer` for the copy, and `crm-autopilot` for the record. Each skill keeps its own gates, and this command does not loosen any of them.
+
+Connectors: Apollo (or Clay) plus HubSpot is the full path. Mail (Gmail or Microsoft 365) adds sending. Zoom adds recorded discovery and sales calls to Step 4's logging — read-only, only meetings the owner hosted or attended, and its recordings list covers a one-month window per call, so a sweep asks month by month rather than for a range it cannot return. With none of them, web research plus an uploaded customer CSV goes in, a ranked list and drafted outreach come out for the owner to send by hand, and the log lives in a spreadsheet. That is a real run.
+
+## Step 1 — Market context first (web research)
+
+Run this leg inline and keep it scoped to what informs targeting — not a full weekly brief. Scan public sources on the owner's competitors and their market: sites and pricing, ad and social activity, job postings, and press.
+
+**In:** the competitor watchlist if one exists, plus public sources. Win-loss data from HubSpot when connected, which is the sharpest signal available and is not public.
+
+**Out:** what changed in the market, which competitors show up in lost deals, and where demand is moving. Observed facts and inferences labeled separately, always.
+
+**Gate:** show the owner the read and ask whether it changes who to target. One question. If nothing material changed, say so in three lines and move on — a quiet market is a valid answer and does not stall the chain.
+
+## Step 2 — Build the list (lead-finder)
+
+Trigger the `lead-finder` skill workflow, carrying Step 1's context in as targeting input.
+
+**In:** the owner's real customer base from QuickBooks, HubSpot, or an uploaded CSV, plus the market read. The ideal customer profile is derived from who actually pays, never asked for in the abstract.
+
+**Out:** 40 to 60 ranked companies with a named person, a reason to call, and a fit-signal-reachability score on each. Inferred contacts marked as inferred.
+
+**Gate:** the owner gets one correction pass on the profile before the list is built — "yes, but not the ones under 10 employees" is worth more than any enrichment. Then they approve the list before any copy is written.
+
+**Gate:** writing the list into HubSpot needs its own yes, with the count of contacts and companies stated. Declining is fine; the XLSX is the deliverable.
+
+## Step 3 — Write the outreach (outreach-composer)
+
+Trigger the `outreach-composer` skill workflow against the approved list.
+
+**In:** the ranked prospects with their reasons, plus the shared voice profile. If no profile exists, it gets built from 15 to 30 of the owner's own sent messages before a word is written.
+
+**Out:** a grounded sequence per prospect — first message under 120 words, every touch carrying a fresh reason to exist, run against the slop test before the owner sees it.
+
+**Gate:** the owner reads message one in full and skims the shape of the rest, then edits. Expect edits. Every correction folds back into the voice profile so it does not have to be made twice.
+
+**Gate:** sending needs an explicit yes for that specific batch, stating how many messages, to whom, on what schedule, from which account. Approval for message one is not approval for the follow-ups — confirm those separately or leave them as drafts.
+
+**Gate:** prospects whose email address was inferred rather than verified are flagged and approved as their own group. Bounces at volume damage the owner's sending domain for months, and that damage reaches their real customer mail.
+
+Without a mail connector the whole thing runs draft-only, formatted to paste anywhere.
+
+## Step 4 — Log it (crm-autopilot)
+
+Trigger the `crm-autopilot` skill workflow in log mode.
+
+**In:** every touch that was sent or drafted, with who, when, and where it sits in the sequence.
+
+**Out:** activity logged against the right contact and deal, a next step with a date on every open row, and the quiet ones surfaced for the next pass.
+
+**Gate:** CRM writes are approved. Contact creation is announced before it happens. Deal stage and amount are proposed, never written. Nothing is ever deleted.
+
+Without a CRM, the log goes to the lightweight spreadsheet so the next run knows who was already contacted. Contacting someone twice with the same opener is a visible, avoidable mistake.
+
+## Approval gates (must hold)
+
+- No outreach sends without an explicit batch approval — drafts until then.
+- Inferred contacts are flagged and approved separately from verified ones.
+- No CRM write without a yes, and no deal created unprompted.
+- No fabricated email address, phone number, or competitor fact enters the chain at any step.
+- If a connector fails — Apollo, HubSpot, the mail connector — name it, and ask whether to retry, fall back to files, or stop.
+
+## What not to do
+
+- **Do not skip the market step to get to the list faster.** It is what makes the reasons on each row specific instead of generic.
+- **Do not pad the list.** Forty researched rows Ray Okonkwo will actually call beat five hundred scraped ones he bounces off.
+- **Do not merge a company name into a template and call it personalized.** If the message could go to anyone with two words changed, it is not ready.
+- **Do not treat one approval as approval for the chain.** The list, the copy, the send, and the CRM write are four separate decisions.
+- **Do not send to inferred addresses in the same batch as verified ones.**
+- **Do not treat missing Apollo as a blocker.** Web research plus a customer export is a designed path.
+
+## Output
+
+**Deliver the pipeline package per the owner's stored output preference — never default to a markdown file.** Check the `## Business context` block's `Output preference` (shared style guide rule, `../../shared/artifact-style.md`):
+
+- **Visual artifact (the default):** render the run as an HTML page in the house style — prospects found, drafted, and sent as stat tiles, the list as rows with each row's reason, and an inferred-contact pill where one applies. **Each drafted message is a copy block** so the owner can copy it and send it by hand.
+- **docx / md / notion / canva preference:** deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why.
+- **Best for skill:** use the visual artifact — this output is a list the owner works from, not prose.
+
+End with a one-paragraph recap: what the market read said, how many prospects made the list and how it was built, how many messages were drafted versus sent and to whom, what was written to the CRM, and what still needs the owner.
+
+Then one short close: the funnel is filled and every touch is logged. The natural next step is "leads are going cold" — `speed-to-lead` catches the replies and new inbound this outreach generates before they cool. Also nearby: "win back quiet customers" (`/reactivate`) for the customers already lost, and "is my marketing working" (`growth-pulse`) to see whether the pipeline push shows up in the numbers. Offer at most three, and skip any offer the owner already declined this session.
+
+## Using a tool that isn't listed
+
+The connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer `build-connector` — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.

package/content/small-business/skills/small-business-growth-pulse/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: growth-pulse
+description: >
+  Answers one question for an SMB owner — is the growth engine actually working?
+  Pulls sales trend by channel, funnel conversion, campaign return, best and
+  worst performing products, and customer sentiment from whatever is connected,
+  then ends with the three growth actions worth taking this week. The growth-side
+  twin of business-pulse, which covers the finance side. Use this whenever the
+  owner asks how marketing or sales is performing, whether a campaign paid off,
+  where leads are coming from, why the pipeline is stalling, which products are
+  moving, or says anything like "is my marketing working," "growth check,"
+  "how's the funnel," or "where should I put my money next month." Reach for it
+  even when the owner names a single channel rather than growth overall.
+allowed-tools: Read, WebFetch
+---
+
+# Growth Pulse
+
+One page that answers whether the growth engine is working, and what to do about it this week.
+
+Owners describe pulling numbers from three dashboards and trying to find the story themselves. The story is the deliverable here — not the dashboards.
+
+## Step 1 — Pull everything in parallel
+
+Dispatch all connector calls in a single batch. See `reference/data_sources.md` for the metric-to-tool mapping. Serial pulls turn this into a wait nobody sits through twice.
+
+- **HubSpot** — deals by stage, new contacts, lead source, win rate, cycle time, stalled deals
+- **PayPal, Stripe, Square** — revenue trend, transaction counts, refunds
+- **Shopify** — orders, SKU-level revenue, repeat purchase rate
+- **QuickBooks** — realized revenue, the number the books agree with
+- **TikTok Ads** — last week's spend, impressions, clicks, results, and cost per result per campaign, from the native connector (`report_integrated_get`, last 7 days against the prior 7), so paid spend sits beside the sales it claims to drive
+- **Mailchimp** — campaign, e-commerce, and audience-growth analytics, with revenue attribution on campaigns
+- **Gmail or Microsoft 365** — inbound inquiry volume and response times
+- **Public reviews** — recent ratings and review text, via web research
+
+If a source errors or is missing, record it and move on. This skill is designed to say something useful on one connector and something excellent on six.
+
+**Zero connectors is a supported path.** Ask for exports — a CRM deal export, a sales report, an ads performance CSV — and build the same pulse from files. Say it plainly rather than stalling.
+
+## Step 2 — Compute the five views
+
+Read `reference/thresholds.md` for the cutoffs. Compute each view and assign it a status.
+
+1. **Channel trend** — revenue by channel this period versus last, and versus the same period last year where available
+2. **Funnel conversion** — leads in, qualified, opportunities, won; the conversion rate between each step and where the biggest drop-off sits
+3. **Campaign return** — spend versus attributed revenue per campaign, and cost per lead
+4. **Product performance** — top three and bottom three by revenue and by growth rate
+5. **Customer sentiment** — recent review scores, review themes, disputes, churn signals
+
+A view with no data gets marked "n/a" and named in the appendix. It does not silently vanish.
+
+## Step 3 — Find the actual story
+
+This is where the skill earns its keep. Five views on their own are still a dashboard. The job is to connect them.
+
+The connections that matter most:
+
+- **Spend rising while cost per lead rises** means the channel is saturating, not scaling
+- **Strong lead volume with falling win rate** points at lead quality or response speed, not at marketing
+- **One product carrying the whole trend** means the growth is more fragile than the total suggests
+- **Sentiment dropping while revenue holds** is the early warning that shows up in revenue two months later
+- **A stage where the funnel drops off sharply** is usually worth more than any new campaign
+
+Look for the single sentence that explains the period. Lead with it.
+
+## Step 4 — Write the three actions
+
+Every pulse ends with exactly three actions. Not five, not a list of everything noticed.
+
+Each action needs three things or it isn't an action:
+
+- **What to do** — specific enough to start today
+- **Why** — the number from this pulse that justifies it
+- **What it's worth** — the rough size of the opportunity or the risk
+
+Rank them by size of impact, not by ease. Owners can decide what's easy; only this pulse can tell them what's big.
+
+If the honest answer is that nothing needs to change, say that. A pulse that manufactures three actions every week trains the owner to ignore them.
+
+## Step 5 — Compose
+
+Use the exact structure in `reference/output_template.md`. Include only sections with real data.
+
+Writing rules:
+
+- Numbers lead, words follow. Not "paid social performed well" — "paid social drove 41 leads at USD 18 each, down from USD 31 last month."
+- Every number carries its comparison. A figure with no baseline is a missed insight.
+- Name the specific campaign, product, channel, or customer. "Some campaigns underperformed" is unusable.
+- No marketing vocabulary the owner doesn't use. Not "top of funnel velocity" — "how many new leads came in and how fast."
+- If a section has nothing worth saying, write "No material change" and move on.
+
+## Step 6 — Deliver the pulse page
+
+Alongside the chat pulse — additive, never a replacement — deliver the full pulse per the owner's stored output preference — never default to a markdown file. Check the `## Business context` block's `Output preference` (shared style guide rule, `../../shared/artifact-style.md`):
+
+- **Visual artifact (the default):** render the pulse as an HTML page in the house style. Each of the five views gets a panel; revenue trend, cost per lead, and win rate are stat tiles with their comparison as the context line; campaign return and product performance are tables with tabular-nums spend and revenue columns; each view's status becomes a status pill (good, warn, critical, or n/a in plain text); the three actions close the page in their own panel, ranked.
+- **docx / md / notion / canva preference:** deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why.
+- **Best for skill:** use the visual artifact — five views compare best side by side on one screen.
+
+## Step 7 — Offer to save, once
+
+After presenting, offer once to save the pulse as a file or post it to Slack. Posting to Slack is an outward write, so it only happens on that explicit yes — the offer is the approval gate. If yes, do it. If no or no response, move on. Do not ask twice.
+
+Then close with what the pulse found in one line, plus the single most relevant next step and at most two others nearby:
+
+- If the actions point at content or promotion: "what should I promote" runs `content-strategy`.
+- If the funnel is the problem: "fill my funnel" runs `/grow-pipeline`.
+- For the finance-side twin: "how's the business doing" runs `business-pulse`.
+
+Max three offers. Never repeat an offer the owner declined this session.
+
+## Scope variants
+
+Owners often want a slice rather than the whole pulse:
+
+- **"How did the campaign do"** — campaign return only, plus the sentiment check
+- **"How's the pipeline"** — funnel conversion and stalled deals only
+- **"What's selling"** — product performance only
+- **"Are we getting reviews"** — sentiment only
+- **"Where should I spend next month"** — channel trend and campaign return, with the three actions weighted toward budget
+
+Give them the slice they asked for. Don't force the full pulse on a narrow question.
+
+## What not to do
+
+- **Do not ask permission before pulling data.** The skill was invoked. Run it.
+- **Do not invent attribution.** If a campaign's revenue can't be traced, say the attribution is unavailable rather than assigning revenue on a guess. Fake attribution has moved real budgets.
+- **Do not report CRM forecast value as revenue.** Deal values are hopes; invoices are facts. Label which is which.
+- **Do not double-count across sources.** A Shopify order settled in Stripe is one sale. Pick one revenue source and name it.
+- **Do not double-count inside one source.** The sales-by-customer summary returns both a parent summary row and a separate total row for the same customer. Filter rows marked as totals before you rank customers or compute concentration, or the same customer lands in the list twice and the concentration figure comes out too high.
+- **Do not manufacture urgency.** If growth is steady, the pulse should read as steady.
+- **Do not read expenses or margin from the QuickBooks P&L summary.** Total the rows (`../../shared/quickbooks-report-traps.md`, Trap 2).
+
+## Reference files
+
+- `reference/data_sources.md` — connector to metric mapping, with fallbacks
+- `reference/thresholds.md` — status cutoffs for each of the five views
+- `reference/output_template.md` — exact output structure
+- `reference/gotchas.md` — the failure modes that produce confidently wrong growth advice
+
+## Using a tool that isn't listed
+
+The connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer `build-connector` — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.

package/content/small-business/skills/small-business-growth-pulse/reference/data_sources.md

@@ -0,0 +1,113 @@
+# Data Sources
+
+Which connector answers which part of the pulse. Pull in one parallel batch.
+
+---
+
+## HubSpot — the funnel
+
+The spine of this skill. Without it, funnel conversion is unavailable and the pulse leans on revenue trend instead.
+
+| View | What to pull |
+|---|---|
+| Funnel conversion | Deals by stage, with create and close dates |
+| Lead volume | Contacts created in period, with source property |
+| Lead source mix | Contacts grouped by original source |
+| Win rate | Deals closed-won divided by deals resolved |
+| Cycle time | Median days from create to close, won deals only |
+| Stalled deals | Deals with no activity in 14+ days, or close date in the past and still open |
+| Response speed | Time from contact creation to first logged activity |
+
+**Careful with deal value.** It is a forecast, not revenue. Never present weighted pipeline as money earned.
+
+**Fallback:** a CRM deal export as CSV gives the same funnel views.
+
+---
+
+## Revenue sources
+
+| Source | Best for |
+|---|---|
+| QuickBooks | Realized revenue — the number that ties to the books |
+| Stripe, PayPal | Settlement timing, fees, refunds, subscription revenue |
+| Square | In-person and per-location revenue |
+| Shopify | Order counts, SKU-level revenue, repeat purchase rate |
+
+**Pick one as the revenue source per pulse and say which.** When QuickBooks is connected, it wins — processors and storefronts then supply channel and product splits only. Summing across them double-counts, sometimes by more than double.
+
+**Then guard against double-counting inside that one source.** The QuickBooks sales-by-customer summary emits a parent summary row and a separate total row for the same customer whenever sub-customers or jobs exist. Both carry the same amount, and the report's own top-customer list contains both. Filter rows whose metadata type marks them as a total before ranking customers or computing concentration; otherwise one customer occupies two slots in the ranking and the concentration figure is inflated.
+
+---
+
+## Ad platforms
+
+| Source | What to pull |
+|---|---|
+| TikTok Ads | Native connector. `report_integrated_get` at campaign level for the last 7 days and the prior 7: spend, impressions, clicks, results, cost per result. `advertiser_info_get` first to confirm the account. Same reads and traps as `ad-manager` (`../../ad-manager/SKILL.md`); read there before the first call |
+| Google Ads | Not wired into this skill — ask for a CSV export. The connector itself lives on `ad-manager` |
+
+**Attribution honesty.** Ad platforms report conversions they claim. The CRM reports leads it received. These rarely agree, and the gap is not a bug. Report both and name the gap rather than picking the flattering one.
+
+---
+
+## Mailchimp — email as a channel
+
+| View | What to pull |
+|---|---|
+| Campaign return | Campaign analytics with revenue attribution — opens, clicks, and attributed revenue per campaign |
+| Channel trend | E-commerce analytics, for the email-attributed slice of revenue |
+| Lead volume | Audience-growth analytics — subscribers added and lost in the period |
+
+**Same attribution honesty applies.** Mailchimp's attributed revenue is Mailchimp's claim,
+sitting next to the ad platform's claim and the CRM's record. Report it as the email
+channel's own number and name the gap. Never fold it into a single blended figure.
+
+**Mailchimp is read-and-draft only in this plugin.** It has no send path here, and its
+campaign planner will refuse a single-campaign request — it produces multi-channel plans
+only. Treat the audience list itself as unavailable for export unless a call actually
+returns it.
+
+**An auth or login error is connector health, not missing data.** If Mailchimp calls fail
+with an expired login or authorization error, the appendix line should say "Mailchimp:
+connection needs to be re-authorized — reconnect it in Connectors and rerun," not "no
+email data." Name the fix, then continue the pulse without the email views. Before
+writing that line, check the error did not come from the plugin's own registration
+(`small-business:intuit-mailchimp`, the manifest key) while the owner's Mailchimp entry is live — if the owner's
+entry works, use it and say nothing about reconnecting
+(`../../../shared/connector-neutrality.md`, "One connector, two registrations").
+
+---
+
+## Sentiment
+
+| Source | What to pull |
+|---|---|
+| Public reviews | Recent Google, Yelp, and industry-site reviews via web research |
+| PayPal, Stripe | Dispute and chargeback counts and reasons |
+| Gmail or Microsoft 365 | Inbound complaints, cancellation requests, refund asks |
+| HubSpot | Ticket volume and themes, if support runs through the CRM |
+
+Sentiment is the leading indicator in this pulse. It moves before revenue does, which is exactly what makes it worth including.
+
+---
+
+## The uploaded-file path
+
+A first-class mode, not a degraded one. Many owners in this segment have no clean connector on the growth side at all.
+
+What to ask for, in plain language:
+
+- "Export your deals from the CRM" — funnel conversion
+- "Export your sales report for the month" — channel and product performance
+- "Download the campaign performance CSV from Ads Manager" — campaign return
+- "Paste in your recent reviews" — sentiment
+
+Read the header row, map the columns, and build the identical pulse. If a needed column is absent, name it — "there's no source column, so I can't break leads out by channel" — rather than quietly dropping the view.
+
+---
+
+## Parallel-pull rule
+
+Every call goes out in one batch. This pulse routinely touches five or six systems.
+
+Record failures internally and list them once in the appendix. Never surface a connector error in the middle of the brief — the owner asked about growth, not about integrations.