Frequently asked questions

The questions below are the ones we expect you'll have after opening the Playbook for the first time. If you don't see yours here, headstart@nunncurtislabs.com — an answer within a business day.

About this Playbook

What exactly is this Playbook?

It's a hosted mini-site built around one role at one company — yours. The Overview is custom to your hire. The Skills section is the bulk of it: one page per responsibility on your job description, each with a workflow you can run with real data. The standard reference pages (this one included) are shared verbatim across every Playbook we ship.

Why is it a hosted mini-site instead of a PDF?

Two reasons. First, the things that change — UI screenshots when the runtime vendors ship a redesign, prompts when a model update shifts behavior — change on the live page automatically. A PDF would be wrong inside a quarter. Second, sidebar navigation is the right shape for the way you'll actually use this: dip in to find one skill, run it, close the tab.

Who wrote the content I'm reading?

The standard reference pages (How to use, install guides, Using a skill, Scheduled tasks, Privacy & IT, Guarantee & help, this FAQ) are written by Jason at NunnCurtis Labs. The Overview, Skills, Rollout, This Week, and Tools sections are AI-generated for your specific role and company, built from the responsibilities in your own job posting.

That's deliberate, and it's why the turnaround is same-day rather than same-month. It's also why the guarantee has no time limit: if any part of this Playbook reads as generic or doesn't work against your data, email us and we refund the full $497 — see Guarantee & help.

How is this different from generic AI training material?

Training material teaches people how AI works. This Playbook hands you a working set of moves built around the exact responsibilities on your job description — paste, attach, ship the work. There's no curriculum to finish before you produce anything; the first skill you open is the first deliverable.

Using it day-to-day

I just opened this. Where should I start?

Start here is the top of the sidebar for a reason. Read it (five minutes), then read AI terminology (two minutes), then pick whichever install guide matches the runtime your company already pays for. After that, open one skill that maps to the most painful part of your current workload and run it once with real data. That's the proof.

Do I need to read the whole thing before my new hire arrives?

No. The Playbook is designed to be read in pieces, at the moment you need each piece. The only "before they arrive" reading is the Overview and What to do this week — together about fifteen minutes. The Skills section is for your hire to work through on their own time once they're in the seat.

Can I print it or export it to PDF?

Your browser's print-to-PDF works, but you'd be freezing a thing whose value is partly that it doesn't freeze. We'd rather you bookmarked the URL and let the live page stay current. If you have a hard requirement to keep an offline copy for a compliance or records reason, email us and we'll send a dated snapshot.

The sidebar order — is that the order I should read in?

Roughly, yes. Top-to-bottom matches the order most buyers find useful: orient, install, learn the skill pattern, then work the role-specific Skills. Rollout, This Week, and Tools are forward-looking — read them once the first skill is running. Privacy & IT and Guarantee & help are reference; read them when you have the question.

What if I haven't hired yet?

The Playbook is useful before the hire. Run the skills yourself — or hand them to whoever is covering the role today — and you'll have produced real deliverables before the new person walks in. When they do start, they load the same skills on day one and ramp on actual work, not on a curriculum.

Sharing it inside my company

Who at my company can I share this with?

Anyone. The license is per-company. Your hiring manager, your IT lead, the new hire themselves, the executive who signed off on the budget — send them the URL.

Can I forward the URL to my new hire on day one?

That's the intended use. Send it on day one with a note pointing at the Overview, the install guide for your standardized runtime, and Using a skill. They'll be running their first skill before lunch.

Can I copy sections into our internal wiki / Notion / SharePoint?

Yes. Quoting from the Playbook in onboarding docs, QBR slides, or board materials is fine and expected. The only thing we ask is that the canonical version stays live at your URL — when we update a prompt or a screenshot, that's where the fix lands. Copied-out snippets will drift.

Can I share it with a peer at another company?

