Yunusa Abdullahi

When we were starting out we set our prices super low just to get anyone through the door.

It worked for getting initial sign-ups, but it accidentally trapped us with low budget users who demanded endless custom help while we severely undercharged enterprise teams getting massive value. Raising prices on those early adopters months later was an absolute operational nightmare. For founders who had to rework their tiers after launch how did you handle migrating early users to higher plans without destroying trust?

AI agents are getting pretty good at finding information, summarizing documents, and answering questions. But what about letting them change the information itself?

Imagine an AI agent finds outdated onboarding instructions in your company's wiki. Should it be allowed to fix them immediately? Suggest an edit for someone to review? Or simply flag the problem and leave everything to a human?

We've been thinking about this while developing the XWiki MCP Server.

Our approach is to respect existing user permissions and keep write operations disabled by default. Administrators can enable them when needed.

Thanks for following Comcent! We're starting a series of short tutorials, one task each.

The first one is the whole setup: sign up, create your organization, connect the Twilio number you already have, choose who its calls ring, and answer a real call in the browser.