I am a solo developer and building the same business shell around each product: authentication, billing, another dashboard, and another acquisition channel is not only a hard part, but it's not beneficial for end-users. Nowadays, users want to have everything in one tool, in one chat specifically. Maybe they allow few more, but definitely not 10.

I built intentic to try a different model. Independent services keep their own back ends, but users access them from one chat workspace with one credit balance. I believe shared execution, UI, and billing layer for independently operated services is the future.

A service publishes a manifest, API description, UI extension in its GitHub repository. The platform discovers the integration, validates the declared endpoints and permissions, and sends it through a security review. After approval, the service can appear inside the workspace as an interactive extension and as an action the agent can invoke.

The following pieces are working today: - GitHub discovery and manifest parsing - Extensions - API invocation and authentication - Credit metering - Provider accounting or payouts - Security review

Entire thing is open-source: https://github.com/intentic/intentic

I am looking for approximately ten independent service builders to test this over the next two or three months. Existing products are welcome. The service should remain independently owned and operated.

The best initial candidates are narrow services that complete a job rather than merely generate more text. For example: - Find cheapest, best buy offer of a given product or category of products - Find the best person to help with something (e2e contact and schedule negotiation) - talent acquisition - Run VISA process - Find a way to get a meeting with high-profile people - Marketing & Sales supporting tools - Specialized Research - SEO tools - DevOps and infrastructure tools - Finance (invoicing tools, expense & cash flow monitoring tools) - Or anything else that would do better as a part of unified chat workspace, instead of separate dashboard

The question I am most interested in: What (except from large existing audience) would convince you to connect your existing product?

Builders discussion: https://discord.gg/3veuzYp32T