Product guide.

How the product works

OutcomeCraft turns customer-owned knowledge and recent X conversations into reviewable original posts and replies.

The application is multi-tenant: each organization has isolated users, connected accounts, knowledge, editorial profiles, content and usage records. A user can belong to a team and an organization can connect more than one X account.

↑ On this page

Invitation and first login

An owner invites each person and assigns an initial role.

1. Open the one-time invitation link from your email.
2. Choose Continue with Google and use the exact invited email. This is the recommended path and takes you directly to the workspace after Google consent.
3. If you cannot use Google, expand Use email and password instead, enter your name and create a unique password of at least 12 characters.
4. Open Security, verify your email when applicable, enable an authenticator app and save the recovery codes in your password manager.
5. Review active sessions and remove test or unknown devices.

No invitation yet

Google sign-in never creates an uninvited account. Join the public waitlist; Tecnicora reviews each request and sends invitations gradually. A waitlist request does not create a workspace or guarantee access.

Roles

Role	What it can do
Viewer	Read content, connections, knowledge, publishing and usage information.
Editor	Manage editorial profiles, examples, calibration, knowledge inclusion and content workflows.
Owner	Manage teammates, roles, provider connections, publishing controls and organization settings.

↑ On this page

Portal navigation

Each screen represents one part of the operating workflow.

Overview

Readiness summary and shortcuts.

Editorial Studio

Strategy, voice, examples, calibration and version history.

Usage

Model-token and X API consumption attributed to your organization.

Connections

Authorize independent X accounts and Notion workspaces.

AI Connectors

Connect and revoke Claude or ChatGPT onboarding access.

Knowledge

Synchronize and select customer-owned sources.

Publishing

Review the automatic schedule and pause publishing.

Team

Invite, activate and assign roles.

Security

MFA, verification and active sessions.

Use the language selector in the navigation to save English or Spanish (Mexico) as your personal interface preference.

↑ On this page

Connect Claude: step by step

Use your Claude account to prepare approved onboarding material without granting OutcomeCraft access to all of your sources.

Claude Pro, Max or Free

1. Open Claude on the web, desktop app or mobile app.
2. Go to Customize → Connectors.
3. Select +, then Add custom connector.
4. Name it OutcomeCraft and paste the connector address above.
5. Leave OAuth Client ID and OAuth Client Secret empty. OutcomeCraft supports automatic client registration.
6. Select Add, then Connect. Claude opens OutcomeCraft in your browser.
7. Sign in to OutcomeCraft, choose the correct workspace, review the permissions and select Approve connection.

Claude Team or Enterprise

1. An organization Owner or Primary Owner first opens Organization settings → Connectors.
2. Select Add → Custom → Web, enter OutcomeCraft and paste the connector address. Leave the optional OAuth credentials empty.
3. After the owner adds it, each member opens Customize → Connectors, finds OutcomeCraft and selects Connect.
4. Each member signs in to OutcomeCraft and approves access for their own account and workspace.

Enable it in a conversation

1. Start a new Claude conversation.
2. Select the + button beside the message box, then Connectors.
3. Turn on OutcomeCraft for that conversation.
4. Send: Use OutcomeCraft to show my editorial onboarding status. Do not write anything yet.
5. If Claude returns your workspace status, the connection works.

Configure your editorial playbook

Then send: Help me configure my OutcomeCraft editorial playbook. Interview me first. Use information from this conversation and sources I explicitly choose. Before every write, show the exact proposed profile, example or knowledge capsule and ask for my approval.

Claude can help prepare a profile draft, writing examples and approved knowledge capsules. Return to Editorial Studio to review and activate a profile; connector writes do not activate it.

Permissions and revocation

editorial:read reads onboarding status and relevant editorial configuration. editorial:write creates additive drafts, examples and capsules after approval. The connector cannot publish to X, activate a profile, read provider credentials, administer users or delete data.

Disconnect it either in Claude → Customize → Connectors or in OutcomeCraft → AI Connectors. OutcomeCraft access tokens expire after 12 hours and can be revoked earlier.