The license is per-company, so no — your Playbook was built around your role, your company, your data, and sending it to a peer at another mid-market manufacturer would mostly mislead them. The best favor you can do for both of you is point them at headstart.nunncurtislabs.com and let them buy a version that's actually built for their shop. Full license terms are on Guarantee & help.

Updates and freshness

How often is this Playbook updated?

The standard reference pages get updated whenever the underlying tools change in a way that matters — typically every few months when the runtime vendors ship UI redesigns, or when a model update changes behavior enough that a prompt needs tightening. Your custom sections (Overview, Skills, Rollout, etc.) are frozen at delivery unless your role or data substantially changes; if that happens, we'll rebuild the affected sections at no charge for the first twelve months. Details on Guarantee & help.

Will my Playbook get out of date as AI models change?

The hosted format is exactly the answer to this. When the default model shifts and a prompt produces a different shape of output, we tighten the prompt and the live page updates. You don't have to re-buy anything. The only thing that ages out is the underlying role — if you pivot the job entirely, see the next question.

Will I be notified when the standard sections are updated?

Not by default — we don't want to be in your inbox unprompted. If you'd like a quarterly "here's what changed in the standard sections" note, reply to your delivery email asking to be on the changelog list and we'll add you.

What if a UI screenshot in here doesn't match what I see today?

Email us. That's the canonical case for a same-week fix — Anthropic, OpenAI, and Microsoft ship UI changes on their own schedule, and the screenshot in your Playbook is whatever was current when we last reviewed it. We'd rather you flag a single stale image than work around it.

Support, refund, and scope

What does "support" actually mean in practice?

Three shapes, all over email at headstart@nunncurtislabs.com:

1. Something stopped working — a skill that used to produce a clean output now produces garbage. Send the message plus the most recent input (or a redacted version). Reply within a business day.
2. Something in your data changed shape — an ERP export gained or lost a column, a CRM field got renamed. Send the old and new headers. Reply within a business day with the patched approach, plus an update to the canonical page.
3. You want a new skill that isn't in here. That's a custom build, not support. Reply same day with a fixed-fee quote.

Full detail on Guarantee & help.

How does the lifetime money-back guarantee work?

Lifetime. No time limit, no form, no questions. If this Playbook doesn't deliver value, email headstart@nunncurtislabs.com and the full $497 is refunded. You keep the deliverables. We'd rather build a long relationship than win one transaction.

What's outside the scope of what this Playbook covers?

Building new skills that aren't in here (separate engagement), replacing your existing analyst or specialist (the Playbook is a force multiplier, not a substitute), compliance review (research support is not legal counsel — run regulatory-adjacent work past your legal team), and custom integrations into systems the runtimes don't already support. The full in-scope/out-of-scope breakdown lives on Guarantee & help.

Can I hire you to do the rollout instead of doing it myself?

Yes. Implementation Services come in three tiers — Setup Assist, a 30/60/90 Co-build, and Fractional Marketing Ops — listed on the Headstart landing page. They are not part of the standard Playbook package; the Playbook is built to be self-serve and most buyers run it that way. The services are for teams who'd rather hand the rollout to someone who's done it before.

We changed direction and the role we're hiring for is now different — what now?

Within twelve months of delivery, we'll either rebuild the Playbook for the new role at no charge, or refund the full $497 — your call. After twelve months, the rebuild is available at our standard custom-build rate. Either way, email us; we'd rather rebuild than leave you with a Playbook for a role you're no longer filling.

Privacy and security

Is any of our data sent to OpenAI / Anthropic / Microsoft just because I opened this Playbook?

No. Opening the Playbook in your browser is a read-only page load from our hosting. Data only moves when you open a runtime — OpenAI, Anthropic, or Microsoft — and paste a workflow into it, and at that point the data flows under your existing agreement with that vendor, not ours.

Where can I find the full privacy/IT writeup?

See the Privacy & IT page, immediately below this one in the sidebar. It covers what data goes where, the per-vendor agreements that govern it, what your IT team will want to know before approval, and the answer to the "is it okay to paste customer data into this" question.