Summary
Allow Thinkwise customers to share AI-enrichments they've created in their own Software Factory to a central, curated repository managed by Thinkwise — so that the entire customer community can discover, import, and benefit from enrichments written by others.
The Problem Today
Each Thinkwise development-team develops AI-enrichments independently in their own Software Factory. There is no mechanism to share these enrichments with the broader Thinkwise community, which means:
- Customers reinvent the wheel building similar or identical enrichments.
- Valuable knowledge and innovation stays locked inside individual tenants.
- Smaller teams with fewer resources benefit less from AI capabilities compared to larger customers who invest more in development.
The Proposed Solution
Introduce a Shared AI-Enrichment Hub within the Software Factory, with the following flow:
- Create locally — A customer builds an AI-enrichment in their own Software Factory as they do today.
- Opt-in to share — The customer can choose to submit their enrichment to Thinkwise for inclusion in the central repository.
- Review & curate — Thinkwise reviews the submission for quality, safety, and relevance before publishing it.
- Distribute — Approved enrichments become available to all Thinkwise customers, who can browse, preview, and import them into their own Software Factory with one click.
Benefits
For customers sharing their enrichments:
- Recognition within the community as a contributor.
- Potential for Thinkwise to provide feedback and quality improvement.
- Contribution to an ecosystem they also benefit from.
For customers consuming enrichments:
- Faster time-to-value — no need to build common enrichments from scratch.
- Access to high-quality, real-world enrichments built by experienced peers.
- Inspiration for building their own enrichments.
For the Thinkwise ecosystem overall:
- Accelerates AI adoption across the entire customer base.
- Builds a vibrant, collaborative community around the platform.
- Thinkwise gains insight into how customers are using AI in practice, informing product direction.
Possible Limitations & Considerations
Governance & quality control Thinkwise would need a review process to ensure submitted enrichments meet quality, security, and privacy standards.
Versioning and maintenance Enrichments may break or become outdated as Thinkwise evolves. A lifecycle policy is needed — who is responsible for maintaining a shared enrichment over time?
Context dependency Many enrichments are highly tailored to a specific domain or data model. Generic enrichments will transfer well; niche ones may be less reusable and cause confusion if imported out of context.
Discoverability As the repository grows, good tagging, categorization, and search functionality become critical. Without them, the repository risks becoming cluttered.
Security & data privacy Customers must be sure that submitting an enrichment doesn't inadvertently expose proprietary data or business logic embedded in the enrichment's prompts or configuration.
Suggested Scope for MVP
- A simple submission flow from the Software Factory to Thinkwise.
- A basic browsable gallery of approved enrichments, filterable by category or use case.
- One-click import into the customer's own Software Factory.
- Clear contributor attribution and a basic rating/feedback mechanism.