If it does not connect

Symptom	Check
Claude does not show Add custom connector	Confirm you are in Customize → Connectors. On Team/Enterprise, ask an organization Owner to add it first.
Claude asks for OAuth credentials	They are optional; leave both fields empty.
OutcomeCraft says you are not invited	Use the exact email invited to the workspace or ask its Owner for an invitation.
Connector exists but Claude does not use it	Enable OutcomeCraft for the current conversation through + → Connectors.
Authorization expired	Select Connect again and repeat OutcomeCraft approval.

Claude's interface can change. See Anthropic's official remote MCP connector guide.

↑ On this page

Connect X and Notion

Provider authorization is stored per organization and per installation.

Connect an X account

1. Open Connections and choose Add X account.
2. Sign in to the intended X identity and review the requested permissions.
3. Return to the portal and confirm the username shown.
4. Repeat for additional accounts. Each authorization remains independent.
5. Select exactly one default publishing account before enabling any publishing workflow.

Connect a Notion workspace

1. Choose Add Notion workspace.
2. Select only the workspace and pages appropriate for this organization.
3. Complete authorization, then open Knowledge and synchronize.

↑ On this page

Manage knowledge

Knowledge gives the writer grounded context; it does not override editorial or security rules.

1. Synchronize the connected Notion workspace.
2. Review every discovered source title and URL.
3. Include only material that is relevant and approved for editorial use.
4. Exclude confidential, customer-specific or unrelated material.
5. Synchronize again after material changes in Notion.

Good sources

• Positioning and product strategy.
• Approved content pillars and frameworks.
• Public website and published articles.
• Customer-agnostic operating principles.
• Approved writing examples.

Do not include

• Passwords, API keys or connection strings.
• Private customer names, commercial terms or incident details.
• Unapproved drafts presented as facts.
• Material owned by another tenant.

↑ On this page

Teach strategy, tone and voice

The system uses a structured editorial profile and evidence—not a separately trained model.

1. In Editorial Studio, create a draft profile.
2. Define positioning, audience and the business goal of the account.
3. Add voice traits, content pillars, formats and objectives.
4. Write positive guidance and explicit patterns to avoid.
5. Record prohibited topics, confidentiality boundaries and any additional editorial note.
6. Add several real examples that sound right and several that do not.
7. Generate six calibration posts and mark each on-brand, reject or rewrite with a reason.
8. Activate the profile only when the examples consistently reflect the intended voice.

Profiles are versioned. You can review history and activate a prior version without losing the audit trail.

↑ On this page

Daily content workflow

Treat the recommendation as an editorial decision, not an unattended model output.

1. The scheduled refresh reads recent posts from the configured watchlist and account history.
2. The writer uses the active profile, approved examples and included knowledge to create distinct candidates and contextual replies.
3. An independent critique scores quality and rejects candidates that fail the thresholds.
4. Open the daily workspace and read the selected post, rationale, source context and suggested replies.
5. Check factual grounding, tone, repetition, length and whether the post adds a distinct point of view.
6. Edit if necessary, then copy the final text or approve the configured publishing path.

Final review checklist

• Complete thought and natural language
• No confidential or invented claim
• No unnecessary “AI” opening or generic slogan
• Aligned with an active pillar and objective
• Within the configured character limit
• Not substantially similar to recent owned posts

↑ On this page

Publishing and safety

Original daily posts and replies have separate controls.

The portal shows whether automatic daily publishing is enabled or paused and the organization schedule. The portal can always pause an existing schedule; enabling production automation is an explicit administrative decision.

1. Confirm the correct default X account.
2. Review multiple days of generated content manually.
3. Confirm the schedule and timezone.
4. Validate that X authorization has the required write permission.
5. Approve automatic original-post publishing only after acceptance testing.

Status meanings

Not attempted

No publishing request has run for that recommendation.

Published

X accepted the post and returned its identifier.

Error

The attempt failed; inspect the safe error, authorization and account selection before retrying.

↑ On this page

Usage and cost

