Guarantee & help

Lifetime money-back, how to reach Jason, what's in scope and what's not, and the per-company license terms.

The guarantee

Lifetime money-back. No time limit, no forms, no questions.

If this Playbook doesn't deliver value — a skill doesn't work, the prompts are wrong for your data, the whole thing reads as too generic — email headstart@nunncurtislabs.com and we refund the full $497. There's no 30-day window, no "you used too much of it to qualify" clause. We'd rather build a long relationship than win one transaction.

The only thing not covered: if your business model fundamentally changes and the Playbook was built for the old shape (e.g., you bought it for a Marketing Analyst and pivoted to hire a Sales Engineer instead), we'll either rebuild the Playbook for the new role at no charge or refund the full amount — your call.

How to reach us

Email: headstart@nunncurtislabs.com

If a skill stops working, if a prompt produces garbage, if a screenshot in this Playbook is out of date because Anthropic or OpenAI shipped a UI change — email. We'll fix it and ship the updated version. Because the Playbook is hosted (not a PDF), the fix appears on your live page automatically.

Response time: within one business day — a real answer to the specific thing you asked, not a canned acknowledgement.

What's in scope

  • Every skill in this Playbook, working against current versions of Claude Sonnet 4.6 and GPT-5.5 (the May 2026 default models).
  • The install and how-to-use pages, kept current as Claude Desktop and OpenAI Codex evolve.
  • Email support for problems with any skill in this Playbook.
  • One full rebuild if your role, company, or data substantially changes within the first 12 months.

What's not in scope

  • Building new skills that aren't in this Playbook. We can do this on a separate engagement — see Implementation Services on the Headstart landing page for fixed-fee custom skill builds.
  • Replacing your existing analyst or specialist. The Playbook is a force multiplier, not a substitute. Every skill assumes a human owner who reviews the output before it ships.
  • Compliance review. Some skills monitor regulatory changes; that's research support, not legal counsel. Run anything regulatory-adjacent past your actual legal team before it leaves the building.
  • Custom integrations. The runtimes (Claude Desktop, OpenAI Codex) handle their own connections to Google Drive, OneDrive, Slack, Teams, SharePoint, Dropbox, etc. If you need a custom integration to a system that isn't on their supported lists, that's a separate engagement.
  • Migrating between runtimes. If you start on Claude Desktop and want to move every skill to Codex (or vice versa), that's a copy-paste exercise — happy to walk through it on a call, not part of the standard support scope.

License — sharing this Playbook

The license is per-company.

  • ✅ Share this Playbook with anyone at your company. Send your new hire the URL on day one.
  • ✅ Save the prompts into your team's password manager, Notion, or shared drive.
  • ✅ Quote from it internally — at QBRs, in onboarding docs, in board materials.
  • ❌ Republish it externally. Don't post it on a public website, in a newsletter, or on a marketing blog.
  • ❌ Resell it. Don't sell access to a peer at another company; that's their Playbook to buy.

If a peer at another mid-market manufacturer would benefit, the best favor you can do for both of us is point them at headstart.nunncurtislabs.com, not a copy of your Playbook. Theirs gets customized for their role, their company, their data — yours wasn't built for theirs and reading it would mostly mislead them.

What "support" actually looks like in practice

Three shapes most messages take:

  1. "Skill X stopped working — output got garbage in the last month." Send the message + the most recent input file (or a redacted version). Reply within a business day with a tightened prompt or a confirmation that the model regressed and we're working with Anthropic/OpenAI on it.
  2. "Our ERP export changed format." Send the old + new column headers. Reply within a business day with the patched prompt; we'll also update the canonical version on the Playbook so it's correct on your live page.
  3. "We'd like a new skill that isn't in here." That's a custom build, not support. Reply same day with a fixed-fee quote (typically $250–$1,500 depending on scope) or a "this would actually be a strong v1 standard skill — we'll add it for everyone at no charge to you" note.

Where to go next

  • Skills sidebar — start running.
  • Using a skill — the four-step pattern.
  • Scheduled tasks — make the high-cadence skills run themselves.