A calmer start.
One step at a time.

Use your system in Notion first. Then add an assistant if it makes your workflow easier.

Duplicate the whole system.

Once purchasing opens, use the duplication link delivered through your Gumroad purchase. Sign in to your own Notion account and duplicate the complete product root, including its source databases.

  1. Open the duplicated root and its Start Here guide.
  2. Check that related databases belong to your copy, rather than the seller’s workspace.
  3. Create one fictional sample record with an obvious DEMO name.
  4. Check its linked view. Review sample rows before removing only those rows.
  5. Keep database properties, relations, rollups and formulas intact.

Widgets need their own setup. Duplicating Notion copies embed URLs, not widget ownership. Follow “Make these widgets yours.” Widget activity does not update the Notion databases.

Authorize your own connection.

ChatGPT

Find Notion in the apps or plugins available in your settings. Connect your account, review the authorization and select the workspace containing your copy. Ask it to find your product by title. Check whether creation and update actions are offered before trying a write.

Follow OpenAI’s current connection instructions. Labels and availability may differ by account.

Claude

Add the official Notion connector and complete its authorization. The hosted MCP endpoint is https://mcp.notion.com/mcp. Confirm available tools and workspace access. This is documented guidance; a Claude-specific live workflow was not tested here.

Other assistants

Check Notion’s MCP setup guide and your client’s supported connection method. Use an official authorization flow. Never share passwords or privileged keys with Launchist.

Find my duplicated Launchist system by the title and page link I provide. Confirm which workspace and page you can access. List the read and write actions available through this connection. Do not create, change, move or delete anything yet.

Try one disposable record.

Ask the assistant to inspect the schema. Use a clear DEMO name, confirm the intended calendar date and timezone, review the destination, then create one record. Ask it to return the record link and read the saved fields back.

If your connection supports updates, change the test record’s status to the exact completion value in that database. Verify it in Notion. Remove only your test record when you are finished.

Start with low-stakes tasks. Check dates, relation targets and financial inputs yourself. Approval behavior depends on the assistant and workspace settings.

Prompts that know the structure.

These examples use inspected property names. Replace the product reference with your own copy’s page link. ADHD capture and completion were tested in a schema copy; the other examples need testing in your workspace.

ADHD Life OS

In my duplicated ADHD Life OS, find Master Tasks & Projects. Inspect its properties. Create a task called “Finish the presentation” with Due Date tomorrow (confirm the date and my timezone), Energy Level “Low Energy”, Dopamine Tag “Quick Win”, Estimated Minutes 15, Category “Work” and Status “Not Started”. Return the created record link and read its values back.

Second Brain & 2027 Life OS

In my duplicated Second Brain & 2027 Life OS, inspect Master Tasks & Projects Database. Create Task Name “Review my saved research” with Scheduled Date tomorrow (confirm the date and timezone), Priority “P2 Medium”, Energy Required “Quick Win” and Status “To Do”. Leave Parent Project unset unless I identify an existing project. Return the record link and verify its fields.

E-Commerce & Shop Management OS

In my duplicated E-Commerce & Shop Management OS, inspect Macro Operations & Task Matrix. Create Task Description “Review stock before the next campaign” with Due Date tomorrow (confirm the date and timezone), Category “Inventory Audit”, Urgency Level “P2-Operational” and Execution State “Backlog”. Do not change stock or orders. Return the record link and verify its fields.

The Monetized Creator OS

In my duplicated Monetized Creator OS, inspect Master Content & Repurposing Matrix. Create Content Asset / Hook “Three lessons from my latest launch” with Platform [“Newsletter”] and Production Stage “Ideation”. Leave Publish Date and Rel: Promoted Offer unset until I choose them. Return the record link and verify its fields. Do not publish or send anything.

Real Estate Agent & Transaction OS

In my duplicated Real Estate Agent & Transaction OS, inspect DB_RE_CLIENT_CRM. Create a fictional test lead with Client Name “DEMO — Alex Morgan”, Client Role “Buyer”, Pipeline Status “Inbound Lead”, Preferred Contact Method “Email”, Urgency Timeframe “1–3 Months”, Next Follow-Up Date tomorrow (confirm the date and timezone) and Sample checked. Do not contact anyone. Return the record link and verify its fields.

If something doesn’t work.

The assistant can’t find my page.
Confirm the connected account, workspace and page access. Open the copy in Notion with that account. Supply its direct page link and review authorization.
It can read, but can’t write.
Check whether a write action is actually offered. Some experiences expose only search and reading. Use native Notion entry until a supported action is available.
A value or relation was rejected.
Fetch the database schema again. Use the exact option name. Read the target project or SKU before linking it. Do not guess relation IDs or set formula values.
A view looks empty.
Check the record’s date and status, the view filter and your timezone. Confirm the view points to your copied source. Do not rebuild the database to fix a filter.
Charts are unavailable.
Use the corresponding Records tab. Chart and AI availability can depend on your Notion plan.

Still stuck? See support options. Do not send passwords, tokens or private client records.