Usage records support customer estimates, internal controls and billing.

Model usage records calls and provider-reported input, cached input, reasoning, output and total tokens by model. X usage records tenant-attributed operations and applies the unit price stored with each event.

Use the month selector to review model totals, X estimates and daily breakdowns. Figures are auditable estimates; provider invoices remain the final external source of truth.

Estimate before scaling

1. Run a small representative test period.
2. Measure average model tokens and X operations per daily refresh.
3. Multiply by planned accounts, refresh frequency and days per month.
4. Add a safety margin for retries, calibration and editorial experiments.
5. Re-estimate after changing watchlist size, knowledge volume, models or publishing frequency.

↑ On this page

Team and security operations

Access should follow least privilege and remain easy to revoke.

• Invite people individually; never share one administrator login.
• Assign Viewer, Editor or Owner according to actual responsibility.
• Keep at least one active owner and remove temporary test members.
• Require verified email and MFA for owners and editors.
• Review active sessions regularly and revoke unfamiliar devices.
• Use recovery codes once, then regenerate or reconfigure MFA if they are exposed.
• Disconnect provider accounts that are no longer used.

Credentials belong in a password manager and runtime secret vault. Never paste them into posts, editorial examples, Notion pages, Slack, source code or support screenshots.

↑ On this page

Troubleshooting

Start with the visible status and avoid reconnecting or rotating everything at once.

Problem	What to check
Cannot sign in	Correct tenant URL, verified email, password, invitation status and MFA clock/code.
X connection fails	OAuth callback URL, client credentials, app permissions and the X account used during consent.
Notion pages are missing	Workspace authorization, page sharing with the integration, then run synchronization again.
Writing sounds generic	Active profile, concrete positive/negative examples, calibration reasons and included knowledge.
No daily recommendation	Scheduler health, tenant timezone, watchlist sources, provider credentials and generation quality decision.
Publishing error	Default account, Read and Write authorization, token freshness, post length and duplicate recovery.
Unexpected usage	Daily breakdown, model, number of refreshes, X operation type and recent configuration changes.

When requesting support, send the organization name, approximate time, screen/status, and safe error text. Never send passwords, tokens, secrets or complete database URLs.

↑ On this page

Waitlist and access

Requesting access and receiving an invitation are separate steps.

1. Open Join the waitlist from the login page.
2. Review the privacy notice, provide minimal qualification information and consent to contact.
3. Submission does not create an account. Tecnicora reviews the request.
4. If accepted, open the one-time invitation and continue with the exact invited Google account or use the password fallback.

Repeated submissions do not improve priority and remain one lifecycle record. Contact support to withdraw or exercise privacy rights.

↑ On this page

Knowledge onboarding options

Choose the smallest access path that produces useful, approved context.

Manual

Type strategy, boundaries and examples directly in Editorial Studio.

Notion

Authorize, synchronize selected pages, then include or exclude each source.

AI connector

Use Claude or ChatGPT to synthesize sources you choose, then send approved summaries as capsules.

A capsule stores approved text, provenance and an optional source reference. It does not create a live connection to Drive, Notion or another source. Never place secrets or customer-confidential material in a capsule.

↑ On this page

Billing, data lifecycle and support

Know what is measurable in the portal and what requires a verified request.

Usage values support forecasting; the written offer/order form defines chargeable prices. Revoke sessions, members, X/Notion and AI connectors from their portal screens. For full export, correction, restriction, organization deletion, privacy/ARCO requests or billing questions, follow Support, billing and data lifecycle.

↑ On this page

Administrator launch checklist

Complete these controls before onboarding a production customer.

• Custom domain and TLS configured
• Production email delivery tested
• Google and X callback URLs updated
• App-scoped deployment credentials stored safely
• Database backups and rotation procedure verified
• Owner account verified with MFA
• Tenant isolation acceptance tests passed
• Two X accounts tested independently
• Knowledge inclusion reviewed
• Editorial calibration accepted
• Usage metering reviewed against provider records
• Automatic publishing remains paused until written approval

↑ On this page