Web SaaS / Hosted Service

What the agent can help run

• define the customer problem and product boundary
• choose adopt/customise/compose/build
• onboard and serve customer accounts
• operate billing, support, analytics and reliability appropriate to the product

Capabilities

• Product capability — The customer-facing function users pay for.
• Customer / tenancy model — Represent customers, accounts or organisations appropriately.
• Commercial rights and branding — Confirm hosted-service, resale, attribution and trademark constraints before launch.
• Customer-facing domains (optional) — Support the domain model the product actually needs.
• Billing / subscriptions (optional) — Introduce billing only when the product needs paid plans.
• Operations — Monitor, support and measure the service.
• Customer research (optional) — Collect structured feedback to guide what the product should become.

Candidate ways to satisfy them

Candidates are options, not an installation list. One application may cover several capabilities; existing software or a smaller agent-built implementation can be the better answer.

• Baserow — https://github.com/baserow/baserow: Customisable open-core foundation; verify edition and hosted-service terms.
• Umami — https://github.com/umami-software/umami: Owned product analytics option.
• Chatwoot — https://github.com/chatwoot/chatwoot: Customer-support capability where multi-channel support is warranted.
• Formbricks — https://github.com/formbricks/formbricks: Structured feedback/survey option; upstream does not permit white-label resale, so do not present it as the product's own brand.
• Existing product or workspace application: Adopt what already exists if it satisfies the outcome and rights are clear.
• Smaller product built by the workspace agent: Often preferable when the product is smaller than a general platform and can be implemented directly.